For SOAPProcessor, how about also supporting the context defined on the "jbossws-endpoint" property (eliminating the need for the "jbossws-context" property) ala:<property name="jbossws-endpoint" value="myapp:fooservice"/>
This is an interesting alternative, although I would prefer to use a jbossws: scheme to clearly separate values for new config from the old config.
For "pure" consistency between SOAPProcessor and SOAPProxy, couldn't they both be coded to also support exactly the same format for internal endpoints i.e.
<property name="jbossws-endpoint" value="foo:HelloWorldWS"/>
<property name="wsdl" value="foo:HelloWorldWS"/>
Now this is where things get really interesting. I was thinking that we couldn't have a config syntax that would make sense between SOAPProcessor and SOAPProxy, but I think you are on to something here. Only thing I would ask is that we actually use the jbossws: scheme (I think David suggested this in an email originally).
Re: the URI issue, a quick read of RFC 2396 leaves me with the impression that ":" is allowed in the path section of the URI. I could be misinterpreting it though; relevant definitions from the RFC below ...
<scheme>://<authority><path>?<query>path = [ abs_path | opaque_part ]abs_path = "/" path_segmentspath_segments = segment *( "/" segment )segment = *pchar *( ";" param )param = *pcharpchar = unreserved | escaped | ":" | "@" | "&" | "=" | "+" | "$" | ","