Hi, We found that we had problems integrating Axis2 with WebLogic in that we couldn't re-use any of the EJB receiver code apparently because the security established at InitialContext creation (org.apache.axis2.rpc.receivers.ejb.EJBUtil) was then lost when org.apache.axis2.rpc.receivers.ejb.EJBUtil.EJBClientWorker invoked its run method in a separate thread for the EJB service, causing a WebLogic security error invoking the service. We checked with Oracle and they feel it's most likely that the separate threads are the cause as WLS doesn't pass/propagate subjects across threads. Thus the second thread that does the actual invocation of the service doesn't have the authentication done in the first thread when the InitialContext is created, which is successfully validated by our login module.
We coded our own receiver to avoid this additional threading-essentially duplicating the Axis2 functionality; but was wondering if this is possibly a bug or if I'm misunderstanding something on the Axis2 side? I've been told that for EJB environments that threading should not be used, leaving it to the container environment to manage. Thanks, William The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you.
