[ http://issues.apache.org/jira/browse/AXIS2-720?page=comments#action_12415939 ]
Christopher Blunck commented on AXIS2-720: ------------------------------------------ I just want to post a follow-up that I'm experiencing a variant of this problem. I'm using xmlbeans for xml marshalling, and when I send a SOAP message to the server the SOAP comes out looking like this: <pre> <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> <soapenv:Header></soapenv:Header> <soapenv:Body> <GetSummary xmlns="http://wxnet.org/inquiry/current";> <Station xmlns=""> <Name xmlns="http://wxnet.org/inquiry/types";>Home_Weather</Name> </Station> </GetSummary> </soapenv:Body> </soapenv:Envelope> Note my Station element has a blank namespace. I'm running the 1.0 release of Axis2, including the 1.0 release of AXIOM. I've tried replacing my wstx with a v3.0 RC and that doesn't seem to do squat. I don't believe that resolving the bug as "fixed" just because you altered somebody's WSDL is appropriate. I made the same modification to my WSDL, and it doesn't work for me. A fix involves changing the software, not changing the data that an end-user runs through your system. > Data binding Error after using WSDL2Java to generate xmlbeans code > ------------------------------------------------------------------ > > Key: AXIS2-720 > URL: http://issues.apache.org/jira/browse/AXIS2-720 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: databinding > Versions: 1.0 > Environment: Server: Axis2 1.0 inside a Tomcat 5.5.15 under Scientific > Linux, 2.6.x kernel > Client: Windows XP SP2 with JDK 1.5.0_06 > Reporter: Rincewind Wizard > Assignee: Ajith Harshana Ranabahu > Attachments: EpiLocService.wsdl, EpiLocService.wsdl, TextLocService.aar, > TextLocServiceSkeleton.java, TextLocServiceTest.java > > We've used the attached WSDL to create a service & client by means of > the WSDL2Java tool (xmlbeans databinding). After implementing the > simplest of business logics in the server, we deployed the service .aar > in the axis2 install inside a tomcat server. According to the status > page, the service is running error free. > The client was also created by WSDL2Java, where we wrote a simple main() > class to test the client. We've pasted it below. > public static void main(String[] args) { > try { > PredictLocalizationRequestDocument pdoc = > PredictLocalizationRequestDocument.Factory.newInstance(); > pdoc.addNewPredictLocalizationRequest(); > pdoc.getPredictLocalizationRequest().setSequence("ASDF"); > pdoc.getPredictLocalizationRequest().setOrganism("ANIMAL"); > TextLocServiceStub sender = new > TextLocServiceStub("http://localhost/axis2/services/TextLocService";); > PredictLocalizationResponseDocument res = > sender.predictLocalization(pdoc); > System.out.println(res.toString()); > } catch (Exception e) { > e.printStackTrace(); > } > } > The client now runs up until the document is being sent, where it throws > an Exception. The stack trace is below. We think it is still a > client-side problem, although the client does complain if it is not > connected to the server and doesn't throw this exception. > Please let us know if we should change anything about our client > generation procedure, or how we can use the test client jar that is also > generated by the WSDL2Java tool. > Thanks a lot for your time! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
