| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue with XSL Transform node |
« View previous topic :: View next topic » |
| Author |
Message
|
| the m |
 Posted: Thu Jan 21, 2010 9:35 am Post subject: Issue with XSL Transform node |
 |
|
Newbie
Joined: 17 Nov 2009
Posts: 6
|
This might be a stupid question but I'll ask it anyway. We have to build one large XML message from multiple XMLs which we retrieve from DB. I'm trying to use a XSL Transform node to modify the XML content but I get the following error:
"RecoverableException BIP2230E: Error detected whilst processing a message in node 'CreatePGMLData_Flow.ProcessPGMLData_Subflow.P2_2 XSL Transform'. The message broker detected an error whilst processing a message in node 'CreatePGMLData_Flow.ProcessPGMLData_Subflow.P2_2 XSL Transform'. An exception has been thrown to cut short the processing of the message. See the following messages for details of the error.
RecoverableException BIP4367E: The method ''evaluate'' in Java node ''ProcessPGMLData_Subflow.P2_2 XSL Transform'' has thrown the following exception: 'java.lang.NullPointerException'. The method ''evaluate'' of the Java node has thrown an exception. Examine previous error messages for details of the cause of the problem. This error is generated by the Java node API. It can occur in a Java Compute node or a Java user-defined node. If the node is a user-defined node, contact the node provider for further details.
RecoverableException BIP4395E: Java exception: ''java.lang.NullPointerException''; thrown from class name: ''com.ibm.xsl.mqsi.XMLTransformNode'', method name: ''setOptionsFromPropertiesFolder'', file: ''XMLTransformNode.java'', line: '1081' The message contains that data associated with a Java exception."
My XML structure looks like this:
| Code: |
<?xml version="1.0" encoding="ISO-8859-1"?>
<Data>
<PGML xmlns:tva="urn:tva:metadata:2002"
xsi:schemaLocation="urn:iptc:std-draft:ProgramGuideML:1.0:spec:xml-schema:1.0:xsd ProgramGuideML_1.0beta-spec-XMLschema_1.xsd"
xmlns:pgml="urn:iptc:std-draft:ProgramGuideML:1.0:spec:xml-schema:1.0:xsd"
xmlns:mpeg7="urn:mpeg:mpeg7:schema:2001"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iptc:std-draft:ProgramGuideML:1.0:spec:xml-schema:1.0:xsd"
version="1.0">
<Item1>
<ItemName>abc</ItemName>
</Item1>
</PGML>
<PGML> xmlns:tva="urn:tva:metadata:2002"
xsi:schemaLocation="urn:iptc:std-draft:ProgramGuideML:1.0:spec:xml-schema:1.0:xsd ProgramGuideML_1.0beta-spec-XMLschema_1.xsd"
xmlns:pgml="urn:iptc:std-draft:ProgramGuideML:1.0:spec:xml-schema:1.0:xsd"
xmlns:mpeg7="urn:mpeg:mpeg7:schema:2001"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:iptc:std-draft:ProgramGuideML:1.0:spec:xml-schema:1.0:xsd"
version="1.0">
<Item2>
<ItemName>xyz</ItemName>
</Item2>
</PGML>
.
.
.
</Data>
|
Does the error occur because the namespaces are declared over and over again in each PGML-element? If that is the case is there any way to remove the namespaces in ESQL code? I'm a little puzzled because when I tried the same thing with a similar XML file by reading the file from MQ queue, the XSL Transform went through without any errors. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Thu Jan 21, 2010 10:44 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| RecoverableException BIP4395E: Java exception: ''java.lang.NullPointerException''; thrown... |
Looks very much like a defect in the XMLTransform node. However...
| Quote: |
| Does the error occur because the namespaces are declared over and over again in each PGML-element? |
That's an interesting question. The answer *should* be 'no' but I wonder why you asked. Did you try removing the namespace declarations and the error went away?
You *can* remove the namespace declarations using ESQL, but I don't recommend that you bother to do that unless you know it will fix the problem.
I do recommend that you raise a PMR. If you do, please refer to this thread as background info for the responder. |
|
| Back to top |
|
|
| krzysiek |
| Posted: Mon Apr 04, 2011 2:06 am Post subject: Issue with XSL Transform node |
|
|
Newbie
Joined: 04 Apr 2011
Posts: 1
|
I had the same problem.
Try this:
Add "Compute Node" before "XSL Transform Node".
In ESQL:
SET OutputRoot = InputRoot;
set OutputRoot.Properties.Encoding = 273; --or some other value
set OutputRoot.Properties.CodedCharSetId = 1208; --or some other value
Values depends on your msg encoding and ccsid. |
|
| 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
|
|
|
|
