[esb-issues] [JBoss JIRA] Created: (JBESB-3517) NELL(0x85) character causes exception with groovy XML Parser in ESB 5.0 GA

Dave Siracusa (JIRA) jira-events at lists.jboss.org
Thu Oct 21 13:55:54 EDT 2010


NELL(0x85) character causes exception with groovy XML Parser in ESB 5.0 GA
--------------------------------------------------------------------------

                 Key: JBESB-3517
                 URL: https://jira.jboss.org/browse/JBESB-3517
             Project: JBoss ESB
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 5.0
         Environment: RHEL 64bit
            Reporter: Dave Siracusa
            Priority: Minor


The script below fails with a legal UTF-8 document.  
Parsing from a custom Java action works just fine (workaround).
Perusal of apache.xerces site indicates that an earlier version of the parser had problems with NELL, and other characters.  I'm not sure this is related.

--------------------------------------------------------------------------------------
org.jboss.soa.esb.actions.ActionProcessingException: Error executing Groovy script.
 at org.jboss.soa.esb.actions.scripting.GroovyActionProcessor.process(GroovyActionProcessor.java:161)
 at sun.reflect.GeneratedMethodAccessor719.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.yellowbook.soa.esb.actions.proxy.ActionProxy.process(ActionProxy.java:244)
 at sun.reflect.GeneratedMethodAccessor506.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
 at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:634)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:588)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:419)
 at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:619)
Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.
 at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
 at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
 at groovy.util.XmlParser.parse(XmlParser.java:172)
 at groovy.util.XmlParser.parseText(XmlParser.java:205)
 at sun.reflect.GeneratedMethodAccessor721.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:86)
 at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:226)
 at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:899)
 at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:740)
 at org.codehaus.groovy.runtime.InvokerHelper.invokePojoMethod(InvokerHelper.java:765)
 at org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:753)
 at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodN(ScriptBytecodeAdapter.java:167)
 at Script1.run(Script1.groovy:5)
 at org.jboss.soa.esb.actions.scripting.GroovyActionProcessor.process(GroovyActionProcessor.java:150)
 ... 16 more


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the esb-issues mailing list