You can't update on the fly dropping jar in a war (wouldnt mean anything seems app is linked at startup). Not sure what you expect here but maybe have a look to jrebel or fakereplace.
If you want just autodeploy an app (not a part of app) we have it now through deployments config in tomee.xml or openejb.xml but i think thats not what you want at all. Can you explain your need please? It sounds like youll break the memory at a moment doing it this way... Le 18 mai 2013 00:29, "Caroline" <[email protected]> a écrit : > Awesome :) > > I learned the JNDI names are printed when I start my webapp. > > Using your instructions on my sample project, I was able to load in-project > implementations through "java:comp/env/plaininput". > > I can load implementations from an outside jar with > "java:global/Aree/sqlitereadonlyreasoner". > This works when I: > - put a dependency to the jar in my pom.xml; or > - define a VirtuallWebappLoader for /a/folder/*.jar through context.xml; or > - add /a/folder/*.jar to jars.txt > > However, I can't seem to come up with a configuration that allows me to > drop > in *.jar files AFTER deployment and load them through an > InitialContext.lookup(); call. > > > I read > > http://openejb.979440.n4.nabble.com/stand-alone-Application-looks-up-remote-EJB-by-global-jndi-name-td4663033.html > but 1.6.0-SNAPSHOT of May 17 isn't doing it yet for me either. > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/EJBContainer-No-provider-definition-found-tp4663028p4663040.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
