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. Acutally this is my mail on "Dispatch all undispatched operations to a special function". We though of implementing it as follows in the mashup server (May be we should look to implement in the same method as suggested by jonathan. Have both options work)
this.undispatched= function"; sounds good? Thanks, Keith. 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 >> > _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
