[ http://issues.apache.org/jira/browse/AXIS2-751?page=comments#action_12412679 ]
Rajith Attapattu commented on AXIS2-751: ---------------------------------------- Robert, As Paul also pointed out we need to refactor the MessageReceivers, there is a lot of common code that can be factored out. Also another concern that I had about the receivers is for me to wrap the receive() or the point of invocation for session mgt/clustering. So if u can kick up a thread on MessageReceivers I also have a few concerns to raise Rajith > Easier customization of message receivers needed > ------------------------------------------------ > > Key: AXIS2-751 > URL: http://issues.apache.org/jira/browse/AXIS2-751 > Project: Apache Axis 2.0 (Axis2) > Type: Wish > Components: core > Versions: 1.0 > Reporter: robert lazarski > > To override method AbstractMessageReceiver.makeNewServiceObject() , one would > need to create a new Class - SpringAbstractMessageReceiver for example - and > all classes that implement the MEP types need to do an extends of that class. > The current implementation makes it hard to override makeNewServiceObject() > in a way that doesn't require a message receiver in services.xml that has, > for example, SpringRawXMLINOutMessageReceiver: > AbstractMessageReceiver > ^ > | > | > SpringAbstractMessageReceiver -- override > makeNewServiceObject() > ^ > | > | > SpringAbstractInOutSyncMessageReceiver > ^ > | > | > SpringRawXMLINOutMessageReceiver > > There should be a less intrusive way to override makeNewServiceObject() and > get the class loaded in an alternative way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
