Re: NameAlreadyBoundException when deploying as EAR

2018-01-18 17:12 GMT+01:00 otbutz : > That answers question number 2 but why is the rebind happening at all? > The beans already exist and are registered within the context otherwise the > error wouldn't be thrown. Shouldn't the webappbuilder just pick up the > existing

Re: NameAlreadyBoundException when deploying as EAR

That answers question number 2 but why is the rebind happening at all? The beans already exist and are registered within the context otherwise the error wouldn't be thrown. Shouldn't the webappbuilder just pick up the existing bean and be done with it? I just want to rule out any errors in our

Re: NameAlreadyBoundException when deploying as EAR

well it depends the rebind. Keep in ming this is an internal part so not respecting the rebind API contract is fine *here*. the idea of this code is to merge tomee and tomcat JNDI models to have the lookups unified (EE and servlet integration if you want). Romain Manni-Bucau @rmannibucau

Re: NameAlreadyBoundException when deploying as EAR

Unaltered behaviour. Checked the corresponding source of openejb-core 4.7.4: public void bindGlobals(Map bindings) throws NamingException { Context containerSystemContext = this.containerSystem.getJNDIContext(); for (Map.Entry value : bindings.entrySet())

Re: NameAlreadyBoundException when deploying as EAR

Try adding this to your setenv.sh or changes system.properties accordingly: -Dopenejb.deploymentId.format={appId}/{ejbJarId}/{ejbName} -Dopenejb.wsAddress.format={ejbName} That will make your deployement Id's for EJB's include the app/jar names and won't impact any web service endpoints you may

Re: NameAlreadyBoundException when deploying as EAR

The EJBs lie in their own modules and are only used by the webapps through injection. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Re: NameAlreadyBoundException when deploying as EAR

It can if multiple modules deploy the same EJB Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: NameAlreadyBoundException when deploying as EAR

Are you refering to the openejb.deploymentId.format property? We're currently using the default format. Could this be the root of our problem? -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Re: NameAlreadyBoundException when deploying as EAR

Hi if you customized EJB deploymentId with the corresponding property to not be ambiguous accross ear modules/webapps then it can be a bug fixed on the 7.x we never backported. This part was improved quite a lot on 7.x Romain Manni-Bucau @rmannibucau | Blog