Hi Farrukh,
one thing I noticed is that you shall be using 2.2.4-1 as 2.2.4 had an
unfortunate customization file issue on some platforms. What you
describe however is not a known issue, so if the 2.2.4-1 replacement
doesn't help, please file an issue with reproduction steps and I'll look
into it,
MartiNG
On 09/07/2011 09:41 PM, Farrukh Najmi wrote:
>
> I have narrowed it down to something peculiar issue when using
> jaxb-impl version *2.2.4.*
>
> The client or the server fails with the same exception trace if its
> provided jar is version 2.2.4 (2.2.1 - 2.2.3) all work.
>
> * The client fails if its dependency include jaxb-impl 2.2.4 when
> run in NetBeans Debug action via netbeans maven plugin.
> * The server fails if deployed in GF 3.1.1 which uses jaxb-impl
> 2.2.4 in its jaxb-osgi.jar
> * The client works if its dependency include jaxb-impl 2.2.3 when
> run in NetBeans Debug action via netbeans maven plugin.
> * The server works if deployed in GF 3.1 which uses jaxb-impl
> 2.2.3 in its jaxb-osgi.jar
>
> Thus why I think jaxb-impl 2.2.4.
>
> The JDK 6 vs. 7 and jaxb-api version does not sem to make a difference
> (tested with jax-api 2.2.1 - 2.2.4). And I am no longer bundling the
> jaxb-api/impl jars and specifying <scope>provided</scope> in pom.xml
> for those dependencies.
>
> Hopefully the data I am providing is adequate. Any one have any
> workaround suggestions?
> Can any one from dev team tell me if this is a known issue or whether
> I should file a new one?
>
> Thanks.
>
> On 09/07/2011 01:22 PM, Farrukh Najmi wrote:
>>
>> I am moving this issue to jaxb list after establishing that I can
>> duplicate the issue in my Swing Client running within NetBeans
>> debugger and outside GF.
>>
>> * jaxb-api/impl version 2.2.1, on GF 3.1 and JDK6:
>> works on both server deployed in GF and Swing Client (started
>> in NetBeans)
>>
>> * jaxb-api/impl version *2.2.4*, on GF 3.1 and JDK6:
>> Server deployed in GF 3.1 worked fine but Swing Client (started
>> in NetBeans) shows the same error trace.
>>
>> * jaxb-api/impl version 2.2.4, on GF 3.1 and *JDK7*:
>> Server deployed in GF 3.1 worked fine but Swing Client (started
>> in NetBeans) shows the same error trace.
>>
>> So same client error happens when NetBeans starts server and client
>> using JDK 6 or 7.
>>
>> Any suggestions of what I should try next?
>>
>> On 09/06/2011 02:27 PM, Farrukh Najmi wrote:
>>>
>>> Hi Guys,
>>>
>>> I am forwarding this message from Glassfish forum here as it touches
>>> on JAXB. Thanks for any tips you can share.
>>>
>>> -------- Original Message --------
>>> Subject: NullPointerException
>>> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.checkOverrideProperties(ClassBeanInfoImpl.java:205)
>>>
>>> Date: Tue, 06 Sep 2011 13:59:50 -0400
>>> From: Farrukh Najmi <farrukh_at_wellfleetsoftware.com>
>>> To: users_at_glassfish.java.net
>>>
>>>
>>>
>>>
>>> While migrating my webapp from Glassfish 3.1 to Glassfish 3.1.1 I am
>>> running into NPE shown in stack trace below:
>>>
>>> Caused by: java.lang.NullPointerException
>>> at
>>> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.checkOverrideProperties(ClassBeanInfoImpl.java:205)
>>> at
>>> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.<init>(ClassBeanInfoImpl.java:186)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getOrCreate(JAXBContextImpl.java:509)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getOrCreate(JAXBContextImpl.java:528)
>>> at
>>> com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.<init>(ArrayElementProperty.java:112)
>>> at
>>> com.sun.xml.bind.v2.runtime.property.ArrayElementNodeProperty.<init>(ArrayElementNodeProperty.java:62)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>>> at
>>> java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>>> at
>>> com.sun.xml.bind.v2.runtime.property.PropertyFactory.create(PropertyFactory.java:128)
>>> at
>>> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.<init>(ClassBeanInfoImpl.java:181)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getOrCreate(JAXBContextImpl.java:509)
>>> at
>>> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.<init>(ClassBeanInfoImpl.java:168)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getOrCreate(JAXBContextImpl.java:509)
>>> at
>>> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.<init>(ClassBeanInfoImpl.java:168)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getOrCreate(JAXBContextImpl.java:509)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:326)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:141)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl$JAXBContextBuilder.build(JAXBContextImpl.java:1157)
>>> at
>>> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:145)
>>> at
>>> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:236)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:187)
>>> at javax.xml.bind.ContextFinder.find(ContextFinder.java:333)
>>> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:446)
>>> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:409)
>>>
>>> Searching suggests
>>> <http://fusesource.com/forums/thread.jspa?threadID=3010> that it has
>>> something to do with version collision in JAXB jars bundled by
>>> Glassfisg 3.1.1 and those in in my war file's WEB-INF/lib directory.
>>>
>>> My war currently uses the following versioned jars as dependencies
>>> bundled within my webapp's WEB-INF/lib directory and my Glassfish
>>> 3.1.1 runs under JDK 6.
>>>
>>> javax.xml.bind:jaxb-api:jar:2.2.1:compile
>>> com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile
>>>
>>> Can any one tell me what is causing this problem and what do I need
>>> to do to fix this problem?
>>>
>>
>
> --
> Regards,
> Farrukh Najmi
>
> Web: http://www.wellfleetsoftware.com
>
--
Martin Grebac, GlassFish/Metro/JAXWS/JAXB/Tooling at Oracle
http://blogs.oracle.com/mgrebac
ICQ: 93478885