The ArtifactDataImpl is not intended to be used directly, it is just
shared by the two deployment providers. To create a new interface,
there are to things you can do:
1. Create your own DeploymentProvider implementing bundle, or
2. Reuse the existing RepositoryAdmin service, and use the
ArtifactRepository to import your bundle (there is an import method
which will extract the metadata from the bundle).
You could check the webui project for an example of how to use this.
Good luck!
Angelo
On 14 Jul 2009, at 23:20, Toni Menzel wrote:
On Tue, Jul 14, 2009 at 11:13 PM, Filippo
Diotalevi<[email protected]> wrote:
Hi,
I'm trying to write a simple shell interface to ace, to learn how it
works. The idea is to write a few commands to create a new version,
add some bundles, and publish the version.
One thing I noticed is that there is an ArtifactDataImpl constructor
that does not require symbolicName and version, so I just used it
hoping that they were determined examining the jar... but in the
gateway side it does not work: the artifact is retrieved, but a "No
resource processor for artifact..." exception is raised.
On the contrary, if I specify, on the deployment provider side, also
the symbolic name and version of the bundle, it works just fine.
Why is that? Is it some limitation of the specification? (maybe
because the artifact can be something different from a bundle?)
Don't know the exact classes you are speaking of (or at least don't
know better than you) but:
Yes, DeploymentPackage Artifacts can be Bundles or Resources.
Resources can have Resource Processors.
Also, Resources can be anything. Configfiles, Binaries etc.
Just as a short pointer. Don't have looked the the classes you
mentioned closer so far.
--
Filippo Diotalevi
--
Toni Menzel
Independent Software Developer
Professional Profile: http://okidokiteam.com
[email protected]
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
