JpdlXmlReader: couldn't parse process definition probable schema validation problem ----------------------------------------------------------------------------------- Key: JBPM-2090 URL: https://jira.jboss.org/jira/browse/JBPM-2090 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA Environment: 3.3.1GA Reporter: Karl Palsson ProcessDefinition.parseXXX all fail for me. FileInputStream fis = new FileInputStream(fileName); ProcessDefinition pd = ProcessDefinition.parseParZipInputStream(new ZipInputStream(fis)); Or any variant thereof, gives me errors that seem related to schema validation. Full stack trace below. According to: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html/JBPM_Refe... and some other brief mentions in bug reports, it seems that schema validation should only be applied if there is an xmlns= attribute on the process defintion tag. However, even without any xmlns attribute, I get these errors. I have tried using my own process definitions, with and without the xmlns attribute. <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="CreateLineService2"> or <process-definition name="CreateLineService2"> or even <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="CreateLineService2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:jbpm.org:jpdl-3.2 http://docs.jboss.org/jbpm/xsd/jpdl-3.2.xsd"> I've even tried using the processdefinition.xml that comes in "examples\simple\src\main\jpdl" from the jbpm-3.3.1GA installer, with exactly the same results. I cannot try the ant task, as it demands a hibernate.cfg.xml, but we're using hibernate annotations and spring, so we don't have a cfg.xml file. There is no longer a deployer servelet like in jbpm 3.1.2 (which we were using before a recent upgrade) so I don't know of any other way of trying to deploy a new process now. The error message has not proved very helpful to me to try and work around this myself. :( 2009-03-09 17:22:25,260 DEBUG [org.jbpm.jpdl.xml.JpdlParser:main] - <schema resource found: org/jbpm/jpdl/xml/jpdl-3.2.xsd> 2009-03-09 17:22:25,260 DEBUG [org.jbpm.jpdl.xml.JpdlParser:main] - <schema resource found: org/jbpm/jpdl/xml/jpdl-3.3.xsd> 2009-03-09 17:22:25,260 DEBUG [org.jbpm.jpdl.xml.JpdlParser:main] - <schema resource found: org/jbpm/jpdl/xml/jpdl-3.0.xsd> 2009-03-09 17:22:25,260 DEBUG [org.jbpm.jpdl.xml.JpdlParser:main] - <schema resource found: org/jbpm/jpdl/xml/jpdl-3.1.xsd> 2009-03-09 17:22:38,073 ERROR [org.jbpm.jpdl.xml.JpdlXmlReader:main] - <couldn't parse process definition> org.dom4j.DocumentException: http://java.sun.com/xml/jaxp/properties/schemaSource Nested exception: http://java.sun.com/xml/jaxp/properties/schemaSource at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.jbpm.jpdl.xml.JpdlParser.parse(JpdlParser.java:66) at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:142) at org.jbpm.jpdl.par.JpdlArchiveParser.readFromArchive(JpdlArchiveParser.java:51) at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:87) at org.jbpm.graph.def.ProcessDefinition.parseParZipInputStream(ProcessDefinition.java:191) at vodafone.nip.applications.processupload.ProcessUploader.loadFile(ProcessUploader.java:50) at vodafone.nip.applications.processupload.ProcessUploader.main(ProcessUploader.java:41) Nested exception: org.xml.sax.SAXException: http://java.sun.com/xml/jaxp/properties/schemaSource at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1176) at org.dom4j.io.SAXReader.read(SAXReader.java:465) at org.jbpm.jpdl.xml.JpdlParser.parse(JpdlParser.java:66) at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:142) at org.jbpm.jpdl.par.JpdlArchiveParser.readFromArchive(JpdlArchiveParser.java:51) at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:87) at org.jbpm.graph.def.ProcessDefinition.parseParZipInputStream(ProcessDefinition.java:191) at mycode.blah() -- 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