Hi, In our application we need to expose a potentially large number of stateless session beans as Axis2 web services. To do so, we have implemented a message receiver which extends org.apache.axis2.rpc.receivers.ejb.EJBMessageReceiver This works ok but it has a quirk whereby it also finds and exposes 'internal' EJB methods which are not relevant to our application.
e.g: - remove (from javax.ejb.EJBObject) - setSessionContext (from javax.ejb.SessionContext) - etc Apart from having these unwanted operations in our wsdl, it also prevents us from using these method names in our interface. E.g. if our bean contains a method named 'remove', this method cannot be invoked by the client because the message receiver finds the version in javax.ejb.EJBObject ahead of our version. >From looking at the code RPCMessageReceiver.invokeBusinessLogic, I don't think >there is currently any workaround for this issue. Has anybody got any ideas or >should I create a jira case for it? Many thanks, Billy Dennigan. 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.
