| Author |
Message
|
| bharathi.tech12 |
 Posted: Tue Jul 09, 2013 8:22 am Post subject: SOAP Input parsing error |
 |
|
Voyager
Joined: 14 May 2013
Posts: 93
|
Hi,
 - i am back with issues.
I am using the WSDL file to expose my message flow as a webservice. when i am trying to invoke the same message flow service, i am getting the error like,
The SOAP Input node not able to parse the byte stream to logical tree.
Any one can help me..
This issues is only for this specific wsdl file. i have used other wsdl file from Internet and thats working fine. This wsdl file related to project. I have also validated the wsdl file structre.
I have another question, if we are not able to get the logical tree, is there any other way to read the input byte stream inside the message flow.
Thanks for your supports.
Regards,
Bharathi S. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Jul 09, 2013 8:31 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jul 09, 2013 8:40 am Post subject: Re: SOAP Input parsing error |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bharathi.tech12 wrote: |
Hi,
- i am back with issues.
I am using the WSDL file to expose my message flow as a webservice. when i am trying to invoke the same message flow service, i am getting the error like,
The SOAP Input node not able to parse the byte stream to logical tree. |
That has nothing to do with the WSDL.
| bharathi.tech12 wrote: |
| This issues is only for this specific wsdl file. |
No. The issue is specific to the message you are sending to the SOAPInput node. |
|
| Back to top |
|
|
| bharathi.tech12 |
| Posted: Tue Jul 09, 2013 8:41 am Post subject: |
|
|
Voyager
Joined: 14 May 2013
Posts: 93
|
I have implemented the same message flow in 2 different ways.
1) Message model created from WSDL file and drag & drop the wsdl and selected the message flow exposing as a webservice. In this case i cant invoke the service. That means when i am invoking from test message or from soapui tool, getting the "Source not found/time out" message. But i can see the .bar deployed in the broker EG.
2) Message Set created from WSDL file and drag & drop the wsdl and selected the message flow exposing as a webservice. In this case i can able to invoke the service, but in my trace node or if placing the SOAP Extract after the Soap input, getting the "bite steam not able to parse to logical tree"
The complete error message i got in soapui tool.
I am suspecting this only because of the WSDL file. Because the WSDL contain lot more information and the xsd imported to wsdl from various sub folders.
Thanks for your support.
Regards,
Bharathi S. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jul 09, 2013 9:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bharathi.tech12 wrote: |
I have implemented the same message flow in 2 different ways.
1) Message model created from WSDL file and drag & drop the wsdl and selected the message flow exposing as a webservice. In this case i cant invoke the service. That means when i am invoking from test message or from soapui tool, getting the "Source not found/time out" message. But i can see the .bar deployed in the broker EG. |
You might have to restart broker after deploying a webservice app with a new URL the first time.
| bharathi.tech12 wrote: |
| 2) Message Set created from WSDL file and drag & drop the wsdl and selected the message flow exposing as a webservice. In this case i can able to invoke the service, but in my trace node or if placing the SOAP Extract after the Soap input, getting the "bite steam not able to parse to logical tree" |
Again, that's specific to the specific message you sent.
| bharathi.tech12 wrote: |
| The complete error message i got in soapui tool. |
Again, you were instructed to look at the *broker* log, not the SOAPUI log.
| bharathi.tech12 wrote: |
| I am suspecting this only because of the WSDL file. Because the WSDL contain lot more information and the xsd imported to wsdl from various sub folders. |
Again, it has nothing to do with the WSDL. |
|
| Back to top |
|
|
| bharathi.tech12 |
| Posted: Tue Jul 09, 2013 9:59 am Post subject: |
|
|
Voyager
Joined: 14 May 2013
Posts: 93
|
| mqjeff wrote: |
I have implemented the same message flow in 2 different ways.
1) Message model created from WSDL file and drag & drop the wsdl and selected the message flow exposing as a webservice. In this case i cant invoke the service. That means when i am invoking from test message or from soapui tool, getting the "Source not found/time out" message. But i can see the .bar deployed in the broker EG. |
You might have to restart broker after deploying a webservice app with a new URL the first time.
| Quote: |
| Let me try this one.This new to me. i have tested various other wsdl file message flows without restarting the broker server. |
| bharathi.tech12 wrote: |
| 2) Message Set created from WSDL file and drag & drop the wsdl and selected the message flow exposing as a webservice. In this case i can able to invoke the service, but in my trace node or if placing the SOAP Extract after the Soap input, getting the "bite steam not able to parse to logical tree" |
Again, that's specific to the specific message you sent.
| Quote: |
| If we are using the SOAP UI tool the message will generate from the wsdl. That we knew already. So there is no need to change or create the request message and the message flow also created with the same WSDL.If that so, how this specific message will not work with the message flow, i am not getting. |
| bharathi.tech12 wrote: |
| The complete error message i got in soapui tool. |
Again, you were instructed to look at the *broker* log, not the SOAPUI log.
| bharathi.tech12 wrote: |
| I am suspecting this only because of the WSDL file. Because the WSDL contain lot more information and the xsd imported to wsdl from various sub folders. |
Again, it has nothing to do with the WSDL.[/quote]
| Quote: |
| Your correct we cant modify the supplied wsdl, but my concern is how effectively the message broke will understand all the complected WSDL file. If that so, how to handle those type of WSDLs in Message Broker. |
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jul 09, 2013 10:07 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Quote: |
| my concern is how effectively the message broke will understand all the complected WSDL file. If that so, how to handle those type of WSDLs in Message Broker. |
The lack of understanding is more on the human side than the automation side.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| bharathi.tech12 |
| Posted: Tue Jul 09, 2013 10:17 am Post subject: |
|
|
Voyager
Joined: 14 May 2013
Posts: 93
|
|
| Back to top |
|
|
|
|
