Hi , Well i was thinking that , assuming the RPC Message Receiver is inadequate for more complex input and output datatypes , we are only left with the RAW XML Message receivers, which assume that one has a compiled java class with a method parameter signature accepting OMElement and returning an OM Element, and a method name which should be *the same* as the name of the operation name. (at least that can be seen from the RawXML MessageReceiver implementations in Axis2, more specifically in the findOperation impl).
So maybe if I don't want to restrict my java impl classes to have the same method names as the operation names , I should write a custom Message Receiver. Can anyone clarify this point? Thanks. Best Regards, Angel On 1/13/07, Comain Chen <[EMAIL PROTECTED]> wrote:
To give the user freedom to decide their own Databinding techniques? Also I have this doubt, why does the codegen module generate MessageReceiver for each Service, not let the binding framework write a general messageReceiver for all services? On 1/13/07, Angel Todorov <[EMAIL PROTECTED]> wrote: > > Hi Axis2 developers, > > I am interested to know what is the motivation behind using custom > message receivers? For example, if I want to invoke non-java > operations, I can have a helper Java class which manages all this > logic, and still be invoked by one of the existing message receivers, > such as the raw XML message receivers. > > Thanks very much for your feedback in advance. > > Regards, > Angel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Best regrads, Comain Chen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
