It looks like adhering strictly to RFC 2396 "Uniform Resource Identifiers (URI):
Generic Syntax" will entail semantic changes to InvokerLocator. The example I see is
the treatment of the path component. By definition, the URI path component begins with
"/", but InvokerLocator.getPath() doesn't return the initial "/".
Is it likely that changing getPath() to return the initial "/" would break
existing software? If so, a deprecated "classic" mode (settable by system
property or static InvokerLocator switch) could be offered in the Remoting 2
InvokerLocator class and eliminated in Remoting 3.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042033#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...