ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou" <matthieu.r...@gmail.com>
Subject Re: Expression language handling in bpelc
Date Tue, 17 Apr 2007 13:48:37 GMT
Thanks! I'll have a look.

On 4/17/07, Janne Savukoski <janne@savukoski.name> wrote:
>
> Yeah, of course! Although there's nothing too fancy about it.. And it
> supports only NS_WSBPEL2_0_FINAL_EXECs for now, so it needs some
> generalization. I'm a bit busy now and I don't need that feat now, so
> if you wouldn't mind extending it..?) If you end up adopting it at
> all, that is.
>
> I'm doing XML parsing twice as there were some line number issues with
> XML schema validation. There's also a caching ResourceFinder (which
> also tries to look up resources from the local system to avoid loading
> over network) and a couple of stub parse/compilation listeners.
>
> The code isn't overly tested, so there may be some bugs.
>
> Usage:
>
>   <taskdef resource="bpelc_taskdef.properties"
>            classpathref="project.classpath" />
>
>     <bpelc destdir="${build.dir}" bpelSchema="ws-bpel_executable.xsd">
>       <fileset dir="${bpel.dir}" includes="*.bpel" />
>     </bpelc>
>
> , where the bpelc_taskdef.properties contains only the single line
> bpelc=com.xernel.util.bpelc.BpelCTask
>
> The attribute bpelc/@bpelSchema is optional; schema validation is
> skipped if undefined. And you might want to use the -verbose -switch.
>
> I give up all the rights for this bit of code so you're welcome to do
> whatever you like with it. Use it well! :) (I guess you need to
> accustom the package first..)
>
> best, janne
>
>
> On 4/16/07, Matthieu Riou <matthieu.riou@gmail.com> wrote:
> > 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 <janne@savukoski.name> 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 < matthieu.riou@gmail.com> 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 <janne@savukoski.name> 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
> > > > >
> > >
> >
> >
>
>
> --
> Janne Savukoski ++ Xernel Oy
> +358.40.5684246 (mobile)
> janne@savukoski.name (email & im)
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message