Re: [Dev] reverting jaxb version in carbon back to 2.1.7
Hi, On Tue, Aug 28, 2012 at 11:33 AM, Sagara Gunathunga wrote: > > I don't think shipping Greg with jaxb version 2.1.7 is a acceptable > solution we need to ship compatible set of libs for whole platform > otherwise this make lot of unwanted issues when installing various > features. What I think is porting ndatasource in to jaxb version > (2.2.5 2.2.6) is the only solution here. > > We have to understand the actual problem here, there is no such thing as porting the ndatasource implementation to a new version. There is nothing to port, it uses standard annotations and libs, and those hasn't changed. It is a class loading issue we are having with the version upgrade, where some classes, in the ndatasources error case, "JAXBContext", happens to be that it's implementation is loaded from the JDK and it's API interface is loaded from the OSGi bundle, so results in a classes not similar and a "instance of" expressions fails in the JAXB code, which is the actual error you get from ndatasources. So it is not only an issue for ndatasources, but a generic error you will get in any place you use JAXB. So the bottom line is, we have to find the actual root cause for these class loading issues and fix those, then we should be able to just upgrade it to the latest version and go from there. Cheers, Anjana. > Thanks ! > > > > > Thanks, > > - Chethiya > > > > On Thu, Aug 23, 2012 at 3:13 PM, Pradeep Fernando > wrote: > >> > >> Hi chethiya, > >> > >> can you test this modification with a hosted JAXRS and JAXWS web-app > >> > >> ---PRadeep > > > > > > > > > > -- > > Chethiya Abeysinghe > > Software Engineer; WSO2, Inc.; http://wso2.com/ > > email: cheth...@wso2.com phone: +94 777444891 > > blog: chethiya3000.blogspot.com > > > > > > > > ___ > > Dev mailing list > > Dev@wso2.org > > http://wso2.org/cgi-bin/mailman/listinfo/dev > > > > > > -- > Sagara Gunathunga > > Technical Lead; WSO2, Inc.; http://wso2.com > V.P Apache Web Services ; http://ws.apache.org/ > Blog ; http://ssagara.blogspot.com > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Anjana Fernando* Associate Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] reverting jaxb version in carbon back to 2.1.7
Hi Sagara,
As explained several times, unlike a few samples, it is not straightforward
to migrate an entire implementation of JAX-WS services written for Axis2
(with all the nitty-gritty details that we had to put in place to get it to
work etc, into CXF in a couple of weeks. We will migrate but that will take
time, and we need a solution that is not so complicated to resolve this
immediately. If we have to use two versions of JAX-WS in two products,
tough luck. But, the same would also apply to anybody who wrote serious
JAX-WS services on AS with this new release.
Thanks,
Senaka.
On Tue, Aug 28, 2012 at 7:47 AM, Sagara Gunathunga wrote:
> On Tue, Aug 28, 2012 at 12:02 PM, Senaka Fernando wrote:
> > Hi Sagara,
> >
> > That's exactly the point here. With the current version of JAXB, Axis2
> > JAX-WS is not working and due to that UDDI is totally busted in G-Reg.
> If we
> > are to use single version of a dependency across the platform, we have to
> > test and ensure that all products are working fine before attempting a
> major
> > upgrade or situations like this become unavoidable.
>
> Unfortunately this was not our call CXF need latest JAXB versions to
> run. Since we have integrated CXF into our platform as the
> JAX-WS/JAX-RS runtime we don't have many options here.
>
> BTW are we still need to run Axis2 JAX-WS within our products ? I
> think we need to migrate them to run with CXF.
>
> Thanks !
>
> >
> > Thanks,
> > Senaka.
> >
> >
> > On Tue, Aug 28, 2012 at 7:03 AM, Sagara Gunathunga
> wrote:
> >>
> >> On Tue, Aug 28, 2012 at 10:22 AM, Chethiya Abeysinghe <
> cheth...@wso2.com>
> >> wrote:
> >> > Hi all,
> >> >
> >> > We have tried replacing jaxb_2.1.7.wso2v1.jar in Aug-22 AS build.
> >> > jaxrs_basic sample has failed with following message in the server.
> >> >
> >> > [2012-08-27 10:18:52,302] WARN
> >> > {org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor} - No message
> >> > body
> >> > writer has been found for response class Customer.
> >> >
> >> > And following message on client
> >> >
> >> > [INFO]
> >> > [INFO] >>> exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic >>>
> >> > [INFO]
> >> > [INFO] <<< exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic <<<
> >> > [INFO]
> >> > [INFO] --- exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic ---
> >> > Sent HTTP GET request to query customer info
> >> > [WARNING]
> >> > java.lang.reflect.InvocationTargetException
> >> > 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 org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> >> > at java.lang.Thread.run(Thread.java:680)
> >> > Caused by: java.io.IOException: Server returned HTTP response code:
> 500
> >> > for
> >> > URL:
> >> >
> >> >
> http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
> >> > at
> >> >
> >> >
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
> >> > at java.net.URL.openStream(URL.java:1010)
> >> > at demo.jaxrs.client.Client.main(Client.java:51)
> >> > ... 6 more
> >> > [INFO]
> >> >
>
> >> > [INFO] BUILD FAILURE
> >> > [INFO]
> >> >
>
> >> > [INFO] Total time: 5.900s
> >> > [INFO] Finished at: Mon Aug 27 10:18:52 IST 2012
> >> > [INFO] Final Memory: 6M/528M
> >> > [INFO]
> >> >
>
> >> > [ERROR] Failed to execute goal
> >> > org.codehaus.mojo:exec-maven-plugin:1.2.1:java (default) on project
> >> > jaxrs_basic: An exception occured while executing the Java class.
> null:
> >> > InvocationTargetException: Server returned HTTP response code: 500 for
> >> > URL:
> >> >
> >> >
> http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
> >> > -> [Help 1]
> >> > [ERROR]
> >> > [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> >> > -e
> >> > switch.
> >> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >> > [ERROR]
> >> > [ERROR] For more information about the errors and possible solutions,
> >> > please
> >> > read the following articles:
> >> > [ERROR] [Help 1]
> >> >
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >> >
> >> > Anjana and I tried to overcome this by creating a jaxb orbit using
> >> > version
> >> > 2.1.0 (which is the version used in jdk). That's also produced a
> similar
> >> > result.
> >> >
> >> > At the moment we don't have a clue about what's going on here. If you
> >> > have
> >> > an idea please let us know.
> >> >
> >> >
> >> > Anyway reverting the
Re: [Dev] reverting jaxb version in carbon back to 2.1.7
On Tue, Aug 28, 2012 at 12:02 PM, Senaka Fernando wrote:
> Hi Sagara,
>
> That's exactly the point here. With the current version of JAXB, Axis2
> JAX-WS is not working and due to that UDDI is totally busted in G-Reg. If we
> are to use single version of a dependency across the platform, we have to
> test and ensure that all products are working fine before attempting a major
> upgrade or situations like this become unavoidable.
Unfortunately this was not our call CXF need latest JAXB versions to
run. Since we have integrated CXF into our platform as the
JAX-WS/JAX-RS runtime we don't have many options here.
BTW are we still need to run Axis2 JAX-WS within our products ? I
think we need to migrate them to run with CXF.
Thanks !
>
> Thanks,
> Senaka.
>
>
> On Tue, Aug 28, 2012 at 7:03 AM, Sagara Gunathunga wrote:
>>
>> On Tue, Aug 28, 2012 at 10:22 AM, Chethiya Abeysinghe
>> wrote:
>> > Hi all,
>> >
>> > We have tried replacing jaxb_2.1.7.wso2v1.jar in Aug-22 AS build.
>> > jaxrs_basic sample has failed with following message in the server.
>> >
>> > [2012-08-27 10:18:52,302] WARN
>> > {org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor} - No message
>> > body
>> > writer has been found for response class Customer.
>> >
>> > And following message on client
>> >
>> > [INFO]
>> > [INFO] >>> exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic >>>
>> > [INFO]
>> > [INFO] <<< exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic <<<
>> > [INFO]
>> > [INFO] --- exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic ---
>> > Sent HTTP GET request to query customer info
>> > [WARNING]
>> > java.lang.reflect.InvocationTargetException
>> > 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 org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
>> > at java.lang.Thread.run(Thread.java:680)
>> > Caused by: java.io.IOException: Server returned HTTP response code: 500
>> > for
>> > URL:
>> >
>> > http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
>> > at
>> >
>> > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
>> > at java.net.URL.openStream(URL.java:1010)
>> > at demo.jaxrs.client.Client.main(Client.java:51)
>> > ... 6 more
>> > [INFO]
>> >
>> > [INFO] BUILD FAILURE
>> > [INFO]
>> >
>> > [INFO] Total time: 5.900s
>> > [INFO] Finished at: Mon Aug 27 10:18:52 IST 2012
>> > [INFO] Final Memory: 6M/528M
>> > [INFO]
>> >
>> > [ERROR] Failed to execute goal
>> > org.codehaus.mojo:exec-maven-plugin:1.2.1:java (default) on project
>> > jaxrs_basic: An exception occured while executing the Java class. null:
>> > InvocationTargetException: Server returned HTTP response code: 500 for
>> > URL:
>> >
>> > http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
>> > -> [Help 1]
>> > [ERROR]
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> > -e
>> > switch.
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> > [ERROR]
>> > [ERROR] For more information about the errors and possible solutions,
>> > please
>> > read the following articles:
>> > [ERROR] [Help 1]
>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> >
>> > Anjana and I tried to overcome this by creating a jaxb orbit using
>> > version
>> > 2.1.0 (which is the version used in jdk). That's also produced a similar
>> > result.
>> >
>> > At the moment we don't have a clue about what's going on here. If you
>> > have
>> > an idea please let us know.
>> >
>> >
>> > Anyway reverting the jaxb version back to 2.1.7 is not the correct
>> > solution.
>> > What we should try to get done is to get the new jaxb version (2.2.5
>> > 2.2.6)
>> > work with ndatasource. I'll start another thread stating problems we are
>> > facing with ndatasource when it uses the latest jaxb-api loaded form
>> > orbit
>> > bundle.
>> >
>> > Since reverting jaxb version back to 2.1.7 resolved the problem we are
>> > having with UDDI on greg, I've change only the greg distribution to ship
>> > it
>> > with jaxb version 2.1.7.
>>
>> I don't think shipping Greg with jaxb version 2.1.7 is a acceptable
>> solution we need to ship compatible set of libs for whole platform
>> otherwise this make lot of unwanted issues when installing various
>> features. What I think is porting ndatasource in to jaxb version
>> (2.2.5 2.2.6) is the only solution here.
>>
>> Thanks !
>>
>> >
>> > Thanks,
>> > - Chethiya
>> >
>> > On Thu, A
Re: [Dev] reverting jaxb version in carbon back to 2.1.7
Hi Sagara,
That's exactly the point here. With the current version of JAXB, Axis2
JAX-WS is not working and due to that UDDI is totally busted in G-Reg. If
we are to use single version of a dependency across the platform, we have
to test and ensure that all products are working fine before attempting a
major upgrade or situations like this become unavoidable.
Thanks,
Senaka.
On Tue, Aug 28, 2012 at 7:03 AM, Sagara Gunathunga wrote:
> On Tue, Aug 28, 2012 at 10:22 AM, Chethiya Abeysinghe
> wrote:
> > Hi all,
> >
> > We have tried replacing jaxb_2.1.7.wso2v1.jar in Aug-22 AS build.
> > jaxrs_basic sample has failed with following message in the server.
> >
> > [2012-08-27 10:18:52,302] WARN
> > {org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor} - No message body
> > writer has been found for response class Customer.
> >
> > And following message on client
> >
> > [INFO]
> > [INFO] >>> exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic >>>
> > [INFO]
> > [INFO] <<< exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic <<<
> > [INFO]
> > [INFO] --- exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic ---
> > Sent HTTP GET request to query customer info
> > [WARNING]
> > java.lang.reflect.InvocationTargetException
> > 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 org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> > at java.lang.Thread.run(Thread.java:680)
> > Caused by: java.io.IOException: Server returned HTTP response code: 500
> for
> > URL:
> >
> http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
> > at
> >
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
> > at java.net.URL.openStream(URL.java:1010)
> > at demo.jaxrs.client.Client.main(Client.java:51)
> > ... 6 more
> > [INFO]
> >
> > [INFO] BUILD FAILURE
> > [INFO]
> >
> > [INFO] Total time: 5.900s
> > [INFO] Finished at: Mon Aug 27 10:18:52 IST 2012
> > [INFO] Final Memory: 6M/528M
> > [INFO]
> >
> > [ERROR] Failed to execute goal
> > org.codehaus.mojo:exec-maven-plugin:1.2.1:java (default) on project
> > jaxrs_basic: An exception occured while executing the Java class. null:
> > InvocationTargetException: Server returned HTTP response code: 500 for
> URL:
> >
> http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
> > -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> please
> > read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >
> > Anjana and I tried to overcome this by creating a jaxb orbit using
> version
> > 2.1.0 (which is the version used in jdk). That's also produced a similar
> > result.
> >
> > At the moment we don't have a clue about what's going on here. If you
> have
> > an idea please let us know.
> >
> >
> > Anyway reverting the jaxb version back to 2.1.7 is not the correct
> solution.
> > What we should try to get done is to get the new jaxb version (2.2.5
> 2.2.6)
> > work with ndatasource. I'll start another thread stating problems we are
> > facing with ndatasource when it uses the latest jaxb-api loaded form
> orbit
> > bundle.
> >
> > Since reverting jaxb version back to 2.1.7 resolved the problem we are
> > having with UDDI on greg, I've change only the greg distribution to ship
> it
> > with jaxb version 2.1.7.
>
> I don't think shipping Greg with jaxb version 2.1.7 is a acceptable
> solution we need to ship compatible set of libs for whole platform
> otherwise this make lot of unwanted issues when installing various
> features. What I think is porting ndatasource in to jaxb version
> (2.2.5 2.2.6) is the only solution here.
>
> Thanks !
>
> >
> > Thanks,
> > - Chethiya
> >
> > On Thu, Aug 23, 2012 at 3:13 PM, Pradeep Fernando
> wrote:
> >>
> >> Hi chethiya,
> >>
> >> can you test this modification with a hosted JAXRS and JAXWS web-app
> >>
> >> ---PRadeep
> >
> >
> >
> >
> > --
> > Chethiya Abeysinghe
> > Software Engineer; WSO2, Inc.; http://wso2.com/
> > email: cheth...@wso2.com phone: +94 777444891
> > blog: chethiya3000.blogspot.com
> >
> >
> >
> > ___
> > Dev mailing list
> > Dev@wso2.org
> > http://wso2.org/cgi-bin/mailman/listinfo/dev
> >
>
>
>
> --
> Sagara G
Re: [Dev] reverting jaxb version in carbon back to 2.1.7
On Tue, Aug 28, 2012 at 10:22 AM, Chethiya Abeysinghe wrote:
> Hi all,
>
> We have tried replacing jaxb_2.1.7.wso2v1.jar in Aug-22 AS build.
> jaxrs_basic sample has failed with following message in the server.
>
> [2012-08-27 10:18:52,302] WARN
> {org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor} - No message body
> writer has been found for response class Customer.
>
> And following message on client
>
> [INFO]
> [INFO] >>> exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic >>>
> [INFO]
> [INFO] <<< exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic <<<
> [INFO]
> [INFO] --- exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic ---
> Sent HTTP GET request to query customer info
> [WARNING]
> java.lang.reflect.InvocationTargetException
> 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 org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for
> URL:
> http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
> at java.net.URL.openStream(URL.java:1010)
> at demo.jaxrs.client.Client.main(Client.java:51)
> ... 6 more
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 5.900s
> [INFO] Finished at: Mon Aug 27 10:18:52 IST 2012
> [INFO] Final Memory: 6M/528M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:java (default) on project
> jaxrs_basic: An exception occured while executing the Java class. null:
> InvocationTargetException: Server returned HTTP response code: 500 for URL:
> http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
> -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> Anjana and I tried to overcome this by creating a jaxb orbit using version
> 2.1.0 (which is the version used in jdk). That's also produced a similar
> result.
>
> At the moment we don't have a clue about what's going on here. If you have
> an idea please let us know.
>
>
> Anyway reverting the jaxb version back to 2.1.7 is not the correct solution.
> What we should try to get done is to get the new jaxb version (2.2.5 2.2.6)
> work with ndatasource. I'll start another thread stating problems we are
> facing with ndatasource when it uses the latest jaxb-api loaded form orbit
> bundle.
>
> Since reverting jaxb version back to 2.1.7 resolved the problem we are
> having with UDDI on greg, I've change only the greg distribution to ship it
> with jaxb version 2.1.7.
I don't think shipping Greg with jaxb version 2.1.7 is a acceptable
solution we need to ship compatible set of libs for whole platform
otherwise this make lot of unwanted issues when installing various
features. What I think is porting ndatasource in to jaxb version
(2.2.5 2.2.6) is the only solution here.
Thanks !
>
> Thanks,
> - Chethiya
>
> On Thu, Aug 23, 2012 at 3:13 PM, Pradeep Fernando wrote:
>>
>> Hi chethiya,
>>
>> can you test this modification with a hosted JAXRS and JAXWS web-app
>>
>> ---PRadeep
>
>
>
>
> --
> Chethiya Abeysinghe
> Software Engineer; WSO2, Inc.; http://wso2.com/
> email: cheth...@wso2.com phone: +94 777444891
> blog: chethiya3000.blogspot.com
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
--
Sagara Gunathunga
Technical Lead; WSO2, Inc.; http://wso2.com
V.P Apache Web Services ; http://ws.apache.org/
Blog ; http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] reverting jaxb version in carbon back to 2.1.7
Hi all,
We have tried replacing jaxb_2.1.7.wso2v1.jar in Aug-22 AS build.
jaxrs_basic sample has failed with following message in the server.
[2012-08-27 10:18:52,302] WARN
{org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor} - No message body
writer has been found for response class Customer.
And following message on client
[INFO]
[INFO] >>> exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic >>>
[INFO]
[INFO] <<< exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic <<<
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic ---
Sent HTTP GET request to query customer info
[WARNING]
java.lang.reflect.InvocationTargetException
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 org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
at java.lang.Thread.run(Thread.java:680)
Caused by: java.io.IOException: Server returned HTTP response code: 500 for
URL:
http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
at java.net.URL.openStream(URL.java:1010)
at demo.jaxrs.client.Client.main(Client.java:51)
... 6 more
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.900s
[INFO] Finished at: Mon Aug 27 10:18:52 IST 2012
[INFO] Final Memory: 6M/528M
[INFO]
[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:java (default) on project
jaxrs_basic: An exception occured while executing the Java class. null:
InvocationTargetException: Server returned HTTP response code: 500 for URL:
http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123->
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Anjana and I tried to overcome this by creating a jaxb orbit using version
2.1.0 (which is the version used in jdk). That's also produced a similar
result.
At the moment we don't have a clue about what's going on here. If you have
an idea please let us know.
Anyway reverting the jaxb version back to 2.1.7 is not the correct
solution. What we should try to get done is to get the new jaxb version
(2.2.5 2.2.6) work with ndatasource. I'll start another thread stating
problems we are facing with ndatasource when it uses the latest jaxb-api
loaded form orbit bundle.
Since reverting jaxb version back to 2.1.7 resolved the problem we are
having with UDDI on greg, I've change only the greg distribution to ship it
with jaxb version 2.1.7.
Thanks,
- Chethiya
On Thu, Aug 23, 2012 at 3:13 PM, Pradeep Fernando wrote:
> Hi chethiya,
>
> can you test this modification with a hosted JAXRS and JAXWS web-app
>
> ---PRadeep
>
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] reverting jaxb version in carbon back to 2.1.7
On Thu, Aug 23, 2012 at 3:13 PM, Pradeep Fernando wrote: > Hi chethiya, > > can you test this modification with a hosted JAXRS and JAXWS web-app > Please test on windows also. Thanks, Kishanthan. > > ---PRadeep > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] reverting jaxb version in carbon back to 2.1.7
Hi chethiya, can you test this modification with a hosted JAXRS and JAXWS web-app ---PRadeep ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] reverting jaxb version in carbon back to 2.1.7
Hi all, As of some of the observations I had with Anjana while trying to resolve issue causing Linkage errors with jaxb, we figured out follows regarding the $subject. *Observations:* 1. If we remove jaxb form bundles.info file, still the server starts without any difference. 2. Current jaxb orbit bundle has following pom.xml file. com.sun.xml.bind jaxb-impl 2.2.5 com.sun.xml.bind jaxb-xjc 2.2.5 com.sun.*, org.relaxng.*, org.kohsuke.*, In here since the jaxb-api is commented out those packages are retrieved from jdk (added to launch.ini) . So the effective version of jaxb-api for java 1.6.0_33 is 2.1.10 as of one of my previous mails. But jaxb-impl is still there and those packages are exported from jaxb orbit bundle. 3. Carbon has been running for more than 1 month without any complains since the jaxb version upgrade except for this linkage error problem. i.e. since jaxb-api is loaded from JVM, it gives linkage error when unmarshaller is called with a bundle loaded javax.xml.stream.XMLStreamReader class object *Conclusions: * Catch in here is that jaxb-api is loaded form JVM. Therefore all what it consumes are also should be loaded from JVM as of the Java class loading mechanism, unless equinox does some tweaks on this. If that's the case jaxb-impl should also be loaded from JVM. @Pradeep can you please verify this? *If we assume that's the case,* it implies exported packages in jaxb-impl under jaxb bundle are not used by JVM loaded jaxb-api. That's why carbon starts even without jaxb orbit bundle. In that case, effective jaxb version running at current carbon builds is JVM dependant and for java 1.6.0_33 it's jaxb 2.1.10. *Actions we can take:* If that's the case we can safely revert back to previous jaxb orbit bundle (2.1.7.wso2v1) given that current jaxb bundle has been not effectively used and the used jaxb version for last month was JVM shipped jaxb (2.1.10 for java 1.6.0_33) Shall we revert back to jaxb 2.1.7.wso2v1 orbit bundle from current jaxb bundle (2.2.5.wso2v1) ? -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: chethiya at wso2.com blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
