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 » WebSphere Message Broker (ACE) Support » XMLTransformation output problem

Post new topic  Reply to topic Goto page Previous  1, 2
 XMLTransformation output problem « View previous topic :: View next topic » 
Author Message
jefflowrey
PostPosted: Fri Jul 29, 2005 9:17 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
That's not the trace I'm looking for.

That's the trace from the XMLTransformation node.

I'm looking for output from a Trace node connected to the out terminal of the XMLTransformation node.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
JT
PostPosted: Fri Jul 29, 2005 9:43 am    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
Quote:
When the ESQL of Compute node excute the following on the output XML msg of XMLtransformation node

DECLARE J INTEGER CARDINALITY(InputRoot.XML.Log[]);

it returns J=0;

Please post all of the ESQL code in the Compute node.
Back to top
View user's profile Send private message
recallsunny
PostPosted: Fri Jul 29, 2005 10:16 am    Post subject: Reply with quote

Disciple

Joined: 15 Jun 2005
Posts: 163
Location: Massachusetts
Quote:
Quick Fix

Add a ResetContentDescriptor node after your XMLtransformation node and change MessageDomain to "XML", check mark the Reset MessageDomain property.

You should be able to see the BLOB converted to your new XML format after XML transformation.

Just an observation, the XML transformation node is awfully slow processing those XSLT's.....Wish there is a better option.
Back to top
View user's profile Send private message
sanks
PostPosted: Fri Jul 29, 2005 11:00 am    Post subject: Reply with quote

Apprentice

Joined: 21 Mar 2005
Posts: 27
Yap, that's the trouble shoot.
I added RecentCoddedDescriptor in between and it works fine.
But I think this is not the actual solution.

Why should I require to add this node?

What is going wrong with XMLtransformation node action?

Will you please explain?
Back to top
View user's profile Send private message
sanks
PostPosted: Fri Jul 29, 2005 11:03 am    Post subject: Reply with quote

Apprentice

Joined: 21 Mar 2005
Posts: 27
jefflowrey

This is the ESQL

CREATE COMPUTE MODULE Dispatcher_LOG CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
DECLARE MT CHARACTER 'A';
DECLARE I INTEGER 0;
DECLARE J INTEGER CARDINALITY(InputRoot.XML.Log.Transaction[]);
SET MT = InputRoot.XML;
CALL CopyEntireMessage();
WHILE I < J DO

IF (InputRoot.XML.Log.Transaction.LocationType = 'CCD'
THEN
RETURN TRUE;
END IF;

SET I = I + 1;
END WHILE;
RETURN FALSE;
END;

CREATE PROCEDURE CopyEntireMessage() BEGIN
SET OutputRoot = InputRoot;
END;
END MODULE;
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » XMLTransformation output problem
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.