Hi Francesco,
I understand your concern and we are working on rewriting this part of the code because it violates the "do not use internal classes" rule. However, we are committed to having the BPEL Designer ready for the Eclipse Juno release this summer, and this will probably mean that the initial release may not support this extension. This feature will probably be part of a Juno service release (BPEL Designer 1.0.1 maybe?) later this year. That said, it may be possible for us to provide a version of BPEL Designer compatible with Eclipse Indigo, which *does* include this feature.
Be assured that this extension point is not going away - it's simply being delayed a bit until we have some time to rewrite the underlying code. Please let us know if you have available resources to help with this effort! Please monitor https://bugs.eclipse.org/bugs/show_bug.cgi?id=378997 for details about this effort.
________________________
Robert ("Bob") Brodt
Senior Software Engineer
JBoss by Red Hat
Hi All,
we are using this extension point in a big project.
We have made an embedded editor implementation using Xtext to define a new _expression_ Language.
We understand your needs but we would like to stay up to date.
So, if you are evaluating to put back this feature in the future, please note that it is a key feature for us.
We are also willing to help, if needed..
Thanks!
Francesco
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
