| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| extract/envelope nodes and long strings |
« View previous topic :: View next topic » |
| Author |
Message
|
| fde |
 Posted: Wed Aug 27, 2008 6:43 am Post subject: extract/envelope nodes and long strings |
 |
|
Acolyte
Joined: 05 Jul 2007
Posts: 65
|
Hello,
I just built a pdf wrapper webservice, which calls an existing webservice, which produces a base64 encoded string, which is the representation of the pdf data.
Unforunately I had a problem using the SOAP nodes, so I tried the HTTP nodes instead.
The generated sublow coming along with the HTTP nodes contains an extract and an envelope node, which should strip the soap-envelope header structure from the message and reapply it later on.
The string representing the pdf is some kind of long, 1,926,600 characters.
During debug I see the message tree being correct directly after HTTP-Request. After that follows the Extract node which throws an exception:
java.lang.RuntimeException:unsupported token - .
Infocenter says "dont use extract/envelope, just use a mapping node instead". http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.etools.mft.doc/ac04710_.htm
I tried that with a similar error.
Is there a limitation regarding long strings?
Should I use an esql-compute instead of graphical mapping?
Maybe I should investigate into getting the SOAP nodes to work?
_________________
Global warming is an unintentional side effect of SOA's hotness.
-- http://soafacts.com/
a business integration methodology |
|
| Back to top |
|
 |
| sridhsri |
| Posted: Wed Aug 27, 2008 6:52 am Post subject: |
|
|
Master
Joined: 19 Jun 2008
Posts: 297
|
Perhaps I have missed something here. Extract node is deprecated but not SOAPExtract Node.
I think your case fits the use of a SOAPExtract Node. |
|
| Back to top |
|
|
| fde |
| Posted: Thu Aug 28, 2008 3:49 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 65
|
You're right. The extract node under databases is the deprecated one.
A SOAP-Extract node is part of the generated subflow after using the expose/invoke-webservice-assistents.
The SOAP-Extract node is currently throwing the exception from my initial post.
For testing, I just replaced the SOAP-Extract with an ESQL-compute to do the deenveloping. This works without exception.
So I am left with the question:
Does the SOAP-Extract node has any limitations regarding big messages or long strings within a single attribute?
_________________
Global warming is an unintentional side effect of SOA's hotness.
-- http://soafacts.com/
a business integration methodology |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
