[jboss-jira] [JBoss JIRA] Commented: (BPEL-293) xsd files in nested directories break deployment

[Alejandro Guizar (JIRA)]

    [ http://jira.jboss.com/jira/browse/BPEL-293?page=comments#action_12408775 ] 
            
Alejandro Guizar commented on BPEL-293:
---------------------------------------

The web module builder preserves the relative path where the XML Schema file is located in the process archive, but does not ensure the corresponding directory exists in the temporary working location. WSDL files are not affected; their directory is ensured to exist.

The fix will be delivered with the next release of jBPM BPEL. You might want to apply it yourself in the meantime. The instructions for building the product from source can be found in our Wiki [a]. Once you check out, follow these steps:

1. Open jbpm.3/bpel/library/src/main/java/org/jbpm/bpel/tools/WebModuleBuilder.java
2. Modify writeFile() as follows:

  private static void writeFile(File file, byte[] data) throws IOException {
    // create parent directory if it does not exist
    File parentDir = file.getParentFile();
    if (parentDir != null)
      parentDir.mkdirs();

    OutputStream fileSink = new FileOutputStream(file);
    try {
      fileSink.write(data);
    }
    finally {
      fileSink.close();
    }
  }
3. Rebuild and redeploy.

[a] http://wiki.jboss.org/wiki/BuildBpelFromSources_bpel_1_1_ga

> xsd files in nested directories break deployment
> ------------------------------------------------
>
>                 Key: BPEL-293
>                 URL: http://jira.jboss.com/jira/browse/BPEL-293
>             Project: JBoss jBPM BPEL
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 GA
>         Environment: JBoss-4.2.2.GA, jbpm-bpel-1.1.GA. Running under Windows XP.
>            Reporter: Conor O'Neill
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1.1
>
>
> BPEL 2 examples fail to deploy if there are any .xsd files in nested directories below the .bpel file.
> I have obtained the up-to-date BPEL 2 examples, and these deploy correctly.
> If you then adjust the 'hello' example as follows, this fails to deploy.
> Add a subdirectory called 'interfaces' (or, in fact, any name at all) below the examples/hello/src/main/bpel2 directory. Put any schema file (.xsd file) into this directory. This file doesn't need to be referenced from anywhere, though I first discovered this bug because I was using this schema as part of a WSDL definition.
> When you try to run the 'deploy.process' ant task, the process fails to deploy, and the log4j messages from JBoss server indicate:
> 2008-04-14 14:19:47,847 ERROR [org.jbpm.bpel.xml.ProblemHandler] could not build web module
> java.io.FileNotFoundException: C:\Temp\hello7nestedxsds10574.war\wsdl\interface\common.xsd (The system cannot find the path specified)
> 	at java.io.FileOutputStream.open(Native Method)
> 	at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
> 	at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
> 	at org.jbpm.bpel.tools.WebModuleBuilder.writeFile(WebModuleBuilder.java:238)
> 	at org.jbpm.bpel.tools.WebModuleBuilder.callWsdlServiceTool(WebModuleBuilder.java:232)
> 	at org.jbpm.bpel.tools.WebModuleBuilder.buildModuleImpl(WebModuleBuilder.java:97)
> 	at org.jbpm.bpel.tools.WebModuleBuilder.buildModule(WebModuleBuilder.java:84)
> 	at org.jbpm.bpel.web.DeploymentServlet.deployWebModule(DeploymentServlet.java:205)
> 	at org.jbpm.bpel.web.DeploymentServlet.doPost(DeploymentServlet.java:99)
> [ snip]
> I appears that the WebModuleBuilder is not correctly coping with the subdirectory, and fails to create the subdirectory before copying this file.

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