ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Kearns" <dan.kea...@gmail.com>
Subject Re: compiler access in iapi
Date Fri, 07 Sep 2007 15:57:15 GMT
Thanks Matthieu,

That make good sense. I'll work up a patch.

-d

On 9/6/07, Matthieu Riou <matthieu@offthelip.org> wrote:
>
> Hey Dan,
>
> I think that BpelC being almost a singleton already, we could just change
> it
> to hold a single instance of itself and the newBpelCompiler() method would
> just return that instance, cleaned up (just by resetting all the SU
> related
> info). You could add a defaultBpelCompiler() method that doesn't go
> through
> that cleanup part so that you can set the listener easily.
>
> // Initialization code
> BpelC.defaultBpelCompiler().setCompileListener(myListener);
>
> // Everybody's compilation code remains unchanged
> Bpelc.newBpelCompiler().compile(....);
>
> This will avoid the whole il->store->DU->BpelC injection problem. Would
> that
> work for you? Have time to contribute a small patch?
>
> Thanks,
> Matthieu
>

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