You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by cheff <st...@gmail.com> on 2007/02/13 03:45:22 UTC
servicemix jsr181
I didn't try the new version but why does a http+jsr181 sonsumer response in
in-out MEP always have an out element? Thegenerated JAXB response object is
correct but the serialization seems not to be o.k.
I hope this is fixed in 3.1
Examples:
<ServiceResponse>
<out>
<message>opsala</message>
</out>
</ServiceResponse>
--
View this message in context: http://www.nabble.com/servicemix-jsr181-tf3218294s12049.html#a8937658
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: servicemix jsr181
Posted by Guillaume Nodet <gn...@gmail.com>.
If you use jaxb2 wsdl2java, you need to make sure you have
the @WebService annotation on your service implementation
or force these informations on the endpoint.
On 2/13/07, cheff <st...@gmail.com> wrote:
>
> 10x for your response.
> You were right. I've done it. The request is now as I've expected but the
> response is for me not correct. At least it is defferent if, I deploy the
> same service with XFire and JAXB binding. Here an example:
>
> <submitRequest>
> <Message>haha</Message>
> <submitRequest>
>
> I expect, as defined in the service response type
> <submitResponse>
> <Message>ahah</Message>
> </submitResponse>
>
> but I receive
>
> <submitout>
> <message>ahah</message>
> </submitout>
>
> The type in the wsdl is defined like:
> <xsd:element name="submitResponse">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="Message" type="xsd:string"></xsd:element>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
>
>
>
>
> gnodet wrote:
> >
> > You need to specify the style="document" on the jsr181 endpoint.
> >
> > On 2/13/07, cheff <st...@gmail.com> wrote:
> >>
> >> I didn't try the new version but why does a http+jsr181 sonsumer response
> >> in
> >> in-out MEP always have an out element? Thegenerated JAXB response object
> >> is
> >> correct but the serialization seems not to be o.k.
> >> I hope this is fixed in 3.1
> >>
> >> Examples:
> >> <ServiceResponse>
> >> <out>
> >> <message>opsala</message>
> >> </out>
> >> </ServiceResponse>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/servicemix-jsr181-tf3218294s12049.html#a8937658
> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Architect, LogicBlaze (http://www.logicblaze.com/)
> > Blog: http://gnodet.blogspot.com/
> >
> >
>
> --
> View this message in context: http://www.nabble.com/servicemix-jsr181-tf3218294s12049.html#a8953540
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: servicemix jsr181
Posted by cheff <st...@gmail.com>.
10x for your response.
You were right. I've done it. The request is now as I've expected but the
response is for me not correct. At least it is defferent if, I deploy the
same service with XFire and JAXB binding. Here an example:
<submitRequest>
<Message>haha</Message>
<submitRequest>
I expect, as defined in the service response type
<submitResponse>
<Message>ahah</Message>
</submitResponse>
but I receive
<submitout>
<message>ahah</message>
</submitout>
The type in the wsdl is defined like:
<xsd:element name="submitResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Message" type="xsd:string"></xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
gnodet wrote:
>
> You need to specify the style="document" on the jsr181 endpoint.
>
> On 2/13/07, cheff <st...@gmail.com> wrote:
>>
>> I didn't try the new version but why does a http+jsr181 sonsumer response
>> in
>> in-out MEP always have an out element? Thegenerated JAXB response object
>> is
>> correct but the serialization seems not to be o.k.
>> I hope this is fixed in 3.1
>>
>> Examples:
>> <ServiceResponse>
>> <out>
>> <message>opsala</message>
>> </out>
>> </ServiceResponse>
>> --
>> View this message in context:
>> http://www.nabble.com/servicemix-jsr181-tf3218294s12049.html#a8937658
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>
>
--
View this message in context: http://www.nabble.com/servicemix-jsr181-tf3218294s12049.html#a8953540
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: servicemix jsr181
Posted by Guillaume Nodet <gn...@gmail.com>.
You need to specify the style="document" on the jsr181 endpoint.
On 2/13/07, cheff <st...@gmail.com> wrote:
>
> I didn't try the new version but why does a http+jsr181 sonsumer response in
> in-out MEP always have an out element? Thegenerated JAXB response object is
> correct but the serialization seems not to be o.k.
> I hope this is fixed in 3.1
>
> Examples:
> <ServiceResponse>
> <out>
> <message>opsala</message>
> </out>
> </ServiceResponse>
> --
> View this message in context: http://www.nabble.com/servicemix-jsr181-tf3218294s12049.html#a8937658
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/