Cool! Would you mind contributing this back? Others might be interested in it and we'd be pretty happy to reuse that. I guess that's already what you're doing but yes, the BpelC should be recreated at each compilation.
Cheers, Matthieu On 4/16/07, Janne Savukoski <[EMAIL PROTECTED]> wrote:
Hi, Yeah, it was pretty easy to guess. :) I built a bpelc ant-task to shorten the compilation cycle and access logging. And then I bumped into these spurious npes at runtime.. -janne On 4/13/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: > Hi Janne, > > But the compiler is not really meant to be reused across several > compilations, it should be reconstructed. How did you get this problem? > > Thanks, > Matthieu > > On 4/12/07, Janne Savukoski <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > Just fyi, when you're re-using BpelCompiler20 instance, expression > > languages (at least xpath 2.0) don't get listed to > > OProcess#expressionLanguages--except for the first compilation. This > > results to null return values from > > ExpressionLanguageRuntimeRegistry#findRuntime(..) and thus npes (with > > the rest of the compilations, that is.) Just my two cents.. :) > > > > -janne > >
