[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[virgo-dev] Building a custom artifact deployer
- From: Peter Gardfjäll <peter.gardfjell@xxxxxxxxx>
- Date: Fri, 9 Jul 2010 16:21:32 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=f6uoSl+P4Kwl3HfsIWao2Ogd3PrNSJRaxgpWCfLin656NiSp7A7A+gM2cgWzcG7Abm S69GzssvaDbRouhuCkpRPOJYS7FqqXYfEcP3mgGKfLNyJGxB6XOMMZT9ZTqizadJSY5G QEfjOt+VYpLUH6TUITYgWzkufk1kNGuGT8Klw=
as far as I can tell part of writing a custom artifact deployer for
Virgo is to register an InstallArtifactTreeFactory in the OSGi service
I assume that all such factories get picked up by the Virgo runtime.
Am I right so far...?
If that is indeed the correct approach, one apparent problem that
strikes me is that the ArtifactStorage interface, which is a parameter
of the InstallArtifactTreeFactory.constructInstallArtifactTree method,
is internal to the org.eclipse.virgo.kernel.deployer bundle (that is,
its package is not exported).
This makes it impossible for me to write a bundle with a custom tree factory.
Maybe some restructuring is required to simplify the development of
What are your thoughts?
best regards, Peter