[
https://jira.jboss.org/jira/browse/JBESB-2087?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-2087.
-------------------------------
Resolution: Done
Workaround committed in revision 23257.
I have also added QA junit tests for this issue and the scout performance issue. They are
now run as part of a CI build.
The junit test is actually a standalone sar (aop-test.sar) which can be dropped into a
server and run by hand. MBean is called jboss.esb:test=AOPServer and it has two verify
methods.
jUDDI fails to parse XML correctly
----------------------------------
Key: JBESB-2087
URL:
https://jira.jboss.org/jira/browse/JBESB-2087
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Kevin Conner
Priority: Blocker
Fix For: 4.4 CP1
jUDDI can fail to parse the XML messages sent between scout and jUDDI, the result of
which can be indeterminate.
One manifestation of this problem is the inability to register clean EPRs, resulting in
the following exception.
org.jboss.soa.esb.services.registry.RegistryException: com.ctc.wstx.exc.WstxEOFException:
Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
at
org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPR(JAXRRegistryImpl.java:344)
The reason for the failure is the inability of jUDDI to handle CDATA sections within the
XML. Instead of parsing the section correctly it will generate an empty string, hence the
above exception when trying to parse the EPR.
I believe this issue exists in *all* releases to date.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira