guess the easiest way to fix it on your side is to write your own InitialContextFactory just replacing incoming properties by standard properties and use this one in JndiProvider.
Side note: Weblogic shouldn't serialize incoming properties directly since the contract is widely open: Hashtable<?,?>. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-08-04 19:01 GMT+02:00 snrmwg <[email protected]>: > Hello, > > I need an external bean in my test case and I did it like this: > > > > But 'myService' does not get injected. > > When I debug into the openejb code I can detect the following error in > NameNode.resolve(ParsedName name): > > > > The lookup goes to a Weblogic 12c server. And the InitialContext has props > of type SuperProperties. I think the Weblogic doesn't know of the class > from > openejb. When I tweak the object while debugging to a plain Properties > instance everything is fine. > > The InitialContext get's constructed in Assember.createExternalContext(). > > But I can't see a chance to override the creation. I would like to init the > InitialContext with plain java.util.Properties. > > Is there a way to do it or how could we enhance openejb to achieve it? > > > Thanks a lot in advance for your help. > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Getting-UnmarshalException-when-using-jndi-ext-because-of-SuperProperties-tp4675705.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
