I don't think so. At least not for the moment.
My idea was to just convert the SA to a bundle and have the jbi deployer
bundle extract the SUs in a private dir inside the ${servicemix.home}/data/
folder, then give the path to the SUs to the JBI components. This will stay
as close as possible to the JBI spec without the need to repackage the SA.
As the SUs won't be deployed as bundles, there's no need to add the manifest
entries.
On Dec 7, 2007 11:01 AM, Jeff Yu <[EMAIL PROTECTED]> wrote:
> Sorry for the delay... am just back to this jira.
>
> For the SAs jar conversion I have a question is that do we need to
> repackage
> the SUs in the SA, say add the Bundle-SymbolicName & Bundle-Version for
> each
> SU in SA??
>
> Thanks
> Jeff
>
> On Dec 1, 2007 12:25 PM, Jeff Yu <[EMAIL PROTECTED]> wrote:
>
> > * I am actually testing it on the linux system(ubuntu), it works fine..
> > not sure what error did you get in the mac? is it always showing that
> "Bad
> > Usage.."?
> > * OK, I am working on adding these two..
> > * Yeah, your suggest sounds great to me, I also like to use the 1st
> > solution, simply rename it to the " convert.jar".
> >
> >
> >
> > On Dec 1, 2007 4:43 AM, Guillaume Nodet (JIRA) <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > [
> https://issues.apache.org/activemq/browse/SM-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40766
> > > ]
> > >
> > > Guillaume Nodet commented on SM-1090:
> > > -------------------------------------
> > >
> > > Good work !
> > > Still, I have a few problems with the patch:
> > > * i can't launch the shell script on mac (haven't looked why yet)
> > > does it work on other unix systems ? If you don't have any
> > > available, i can handle that
> > > * the tool only handles components so far, we need to also handle SLs
> > > and SAs by extracting
> > > the informations from the jbi descriptor if available or from the
> > > manifest if not
> > > * the shell scripts includes the version number which is a really bad
> > > idea, as it would require manual editing
> > > before releasing. There are two solutions to that: just rename
> the
> > > jar "convert.jar" or use the the maven
> > > resource filtering to put the version number at build time (i'd
> > > rather use the first one).
> > >
> > > > JBI 1.0 compatibility layer: Offline tool to transform JBI artifacts
> > > in OSGi bundles
> > > >
> > >
> ------------------------------------------------------------------------------------
> > >
> > > >
> > > > Key: SM-1090
> > > > URL:
> https://issues.apache.org/activemq/browse/SM-1090
> > > > Project: ServiceMix
> > > > Issue Type: New Feature
> > > > Reporter: Guillaume Nodet
> > > > Assignee: Jeff Yu
> > > > Fix For: 4.0
> > > >
> > > > Attachments: SM-1090.patch
> > > >
> > > >
> > >
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > You can reply to this email to add a comment to the issue online.
> > >
> > >
> >
> >
> > --
> > Thanks
> > Jeff
>
>
>
>
> --
> Thanks
> Jeff
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
