On 8/28/07, Janne Savukoski <[EMAIL PROTECTED]> wrote: > > I have the deploy.xml there, but some xsd/wsdls may be missing. > However, from the code it strongly looks like the execution is aborted > if no bpels are found. > > The relevant(?) two stack pointers are following: > > org/apache/ode/store/DeploymentUnitDir.java:123 > org/apache/ode/store/ProcessStoreImpl.java:165 > > and there the DeploymentUnitDir throws an exception; ProcessStoreImpl > never gets to 'du.scan()' at 172. After I manually skipped the > exception the deploy seemed to complete normally.
Yeah, I think the BPEL is always needed. We've never thought that the ability to deploy without the BPEL (and only the cbp) could be a needed feature. What's your use case? We're basically always requiring the BPEL because others than us could need it (mostly through the management console). It's just a conservative approach. Cheers, Matthieu On 8/29/07, Alex Boisvert <[EMAIL PROTECTED]> wrote: > > A pre-compiled process is only a replacement for the .bpel file. I > think > > you still need to include deploy.xml, and related WSDLs and XSDs. > > > > alex > > > > On 8/28/07, Janne Savukoski <[EMAIL PROTECTED]> wrote: > > > > > > Hello, > > > > > > I'm trying to deploy a unit with only precompiled (.cbp) files and my > > > futile attempt ends to a message "Directory xyzzy does not contain any > > > process!". I guess the commit 549966 with message "Deployment of empty > > > DUs shouldn't be allowed." may have something to do with this?) (See > > > > > > > /bpel-store/src/main/java/org/apache/ode/store/DeploymentUnitDir.java:122.) > > > So, should it still be possible to deploy precompiled processes and > > > this is just a bug, or? > > > > > > Thanks! > > > > > > best, Janne >
