I appreciate this post (blog) as well.....
However, if you include the Asynchronous Service in the same Service Assembly (aka Composite Application) as the BPEL process, then the process fails to continue executing. In fact, the entire process waits endlessly. To understand why this occurs you need to look a bit deeper at what is happening under the covers in the JBI infrastructure.
Thanks Jason!
On Thu, May 21, 2009 at 4:43 PM, jsexton0
<jsexton0@...> wrote:
Today I've been experimenting with SSL/HTTPS in Glassfish. I'm working with
a BPEL that includes an invocation of an EJB. The BPEL and the EJB are
deployed in the same SA. I changed the EJB to use HTTPS, which seemed to
work. The invocation of the BPEL is through a normal HTTP SOAP request.
When the BPEL comes to the invoke element to the now secure EJB WSDL, I get
an exception:
javax.xml.ws.soap.SOAPFaultException: Security Requirements not met - No
Security header in message
Is this normal? The BPEL can not invoke an EJB through HTTPS even
internally, and even though the EJB is in the same SA?
Thanks
--
View this message in context: http://www.nabble.com/SSL-Inside-a-BPEL--tp23660135p23660135.html
Sent from the NetBeans - EntPack mailing list archive at Nabble.com.
