This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 124683 - FAST: Too many steps to expose Java logic to BPEL process
Summary: FAST: Too many steps to expose Java logic to BPEL process
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Project (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Sergey Lunegov
Depends on:
Reported: 2008-01-04 02:16 UTC by lpolycarpou
Modified: 2008-04-30 15:43 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description lpolycarpou 2008-01-04 02:16:33 UTC
Currently with Sierra MS4, in order to invoke some custom Java logic from within the BPEL process we need to do the
following steps:

* Create an EJB module and EJB WS
* Add operation
* Implement Java logic
* Build and deploy it (to retrieve the WSDL)
* Drag and drop the Web Service into the BPEL canvas
* Select the WSDL again and create the necessary Partner Link type (partner role)
* Create the invoke event and BPEL inbound / outbound variables for that PL
* Wire it all up!

That's a lot of steps!  It is such overkill that it makes the use of BPEL very unattractive if you need to invoke any
Java services, considering how much simpler it is to do this from EJBs using annotations and WS references.  It should
be possible to create a new EJB-WS directly from the BPEL module itself which takes you through a wizard to achieve all
of the above leaving just the Java logic and wiring to implement.
Comment 1 lpolycarpou 2008-01-04 02:20:38 UTC
Furthermore, we need to lock down the EJB so it is not externally callable (assuming the service is only a WS so that it
can be used from within BPEL).  The use case here is using a Global RAR or OTD Link via BPEL which can only be via an
EJB-WS interface.
Comment 2 Sergey Lunegov 2008-01-15 08:29:19 UTC
It requires some changes from NB core modules. Not sure we'll be able to implement it for Sierra.
Comment 3 lpolycarpou 2008-01-20 01:41:47 UTC
Related to this, all Java logic needs to be EJB-WS and therefore externally callable.  How about just exposing it for
use with BPEL?  There needs to be a simpler way to work with Java & BPEL, possibly without the need for externally
callable web services.
Comment 4 Sergey Lunegov 2008-04-30 15:43:58 UTC
"WSDL friendly" project related feature.