Hi Eric
AFAIK, the changes "required" should be just the following for 1.7:
The interesting results of a quick grep have shown this:
classes/conf/axis2.xml: <parameter name="servicePath"
locked="false">soap</parameter>
web.xml: <url-pattern>/soap/*</url-pattern>
Cool! I really like to change it, but I was just too anxious to try it
out. ;-)
But with the ESB 1.6, we had to change the following too:
But also this:
webapp/extensions/core/js/esb.js:var SERVICE_CONTEXT = "/soap";
Hmmm, I executed the grep on wso2esb beta 2 (based on Synapse 1.2 beta 1).
Sorry.. this is still required for the ESB 1.7 :(.. I was assuming we
fixed this.. so the worst case, you can still switch the "soap" to
anything else.. can you please file a JIRA so that we can fix this more
elegantly for the next release
Yes, some customers have changed this since 1.6
I'm happy to here that. Do you know whether they wanted to change it to
a value specific to their environment or also to a more generic one,
like services?
I think this is commonly changed to "services".. one specific customer
wanted this to adhere to their own naming conventions for service EPR
URL's.. and that was "services" for a case where many SOAP and REST
services existed
What do other users think about this? Would it make sense to use a less
specific default value than soap? Maybe services?
I am fine to change this to "services" (infact we had that sometime
back.. I think for 1.0) if users like that better..
asankha
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
