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 <[email protected]> wrote: > On Tue, Aug 28, 2012 at 12:02 PM, Senaka Fernando <[email protected]> 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 <[email protected]> > wrote: > >> > >> On Tue, Aug 28, 2012 at 10:22 AM, Chethiya Abeysinghe < > [email protected]> > >> 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 <[email protected]> > >> > 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: [email protected] phone: +94 777444891 > >> > blog: chethiya3000.blogspot.com > >> > > >> > > >> > > >> > _______________________________________________ > >> > Dev mailing list > >> > [email protected] > >> > 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 > >> [email protected] > >> http://wso2.org/cgi-bin/mailman/listinfo/dev > > > > > > > > > > -- > > Senaka Fernando > > Member - Integration Technologies Management Committee; > > Technical Lead; WSO2 Inc.; http://wso2.com > > Member; Apache Software Foundation; http://apache.org > > > > E-mail: senaka AT wso2.com > > P: +1 408 754 7388; ext: 51736; M: +94 77 322 1818 > > Linked-In: http://linkedin.com/in/senakafernando > > > > Lean . Enterprise . Middleware > > > > > > -- > Sagara Gunathunga > > Technical Lead; WSO2, Inc.; http://wso2.com > V.P Apache Web Services ; http://ws.apache.org/ > Blog ; http://ssagara.blogspot.com > -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
