[ 
https://issues.apache.org/activemq/browse/SM-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42910#action_42910
 ] 

Kristian Koehler commented on SM-1365:
--------------------------------------

Hi

the test hang on my machine. After investigation i found some 
java.net.ConnectExceptions caused by the XML parser. 

The parser is trying to resolve the dtd (version 2.8) via the DTDentityResolver 
from OpenWorkflow (com.opensymphony.workflow.loader.DTDEntityResolver). The 
resolver looks for the dtd within the jar file (META-INF directory) but isn't 
able to find it in the file. (On my local machine the jar file (version 2.7.0) 
doesn't contain the dtd in version 2.8.) So the parser tries to download the 
file casuing the exception.

After changing the dtd declaration to a dtd which is contained within the jar 
file everything works fine...

Wrong?

Kristian

ps: please see also my mail 
http://mail-archives.apache.org/mod_mbox/servicemix-dev/200805.mbox/[EMAIL 
PROTECTED]

> OSWorkflow tests using example file which includes wrong dtd version
> --------------------------------------------------------------------
>
>                 Key: SM-1365
>                 URL: https://issues.apache.org/activemq/browse/SM-1365
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-osworkflow
>    Affects Versions: 3.2.2
>            Reporter: Kristian Koehler
>            Assignee: Kristian Koehler
>         Attachments: osworkflow-version.patch
>
>
> Hi
> i encountered problems while running the OSWorkflow test. The example 
> workflow can't be deployed because the sample file uses a wrong dtd version 
> and the dtd file isn't included in the OSWorkflow distribution.
> Sample file dtd:
> --- 8< ---
> <!DOCTYPE workflow PUBLIC 
>                  "-//OpenSymphony Group//DTD OSWorkflow 2.8//EN"
>                  "http://www.opensymphony.com/osworkflow/workflow_2_8.dtd";>
> --- 8< ---
> Version 2.8 isn't included. Changing this to 2.7 works because the file is in 
> the osworkflow.jar ;-)
> Kristian

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to