So why am i getting the end body tag?
The xml snippet i'm sending is just for testing. In reality, i also
will not know until runtime the exact structure of the XML message.
Quoting Zden?k Vráblík <[EMAIL PROTECTED]>:
Hi
That is correct,
you can't have envelop. It is XFire business to parse envelop and give
you only message.
I have looked at your service. It is any booking service. Why do you
use MessageBinding?
This should be used only in emergency when JAXB or other xml binding
is not possible to use.
I use it because my xml protocol may have different element names and
I am not able to define this xml element names only at runtime.
Regards,
Zdenek
On Nov 20, 2007 5:27 PM, Nayan Hajratwala <[EMAIL PROTECTED]> wrote:
When I am parsing through the XML inside the service, I get
<orchLayerProcessTicket xmlns="http://com/ticketingServices/ticket/";>
<internalTrackingID>0</internalTrackingID>
<busOrgID>jms_test</busOrgID>
</orchLayerProcessTicket>
but then, I also get a close tag for SOAP-ENV:Body
This causes my XML parsing to fail....
2 questions come up:
* Why is the end BODY tag there?
* Is there anyway to get the WHOLE message, including the soap tags?
Thanks!
Quoting Zden?k Vráblík <[EMAIL PROTECTED]>:
> Hi,
> and you can see
> <orchLayerProcessTicket xmlns="http://com/ticketingServices/ticket/";>
> <internalTrackingID>0</internalTrackingID>
> <busOrgID>jms_test</busOrgID>
> </orchLayerProcessTicket>
>
> or only
>
> <internalTrackingID>0</internalTrackingID>
> <busOrgID>jms_test</busOrgID>
>
> Regards,
> Zdenek
>
> On Nov 20, 2007 2:41 PM, Nayan Hajratwala <[EMAIL PROTECTED]> wrote:
>> Nope, that didn't help ... what exactly does that "use" property mean,
>> anyway? I've searched the docs but can't find a good explanation.
>>
>> FYI -- here is the request as shown from nettool in case there are any
>> glaring errors.
>>
>> ====================
>> POST /caps2/services/AggregatorService?invoke HTTP/1.1
>> SOAPAction: ""
>> User-Agent: Jakarta Commons-HttpClient/3.1
>> Host: localhost:7000
>> Content-Length: 465
>> Content-Type: text/xml; charset=UTF-8
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>>
>> <SOAP-ENV:Envelope
>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>> <SOAP-ENV:Body>
>> <orchLayerProcessTicket xmlns="http://com/ticketingServices/ticket/";>
>> <internalTrackingID>0</internalTrackingID>
>> <busOrgID>jms_test</busOrgID>
>> </orchLayerProcessTicket>
>> </SOAP-ENV:Body>
>> </SOAP-ENV:Envelope>
>> ===================
>>
>>
>>
>> Quoting Zden?k Vráblík <[EMAIL PROTECTED]>:
>>
>> > Hi,
>> > I didn't have this problem.
>> >
>> > Try set property literal. (see previous mail with servicex.xml)
>> >
>> > <property name="style" value="message" />
>> > <property name="use" value="literal" />
>> >
>> > Regards,
>> > Zdenek
>> >
>> > On Nov 19, 2007 6:38 PM, Nayan Hajratwala <[EMAIL PROTECTED]> wrote:
>> >> Folks,
>> >>
>> >> I'm running into the problem described in the JIRA issue:
>> >>
>> >> http://jira.codehaus.org/browse/XFIRE-866
>> >>
>> >> in that I don't have access to my full XML message in my
service method.
>> >>
>> >> i.e -- if i send the XML message:
>> >>
>> >> <A>
>> >> <B>
>> >> <C />
>> >> </B>
>> >> </A>
>> >>
>> >> to my webservice,
>> >>
>> >> in my invoke(XmlStreamReader reader) method, the reader references
>> >> the node <B>, rather than <A>
>> >>
>> >> I've tried using the suggestion as described in the JIRA, by using
>> >> MessageContext, but i ended up with the same result.
>> >>
>> >> Are others experiencing the same problem? How can I get around it?
>> >>
>> >> Thanks!
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
