It appears that unmarshaling/marshaling message elements is very costly.
This processing must be reduced. Reducing this processing has a non negligeable
impact on the current API of major classes (Message, Management, SOAP...).
Unmarshalling is done each time a piece of data is get from Message class.
Marshaling and unbind of existing element is done each time a piece of
information is set to the Message. This is required when you want the internal
SOAPMessage to be in sync with the wrapper. Do we really want this perpetual
We should be able to get/set information without doing any marshal/unmarshal
processing and finally ask for a SOAPMessage. Currently the Message.getMessage()
returns the actual internal SOAPMessage. It should be replaced by a SOAPMessage
createMessage() that will create a SOAPMessage based on what was previously get/set.
As said, it changes the way these core classes are behaving.