I looked at the casa editor for this assembly and found that the BPEL was not directly connected to the EJB. It looks like it was in fact using, or trying to use, https even though the units were altogether. It also did not like me trying to change those connections. It complained that the types were not correct.
I'm going to just recreate the WSDL and EJB in question, and I suspect it will behave. All I was looking for right now is confirmation that the EJB invocation is not subject to the transport security when invoked through the NMR, and you've answered that question. Thanks!
Jason Baragry-2 wrote:
AFAIK, the EJB should not be enforcing a transport level security option
if the communication is happening over the NMR.
However, as detailed in the 2nd link I sent, the JavaEE Service Engine
isn't like other engines. Its really a bridge between the JBI container
and the Web/EJB containers in Glassfish. That bridge makes use of HTTP
pieces in Glassfish to implement the JAX-WS pieces necessary to provide
and consume webservice interfaces. It may be that those pieces are
enforcing some SSL implementation that it shouldn't be in your scenario.
This is going beyond my knowledge of how the JavaEE SE is implemented. I
suggest you ask on users@openesb so that one of the engineers can comment.
rgds
Jason
--
<
http://www.java.com> * Jason Baragry *
Senior Solution Architect
Software Practice
*Sun Microsystems, Inc.*
Central & Northern Europe
Phone x43697/+47-23-369 697
Mobile +47 4899 4603
Email Jason.Baragry@Sun.COM
<
http://www.java.com>