Messages

[Glen Daniels <gd...@macromedia.com>]

As it stands right now, Messages require MessageContexts for serialization
and deserialization, since the MC is where the typemapping and service
description information are stored.  Right now there are a few "buggy" areas
of code which create Messages and don't link them to MessageContexts,
provoking NullPointerExceptions in certain situations.  I propose making
MessageContext into a Message factory, and forcing the Messsage constructors
to take a MessageContext.

So the pattern in general will be:

AxisEngine e = new AxisClient/Server()
MessageContext ctx = new MessageContext(e);
...
Message msg = ctx.createMessage(SOAPenvelope);
   OR
Message msg = new Message(ctx, SOAPenvelope);

Any opinions either way on this?  Removing the dependency is another option,
but I only see that being useful for unit testing.

Glen Daniels
Macromedia
http://www.macromedia.com/
                                Building cool stuff for web developers