Neat idea :) Ruby guys use that a LOT. I think its very cool and could
be used for a lot of error handling. In fact, generally it would be a
nice way of implementing dynamic services, because the pattern is
clearly understood by anyone who's looked at Ruby or Groovy.
Paul
Sanjiva Weerawarana wrote:
I'd also like to see an "unknown_operation" function. That function
would get set by the dispatch logic when the operation to deliver the
message to cannot be figured out. So that's like how a dynamic proxy
works in Java or how the "method_unknown" thing works in Ruby.
I'd actually like to extend the service lifecycle stuff in Axis2 to have
this concept too. Then if the dispatcher hasn't found an operation to
dispatch to and if this operation is present, the message will be
dispatched to that operation.
Sanjiva.
Keith Chapman wrote:
Hi,
I think its good to introduce some service life cycle stuff to our
mashups. It makes our stuff more interesting. So basically it would
calla special function at deployment time and another on undeployment.
I propose introducing some annotations to take care of this.
this.init="functionName"; -> To be called in deployment
this.destroy="functionName"; -> To be called on undeployment
Jonathan proposed destruct instead of destroy.
What do u guys this how should we go about this?
Thanks,
Keith.
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
Office: +1 646 290 8050
Cell: +44 798 447 4618
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
