After looking at the pax-runner-hanlder-wrap, it solves the problem more elegantly, I will continue look at this and try to provide a jbi-handler patch next week.
On Jan 4, 2008 5:13 PM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > On Jan 4, 2008 9:48 AM, Jeff Yu <[EMAIL PROTECTED]> wrote: > > > Now, I've only implemented the fileMonitor module, which means only if > you > > copy the JBI artifact to the deploy folder, it would install it > correctly. > > Seems there are still other 2 scenarios left. > > > > I will looking at your patch right now. > > > > > > 1. Install the artifact using Gshell Command. ( I noticed that we have > JBI > > specific command in the jbi module, maybe a jbi:install command can be > > used > > to install a jbi artifact?). > > > > 2. Install the artifact from the OBR. (I am not familiar with this code, > > but > > it seems we can add a deploymentListener invocation, as I register the > > Deployment listeners in the OSGi Container, before calling the > > bundle.install & start method). > > > > Any thoughts ? > > > Another way we may want to use and which seems more OSGi friendly is to > use > a URL handler. > This means registering URLStreamHandlerService service in OSGi which would > handle the "jbi" protocol. > Then, if you run: > osgi install jbi:xxxx > it would call the jbi handler, which would in turn download the file from > xxx and perform any additional processing. > > You can find an example of such a url handler at > > http://scm.ops4j.org/browse/OPS4J/projects/pax/runner/pax-runner-handler-wrap/ > > > > > > > > On Jan 4, 2008 3:46 PM, Jeff Yu (JIRA) <[EMAIL PROTECTED]> wrote: > > > > > > > > [ > > > > > > https://issues.apache.org/activemq/browse/SMX4NMR-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > ] > > > > > > Jeff Yu updated SMX4NMR-1: > > > -------------------------- > > > > > > Attachment: smx-nmr.diff > > > smx-runtime.diff > > > > > > please apply these two patches in the $SMX4.0/runtime/trunk & > > > $SMX4.0/nmr/trunk respectively. > > > > > > As Guillaume's mentioned above: > > > * Define a deploymentListener in the filemonitor module. > > > * Define a JBI artifactDeployment Listener for dealing with JBI > > artifact, > > > to transform it to OSGified bundle automatically. > > > > > > With these two little patch, users can put JBI artifact in the deploy > > > folder directly to install & start it. > > > > > > > JBI 1.0 compatibility layer: Offline tool to transform JBI artifacts > > in > > > OSGi bundles > > > > > > > > > > ------------------------------------------------------------------------------------ > > > > > > > > Key: SMX4NMR-1 > > > > URL: > > https://issues.apache.org/activemq/browse/SMX4NMR-1 > > > > Project: ServiceMix NMR > > > > Issue Type: New Feature > > > > Reporter: Guillaume Nodet > > > > Assignee: Jeff Yu > > > > Attachments: smx-nmr.diff, smx-runtime.diff > > > > > > > > > > > > > > > > > -- > > > This message is automatically generated by JIRA. > > > - > > > You can reply to this email to add a comment to the issue online. > > > > > > > > > > > > -- > > Thanks > > Jeff > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > -- Thanks Jeff
