ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Workflow XML API: complete XML doc as part of InputContainer

Post new topic  Reply to topic
 Workflow XML API: complete XML doc as part of InputContainer « View previous topic :: View next topic » 
Author Message
igorbunov
PostPosted: Tue Feb 25, 2003 2:29 pm    Post subject: Workflow XML API: complete XML doc as part of InputContainer Reply with quote

Newbie

Joined: 25 Feb 2003
Posts: 2

Hello,

I am trying to send a complete XML document within workflow XML envelope (as a field in InputContainer). It looks like Workflow tries to parse it and therefore returns "malformed message" response.

The obvious solution would be to use CDATA[...] on that container field, but it's not good enough for me, because enclosed document may also contain CDATA[...] elements.

Has anyone solved similar problem before (I'm sure somebody has, my sitations seems pretty common)?

Thank you in advance,
Igor Gorbunov
Back to top
View user's profile Send private message
dkrawczynski
PostPosted: Tue Feb 25, 2003 3:13 pm    Post subject: Reply with quote

Apprentice

Joined: 19 Dec 2002
Posts: 26
Location: Dallas, TX

You could very well be the first person to try to stuff a complete XML message into a workflow container field. I would question the need to do such a thing as these fields are meant to hold individual data elements mostly used for control connector evaluation. Note, there is a performance cost associated with workflow data elements in the input/output containers, especially when they contain larges amounts of data.

If you are bound and determined to do this, you should post a message to the ibm.software.websphere.mqworkflow news group so that the MQWF lab in Germany will see your problem and comment on it.
_________________
Doug Krawczynski
IBM Certified Solutions Expert -
MQSeries Workflow
Back to top
View user's profile Send private message Send e-mail Visit poster's website
igorbunov
PostPosted: Tue Feb 25, 2003 3:30 pm    Post subject: Reply with quote

Newbie

Joined: 25 Feb 2003
Posts: 2

Well, I really need to do this exact thing. I am actually sending an arbitrary Data Structure (more precisely, arbitrary Java Bean), serialized into XML (SOAP encoding).

I know people did similar things with Java objects serialized into binary streams, so I can't imagine my case as being very exotic

Thanks,
Igor
Back to top
View user's profile Send private message
Ratan
PostPosted: Tue Feb 25, 2003 3:47 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

doug is right. I think you should have a pointer to the xml document needed stored in a data structure member instead. That way you can retrieve it whereever needed. You can find info regarding storing pointers to actual data in this forum.

-Laze
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Workflow XML API: complete XML doc as part of InputContainer
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.