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

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

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

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())