ICAN 5.0.5: Alerter does not encrypt XML data
(Doc ID 1028928.1)
Last updated on MARCH 28, 2005
Applies to:Sun SeeBeyond Integrated Composite Application Network (ICAN) - Version: 5.0.5 and later
Information in this document applies to any platform.
Using the "alerter" object within a java collab, a custom XML is supposed to be as the message in the alert. The collab code looks like:
where xmlStr is an XML string. The Alert Agent is set up to send the alert to a JMS topic.
The problem is that the XML data that is inserted into the <MessageDetails> node of the ICAN alert object is not "encrypted" as an OTD would normally do. For example, "<" would get replaced with "<", and so on. Since this embedded XML object is not "encrypted", this causes a problem when he tries to use the ICAN Alert OTD to unmarshal the data. he gets the following exception:
ERROR [JMS Async S9] [Testing.jcdAlertHandler1.jcdAlertHandler_Runtime_Handler]  Line 15.76: XmlLexer.nextTag() failed: Invalid context - PI cannot use name 'xml'
com.stc.otd.runtime.UnmarshalException: Line 15.76: XmlLexer.nextTag() failed: Invalid context - PI cannot use name 'xml'
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document