Yes, the second option is better IMO. Anyway, thanks for the feedback and sorry for the delay.
Jean-Louis 2011/5/18 Roy van Rijn <roy.van.r...@gmail.com> > Sorry, I can't do that.. But after some searching we've found the problem. > > One way to get rid of the NPE is to call the following code: > //This is needed to avoid deep NPE in OpenEJB: > PortAddressRegistry portAddressRegistry = > SystemInstance.get().getComponent(PortAddressRegistry.class); > if (portAddressRegistry == null) { > portAddressRegistry = new PortAddressRegistryImpl(); > SystemInstance.get().setComponent(PortAddressRegistry.class, > portAddressRegistry); > } > > Another (better approach) is to set this parameter: > properties.setProperty("openejb.embedded.remotable", "true") > > Obviously I still think there should be some fix. Getting such a deep > meaningless NPE is always wrong :-) Maybe add the code above at that > point? Or add a meaningful check if that property is set? > > Roy > > On Wed, May 18, 2011 at 2:52 PM, Jean-Louis MONTEIRO <jeano...@gmail.com> > wrote: > > Hi, > > > > Is it possible to get your example? > > It would be easier to reproduce the problem and fix it if possible. > > > > Jean-Louis > > > > -- > > View this message in context: > http://openejb.979440.n4.nabble.com/NPE-when-calling-webservice-tp3527162p3532559.html > > Sent from the OpenEJB User mailing list archive at Nabble.com. > > >