subject:"wsdl 2.0 questions"

Re: wsdl 2.0 questions

2007-08-02 Thread Chathura Herath

Its the MEP in your operation. Interface->operation pattern attribute.

Again a namespace problem. Please try replacing it with the following.
http://www.w3.org/ns/wsdl/in-out

Thanks
Chathura

On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Right.  That makes sense and the soap12 one must be changed as well.
>
> Ok so using the same batch file as before and making those changes (see
> below).  I am now back to yesterday's error message about the message
> exchange pattern.  Where is this http://www.w3.org/2004/03/wsdl/in-outcoming 
> from?
>
> >wsdl2java.bat -uri hilton2.wsdl -wv 2.0
> Using AXIS2_HOME: C:\Java\axis2-1.3RC2
> Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
> at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(
> CodeGenerationEngine.java:147)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: org.apache.axis2.AxisFault: An unsupported message exchange
> pattern (MEP) exists in ID is http://www.w3.org/2004/03/wsdl/in-out
> ...
>
> -
> hilton2.wsdl
> -
>
>  xmlns="http://www.w3.org/ns/wsdl";
> targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap";
> xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
>
>   
> This document describes the GreatH Web service.  Additional
> application-level requirements for use of this service --
> beyond what WSDL 2.0 is able to describe -- are available
> at http://greath.example.com/2004/reservation-documentation.html
>   
>
>   
>  xmlns:xs="http://www.w3.org/2001/XMLSchema";
> targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd
> "
> xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>
>
>   
>   
> 
>   
>   
>   
> 
>   
>
>   
>
>   
>
> 
>   
>
>   
>
>  element = "ghns:invalidDataError"/>
>
>  pattern=" http://www.w3.org/2004/03/wsdl/in-out"; >
>element="ghns:checkAvailability" />
>element="ghns:checkAvailabilityResponse" />
> 
> 
>
>   
>
>  interface="tns:reservationInterface"
>   type="http://www.w3.org/ns/wsdl/soap";
>   wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>
>
>
> wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/>
>
>
>wsoap:code="soap:Sender"/>
>
>   
>
>   interface="tns:reservationInterface">
>
>  binding="tns:reservationSOAPBinding"
>address ="http://greath.example.com/2004/reservation"/
> >
>
>   
>
> 
>
>
> On 8/2/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> >
> > Make sure you're using the correct WSDL namespace.
> >
> > You're currently using " 
> > http://www.w3.org/2004/08/wsdl";
> >
> > You should be using "http://www.w3.org/ns/wsdl
> >  "
> >
> > Anne
> >
> > On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Keith,
> > >
> > > Thanks for looking at this.  I'm reading your message and I'm
> > > confused. I am using Axis2 1.3 RC2 which is the latest RC from the url
> > > you listed. If you are using the same one, then perhaps I have some kind 
> > > of
> > > pilot error in my wsdl2java usage.  Actually I seem to be heading full 
> > > speed
> > > into reverse because now the error message is
> > >
> > > Using AXIS2_HOME:
> > >
> > > 
> > > Here's my fancy batch file:
> > >
> > > echo %AXIS2_HOME%
> > > wsdl2java.bat -uri hilton.wsdl  -wv 2.0
> > > -
> > > and I get
> > >
> > > Using AXIS2_HOME: c:\Java\axis2-1.3RC2
> > > Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
> > > Woden[Fatal Error],0:0, WSDL501, Expected a "{
> > > http://www.w3.org/ns/wsdl}description"
> > > element, but found a "{ 
> > > http://www.w3.org/2004/08/wsdl}description"
> > > element instead.
> > > Exception in thread "main"
> > > org.apache.axis2.wsdl.codegen.CodeGenerationException: Error in
> > > parsing WSDL
> > > ...
> > >
> > > But maybe this isn't so weird because the w3c example uses
> > >
> > >  > > xmlns="http://www.w3.org/2004/08/wsdl";
> > > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl
> > > "
> > > xmlns:tns= " http://greath.example.com/2004/wsdl/resSvc.wsdl";
> > > xmlns:ghns = " http://g

Re: wsdl 2.0 questions

2007-08-02 Thread New AxisU

Right.  That makes sense and the soap12 one must be changed as well.

Ok so using the same batch file as before and making those changes (see
below).  I am now back to yesterday's error message about the message
exchange pattern.  Where is this
http://www.w3.org/2004/03/wsdl/in-outcoming from?

>wsdl2java.bat -uri hilton2.wsdl -wv 2.0
Using AXIS2_HOME: C:\Java\axis2-1.3RC2
Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(
CodeGenerationEngine.java:147)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: org.apache.axis2.AxisFault: An unsupported message exchange
pattern (MEP) exists in ID is http://www.w3.org/2004/03/wsdl/in-out
...

-
hilton2.wsdl
-

http://www.w3.org/ns/wsdl";
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>

  
This document describes the GreatH Web service.  Additional
application-level requirements for use of this service --
beyond what WSDL 2.0 is able to describe -- are available
at http://greath.example.com/2004/reservation-documentation.html
  

  
http://www.w3.org/2001/XMLSchema";
targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>

  
  

  
  
  

  

  

  


  

  



http://www.w3.org/2004/03/wsdl/in-out"; >





  

  http://www.w3.org/ns/wsdl/soap";
  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>

http://www.w3.org/2003/05/soap/mep/request-response"/>



  

  

 http://greath.example.com/2004/reservation"/>

  




On 8/2/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
>
> Make sure you're using the correct WSDL namespace.
>
> You're currently using " 
> http://www.w3.org/2004/08/wsdl";
>
> You should be using 
> "http://www.w3.org/ns/wsdl"
>
> Anne
>
> On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
> >
> > Hi Keith,
> >
> > Thanks for looking at this.  I'm reading your message and I'm
> > confused. I am using Axis2 1.3 RC2 which is the latest RC from the url
> > you listed. If you are using the same one, then perhaps I have some kind of
> > pilot error in my wsdl2java usage.  Actually I seem to be heading full speed
> > into reverse because now the error message is
> >
> > Using AXIS2_HOME:
> >
> > 
> > Here's my fancy batch file:
> >
> > echo %AXIS2_HOME%
> > wsdl2java.bat -uri hilton.wsdl  -wv 2.0
> > -
> > and I get
> >
> > Using AXIS2_HOME: c:\Java\axis2-1.3RC2
> > Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
> > Woden[Fatal Error],0:0, WSDL501, Expected a "{
> > http://www.w3.org/ns/wsdl}description"
> > element, but found a "{ 
> > http://www.w3.org/2004/08/wsdl}description"
> > element instead.
> > Exception in thread "main"
> > org.apache.axis2.wsdl.codegen.CodeGenerationException: Error in parsing
> > WSDL
> > ...
> >
> > But maybe this isn't so weird because the w3c example uses
> >
> >  > xmlns="http://www.w3.org/2004/08/wsdl";
> > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl "
> >
> > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> > xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12 "
> > xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
> >
> > and I thought that xmlns should be http://www.w3.org/ns/wsdl
> > but then I am less clear on what other changes should be made does 
> > www.w3.org/2004/08/wsdl/soap12
> > become www.w3.org/ns/wsdl/soap12 ?
> >
> > Could you send me the example wsdl you used successfully?
> >
> > Thanks
> >
> >
> >
> >
> > -
> >
> > Here's the hilton wsdl
> >
> > -
> >
> >  > xmlns="http://www.w3.org/2004/08/wsdl";
> > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl "
> >
> > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> > xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12 "
> > xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
> >
> >   
> > This document describes the GreatH Web service.  Additional
> > a

Re: wsdl 2.0 questions

2007-08-02 Thread Anne Thomas Manes

Make sure you're using the correct WSDL namespace.

You're currently using
"http://www.w3.org/2004/08/wsdl";

You should be using
"http://www.w3.org/ns/wsdl
"

Anne

On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Hi Keith,
>
> Thanks for looking at this.  I'm reading your message and I'm confused. I
> am using Axis2 1.3 RC2 which is the latest RC from the url you listed. If
> you are using the same one, then perhaps I have some kind of pilot error in
> my wsdl2java usage.  Actually I seem to be heading full speed into reverse
> because now the error message is
>
> Using AXIS2_HOME:
>
> 
> Here's my fancy batch file:
>
> echo %AXIS2_HOME%
> wsdl2java.bat -uri hilton.wsdl  -wv 2.0
> -
> and I get
>
> Using AXIS2_HOME: c:\Java\axis2-1.3RC2
> Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
> Woden[Fatal Error],0:0, WSDL501, Expected a "{
> http://www.w3.org/ns/wsdl}description"
> element, but found a "{ 
> http://www.w3.org/2004/08/wsdl}description"
> element instead.
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error in parsing
> WSDL
> ...
>
> But maybe this isn't so weird because the w3c example uses
>
>  xmlns="http://www.w3.org/2004/08/wsdl";
> targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12";
> xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
>
> and I thought that xmlns should be http://www.w3.org/ns/wsdl
> but then I am less clear on what other changes should be made does
> www.w3.org/2004/08/wsdl/soap12 become www.w3.org/ns/wsdl/soap12 ?
>
> Could you send me the example wsdl you used successfully?
>
> Thanks
>
>
>
>
> -
>
> Here's the hilton wsdl
>
> -
>
>  xmlns="http://www.w3.org/2004/08/wsdl";
> targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12";
> xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
>
>   
> This document describes the GreatH Web service.  Additional
> application-level requirements for use of this service --
> beyond what WSDL 2.0 is able to describe -- are available
> at http://greath.example.com/2004/reservation-documentation.html
>   
>
>   
>  xmlns:xs="http://www.w3.org/2001/XMLSchema";
>
> targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd
> "
> xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>
>
>   
>   
> 
>   
>   
>   
> 
>   
>
>   
>
>   
>
> 
>   
>
>   
>
>  element = "ghns:invalidDataError"/>
>
>  pattern=" http://www.w3.org/2004/03/wsdl/in-out"; >
>element="ghns:checkAvailability" />
>element="ghns:checkAvailabilityResponse" />
> 
> 
>
>   
>
>  interface="tns:reservationInterface"
>   type="http://www.w3.org/2004/08/wsdl/soap12 "
>   wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>
>
>
> wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/>
>
>
>wsoap:code="soap:Sender"/>
>
>   
>
>   interface="tns:reservationInterface">
>
>  binding="tns:reservationSOAPBinding"
>address ="http://greath.example.com/2004/reservation"/
> >
>
>   
>
> 
>
>
>
>  **
>
> On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
> >
> > Axis2 1.3 RC2
> >
> > On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote:
> > >
> > > Hi,
> > >
> > > I just tried the wsdl located at
> > > http://www.w3.org/TR/wsdl20-primer/#basics-greath-scenario in the
> > > primer with Axis2-1.3-RC2. It worked without any problems. WSDL 
> > > 2.0support was only available in
> > > Axis2-1.2 prior to this. Please use the latest RC located at
> > > http://ws.apache.org/axis2/download.cgi. The 1.3 release will be out
> > > very soon. You can swtich to that once its released. The 1.3 release
> > > will be very stable.
> > >
> > > Thanks,
> > > Keith.
> > >
> > > On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote:
> > > >
> > > > Hi,
> > > >
> > > > Wats your Axis2 version?
> > > >
> > > > Thanks,
> > > > Keith.
> > > >
> > > > On 8/2/07, New AxisU <[EMAIL PROTECTED] > wrote:
> > >

Re: wsdl 2.0 questions

2007-08-02 Thread New AxisU

Hi Keith,

Thanks for looking at this.  I'm reading your message and I'm confused. I am
using Axis2 1.3 RC2 which is the latest RC from the url you listed. If you
are using the same one, then perhaps I have some kind of pilot error in my
wsdl2java usage.  Actually I seem to be heading full speed into reverse
because now the error message is

Using AXIS2_HOME:


Here's my fancy batch file:

echo %AXIS2_HOME%
wsdl2java.bat -uri hilton.wsdl  -wv 2.0
-
and I get

Using AXIS2_HOME: c:\Java\axis2-1.3RC2
Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
Woden[Fatal Error],0:0, WSDL501, Expected a "{
http://www.w3.org/ns/wsdl}description";  element, but found a "{
http://www.w3.org/2004/08/wsdl}description"; element instead.
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error in parsing WSDL
...

But maybe this isn't so weird because the w3c example uses

http://www.w3.org/2004/08/wsdl";
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>

and I thought that xmlns should be http://www.w3.org/ns/wsdl
but then I am less clear on what other changes should be made does
www.w3.org/2004/08/wsdl/soap12 become www.w3.org/ns/wsdl/soap12?

Could you send me the example wsdl you used successfully?

Thanks




-

Here's the hilton wsdl

-

http://www.w3.org/2004/08/wsdl";
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>

  
This document describes the GreatH Web service.  Additional
application-level requirements for use of this service --
beyond what WSDL 2.0 is able to describe -- are available
at http://greath.example.com/2004/reservation-documentation.html
  

  
http://www.w3.org/2001/XMLSchema";
targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>

  
  

  
  
  

  

  

  


  

  



http://www.w3.org/2004/03/wsdl/in-out"; >





  

  http://www.w3.org/2004/08/wsdl/soap12";
  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>

http://www.w3.org/2003/05/soap/mep/request-response"/>



  

  

 http://greath.example.com/2004/reservation"/>

  




 **
On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Axis2 1.3 RC2
>
> On 8/2/07, keith chapman <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I just tried the wsdl located at
> > http://www.w3.org/TR/wsdl20-primer/#basics-greath-scenario in the primer
> > with Axis2-1.3-RC2. It worked without any problems. WSDL 2.0 support was
> > only available in Axis2-1.2 prior to this. Please use the latest RC
> > located at http://ws.apache.org/axis2/download.cgi. The 1.3 release will
> > be out very soon. You can swtich to that once its released. The 1.3release 
> > will be very stable.
> >
> > Thanks,
> > Keith.
> >
> > On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote:
> > >
> > > Hi,
> > >
> > > Wats your Axis2 version?
> > >
> > > Thanks,
> > > Keith.
> > >
> > > On 8/2/07, New AxisU <[EMAIL PROTECTED] > wrote:
> > > >
> > > > Hi, I am looking at migrating our wsdls from 1.1 to 2.0.  I am using
> > > > axis2 wsdl2java as a way of sanity checking the wsdls.  I am seeing 
> > > > messages
> > > > about "unsupported message exchange patterns".  The wsdl below is much
> > > > simpler than the one I'm using but it gets that same message.  I got it 
> > > > from
> > > > the w3c wsdl 2.0 primer.  Any idea what is wrong with it?
> > > >
> > > > Thanks
> > > >
> > > >
> > > >  > > > xmlns="http://www.w3.org/ns/wsdl";
> > > > targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> > > >
> > > > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> > > > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> > > > xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap12 "
> > > > xmlns:soap=" http://www.w3.org/ns/soap-envelope";>
> > > >
> > > >   
> > > > This document describes the GreatH Web service.  Additional
> > > > application-level requirements for use of this service --
> > > > beyond what WSDL 2.0 is able to describe -- are available
> > > > at http://greath.example.com/2004/reservation-documentation.html
> > > >   
> > > >
> > > >   
> > > >  > > > xmlns:xs="

Re: wsdl 2.0 questions

2007-08-02 Thread New AxisU

Axis2 1.3 RC2

On 8/2/07, keith chapman <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I just tried the wsdl located at
> http://www.w3.org/TR/wsdl20-primer/#basics-greath-scenario in the primer
> with Axis2-1.3-RC2. It worked without any problems. WSDL 2.0 support was
> only available in Axis2-1.2 prior to this. Please use the latest RC
> located at http://ws.apache.org/axis2/download.cgi. The 1.3 release will
> be out very soon. You can swtich to that once its released. The 1.3release 
> will be very stable.
>
> Thanks,
> Keith.
>
> On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote:
> >
> > Hi,
> >
> > Wats your Axis2 version?
> >
> > Thanks,
> > Keith.
> >
> > On 8/2/07, New AxisU <[EMAIL PROTECTED] > wrote:
> > >
> > > Hi, I am looking at migrating our wsdls from 1.1 to 2.0.  I am using
> > > axis2 wsdl2java as a way of sanity checking the wsdls.  I am seeing 
> > > messages
> > > about "unsupported message exchange patterns".  The wsdl below is much
> > > simpler than the one I'm using but it gets that same message.  I got it 
> > > from
> > > the w3c wsdl 2.0 primer.  Any idea what is wrong with it?
> > >
> > > Thanks
> > >
> > >
> > >  > > xmlns="http://www.w3.org/ns/wsdl";
> > > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl
> > > "
> > > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> > > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> > > xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap12 "
> > > xmlns:soap=" http://www.w3.org/ns/soap-envelope";>
> > >
> > >   
> > > This document describes the GreatH Web service.  Additional
> > > application-level requirements for use of this service --
> > > beyond what WSDL 2.0 is able to describe -- are available
> > > at http://greath.example.com/2004/reservation-documentation.html
> > >   
> > >
> > >   
> > >  > > xmlns:xs="XMLSchema.xsd"
> > > targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd
> > > "
> > > xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>
> > >> > type="tCheckAvailability"/>
> > >   
> > > 
> > >   
> > >   
> > >   
> > > 
> > >   
> > >> > type="xs:double"/>
> > >   
> > > 
> > >   
> > >
> > >   
> > >  > > element = "ghns:invalidDataError"/>
> > >  > > pattern=" http://www.w3.org/2004/03/wsdl/in-out " >
> > >  > >   element="ghns:checkAvailability" />
> > >  > >   element="ghns:checkAvailabilityResponse" />
> > > 
> > > 
> > >   
> > >
> > >> >   interface="tns:reservationInterface"
> > >   type=" http://www.w3.org/2004/08/wsdl/soap12 "
> > >   wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>
> > >
> > >  > >   
> > > wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/>
> > >  > >   wsoap:code="soap:Sender"/>
> > >   
> > >
> > >> >interface="tns:reservationInterface">
> > >   > >binding="tns:reservationSOAPBinding"
> > >address 
> > > ="http://greath.example.com/2004/reservation"/
> > > >
> > >   
> > > 
> > >
> >
> >
> >
> > --
> > Keith Chapman
> > WSO2 Inc.
> > Oxygen for Web Services Developers.
> > http://wso2.org/
>
>
>
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/
>

Re: wsdl 2.0 questions

2007-08-01 Thread keith chapman

Hi,

I just tried the wsdl located at
http://www.w3.org/TR/wsdl20-primer/#basics-greath-scenario in the primer
with Axis2-1.3-RC2. It worked without any problems. WSDL 2.0 support was
only available in Axis2-1.2 prior to this. Please use the latest RC located
at http://ws.apache.org/axis2/download.cgi. The 1.3 release will be out very
soon. You can swtich to that once its released. The 1.3 release will be very
stable.

Thanks,
Keith.

On 8/2/07, keith chapman <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Wats your Axis2 version?
>
> Thanks,
> Keith.
>
> On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
> >
> > Hi, I am looking at migrating our wsdls from 1.1 to 2.0.  I am using
> > axis2 wsdl2java as a way of sanity checking the wsdls.  I am seeing messages
> > about "unsupported message exchange patterns".  The wsdl below is much
> > simpler than the one I'm using but it gets that same message.  I got it from
> > the w3c wsdl 2.0 primer.  Any idea what is wrong with it?
> >
> > Thanks
> >
> >
> >  > xmlns="http://www.w3.org/ns/wsdl";
> > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl "
> >
> > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> > xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap12 "
> > xmlns:soap=" http://www.w3.org/ns/soap-envelope";>
> >
> >   
> > This document describes the GreatH Web service.  Additional
> > application-level requirements for use of this service --
> > beyond what WSDL 2.0 is able to describe -- are available
> > at http://greath.example.com/2004/reservation-documentation.html
> >   
> >
> >   
> >  > xmlns:xs="XMLSchema.xsd"
> > targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd
> > "
> > xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>
> >> type="tCheckAvailability"/>
> >   
> > 
> >   
> >   
> >   
> > 
> >   
> >   
> >
> >   
> > 
> >   
> >
> >   
> >  > element = "ghns:invalidDataError"/>
> >  > pattern=" http://www.w3.org/2004/03/wsdl/in-out " >
> >  >   element="ghns:checkAvailability" />
> >  >   element="ghns:checkAvailabilityResponse" />
> > 
> > 
> >   
> >
> >>   interface="tns:reservationInterface"
> >   type=" http://www.w3.org/2004/08/wsdl/soap12 "
> >   wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>
> >
> >  >   
> > wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/>
> >  >   wsoap:code="soap:Sender"/>
> >   
> >
> >>interface="tns:reservationInterface">
> >   >binding="tns:reservationSOAPBinding"
> >address 
> > ="http://greath.example.com/2004/reservation"/
> > >
> >   
> > 
> >
>
>
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/




