|   | 
	 
  
    | 
RSS Feed - WebSphere MQ Support
 | 
RSS Feed - Message Broker Support
 |   
 
  
	     | 
	 | 
   
 
  
	|  XSLTransform does not work with MRM domain | 
	« View previous topic :: View next topic »  | 
   
  
  	
	  
		
		
		  | Author | 
		  Message
		 |  
		
		  | lium | 
		  
		    
			  
				 Posted: Fri Sep 19, 2014 5:51 am    Post subject: XSLTransform does not work with MRM domain | 
				     | 
			   
			 
		   | 
		 
		
		   Disciple
 
 Joined: 17 Jul 2002 Posts: 184
  
  | 
		  
		    
			  
				Currently, I got my code working with the following:
 
 
XSLTransform + Compute
 
 
The XSLTransform will take XMLNSC - > XMLNSC
 
 
The Compute node will have code like the following:
 
	CREATE FUNCTION Main() RETURNS BOOLEAN
 
	BEGIN
 
		SET OutputRoot.Properties.MessageSet = 'MyMessageSet';
 
		SET OutputRoot.Properties.MessageType = 'MyType';
 
		SET OutputRoot.Properties.MessageFormat = 'Text1';		
 
		SET OutputRoot.MRM = InputRoot.XMLNSC.Result;
 
		RETURN TRUE;
 
        END;
 
 
You can compute just convert the XMLNSC to MRM domain.
 
 
I would like to remove the Compute node, because the XSLTransform has capability to generate the output with specified format in its "Output Message Parsing", where I can specify the message domain, message set, message type, message format and Character set.
 
 
However, when I specifies MRM/MyMessageSet/MyType/Text1/blank, I got exception as following:
 
 
ParserException
 
	File:CHARACTER:F:\build\S700_P\src\MTI\MTIforBroker\MtiImbParser2\MtiImbFIHandler.cpp
 
	Line:INTEGER:1018
 
	Function:CHARACTER:MtiImbFIHandler::endMessageContent
 
	Type:CHARACTER:
 
	Name:CHARACTER:
 
	Label:CHARACTER:
 
	Catalog:CHARACTER:BIPmsgs
 
	Severity:INTEGER:3
 
	Number:INTEGER:5288
 
	Text:CHARACTER:MTI. Not all the buffer was used when reading message
 
	Insert
 
			Type:INTEGER:2
 
			Text:CHARACTER:0
 
	Insert
 
			Type:INTEGER:2
 
			Text:CHARACTER:739
 
 
 
 
Could anyone give me any idea how to solve this?
 
 
Thanks | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Fri Sep 19, 2014 6:41 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				my understanding is that the XSLT should only worry about transforming the content of the message and not try to set the properties or headers.
 
 
Have fun   _________________ MQ & Broker admin | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | lium | 
		  
		    
			  
				 Posted: Fri Sep 19, 2014 7:11 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		   Disciple
 
 Joined: 17 Jul 2002 Posts: 184
  
  | 
		  
		    
			  
				| I agree that the XSLTransform focus on the transformation of content, however, why it has the attribute of "Output Message Parsing", if it does, it means it has such capability | 
			   
			 
		   | 
		 
		
		  | 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
  | 
  		 
	   
	 | 
   
 
  	 | 
	  |