This content has been marked as final. Show 3 replies
No changes are planned for 11, the Java Embedding activity will stay as it is. The intention is not that people put large amounts of code there. It was intended for small, short utility operations. If you're putting business logic in there you may want to consider changing the design, perhaps to call out to an EJB service, for example.
> (notepad coding inside jdev would make me laugh if I hadn't to use it).
It is far superior to Notepad: comments are in a grey color. ;)
Incidentally when the BPEL design tool was Eclipse-based, it was the same thing. It's independent of the underlying IDE.
> This doesn't help coding, especially when you try to guess what is behind the
BPELXExecLet class (the documentation doesn't really help).
The recommended practice is to develop your code in a separate Java project (where you have full Java editing capabilities), then jar it up, include it in your BPEL project, and simply call your method from the Java Embedding activity.
Create a new library -- I call mine BPEL -- with the following classes:
SOA_HOME/bpel/lib/orabpel.jarAttach that library to a Java project and now you can browse the classes, use auto-complete, etc.