Axis2 Client receiving element, but value object is null

2013-03-20 Thread Adam
All, A quick description of my problem. I'm using axis2 1.6.2 and am generating the stubs using xmlbeans binding. I'm calling a web service that has a response consisting of different namespace elements. I've installed a log handler, and see the full message coming back, with sub element Transactio

RE: java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to org.apache.axiom.soap.SOAPFaultDetail

2013-03-20 Thread Shah, Sumit (CGI Federal)
Thanks Andreas...I will try your suggestion. -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Saturday, March 16, 2013 2:47 PM To: java-user Subject: Re: java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to org.apac

WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Generated stub fails compilation

2013-03-20 Thread Shah, Sumit (CGI Federal)
Hi, I am using WSImport to generate the client stubs for a bunch of wsdl files. After the generation the code fails to compile. I am using this with Axis2 1.6.2. The following code block fails: If you notice: the line: 'com.sample.test.webservices.impl.participant.Notify.class,' ends with a co

RE: WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Generated stub fails compilation - Update: Actually issue occurring in WSDL2Code

2013-03-20 Thread Shah, Sumit (CGI Federal)
I take the WSImport part back. It is actually happening with WSDL2Code. It does not happen if I use the WSDL2Code with Axis2 1.6.0. The issue is happening with WSDL2Code in Axis2 1.6.2 and I am using Axiom 1.2.14. Is anyone aware of the issue with 1.6.2? From: Shah, Sumit (CGI Federal) Sent: We

RE: WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Generated stub fails compilation - Update: Actually issue occurring in WSDL2Code

2013-03-20 Thread Shah, Sumit (CGI Federal)
I did some research and it's the code/XSL in JaxbRIDatabindingTemplate.xsl that is writing out the portion of the stub that causing the compilation issue. Unless a concurrency issue, I wonder why consistently in couple of cases the 'position() != last()' seems to be 'true' when it should be fals

RE: WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Generated stub fails compilation

2013-03-20 Thread Martin Gainty
com.sample.test.webservices.impl.participant.Notify.class, reason why the last class parameter has a trailing comma Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht

RE: WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Generated stub fails compilation - Update: Actually issue occurring in WSDL2Code

2013-03-20 Thread Shah, Sumit (CGI Federal)
That is precisely what I am trying to find out why it is adding the comma after the last class parameter. Thanks Sumit From: Martin Gainty [mailto:mgai...@hotmail.com] Sent: Wednesday, March 20, 2013 7:49 PM To: java-user@axis.apache.org Subject: RE: WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Gen

RE: WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Generated stub fails compilation - Update: Actually issue occurring in WSDL2Code

2013-03-20 Thread Shah, Sumit (CGI Federal)
What I have found out though is the following, The class(com.sample.test.webservices.impl.participant.Notify.class) is question is for a one way operation (notify). The wsdl for that operation looks like: