You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Tim Koop <gr...@timkoop.com> on 2007/03/20 20:39:45 UTC
It worked with Axis 1.4, but not Axis2
Hi everyone. I've got a little problem. I'll try to explain it the
best I can. I got a POJO working with Axis, but it doesn't work quite
right with Axis2.
I'm serving out a Web Service with Tomcat and Axis2 and my client is
PHP. Everything worked find when I used Axis (1.4), but with Axis2, the
return types aren't the same. The WSDL file in Axis2 says the return
types are all complex, but with Axis1 they are simple. Simple types
work with PHP, but PHP chokes on these complex types.
I'm guessing the problem is that PHP (http://php.net/soap) supports SOAP
1.1, 1.2, and WSDL 1.1, which Axis1 did too, but now Axis2 is using WSDL
2.0 by default. Does this sound right to anyone else?
If so, how can I get Axis2 to use WSDL 1.1 ? I've looked through the
documentation, but I can't find anything. If anyone knows a specific
place to look for the answer, I thank you.
I'm thinking this is a setting in server.xml with a messageReceiver, but
I don't know what to set and I can't find this documented anywhere.
Thanks a lot everyone!
--
Tim Koop
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Florian Wachs <fe...@online.de>.
Deepal Jayasinghe schrieb:
> Hi Tim;
>
>
>> Hi everyone. I've got a little problem. I'll try to explain it the
>> best I can. I got a POJO working with Axis, but it doesn't work quite
>> right with Axis2.
>>
>> I'm serving out a Web Service with Tomcat and Axis2 and my client is
>> PHP. Everything worked find when I used Axis (1.4), but with Axis2,
>> the return types aren't the same. The WSDL file in Axis2 says the
>> return types are all complex, but with Axis1 they are simple. Simple
>> types work with PHP, but PHP chokes on these complex types.
>>
>
> This is not clear to me , can you please explain bit more. In Axis2 if
> you have a pojo that with a method that return string or any simple type
> then there wont be any issue with that. And when some one invoke the
> service it will send the correct response for example , let's say your
> service pojo is as follows;
>
> public String echo(String val){
> return val;
> }
>
> then the response will be smt like;
>
> <echoResponse>
> <return>val</return>
> <echoResponse>
>
> In the meantime it will be great if you could provide a way to create
> the issue.
>
>
>> I'm guessing the problem is that PHP (http://php.net/soap) supports
>> SOAP 1.1, 1.2, and WSDL 1.1, which Axis1 did too, but now Axis2 is
>> using WSDL 2.0 by default. Does this sound right to anyone else?
>>
>
> Nope , Axis2 does not use WSDL 2.0 by default.
>
>
>> If so, how can I get Axis2 to use WSDL 1.1 ? I've looked through the
>> documentation, but I can't find anything. If anyone knows a specific
>> place to look for the answer, I thank you.
>>
>> I'm thinking this is a setting in server.xml with a messageReceiver,
>> but I don't know what to set and I can't find this documented anywhere.
>>
>> Thanks a lot everyone!
>>
>>
>> --
>>
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
Hi Tim, I think I´m facing a quite similar problem. Do you mean that,
instead getting the direct type/object, you only get "wrapped types" ?
I´ve already written some questions to the maillist (topic : [Axis2] Is
Axis2 wsdl autogeneration configureable ?). Maybe we are facing the same
problem ??
Thanks Florian
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Tim;
> Hi everyone. I've got a little problem. I'll try to explain it the
> best I can. I got a POJO working with Axis, but it doesn't work quite
> right with Axis2.
>
> I'm serving out a Web Service with Tomcat and Axis2 and my client is
> PHP. Everything worked find when I used Axis (1.4), but with Axis2,
> the return types aren't the same. The WSDL file in Axis2 says the
> return types are all complex, but with Axis1 they are simple. Simple
> types work with PHP, but PHP chokes on these complex types.
This is not clear to me , can you please explain bit more. In Axis2 if
you have a pojo that with a method that return string or any simple type
then there wont be any issue with that. And when some one invoke the
service it will send the correct response for example , let's say your
service pojo is as follows;
public String echo(String val){
return val;
}
then the response will be smt like;
<echoResponse>
<return>val</return>
<echoResponse>
In the meantime it will be great if you could provide a way to create
the issue.
>
> I'm guessing the problem is that PHP (http://php.net/soap) supports
> SOAP 1.1, 1.2, and WSDL 1.1, which Axis1 did too, but now Axis2 is
> using WSDL 2.0 by default. Does this sound right to anyone else?
Nope , Axis2 does not use WSDL 2.0 by default.
>
> If so, how can I get Axis2 to use WSDL 1.1 ? I've looked through the
> documentation, but I can't find anything. If anyone knows a specific
> place to look for the answer, I thank you.
>
> I'm thinking this is a setting in server.xml with a messageReceiver,
> but I don't know what to set and I can't find this documented anywhere.
>
> Thanks a lot everyone!
>
>
> --
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: !!!client-config.wsdd file problem!!!
Posted by Thilina Gunarathne <cs...@gmail.com>.
> I am writing an Axis2 service to invoke a legacy service using Axis.
> Therefore, the Axis2 service will act as a client to the Axis service.
> But the problem is to invoke the Axis service, Axis client must have
> this client-config.wsdd file on current working directory or set as the
> classpath. It's not a problem when I run the Axis client locally, but it
> is when I change the Axis client into a Axis2 service. No matter where I
> put the client-config.wsdd file inside the Tomcat, it cannot be found.
> Does anyone knows how to solve this issue? I really appreciate.
Ok..Let's first get your use case clarified....
Are you trying to call a service implemented in Axis1.x using a Axis2
client. or are you trying to use a Axis client inside a Axis2
service.. If it's the latter one, I would recomend you to use Axis2
it self to call the service.
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Paul Fremantle <pz...@gmail.com>.
Oh I thought it was the other way around - that it was an Axis2 server
that needed doc/lit and a PHP client that can only do rpc/encoded. The
wsf4php supports doc/lit.
If you do need to carry on with rpc/encoded then wsf4php won't help at all!
Paul
On 3/26/07, Davanum Srinivas <da...@gmail.com> wrote:
> Paul,
>
> He needs rpc/encoded :)
>
> -- dims
>
> On 3/26/07, Paul Fremantle <pz...@gmail.com> wrote:
> > Tim
> >
> > By the way there is a PHP client based on Axis2/C. Its' here:
> > http://wso2.org/projects/wsf/php
> >
> > Its still alpha level, so if you want to try it let me know and I'll
> > try and help.
> >
> > Paul
> >
> > On 3/26/07, Tim Koop <gr...@timkoop.com> wrote:
> > > I think my options are:
> > > - find a different PHP client (I'll do this if I have to)
> > > - use Axis1 (I don't really want to do this)
> > > - try to get Axis2 to create a different WSDL file (I'm hoping this is
> > > possible)
> > >
> > > I would like to use a POJO and get Axis to automatically create the
> > > WSDL. Ajith, I think your idea of removing the SOAP 1.2 and HTTP
> > > bindings can't be done when using a POJO, can it?
> > >
> > > Can Axis2 be configured to automatically create a WSDL file (for POJOs)
> > > differently depending on the configuration?
> > >
> > > Thanks.
> > >
> > > Tim Koop
> > >
> > >
> > >
> > >
> > > Ajith Ranabahu wrote:
> > > > Hmm...
> > > > Well Axis2 does not have the capability to do rpc/encoded so
> > > > unfortunately that is not an option. However it seems to me that you
> > > > are seeing three methods because of the three bindings ! (Since we
> > > > have no idea of how the PHP client works this is just a thought)
> > > >
> > > > May be you can try using a modified WSDL with the SOAP 1.2 and HTTP
> > > > bindings removed.
> > > >
> > > > Ajith
> > > >
> > > > On 3/23/07, Tim Koop <gr...@timkoop.com> wrote:
> > > >> Thanks for your analysis, Ajith.
> > > >>
> > > >> To answer your question about the errors I see, I don't exactly see
> > > >> errors; it just looks like it isn't working the way SOAP is supposed to
> > > >> work. I can find these three problems using the PHP client with Axis2.
> > > >> Using it with Axis1 all works normal and good.
> > > >>
> > > >> 1. To get the response, I have to use $client->greeting()->return
> > > >> instead of just $client->greeting().
> > > >>
> > > >> 2. When I list all the functions of this service with
> > > >> $client->__getFunctions(), it lists three of them for some reason (and
> > > >> with a complex return type)
> > > >> greetingResponse greeting()
> > > >> greetingResponse greeting()
> > > >> greetingResponse greeting()
> > > >>
> > > >> instead of the one when I use Axis1.
> > > >> string greeting()
> > > >>
> > > >> 3. If I had a function that required arguments, I would have to call it
> > > >> like this:
> > > >> $client->add(array(param0=>3, param1=>5))
> > > >> instead of the normal way like this with Axis1:
> > > >> $client->add(3, 5)
> > > >>
> > > >>
> > > >> Thank you to everyone who has commented so far, and thanks for any more
> > > >> ideas.
> > > >>
> > > >> (Is there some way to tell Axis2 to use rpc-encoded binding? It sounds
> > > >> like that might solve it.)
> > > >>
> > > >>
> > > >> Tim Koop
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> Ajith Ranabahu wrote:
> > > >> > Hi,
> > > >> > It seems to me that this may be an issue with the PHP client. Here is
> > > >> > what I gather from the information
> > > >> >
> > > >> > 1. The Axis1 WSDL has a rpc-encoded binding
> > > >> > 2. The Axis2 WSDL has doc/lit bindings for both SOAP 1.1 and 1.2
> > > >> > 3. The requests and responses (according to their WSDL's) seem to be
> > > >> > correct in both cases. From the looks of it even the response from
> > > >> > Axis2 server seems to agree with the schema that the WSDL refers to.
> > > >> >
> > > >> > I have a feeling this could be the PHP client that fails to parse the
> > > >> > response (However the SOAP request has been formed correctly which
> > > >> > makes me doubt my conclusion). What kind of error are you seeing ?
> > > >> >
> > > >> > Ajith
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > > >> For additional commands, e-mail: axis-user-help@ws.apache.org
> > > >>
> > > >>
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > Paul Fremantle
> > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> > paul@wso2.com
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Davanum Srinivas <da...@gmail.com>.
Paul,
He needs rpc/encoded :)
-- dims
On 3/26/07, Paul Fremantle <pz...@gmail.com> wrote:
> Tim
>
> By the way there is a PHP client based on Axis2/C. Its' here:
> http://wso2.org/projects/wsf/php
>
> Its still alpha level, so if you want to try it let me know and I'll
> try and help.
>
> Paul
>
> On 3/26/07, Tim Koop <gr...@timkoop.com> wrote:
> > I think my options are:
> > - find a different PHP client (I'll do this if I have to)
> > - use Axis1 (I don't really want to do this)
> > - try to get Axis2 to create a different WSDL file (I'm hoping this is
> > possible)
> >
> > I would like to use a POJO and get Axis to automatically create the
> > WSDL. Ajith, I think your idea of removing the SOAP 1.2 and HTTP
> > bindings can't be done when using a POJO, can it?
> >
> > Can Axis2 be configured to automatically create a WSDL file (for POJOs)
> > differently depending on the configuration?
> >
> > Thanks.
> >
> > Tim Koop
> >
> >
> >
> >
> > Ajith Ranabahu wrote:
> > > Hmm...
> > > Well Axis2 does not have the capability to do rpc/encoded so
> > > unfortunately that is not an option. However it seems to me that you
> > > are seeing three methods because of the three bindings ! (Since we
> > > have no idea of how the PHP client works this is just a thought)
> > >
> > > May be you can try using a modified WSDL with the SOAP 1.2 and HTTP
> > > bindings removed.
> > >
> > > Ajith
> > >
> > > On 3/23/07, Tim Koop <gr...@timkoop.com> wrote:
> > >> Thanks for your analysis, Ajith.
> > >>
> > >> To answer your question about the errors I see, I don't exactly see
> > >> errors; it just looks like it isn't working the way SOAP is supposed to
> > >> work. I can find these three problems using the PHP client with Axis2.
> > >> Using it with Axis1 all works normal and good.
> > >>
> > >> 1. To get the response, I have to use $client->greeting()->return
> > >> instead of just $client->greeting().
> > >>
> > >> 2. When I list all the functions of this service with
> > >> $client->__getFunctions(), it lists three of them for some reason (and
> > >> with a complex return type)
> > >> greetingResponse greeting()
> > >> greetingResponse greeting()
> > >> greetingResponse greeting()
> > >>
> > >> instead of the one when I use Axis1.
> > >> string greeting()
> > >>
> > >> 3. If I had a function that required arguments, I would have to call it
> > >> like this:
> > >> $client->add(array(param0=>3, param1=>5))
> > >> instead of the normal way like this with Axis1:
> > >> $client->add(3, 5)
> > >>
> > >>
> > >> Thank you to everyone who has commented so far, and thanks for any more
> > >> ideas.
> > >>
> > >> (Is there some way to tell Axis2 to use rpc-encoded binding? It sounds
> > >> like that might solve it.)
> > >>
> > >>
> > >> Tim Koop
> > >>
> > >>
> > >>
> > >>
> > >> Ajith Ranabahu wrote:
> > >> > Hi,
> > >> > It seems to me that this may be an issue with the PHP client. Here is
> > >> > what I gather from the information
> > >> >
> > >> > 1. The Axis1 WSDL has a rpc-encoded binding
> > >> > 2. The Axis2 WSDL has doc/lit bindings for both SOAP 1.1 and 1.2
> > >> > 3. The requests and responses (according to their WSDL's) seem to be
> > >> > correct in both cases. From the looks of it even the response from
> > >> > Axis2 server seems to agree with the schema that the WSDL refers to.
> > >> >
> > >> > I have a feeling this could be the PHP client that fails to parse the
> > >> > response (However the SOAP request has been formed correctly which
> > >> > makes me doubt my conclusion). What kind of error are you seeing ?
> > >> >
> > >> > Ajith
> > >> >
> > >> >
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > >> For additional commands, e-mail: axis-user-help@ws.apache.org
> > >>
> > >>
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Paul Fremantle <pz...@gmail.com>.
Tim
By the way there is a PHP client based on Axis2/C. Its' here:
http://wso2.org/projects/wsf/php
Its still alpha level, so if you want to try it let me know and I'll
try and help.
Paul
On 3/26/07, Tim Koop <gr...@timkoop.com> wrote:
> I think my options are:
> - find a different PHP client (I'll do this if I have to)
> - use Axis1 (I don't really want to do this)
> - try to get Axis2 to create a different WSDL file (I'm hoping this is
> possible)
>
> I would like to use a POJO and get Axis to automatically create the
> WSDL. Ajith, I think your idea of removing the SOAP 1.2 and HTTP
> bindings can't be done when using a POJO, can it?
>
> Can Axis2 be configured to automatically create a WSDL file (for POJOs)
> differently depending on the configuration?
>
> Thanks.
>
> Tim Koop
>
>
>
>
> Ajith Ranabahu wrote:
> > Hmm...
> > Well Axis2 does not have the capability to do rpc/encoded so
> > unfortunately that is not an option. However it seems to me that you
> > are seeing three methods because of the three bindings ! (Since we
> > have no idea of how the PHP client works this is just a thought)
> >
> > May be you can try using a modified WSDL with the SOAP 1.2 and HTTP
> > bindings removed.
> >
> > Ajith
> >
> > On 3/23/07, Tim Koop <gr...@timkoop.com> wrote:
> >> Thanks for your analysis, Ajith.
> >>
> >> To answer your question about the errors I see, I don't exactly see
> >> errors; it just looks like it isn't working the way SOAP is supposed to
> >> work. I can find these three problems using the PHP client with Axis2.
> >> Using it with Axis1 all works normal and good.
> >>
> >> 1. To get the response, I have to use $client->greeting()->return
> >> instead of just $client->greeting().
> >>
> >> 2. When I list all the functions of this service with
> >> $client->__getFunctions(), it lists three of them for some reason (and
> >> with a complex return type)
> >> greetingResponse greeting()
> >> greetingResponse greeting()
> >> greetingResponse greeting()
> >>
> >> instead of the one when I use Axis1.
> >> string greeting()
> >>
> >> 3. If I had a function that required arguments, I would have to call it
> >> like this:
> >> $client->add(array(param0=>3, param1=>5))
> >> instead of the normal way like this with Axis1:
> >> $client->add(3, 5)
> >>
> >>
> >> Thank you to everyone who has commented so far, and thanks for any more
> >> ideas.
> >>
> >> (Is there some way to tell Axis2 to use rpc-encoded binding? It sounds
> >> like that might solve it.)
> >>
> >>
> >> Tim Koop
> >>
> >>
> >>
> >>
> >> Ajith Ranabahu wrote:
> >> > Hi,
> >> > It seems to me that this may be an issue with the PHP client. Here is
> >> > what I gather from the information
> >> >
> >> > 1. The Axis1 WSDL has a rpc-encoded binding
> >> > 2. The Axis2 WSDL has doc/lit bindings for both SOAP 1.1 and 1.2
> >> > 3. The requests and responses (according to their WSDL's) seem to be
> >> > correct in both cases. From the looks of it even the response from
> >> > Axis2 server seems to agree with the schema that the WSDL refers to.
> >> >
> >> > I have a feeling this could be the PHP client that fails to parse the
> >> > response (However the SOAP request has been formed correctly which
> >> > makes me doubt my conclusion). What kind of error are you seeing ?
> >> >
> >> > Ajith
> >> >
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Tim Koop <gr...@timkoop.com>.
I think my options are:
- find a different PHP client (I'll do this if I have to)
- use Axis1 (I don't really want to do this)
- try to get Axis2 to create a different WSDL file (I'm hoping this is
possible)
I would like to use a POJO and get Axis to automatically create the
WSDL. Ajith, I think your idea of removing the SOAP 1.2 and HTTP
bindings can't be done when using a POJO, can it?
Can Axis2 be configured to automatically create a WSDL file (for POJOs)
differently depending on the configuration?
Thanks.
Tim Koop
Ajith Ranabahu wrote:
> Hmm...
> Well Axis2 does not have the capability to do rpc/encoded so
> unfortunately that is not an option. However it seems to me that you
> are seeing three methods because of the three bindings ! (Since we
> have no idea of how the PHP client works this is just a thought)
>
> May be you can try using a modified WSDL with the SOAP 1.2 and HTTP
> bindings removed.
>
> Ajith
>
> On 3/23/07, Tim Koop <gr...@timkoop.com> wrote:
>> Thanks for your analysis, Ajith.
>>
>> To answer your question about the errors I see, I don't exactly see
>> errors; it just looks like it isn't working the way SOAP is supposed to
>> work. I can find these three problems using the PHP client with Axis2.
>> Using it with Axis1 all works normal and good.
>>
>> 1. To get the response, I have to use $client->greeting()->return
>> instead of just $client->greeting().
>>
>> 2. When I list all the functions of this service with
>> $client->__getFunctions(), it lists three of them for some reason (and
>> with a complex return type)
>> greetingResponse greeting()
>> greetingResponse greeting()
>> greetingResponse greeting()
>>
>> instead of the one when I use Axis1.
>> string greeting()
>>
>> 3. If I had a function that required arguments, I would have to call it
>> like this:
>> $client->add(array(param0=>3, param1=>5))
>> instead of the normal way like this with Axis1:
>> $client->add(3, 5)
>>
>>
>> Thank you to everyone who has commented so far, and thanks for any more
>> ideas.
>>
>> (Is there some way to tell Axis2 to use rpc-encoded binding? It sounds
>> like that might solve it.)
>>
>>
>> Tim Koop
>>
>>
>>
>>
>> Ajith Ranabahu wrote:
>> > Hi,
>> > It seems to me that this may be an issue with the PHP client. Here is
>> > what I gather from the information
>> >
>> > 1. The Axis1 WSDL has a rpc-encoded binding
>> > 2. The Axis2 WSDL has doc/lit bindings for both SOAP 1.1 and 1.2
>> > 3. The requests and responses (according to their WSDL's) seem to be
>> > correct in both cases. From the looks of it even the response from
>> > Axis2 server seems to agree with the schema that the WSDL refers to.
>> >
>> > I have a feeling this could be the PHP client that fails to parse the
>> > response (However the SOAP request has been formed correctly which
>> > makes me doubt my conclusion). What kind of error are you seeing ?
>> >
>> > Ajith
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hmm...
Well Axis2 does not have the capability to do rpc/encoded so
unfortunately that is not an option. However it seems to me that you
are seeing three methods because of the three bindings ! (Since we
have no idea of how the PHP client works this is just a thought)
May be you can try using a modified WSDL with the SOAP 1.2 and HTTP
bindings removed.
Ajith
On 3/23/07, Tim Koop <gr...@timkoop.com> wrote:
> Thanks for your analysis, Ajith.
>
> To answer your question about the errors I see, I don't exactly see
> errors; it just looks like it isn't working the way SOAP is supposed to
> work. I can find these three problems using the PHP client with Axis2.
> Using it with Axis1 all works normal and good.
>
> 1. To get the response, I have to use $client->greeting()->return
> instead of just $client->greeting().
>
> 2. When I list all the functions of this service with
> $client->__getFunctions(), it lists three of them for some reason (and
> with a complex return type)
> greetingResponse greeting()
> greetingResponse greeting()
> greetingResponse greeting()
>
> instead of the one when I use Axis1.
> string greeting()
>
> 3. If I had a function that required arguments, I would have to call it
> like this:
> $client->add(array(param0=>3, param1=>5))
> instead of the normal way like this with Axis1:
> $client->add(3, 5)
>
>
> Thank you to everyone who has commented so far, and thanks for any more
> ideas.
>
> (Is there some way to tell Axis2 to use rpc-encoded binding? It sounds
> like that might solve it.)
>
>
> Tim Koop
>
>
>
>
> Ajith Ranabahu wrote:
> > Hi,
> > It seems to me that this may be an issue with the PHP client. Here is
> > what I gather from the information
> >
> > 1. The Axis1 WSDL has a rpc-encoded binding
> > 2. The Axis2 WSDL has doc/lit bindings for both SOAP 1.1 and 1.2
> > 3. The requests and responses (according to their WSDL's) seem to be
> > correct in both cases. From the looks of it even the response from
> > Axis2 server seems to agree with the schema that the WSDL refers to.
> >
> > I have a feeling this could be the PHP client that fails to parse the
> > response (However the SOAP request has been formed correctly which
> > makes me doubt my conclusion). What kind of error are you seeing ?
> >
> > Ajith
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Amila Suriarachchi <am...@gmail.com>.
hi,
your two responses like this
<soapenv:Body><ns1:greetingResponse
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="http://DefaultNamespace"><greetingReturn
xsi:type="xsd:string">Hello</greetingReturn></ns1:greetingResponse></soapenv:Body>
<ns:greetingResponse
xmlns:ns="http://ws.apache.org/axis2/xsd"><ns:return>Hello</ns:return></ns:greetingResponse>
1. To get the response, I have to use $client->greeting()->return
> instead of just $client->greeting().
in both cases response message have a similar xml structure with different
names. So it is difficult to realy answer your question without having a
knowledge about the PHP client. I depends on how php client parse the
response.
2. When I list all the functions of this service with
> $client->__getFunctions(), it lists three of them for some reason (and
> with a complex return type)
> greetingResponse greeting()
> greetingResponse greeting()
> greetingResponse greeting()
>
> instead of the one when I use Axis1.
> string greeting()
>
> 3. If I had a function that required arguments, I would have to call it
> like this:
> $client->add(array(param0=>3, param1=>5))
> instead of the normal way like this with Axis1:
> $client->add(3, 5)
Again it depends on how PHP client work on these things.
Thank you to everyone who has commented so far, and thanks for any more
> ideas.
>
> (Is there some way to tell Axis2 to use rpc-encoded binding? It sounds
> like that might solve it.)
>
>
> Tim Koop
>
>
>
>
> Ajith Ranabahu wrote:
> > Hi,
> > It seems to me that this may be an issue with the PHP client. Here is
> > what I gather from the information
> >
> > 1. The Axis1 WSDL has a rpc-encoded binding
> > 2. The Axis2 WSDL has doc/lit bindings for both SOAP 1.1 and 1.2
> > 3. The requests and responses (according to their WSDL's) seem to be
> > correct in both cases. From the looks of it even the response from
> > Axis2 server seems to agree with the schema that the WSDL refers to.
> >
> > I have a feeling this could be the PHP client that fails to parse the
> > response (However the SOAP request has been formed correctly which
> > makes me doubt my conclusion). What kind of error are you seeing ?
> >
> > Ajith
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Amila Suriarachchi,
WSO2 Inc.
Re: It worked with Axis 1.4, but not Axis2
Posted by Tim Koop <gr...@timkoop.com>.
Thanks for your analysis, Ajith.
To answer your question about the errors I see, I don't exactly see
errors; it just looks like it isn't working the way SOAP is supposed to
work. I can find these three problems using the PHP client with Axis2.
Using it with Axis1 all works normal and good.
1. To get the response, I have to use $client->greeting()->return
instead of just $client->greeting().
2. When I list all the functions of this service with
$client->__getFunctions(), it lists three of them for some reason (and
with a complex return type)
greetingResponse greeting()
greetingResponse greeting()
greetingResponse greeting()
instead of the one when I use Axis1.
string greeting()
3. If I had a function that required arguments, I would have to call it
like this:
$client->add(array(param0=>3, param1=>5))
instead of the normal way like this with Axis1:
$client->add(3, 5)
Thank you to everyone who has commented so far, and thanks for any more
ideas.
(Is there some way to tell Axis2 to use rpc-encoded binding? It sounds
like that might solve it.)
Tim Koop
Ajith Ranabahu wrote:
> Hi,
> It seems to me that this may be an issue with the PHP client. Here is
> what I gather from the information
>
> 1. The Axis1 WSDL has a rpc-encoded binding
> 2. The Axis2 WSDL has doc/lit bindings for both SOAP 1.1 and 1.2
> 3. The requests and responses (according to their WSDL's) seem to be
> correct in both cases. From the looks of it even the response from
> Axis2 server seems to agree with the schema that the WSDL refers to.
>
> I have a feeling this could be the PHP client that fails to parse the
> response (However the SOAP request has been formed correctly which
> makes me doubt my conclusion). What kind of error are you seeing ?
>
> Ajith
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
It seems to me that this may be an issue with the PHP client. Here is
what I gather from the information
1. The Axis1 WSDL has a rpc-encoded binding
2. The Axis2 WSDL has doc/lit bindings for both SOAP 1.1 and 1.2
3. The requests and responses (according to their WSDL's) seem to be
correct in both cases. From the looks of it even the response from
Axis2 server seems to agree with the schema that the WSDL refers to.
I have a feeling this could be the PHP client that fails to parse the
response (However the SOAP request has been formed correctly which
makes me doubt my conclusion). What kind of error are you seeing ?
Ajith
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Tim Koop <gr...@timkoop.com>.
OK. Here goes:
This is the wsdl from Axis 1:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://localhost:8080/axis/Greeting.jws" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://calebdev.om.org:8080/axis/Greeting.jws" xmlns:intf="http://calebdev.om.org:8080/axis/Greeting.jws" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<!--WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)-->
<wsdl:message name="greetingResponse">
<wsdl:part name="greetingReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="greetingRequest">
</wsdl:message>
<wsdl:portType name="Greeting">
<wsdl:operation name="greeting">
<wsdl:input message="impl:greetingRequest" name="greetingRequest"/>
<wsdl:output message="impl:greetingResponse" name="greetingResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="GreetingSoapBinding" type="impl:Greeting">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="greeting">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="greetingRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://DefaultNamespace" use="encoded"/>
</wsdl:input>
<wsdl:output name="greetingResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/axis/Greeting.jws" use="encoded"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="GreetingService">
<wsdl:port binding="impl:GreetingSoapBinding" name="Greeting">
<wsdlsoap:address location="http://localhost:8080/axis/Greeting.jws"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
This is the tcp request: (port numbers have been changed to get tcpmon
to work)
POST /axis/Greeting.jws HTTP/1.1
Host: 127.0.0.1:8880
Connection: Keep-Alive
User-Agent: PHP-SOAP/5.1.6
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Content-Length: 445
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns1="http://DefaultNamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><ns1:greeting/></SOAP-ENV:Body></SOAP-ENV:Envelope>
And this is the response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=29D92B6BE075163CA8617AFEBAA57825; Path=/axis
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Fri, 23 Mar 2007 16:29:58 GMT
1d4
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:greetingResponse
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="http://DefaultNamespace"><greetingReturn
xsi:type="xsd:string">Hello</greetingReturn></ns1:greetingResponse></soapenv:Body></soapenv:Envelope>
0
This is the wsdl from Axis2:
<wsdl:definitions xmlns:axis2="http://ws.apache.org/axis2" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns0="http://ws.apache.org/axis2/xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" targetNamespace="http://ws.apache.org/axis2"><wsdl:documentation>Greeting</wsdl:documentation><wsdl:types><xs:schema xmlns:ns="http://ws.apache.org/axis2/xsd" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://ws.apache.org/axis2/xsd">
<xs:element name="greetingResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="return" nillable="true" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema></wsdl:types><wsdl:message name="greetingMessage" /><wsdl:message name="greetingResponse"><wsdl:part name="part1" element="ns0:greetingResponse" /></wsdl:message><wsdl:portType name="GreetingPortType"><wsdl:operation name="greeting"><wsdl:input xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" message="axis2:greetingMessage" wsaw:Action="urn:greeting" /><wsdl:output message="axis2:greetingResponse" /></wsdl:operation></wsdl:portType><wsdl:binding name="GreetingSOAP11Binding" type="axis2:GreetingPortType"><soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /><wsdl:operation name="greeting"><soap:operation soapAction="urn:greeting" style="document" /><wsdl:input><soap:body use="literal" /></wsdl:input><wsdl:output><soap:body use="literal" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:binding name="GreetingSOAP12Binding" type="axis2:GreetingPortType"><soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /><wsdl:operation name="greeting"><soap12:operation soapAction="urn:greeting" style="document" /><wsdl:input><soap12:body use="literal" /></wsdl:input><wsdl:output><soap12:body use="literal" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:binding name="GreetingHttpBinding" type="axis2:GreetingPortType"><http:binding verb="POST" /><wsdl:operation name="greeting"><http:operation location="greeting" /><wsdl:input><mime:content type="text/xml" /></wsdl:input><wsdl:output><mime:content type="text/xml" /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:service name="Greeting"><wsdl:port name="GreetingSOAP11port_http" binding="axis2:GreetingSOAP11Binding"><soap:address location="http://localhost:8080/axis2/services/Greeting" /></wsdl:port><wsdl:port name="GreetingSOAP12port_http" binding="axis2:GreetingSOAP12Binding"><soap12:address location="http://localhost:8080/axis2/services/Greeting" /></wsdl:port><wsdl:port name="GreetingHttpport1" binding="axis2:GreetingHttpBinding"><http:address location="http://localhost:8080/axis2/rest/Greeting" /></wsdl:port></wsdl:service></wsdl:definitions>
This is the request:
POST /axis2/services/Greeting HTTP/1.1
Host: 127.0.0.1:8880
Connection: Keep-Alive
User-Agent: PHP-SOAP/5.1.6
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:greeting"
Content-Length: 154
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body/></SOAP-ENV:Envelope>
And this is the response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Fri, 23 Mar 2007 16:29:58 GMT
125
<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header
/><soapenv:Body><ns:greetingResponse
xmlns:ns="http://ws.apache.org/axis2/xsd"><ns:return>Hello</ns:return></ns:greetingResponse></soapenv:Body></soapenv:Envelope>
0
I hope this tells you something, Amila, or anyone else, because it took
me a bit of work to get this.
Thanks for all your continuing ideas and help.
Tim Koop
Amila Suriarachchi wrote:
> Basically you have two senarios
> PHP Client ----- Axis1 server
> PHP Client ----- Axis2 Server
>
> Can you use the tcp mon and tell me the responses you get in each case?
> Can you send your two wsdls as well?
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Amila Suriarachchi <am...@gmail.com>.
Basically you have two senarios
PHP Client ----- Axis1 server
PHP Client ----- Axis2 Server
Can you use the tcp mon and tell me the responses you get in each case?
Can you send your two wsdls as well?
On 3/23/07, Tim Koop <gr...@timkoop.com> wrote:
>
> Thanks Sanjiva.
>
> Yes, I think we can use the nightlies for a few weeks.
>
> Can you or anyone else tell me how to configure Axis2 to unwrap the
> response messages? It is something in /WEB-INF/conf/axis2.xml?
>
> Thanks a lot!
>
> Tim Koop
>
>
>
>
> Sanjiva Weerawarana wrote:
> > Tim Koop wrote:
> >> Thanks Anne!
> >>
> >> According to http://www.apachenews.org/archives/000908.html,
> >> unwrapping Web service requests works but "unwrapping of response
> >> messages (coming in 1.2)" doesn't work yet.
> >>
> >> Are my only choices to choose Axis1.4 over Axis2 or to wait for 1.2?
> >
> > This feature is supported in the current nightlies and 1.2 is due out
> > in a few weeks. Is that not an option for you?
> >
> > Sanjiva.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Amila Suriarachchi,
WSO2 Inc.
Re: It worked with Axis 1.4, but not Axis2
Posted by Tim Koop <gr...@timkoop.com>.
Thanks Sanjiva.
Yes, I think we can use the nightlies for a few weeks.
Can you or anyone else tell me how to configure Axis2 to unwrap the
response messages? It is something in /WEB-INF/conf/axis2.xml?
Thanks a lot!
Tim Koop
Sanjiva Weerawarana wrote:
> Tim Koop wrote:
>> Thanks Anne!
>>
>> According to http://www.apachenews.org/archives/000908.html,
>> unwrapping Web service requests works but "unwrapping of response
>> messages (coming in 1.2)" doesn't work yet.
>>
>> Are my only choices to choose Axis1.4 over Axis2 or to wait for 1.2?
>
> This feature is supported in the current nightlies and 1.2 is due out
> in a few weeks. Is that not an option for you?
>
> Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Tim Koop wrote:
> Thanks Anne!
>
> According to http://www.apachenews.org/archives/000908.html, unwrapping
> Web service requests works but "unwrapping of response messages (coming
> in 1.2)" doesn't work yet.
>
> Are my only choices to choose Axis1.4 over Axis2 or to wait for 1.2?
This feature is supported in the current nightlies and 1.2 is due out in a
few weeks. Is that not an option for you?
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
!!!client-config.wsdd file problem!!!
Posted by Jipu Jiang <j....@nesc.gla.ac.uk>.
Dear all,
I am writing an Axis2 service to invoke a legacy service using Axis.
Therefore, the Axis2 service will act as a client to the Axis service.
But the problem is to invoke the Axis service, Axis client must have
this client-config.wsdd file on current working directory or set as the
classpath. It's not a problem when I run the Axis client locally, but it
is when I change the Axis client into a Axis2 service. No matter where I
put the client-config.wsdd file inside the Tomcat, it cannot be found.
Does anyone knows how to solve this issue? I really appreciate.
Thanks,
Jipu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Tim Koop <gr...@timkoop.com>.
Thanks Anne!
According to http://www.apachenews.org/archives/000908.html, unwrapping
Web service requests works but "unwrapping of response messages (coming
in 1.2)" doesn't work yet.
Are my only choices to choose Axis1.4 over Axis2 or to wait for 1.2?
Thanks again to anyone who can shed some light on this for me.
Tim Koop
Anne Thomas Manes wrote:
> You're looking for the "unwrapping" option.
>
> On 3/21/07, Tim Koop <gr...@timkoop.com> wrote:
>> Thanks Anne and Deepal for your responses, and thanks to everyone else
>> for reading and considering this.
>>
>> I would love to give more details. Here goes:
>>
>> With Axis 1.4, a plain old Java object like this:
>>
>> public class Greeting {
>> public String greeting() {
>> return "Hello";
>> }
>> }
>>
>> would produce a WSDL that contains these lines:
>>
>> <wsdl:message name="greetingResponse">
>> <wsdl:part name="greetingReturn" type="xsd:string"/>
>> </wsdl:message>
>>
>> And to display this with PHP would be done like this:
>>
>> <? $client = new
>> SoapClient("http://localhost:8080/axis/Greeting.jws?wsdl"); ?>
>> <? echo $client->greeting() ?>
>>
>> This all works very nicely, and thank you to the makers of Axis for a
>> fine piece of software. :)
>>
>>
>>
>> Now in Axis2, the very same pojo (compiled and with a services.xml file)
>> would produce a WSDL file that contains these lines:
>>
>> <xs:element name="greetingResponse">
>> <xs:complexType>
>> <xs:sequence>
>> <xs:element name="return" nillable="true" type="xs:string"/>
>> </xs:sequence>
>> </xs:complexType>
>> </xs:element>
>>
>> <wsdl:message name="greetingResponse">
>> <wsdl:part name="part1" element="ns0:greetingResponse"/>
>> </wsdl:message>
>>
>> And the PHP code now has to look like this:
>>
>> <? $client = new
>> SoapClient("http://localhost:8080/axis2/services/Greeting?wsdl"); ?>
>> <? echo $client->greeting()->return ?>
>>
>> Now admittedly, this php code isn't too much worse; there is just that
>> extra "->return" part there. But there are 2 other problems also.
>> Firstly, I don't even know how to pass in arguments using PHP and Axis2
>> (note that this example doesn't require any). Everything I've tried
>> just throws errors, but it works as expected using Axis1.4. The other
>> thing is that when I list all the functions available in this web
>> service using PHP, the Axis1.4 WSDL tells me there is one function with
>> a return type of "string" (of course), but the Axis2 WSDL tells me there
>> are three identical functions that each return a type of
>> "greetingResonse".
>>
>> Any ideas at all are very welcome. I'm new to Axis and Soap, but I've
>> already searched through all the documentation I can find. Hopefully
>> someone here will have an answer or some thoughts that lead to an
>> answer.
>>
>> Thank you all very much.
>>
>> I suspect this is the same problem that Florian is facing.
>>
>> Tim Koop
>>
>>
>>
>>
>> Tim Koop wrote:
>> > Hi everyone. I've got a little problem. I'll try to explain it the
>> > best I can. I got a POJO working with Axis, but it doesn't work quite
>> > right with Axis2.
>> >
>> > I'm serving out a Web Service with Tomcat and Axis2 and my client is
>> > PHP. Everything worked find when I used Axis (1.4), but with Axis2,
>> > the return types aren't the same. The WSDL file in Axis2 says the
>> > return types are all complex, but with Axis1 they are simple. Simple
>> > types work with PHP, but PHP chokes on these complex types.
>> >
>> > I'm guessing the problem is that PHP (http://php.net/soap) supports
>> > SOAP 1.1, 1.2, and WSDL 1.1, which Axis1 did too, but now Axis2 is
>> > using WSDL 2.0 by default. Does this sound right to anyone else?
>> >
>> > If so, how can I get Axis2 to use WSDL 1.1 ? I've looked through the
>> > documentation, but I can't find anything. If anyone knows a specific
>> > place to look for the answer, I thank you.
>> >
>> > I'm thinking this is a setting in server.xml with a messageReceiver,
>> > but I don't know what to set and I can't find this documented
>> anywhere.
>> >
>> > Thanks a lot everyone!
>> >
>> >
>> > --
>> > Tim Koop
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Anne Thomas Manes <at...@gmail.com>.
You're looking for the "unwrapping" option.
On 3/21/07, Tim Koop <gr...@timkoop.com> wrote:
> Thanks Anne and Deepal for your responses, and thanks to everyone else
> for reading and considering this.
>
> I would love to give more details. Here goes:
>
> With Axis 1.4, a plain old Java object like this:
>
> public class Greeting {
> public String greeting() {
> return "Hello";
> }
> }
>
> would produce a WSDL that contains these lines:
>
> <wsdl:message name="greetingResponse">
> <wsdl:part name="greetingReturn" type="xsd:string"/>
> </wsdl:message>
>
> And to display this with PHP would be done like this:
>
> <? $client = new
> SoapClient("http://localhost:8080/axis/Greeting.jws?wsdl"); ?>
> <? echo $client->greeting() ?>
>
> This all works very nicely, and thank you to the makers of Axis for a
> fine piece of software. :)
>
>
>
> Now in Axis2, the very same pojo (compiled and with a services.xml file)
> would produce a WSDL file that contains these lines:
>
> <xs:element name="greetingResponse">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="return" nillable="true" type="xs:string"/>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
>
> <wsdl:message name="greetingResponse">
> <wsdl:part name="part1" element="ns0:greetingResponse"/>
> </wsdl:message>
>
> And the PHP code now has to look like this:
>
> <? $client = new
> SoapClient("http://localhost:8080/axis2/services/Greeting?wsdl"); ?>
> <? echo $client->greeting()->return ?>
>
> Now admittedly, this php code isn't too much worse; there is just that
> extra "->return" part there. But there are 2 other problems also.
> Firstly, I don't even know how to pass in arguments using PHP and Axis2
> (note that this example doesn't require any). Everything I've tried
> just throws errors, but it works as expected using Axis1.4. The other
> thing is that when I list all the functions available in this web
> service using PHP, the Axis1.4 WSDL tells me there is one function with
> a return type of "string" (of course), but the Axis2 WSDL tells me there
> are three identical functions that each return a type of "greetingResonse".
>
> Any ideas at all are very welcome. I'm new to Axis and Soap, but I've
> already searched through all the documentation I can find. Hopefully
> someone here will have an answer or some thoughts that lead to an answer.
>
> Thank you all very much.
>
> I suspect this is the same problem that Florian is facing.
>
> Tim Koop
>
>
>
>
> Tim Koop wrote:
> > Hi everyone. I've got a little problem. I'll try to explain it the
> > best I can. I got a POJO working with Axis, but it doesn't work quite
> > right with Axis2.
> >
> > I'm serving out a Web Service with Tomcat and Axis2 and my client is
> > PHP. Everything worked find when I used Axis (1.4), but with Axis2,
> > the return types aren't the same. The WSDL file in Axis2 says the
> > return types are all complex, but with Axis1 they are simple. Simple
> > types work with PHP, but PHP chokes on these complex types.
> >
> > I'm guessing the problem is that PHP (http://php.net/soap) supports
> > SOAP 1.1, 1.2, and WSDL 1.1, which Axis1 did too, but now Axis2 is
> > using WSDL 2.0 by default. Does this sound right to anyone else?
> >
> > If so, how can I get Axis2 to use WSDL 1.1 ? I've looked through the
> > documentation, but I can't find anything. If anyone knows a specific
> > place to look for the answer, I thank you.
> >
> > I'm thinking this is a setting in server.xml with a messageReceiver,
> > but I don't know what to set and I can't find this documented anywhere.
> >
> > Thanks a lot everyone!
> >
> >
> > --
> > Tim Koop
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Tim Koop <gr...@timkoop.com>.
Thanks Anne and Deepal for your responses, and thanks to everyone else
for reading and considering this.
I would love to give more details. Here goes:
With Axis 1.4, a plain old Java object like this:
public class Greeting {
public String greeting() {
return "Hello";
}
}
would produce a WSDL that contains these lines:
<wsdl:message name="greetingResponse">
<wsdl:part name="greetingReturn" type="xsd:string"/>
</wsdl:message>
And to display this with PHP would be done like this:
<? $client = new
SoapClient("http://localhost:8080/axis/Greeting.jws?wsdl"); ?>
<? echo $client->greeting() ?>
This all works very nicely, and thank you to the makers of Axis for a
fine piece of software. :)
Now in Axis2, the very same pojo (compiled and with a services.xml file)
would produce a WSDL file that contains these lines:
<xs:element name="greetingResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="return" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<wsdl:message name="greetingResponse">
<wsdl:part name="part1" element="ns0:greetingResponse"/>
</wsdl:message>
And the PHP code now has to look like this:
<? $client = new
SoapClient("http://localhost:8080/axis2/services/Greeting?wsdl"); ?>
<? echo $client->greeting()->return ?>
Now admittedly, this php code isn't too much worse; there is just that
extra "->return" part there. But there are 2 other problems also.
Firstly, I don't even know how to pass in arguments using PHP and Axis2
(note that this example doesn't require any). Everything I've tried
just throws errors, but it works as expected using Axis1.4. The other
thing is that when I list all the functions available in this web
service using PHP, the Axis1.4 WSDL tells me there is one function with
a return type of "string" (of course), but the Axis2 WSDL tells me there
are three identical functions that each return a type of "greetingResonse".
Any ideas at all are very welcome. I'm new to Axis and Soap, but I've
already searched through all the documentation I can find. Hopefully
someone here will have an answer or some thoughts that lead to an answer.
Thank you all very much.
I suspect this is the same problem that Florian is facing.
Tim Koop
Tim Koop wrote:
> Hi everyone. I've got a little problem. I'll try to explain it the
> best I can. I got a POJO working with Axis, but it doesn't work quite
> right with Axis2.
>
> I'm serving out a Web Service with Tomcat and Axis2 and my client is
> PHP. Everything worked find when I used Axis (1.4), but with Axis2,
> the return types aren't the same. The WSDL file in Axis2 says the
> return types are all complex, but with Axis1 they are simple. Simple
> types work with PHP, but PHP chokes on these complex types.
>
> I'm guessing the problem is that PHP (http://php.net/soap) supports
> SOAP 1.1, 1.2, and WSDL 1.1, which Axis1 did too, but now Axis2 is
> using WSDL 2.0 by default. Does this sound right to anyone else?
>
> If so, how can I get Axis2 to use WSDL 1.1 ? I've looked through the
> documentation, but I can't find anything. If anyone knows a specific
> place to look for the answer, I thank you.
>
> I'm thinking this is a setting in server.xml with a messageReceiver,
> but I don't know what to set and I can't find this documented anywhere.
>
> Thanks a lot everyone!
>
>
> --
> Tim Koop
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: It worked with Axis 1.4, but not Axis2
Posted by Anne Thomas Manes <at...@gmail.com>.
Axis2 does not use WSDL 2.0 by default. That is not your problem.
Please provide more information and we will try to help you.
Anne
On 3/20/07, Tim Koop <gr...@timkoop.com> wrote:
> Hi everyone. I've got a little problem. I'll try to explain it the
> best I can. I got a POJO working with Axis, but it doesn't work quite
> right with Axis2.
>
> I'm serving out a Web Service with Tomcat and Axis2 and my client is
> PHP. Everything worked find when I used Axis (1.4), but with Axis2, the
> return types aren't the same. The WSDL file in Axis2 says the return
> types are all complex, but with Axis1 they are simple. Simple types
> work with PHP, but PHP chokes on these complex types.
>
> I'm guessing the problem is that PHP (http://php.net/soap) supports SOAP
> 1.1, 1.2, and WSDL 1.1, which Axis1 did too, but now Axis2 is using WSDL
> 2.0 by default. Does this sound right to anyone else?
>
> If so, how can I get Axis2 to use WSDL 1.1 ? I've looked through the
> documentation, but I can't find anything. If anyone knows a specific
> place to look for the answer, I thank you.
>
> I'm thinking this is a setting in server.xml with a messageReceiver, but
> I don't know what to set and I can't find this documented anywhere.
>
> Thanks a lot everyone!
>
>
> --
> Tim Koop
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org