|Re: Will the bpel designer initial contribution be based on the Collaxa code? [message #737 is a reply to message #721]
||Mon, 25 July 2005 18:10
| Philippe Ombredanne
Registered: July 2009
Thanks for your reply.
Just my 2 cents: if you have a working contribution as a starting point,
even if you may want to re-implement it as a native Java/SWT application, I
would be a strong advocate of starting with that.
Projects that start with a clean slate have a hard time to create a
And a plug-in with a DHTML UI would be quite interesting in itself too.
"Edwin Khodabakchian" <email@example.com> wrote in message
> Thanks Philippe (sorry for the delay).
> The initial contribution is still an open question: we have an eclipse
> implementation today (which is indeed based on the Collaxa code base) but
> that contribution is built in DHTML/Ajax. At this point, the thinking is
> to carry forward the knowledge and some of the design elements but
> re-implement a more native eclipse solution. By native, we mean
> implemented in Java and taking advantage of EMF and other graphical
> frameworks available in Eclipse. (Note: if you want to look at what the
> latest designer implementation looks like, you can download the eclipse
> plugin from the http://otn.oracle.com/bpel site, given that is implemented
> in DHTML, all the code is there!)
> From a timeline perspective, the eclipse process has a 1-month review
> process before making a decision. The goal during that month is to build a
> community around the project and this is what we are actively doing.
Powered by FUDForum
. Page generated in 0.02460 seconds