The ejb transport is independent of the naming service transport. The ejb remote binding being looked up has to be configured to use ssl.
The ejb transport is independent of the naming service transport.
OK, but it is involved/used to create the InvokerLocation for the ejb transport. That's what I wanna tweak wrt. the request.
The ejb remote binding being looked up has to be configured to use ssl.
Well, ssl or not is not really my point.
I assume, that I can make ejb3 transport service available via several transport mechanismen (at least that's my limited clue of Jboss remoting) and even by using the "default" servlet container via EJBInvokerServlet aka HttpInvoker.java. Is this correct ?
If so, my problem is simply to find a way to set or modify the InvokerLocation (which gets send back to the client) wrt. to the received request. So can you give me a hint, where it gets generated?
Moved to the remoting forum. SSL is the point as your asking about having this requirement along two separate transport channels. If you can't find the config info for this in either the ejb3 or remoting docs raise a feature request to get this added.