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.
It is possible to invoke/consume EJB-WS from business process via HTTP-BC when EJB-WS is configured with QOS features like MTOM, Reliable Message Delivery, and Transaction. Secure Service is not tested yet. This to work user needs to follow exact steps outlined below. 1. import the WSDL into BPEL module by <Service EP URL>?WSDL. 2. On the CASA editor, clone EP. 3. "Edit web service attributes/Client" action on the context menu and open "WS-Policy" windows known as WSIT configuration window. No configuration options but this action creates wsit-client.xml User working with business process may work with abstract WSDL document or WSDL document prior to QOS feature configuration. In this scenario user is stuck, only workaround is to update the WSDL. Another point to note, CASA looses it consistency with QOS configuration. CASA facilitates user to either create a new SOAP EP or configure existing one. On the same line QOS can not be configured. CASA needs to provide a mechanism similar to QOS configuration for SOAP Server EP. When I pointed these issue Tien pointed me to http://www.netbeans.org/issues/show_bug.cgi?id=131360 http://www.netbeans.org/issues/show_bug.cgi?id=136408 But they cover very subset of issues I have pointed here. Another bug I have related to this issue is http://www.netbeans.org/issues/show_bug.cgi?id=137526
The first part of the request is for an enhancement to associate QoS additions to WSDL files already included in a BPEL project. This is related to the more general issue of syncing external WSDL changes with WSDL included in SU projects. The second part of the request for client-side QoS enhancement is similar to that reported in http://www.netbeans.org/issues/show_bug.cgi?id=137526 I will re-classify this as an enhancement and link it to IZ# 137526.