Minor Description
FYI: based on thread "[Axis2] Fault in handling values in addressing parameters"
Most values (messageID,Action, address in a EPR ) in the Adressing is
typed as URI in the Spec but our implementation and the dispatching
treats them as string.
This relaxation aollow our Axis2 to send wrong Addressing headers
e.g.
<wsa:MessageID> 11234 </wsa:MessageID>
I belive we should check for and reject the non URI values that are
set, Shall I add a JIRA issue?
Thanks
Srinath
--------------------------------------------------------------------------------
This was done intentionally as some people suggested me that java URI
handling is very slow. So I put String for them purposely.
But as you proposed we can do a check on these values in
AddressingOutHandler.
What abt others think on this ....
Regards,
Chinthaka
--------------------------------------------------------------------------------
+1 for checking in the out handler but I also think parsing those
strings as URIs is waaay overkill. Maybe a small "parser" to check that
the strings have a scheme would be sufficient.
Sanjiva.
--------------------------------------------------------------------------------
+1 to use a efficient our URI class .. I think rather than do it in
the out handler we should change the signatures of our methods to
accept our URI and do the check in the URI constructor.
Thanks
Srinath