Hi David and all, First thanks for clarifying these as you were involved in addressing WG more than me. Let me answer these questions from Axis2 pov.
David Illsley wrote: > > >> 3) Must I make sure that I can safely write MessageID without >> contradicting database schema constraints, if it has passed through >> Axis2? > > A quick look at the code suggests no :-( I can't see any validation of the > MessageID e.g. that it is actually a valid URI/IRI > We didn't validate this as we thought that this is an un-necessary burden. I thought abt the mostly used case, where user let the engine to pick the messageId. Axis2 happily sets an IRI. If user sets a message id he must know what he is doing. As we all know the URI class in java is bit slow. So if we do this for each and every message id, even when user is not setting this, this is an unnecessary burden, IMO. This is the case for other IRIs as well. -- Chinthaka
signature.asc
Description: OpenPGP digital signature
