Hi, today I got a strange behaviour when starting up smx4 with a new file in the deploy folder.
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. As this was supported behaviour in smx3 I think this could be a bug. Regards, Lars -- View this message in context: http://www.nabble.com/smx4%3A-startup-issue-in-recognizing-new-files-in-deploy-folder-tp14997795s12049p14997795.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
