-
1. Re: JBPM4.4: XMLUtil.element(Element, String, Parse) always returns null
aguizar Jul 9, 2010 6:13 AM (in response to kevinmoodley)I can run the jBPM test suite with Sun JDK 1.5.0_20 and OpenJDK 1.6.0_18 on Fedora Linux and XML parsing works without any external JAXP library. Can you please indicate your OS and exact JDK version?
If you are willing and able, please jBPM4 Building from Source and tell us what your test results are.
-
2. Re: JBPM4.4: XMLUtil.element(Element, String, Parse) always returns null
kevinmoodley Jul 9, 2010 2:19 PM (in response to aguizar)Experienced the problem on:
Windows XP with sun JDK 1.6.0_20Redhat Linux 5.4 with jdk 1.6.0_16-b01
Note:
I am trying to use XmlUtil directly, as a utility. I was not using it via the BPM Engine. This is probably why the default implementation of org.w3c.dom.Node (i.e com.sun.org.apache.xerces.internal.dom.NodeImpl) gets used. I did use it successfully with jBPM 4.3
I have subsequently created my own XmlParserUtility, so this is not a major issue at this time.
I will attempt to build jbpm 4 from source. I have never done this before.
-
3. Re: JBPM4.4: XMLUtil.element(Element, String, Parse) always returns null
aguizar Jul 10, 2010 4:45 AM (in response to kevinmoodley)I am trying to use XmlUtil directly, as a utility. I was not using it via the BPM Engine. This is probably why the default implementation of org.w3c.dom.Node (i.e com.sun.org.apache.xerces.internal.dom.NodeImpl) gets used. I did use it successfully with jBPM 4.3
Alright, this makes things clearer. I believe the reason why your own Element instances return null to getLocalName is that the DocumentBuilder they were created with is not namespace aware. The jBPM Parser class always sets the namespaceAware property of its DocumentBuilderFactory instance to true. This is probably what your own app is missing.