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.
Summary: | FAST: Too many steps to expose Java logic to BPEL process | ||
---|---|---|---|
Product: | soa | Reporter: | lpolycarpou <lpolycarpou> |
Component: | BPEL Project | Assignee: | Sergey Lunegov <slunegov> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
lpolycarpou
2008-01-04 02:16:33 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. It requires some changes from NB core modules. Not sure we'll be able to implement it for Sierra. 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. "WSDL friendly" project related feature. |