Data binding problem (xmlbeans) - binding subelement to toplevel element?
Apologies in advance if this is known problem, but I'm hoping the answer to this is easy... I can't seem to get passed a data binding problem in my client stub on a response for a very simple scenario. It appears that the client stub is trying to bind a subelement of my response (testid) to the top level element (testSearchResponse). The error is: Exception: Data Binding Error caused by: Caused by: org.apache.xmlbeans.XmlException: error: The document is not a [EMAIL PROTECTED]://net.semandex.searchservice.webservice/xsd: document element local name mismatch expected testSearchResponseParam got testid Here is the simple WSDL: // TYPES complexType name=testSearchRequest sequence element name=testid type=xsd:integer minOccurs=1 maxOccurs=1/ element name=testid2 type=xsd:integer minOccurs=1 maxOccurs=1/ /sequence /complexType complexType name=testSearchResponse sequence element name=testid type=xsd:integer minOccurs=1 maxOccurs=1/ element name=testid2 type=xsd:integer minOccurs=1 maxOccurs=1/ /sequence /complexType // MESSAGES message name=testSearchRequest part element=xsd1:testSearchRequestParam name=testSearchRequest/ /message message name=testSearchResponse part element=xsd1:testSearchResponseParam name=testSearchResponse/ /message // PORTTYPE portType name=SearchPortType operation name=testSearch input message=tns:testSearchRequest name=testSearchRequest/ output message=tns:testSearchResponse name=testSearchResponse/ /operation /porttype // BINDING binding name=SearchPortBinding type=tns:SearchPortType soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ operation name=testSearch soap:operation soapAction=testSearch style=rpc/ input name=testSearchRequest soap:body namespace=http://net.semandex.search.service/Search; use=literal/ /input output name=testSearchResponse soap:body namespace=http://net.semandex.search.service/Search; use=literal/ /output /operation /binding Thanks, Andrew
RE: Data binding problem (xmlbeans) - binding subelement to toplevel element?
Anne, Thank you! That did the trick J -Andrew. From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 17, 2006 2:50 PM To: axis-user@ws.apache.org Subject: Re: Data binding problem (xmlbeans) - binding subelement to toplevel element? Andrew, With RPC style, your message parts must reference types rather than elements Your WSDL should look something like this: // TYPES complexType name=testSearchRequest sequence element name=testid type=xsd:integer minOccurs=1 maxOccurs=1/ element name=testid2 type=xsd:integer minOccurs=1 maxOccurs=1/ /sequence /complexType complexType name=testSearchResponse sequence element name=testid type=xsd:integer minOccurs=1 maxOccurs=1/ element name=testid2 type=xsd:integer minOccurs=1 maxOccurs=1/ /sequence /complexType // MESSAGES message name=testSearchRequest part type=xsd1:testSearchRequest name=testSearchRequest/ /message message name=testSearchResponse part type=xsd1:testSearchResponse name=testSearchResponse/ /message Anne On 5/17/06, Andrew Cohen [EMAIL PROTECTED] wrote: Apologies in advance if this is known problem, but I'm hoping the answer to this is easy... I can't seem to get passed a data binding problem in my client stub on a response for a very simple scenario. It appears that the client stub is trying to bind a subelement of my response (testid) to the top level element (testSearchResponse). The error is: Exception: Data Binding Error caused by: Caused by: org.apache.xmlbeans.XmlException : error: The document is not a testSearchResponseParam@http://net.semandex.searchservice.webservice/xsd: document element local name mismatch expected testSearchResponseParam got testid Here is the simple WSDL: // TYPES complexType name=testSearchRequest sequence element name=testid type=xsd:integer minOccurs=1 maxOccurs=1/ element name=testid2 type=xsd:integer minOccurs=1 maxOccurs=1/ /sequence /complexType complexType name=testSearchResponse sequence element name=testid type=xsd:integer minOccurs=1 maxOccurs=1/ element name=testid2 type=xsd:integer minOccurs=1 maxOccurs=1/ /sequence /complexType // MESSAGES message name=testSearchRequest part element=xsd1:testSearchRequestParam name=testSearchRequest/ /message message name=testSearchResponse part element=xsd1:testSearchResponseParam name=testSearchResponse/ /message // PORTTYPE portType name=SearchPortType operation name=testSearch input message=tns:testSearchRequest name=testSearchRequest/ output message=tns:testSearchResponse name=testSearchResponse/ /operation /porttype // BINDING binding name=SearchPortBinding type=tns:SearchPortType soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ operation name=testSearch soap:operation soapAction=testSearch style=rpc/ input name=testSearchRequest soap:body namespace= http://net.semandex.search.service/Search use=literal/ /input output name=testSearchResponse soap:body namespace= http://net.semandex.search.service/Search use=literal/ /output /operation /binding Thanks, Andrew
Error logging into Axis2(v1.0) admin console
Hi all, I'm a newbie to Axis2 and I'm unable to login to the administration console (see the exception below). I am running JDK 1.5.0_06 and have deployed the axis2.war file to a Jetty v5.1.5 server. I followed the instructions to change the java.security file for Java 1.5. Any help would be greatly appreciated! :-) Exception details (after logging in as admin/axis2): - Error dispatching request /SemandexWebServices/axis2-admin/login java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.axis2.transport.http.AbstractAgent.handle(AbstractAgent.ja va:77) at org.apache.axis2.transport.http.AdminAgent.handle(AdminAgent.java:93) at org.apache.axis2.transport.http.AxisAdminServlet.doGet(AxisAdminServl et.java:41) at org.apache.axis2.transport.http.AxisAdminServlet.doPost(AxisAdminServ let.java:35) at javax.servlet.http.HttpServlet.service(HttpServlet.java:616) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427 ) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati onHandler.java:473) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5 68) at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplication Context.java:635) at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) at org.mortbay.http.HttpServer.service(HttpServer.java:954) at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java: 244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) Caused by: org.apache.jasper.JasperException: String index out of range: -1 at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper .java:372) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2 92) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427 ) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati onHandler.java:473) at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:262) at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:162) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary .java:966) at org.apache.jsp.axis2_002dweb.admin_jsp._jspService(admin_jsp.java:71) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper .java:324) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2 92) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427 ) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati onHandler.java:473) at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:262) at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:162) at org.apache.axis2.transport.http.AbstractAgent.renderView(AbstractAgen t.java:116) at org.apache.axis2.transport.http.AdminAgent.processLogin(AdminAgent.ja va:174) Thanks, -Andrew Andrew J. Cohen Senior Software Engineer Semandex Networks, Inc. 201 Washington Road Princeton, NJ 08540-6449 [EMAIL PROTECTED] phone: 609-720-4929 fax: 609-514-4061 The information contained in this e-mail may be privileged and confidential, and is intended only for the use of the individual(s) or entity named above who has specifically been authorized to receive it. I apologize if you are not the intended recipient-- If you have received this communication in error, please notify me immediately by telephone or email to avoid any further misdirected e-mails and please permanently delete the message and all attachments. Please note that any dissemination, distribution or copying of this communication is strictly prohibited.
