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 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 Following these steps user could make runtime work except few cases, bugs are filed for these issues. Issue I like to note is user has no mechanism to view QOS features enabled with the end point (EP). Only workaround available is view it in the WSDL editor. It is very hard to identify the WSDL for the EP. User required to open "WS-Policy" window for WSIT features to work is not intuitive.
As the user indicated, the QoS features can be view in the WSDL. Also, the WSIT GUI does show client-side QoS configuration clearly. The request is for enhancements of NetBeans WSIT GUI displaying of Server-side QoS features and the current work flow. I will re-assign this ticket to the WSIT GUI module.
I have to say I'm confused and don't really understand what is the expected behaviour. I'm not very much used to CASA editor, so would you please be more specific and descriptive?
Without more descriptive info, I can't do much here.