It would seem important to preserve access to the MessageContext (as some of
the previous method signatures did). I don't see how this captured in your
proposal for those three method sigs.
Sorry if I'm off here, but I'm just jumping into all this, and you sounded
urgent in your ALL CAPS RFC. The current MessageContext-containing
signature is the one I am planning on using (for flexibility), so I'd hate
to see it go.
--
Dan Kamins
-----
Glen Daniels <[EMAIL PROTECTED]> wrote:
I'd like to make THESE THREE the accepted APIs for message-style service
methods:
public class MessageService {
public SOAPBodyElement [] bodyMethod(SOAPBodyElement [] bodies)
public SOAPEnvelope envelopeMethod(SOAPEnvelope envelope)
public Element [] bodyAsDOMMethod(Element [] bodies)
}
I think these make a lot more sense than what we've got now.
IF THIS WILL AFFECT YOU IN A NEGATIVE WAY, or IF YOU DISAGREE WITH THESE
CHANGES, \
please send mail to axis-dev in reply to this message.
-----
_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail.
http://www.hotmail.com
