The webservices get deployed fine now but I am getting an WSDLException when I call any method. Any ideas? Could it be my IBM jvm? Probabily not...just wondering....
Caused by: WSDLException: faultCode=PARSER_ERROR: Problem parsing '- WSDL Document -'.: The value of the attribute "xmlns:tns1" is invalid. Prefixed namespace bindings may not be empty.: org.xml.sax.SAXParseException: The value of the attribute "xmlns:tns1" is invalid.
Prefixed namespace bindings may not be empty.
at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:235)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:209)
at com.ibm.wsdl.xml.WSDLWriterImpl.getDocument(Unknown Source)
at com.ibm.wsdl.xml.WSDLWriterImpl.getDocument(Unknown Source)
at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:236)
at org.apache.axis.providers.java.JavaProvider.generateWSDL(JavaProvider.java:418) at org.jboss.net.axis.server.EJBProvider.generateWSDL(EJBProvider.java:243)
at org.apache.axis.strategies.WSDLGenStrategy.visit(WSDLGenStrategy.java:72)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
at org.apache.axis.SimpleChain.generateWSDL(SimpleChain.java:143)
at org.apache.axis.handlers.soap.SOAPService.generateWSDL(SOAPService.java:355)
at org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:490)
at org.apache.axis.transport.http.AxisServlet.processWsdlRequest(AxisServlet.java:428)
at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:280)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:558)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1714)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:507)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1664)
at org.mortbay.http.HttpServer.service(HttpServer.java:863)
at org.jboss.jetty.Jetty.service(Jetty.java:460)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:775)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:939)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:792)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)
at com.ibm.wsdl.xml.WSDLWriterImpl.getDocument(Unknown Source) at com.ibm.wsdl.xml.WSDLWriterImpl.getDocument(Unknown Source) at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:236)
Jason Essington wrote:
On Monday, June 9, 2003, at 01:00 PM, Felipe Oliveira wrote:
hi i am using xdoclet to generate my entity and session beans but i also want it to generate my webservices. i have the part where it generates the web-service.xml defining my services and mapping them to the correct jndi entries of my session beans. my session bean methods return custom data objects. the problem is that xdoclet is not adding the data mapping for my data objects. i assume i have to use @jboss-net:xml-schema right? where should i add this entry? my data objects are generated automatically by xdoclet so i don't think it's there. any ideas anyone? dr jung?
ya, I have an Idea :-)
I am doing something like:
* @ejb.value-object * name = "Symbol" * match = "*" * @jboss-net.xml-schema * object-type="value"
But that is using value objects (and a hacked template file).
If you want to map your dataobjects, it is a simple matter of doing something like:
* @jboss-net.xml-schema * data-object="true" * urn="symbol"
of course you'll have to grab the xdoclet-module-jboss-net.jar (from the jboss.net/output/lib directory after you've built jboss from source) and place it where ever the rest of your xdoclet jar files are. your ejb-doclet task looks set up o.k. to make it all work
-jason
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user