We have complex wsdl with several services/namespaces/complex types. Are
there 'easy to use' tools to validate the wsdl?
It could be usefull to verify the wsdl on every stay and see if it
breaks at a point.

We have complex types that need to be shared between services. Now we
put all services in one wsdl to accomplish this. 
When using several wsdl's we had the problem that when importing them in
for example .NET the dataclasses all became in separate namespaces
making it hard to share them between services.  Is there a more elegant
way to solve this?

Thanks,
Arent-Jan

-----Original Message-----
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 22, 2004 6:25 PM
To: [EMAIL PROTECTED]
Subject: RE: streaming=on working?


This is one of the problems that needs to be fixed. We need a good test
scenario. If you are willing to help fix this....you will have to start
with a simple service and then keep adding stuff, till it breaks and
then submit a bug report.

thanks,
dims
--- "Banck, Arent-Jan" <[EMAIL PROTECTED]> wrote:
> Yes, the was generated with wsdl2java. There are several services in 
> the same wsdl to avoid duplicating complex types in several 
> namespaces. Not sure if that might cause the problems.
> 
> -----Original Message-----
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 22, 2004 6:07 PM
> To: [EMAIL PROTECTED]
> Subject: Re: streaming=on working?
> 
> 
> Arent-Jan,
> 
> is this a service that you generated using wsdl2java? if not, can you 
> please try a service that was generated using wsdl2java?
> 
> thanks,
> dims
> 
> --- "Banck, Arent-Jan" <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I am experimenting with Axis 1.2(cvs) on WebLogic 8.1, but I am 
> > having
> 
> > problems when setting streaming=on for a service in the wsdd. The
> > documentation warns about turning it on, but is it supposed to work?

> > With streaming=on, I get exceptions on every call:
> >  
> > org.xml.sax.SAXException: operation description is missing parameter
> > description!
> >         at org.apache.axis.AxisFault.makeFault(AxisFault.java:98)
> >         at
> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:573)
> >         at org.apache.axis.Message.getSOAPEnvelope(Message.java:427)
> >         at org.apache.axis.Message.getContentType(Message.java:456)
> >         at 
> > org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:6
> > 97
> > )
> >  
> > and
> > org.xml.sax.SAXException: SimpleDeserializer encountered a child
> > element, which is NOT expected, in something it was try ing to 
> > deserialize.
> >         at org.apache.axis.AxisFault.makeFault(AxisFault.java:98)
> >         at
> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:573)
> >         at org.apache.axis.Message.getSOAPEnvelope(Message.java:427)
> >         at org.apache.axis.Message.getContentType(Message.java:456)
> >         at
> >
> org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:697
> )
> >         at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> >         at
> >
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase
> > .j
> > ava:301)
> >         at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> >  
> > Any clue what causes this/how to find out/how to fix?
> >  
> > Thanks,
> > Arent-Jan
> > 
> 
> 
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/


=====
Davanum Srinivas - http://webservices.apache.org/~dims/

Reply via email to