Eran, Can you explain to me how the user of this method will be able to tell the difference between e.g. a SOAP and a REST EPR?
I'm a little nervous about making a change like this without fully understanding what and how the multiple EPRs can be used as if it's not totally clear it's a probable source of problems. Also, are you intending to update the ListenerManager.getEPRforService method as well? If so, how will its users determine which EPR to use? David On 12/09/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
+1 to add new method and remove old one. Thanks Deepal Eran Chinthaka wrote: >Hi, > >Current transport listener interface enables a listener to return only >one EPR per listener. But some listeners can handle more than one EPRs. >One of the examples is that the same servlet can be used to handle both >SOAP and REST messages, but can have different endpoints. > >So this is a proposal to add a method to transport listener interface >which can return an array of EPRs. > >public EndpointReference[] getEPRsForService(String serviceName, String >ip) throws AxisFault; > >This will make the EndpointReference getEPRForService(String >serviceName, String ip) method to be redundant. So let's make that >method deprecated (can we remove it now itself?) and will be changing >all the internal classes to use the new method. > >Please review and comment on this and the commit with this change will >follow soon. > >Thanks, >Chinthaka > > > -- Thanks, Deepal ................................................................ ~Future is Open~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
