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.
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 ? 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
