On Fri, 2007-02-09 at 23:19 +1300, Dennis Sosnoski wrote: > > I really dislike using reflection for this type of thing, since it means
There's no reflection involved .. the generate MR would have the right code in it. > that "magic" methods change the behavior of things at runtime. It'd be > easy enough to do this as an interface, though. So the message receiver > could check if the service class implements the pingable interface, and > if so it calls the method defined by that interface. Otherwise, it just > checks that it can create an instance of the service class. This is fine with me too. > That seems like a reasonable approach - no impact on users who just use > the default behavior, but easy for anyone who wants to support the added > value to do so. Does anyone object to implementing it this way? Are you in agreement with Thilina's point: we need to add a ping() method to MR which would in turn interrogate the service class (at least for Java class implemented services .. obviously it does squat for a service implemented as bpel script or javascript or something else). Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
