This means having "foo/bar" as a service name should be wrong. Then, what happens to our hierarchical deployment model? Currently it creates service names in that manner. So, how do we differentiate the same service in different contexts at wsdl level? Do we have to follow a convention like "foo-bar" for a service "bar" under the context "foo". Or any other solution?
regards, Ruchira. On Mon, Oct 18, 2010 at 9:32 PM, Sanjiva Weerawarana <[email protected]>wrote: > Nope can't have "/" in an NCName. That's a bug ... > > Sanjiva. > >
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
