When deploying the webservice_esb_bpel example, it results in a number of problems (as shown in the attached file), but the root cause appears to be:

Caused by: java.io.IOException: Child not found WEB-INF/wsdl/../schema/CustomerOrder.xsd for FileHandler@2097884[path= context=file:/NotBackedUp/gbrown/testing/riftsaw/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-a922bebe-2d92-464e-81f7-784f917e7649.war/ real=file:/NotBackedUp/gbrown/testing/riftsaw/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-a922bebe-2d92-464e-81f7-784f917e7649.war/], available children: [FileHandler@26983592[path=WEB-INF context=file:/NotBackedUp/gbrown/testing/riftsaw/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-a922bebe-2d92-464e-81f7-784f917e7649.war/ real=file:/NotBackedUp/gbrown/testing/riftsaw/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-a922bebe-2d92-464e-81f7-784f917e7649.war/WEB-INF/]]
at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)
at org.jboss.metadata.serviceref.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:99)
at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:106)
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:249)
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:276)
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:276)
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlImports(WSDLFilePublisher.java:199)
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:125)
... 30 more

On examining the referenced location, the WEB-INF folder is empty. When deploying the riftsaw quickstart hello_world, another tmp war structure is also created in this tmp/riftsaw location, but equally it's WEB-INF folder is empty.

Not sure what this tmp war structure is intended to hold?