I changed to the RPCMessageReceiver and now I get a NPE
org.apache.axis2.AxisFault: null; nested exception is:
java.lang.NullPointerException
at org.apache.axis2.description.AxisService.getWSDL(AxisService.java:663)
at org.apache.axis2.description.AxisService.printWSDL(AxisService.java:549)
at org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:167)
at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:166)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
-----Original Message-----
From: John Pfeifer [mailto:[EMAIL PROTECTED]]
Sent: Mon 10/30/2006 5:05 PM
To: [email protected]
Subject: RE: WSDL Generation for Doc Literal Web Services
Thanks, how do I tell it what my schema looks like?
-----Original Message-----
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Sent: Mon 10/30/2006 5:04 PM
To: [email protected]
Subject: Re: WSDL Generation for Doc Literal Web Services
If you use the RPC receiver, Axis2 will generate a doc/literal WSDL for you.
Anne
On 10/30/06, John Pfeifer <[EMAIL PROTECTED]> wrote:
>
>
>
>
> We are currently using Document Literal Web Services with XSD Schema
> Validation. The XSD Validation is performed before the XML is transformed
> into JiBX objects. Our schemas are fairly simple but perform a lot of data
> type validation. I have a couple of questions.
>
> 1. Is there any plan to make schema validation an option for Axis2 where
> it could be enabled/disabled at the service level? I can't understand why
> schema validation isn't part of the framework already. We use JiBX for data
> binding, which at some point will tell you if your XML is bad, but I think
> their is a lot of value in the data field validation such as length, pattern
> matching, etc.
>
> 2. Is there any way to have Axis2 generate a WSDL for a document literal
> web service. JiBXSOAP has a nice option where it will take an XSD and embed
> it into the WSDL. This is nice because we don't have to maintain the XSD
> and the WSDL. Are there any plans to do this in Axis2?
>
>
> Thanks,
>
> John
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Title: RE: WSDL Generation for Doc Literal Web Services
- RE: WSDL Generation for Doc Literal Web Services John Pfeifer
- Re: WSDL Generation for Doc Literal Web Services Davanum Srinivas
