[
https://issues.apache.org/activemq/browse/SMX4KNL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SMX4KNL-13.
------------------------------------
Assignee: Guillaume Nodet
Resolution: Fixed
Sending
filemonitor/src/main/java/org/apache/servicemix/kernel/filemonitor/FileMonitor.java
Transmitting file data .
Committed revision 630199.
A problem will still occur if the artifact *is* an OSGi bundle but should be
processed by a DeploymentListener.
In such case, it will be deployed at startup time without being processed at
all.
> startup issue in recognizing new files in deploy folder
> -------------------------------------------------------
>
> Key: SMX4KNL-13
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-13
> Project: ServiceMix Kernel
> Issue Type: Bug
> Environment: Linux
> Reporter: Lars Heinemann
> Assignee: Guillaume Nodet
> Fix For: 1.0-m2
>
>
> The situation:
> As base there is a clean smx4 installation with jbi layer installed. I put
> the servicemix-shared-compat installer archive inside the deploy folder.
> Afterwards I start up the smx4.
> I would expect that the shared compat will be recognized by smx and installed
> / started, but it's not listed in osgi list and also not shown in jbi ls.
> When I now copy the same file again to the deploy folder replacing the
> existing file while smx is running, then it will be recognized and correctly
> installed / started.
> I also tried it with servicemix-file and jsr181 to be sure it's not related
> to a single file, but the behaviour is the same.
> see:
> http://www.nabble.com/smx4%3A-startup-issue-in-recognizing-new-files-in-deploy-folder-to14997795s12049.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