-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

Re: wsdl 2.0 questions

2007-08-01 Thread keith chapman

Hi,

Wats your Axis2 version?

Thanks,
Keith.

On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Hi, I am looking at migrating our wsdls from 1.1 to 2.0.  I am using axis2
> wsdl2java as a way of sanity checking the wsdls.  I am seeing messages about
> "unsupported message exchange patterns".  The wsdl below is much simpler
> than the one I'm using but it gets that same message.  I got it from the w3c
> wsdl 2.0 primer.  Any idea what is wrong with it?
>
> Thanks
>
>
>  xmlns="http://www.w3.org/ns/wsdl";
> targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap12";
> xmlns:soap=" http://www.w3.org/ns/soap-envelope";>
>
>   
> This document describes the GreatH Web service.  Additional
> application-level requirements for use of this service --
> beyond what WSDL 2.0 is able to describe -- are available
> at http://greath.example.com/2004/reservation-documentation.html
>   
>
>   
>  xmlns:xs="XMLSchema.xsd"
> targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd
> "
> xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>
>   
>   
> 
>   
>   
>   
> 
>   
>   
>   
> 
>   
>
>   
>  element = "ghns:invalidDataError"/>
>  pattern="http://www.w3.org/2004/03/wsdl/in-out " >
>element="ghns:checkAvailability" />
>element="ghns:checkAvailabilityResponse" />
> 
> 
>   
>
>  interface="tns:reservationInterface"
>   type="http://www.w3.org/2004/08/wsdl/soap12 "
>   wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>
>
> wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/
> >
>wsoap:code="soap:Sender"/>
>   
>
>   interface="tns:reservationInterface">
>  binding="tns:reservationSOAPBinding"
>address 
> ="http://greath.example.com/2004/reservation"/
> >
>   
> 
>



-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

wsdl 2.0 questions

2007-08-01 Thread New AxisU

Hi, I am looking at migrating our wsdls from 1.1 to 2.0.  I am using axis2
wsdl2java as a way of sanity checking the wsdls.  I am seeing messages about
"unsupported message exchange patterns".  The wsdl below is much simpler
than the one I'm using but it gets that same message.  I got it from the w3c
wsdl 2.0 primer.  Any idea what is wrong with it?

Thanks


http://www.w3.org/ns/wsdl";
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap12";
xmlns:soap="http://www.w3.org/ns/soap-envelope";>

  
This document describes the GreatH Web service.  Additional
application-level requirements for use of this service --
beyond what WSDL 2.0 is able to describe -- are available
at http://greath.example.com/2004/reservation-documentation.html
  

  
http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>
  
  

  
  
  

  
  
  

  

  

http://www.w3.org/2004/03/wsdl/in-out"; >




  

  http://www.w3.org/2004/08/wsdl/soap12";
  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>
http://www.w3.org/2003/05/soap/mep/request-response"/>

  

  
 http://greath.example.com/2004/reservation"/>

Re: wsdl 2.0 questions

Re: wsdl 2.0 questions

Re: wsdl 2.0 questions

Re: wsdl 2.0 questions

Re: wsdl 2.0 questions

Re: wsdl 2.0 questions

Re: wsdl 2.0 questions

wsdl 2.0 questions

8 matches

Site Navigation

Mail list logo

Footer information