Roll up patch FSW_6.0_3_2014 seems to have broken REST.
Tha attached applications can be deployed to FSW 6.0GA, then tested with a browser:
http://localhost:8080/icc/test/aaa/dummy // checks application 1
http://localhost:8080/icc/test/bbb/dummy // checks application 2
These can be deployed to FSW 6.0GA, they can be invoked in any order and all is well. They return proper responses to the browser.
Deploy the same applications to Roll up 3, we see that invoking application 2 gets an Exception on invocation. (Null Pointer at at org.switchyard.component.resteasy.InboundHandler.invoke(InboundHandler.java:129) [switchyard-component-resteasy-1.1.1-p8-redhat-1.jar:1.1.1-p8-redhat-1]
If we deploy application 2 after app 1, then app 2 is ok but 1 is broken.
Deploy app 1 again, then 1 is ok and 2 is broken. Last application deployed 'wins', the other loses.
Created attachment 997241 [details]
Test App 1.
Created attachment 997244 [details]
Test App 2.
This is an inherent problem with any web container. You cannot share the same context path between applications.
I understand your point, but please note that you CAN indeed share the same context path between applications in FSW 6.0. So the current behaviour may be regarded as a correct one, but it still introduces an incompatibility from the old version.
We think it's ideal to keep backward compatibility as much as possible.
You are right. It worked in FSW 6.0. I have narrowed down the commit to this:
This looks like it doesn't cater to the domain. I am yet to verify if this is removed if it would break https://bugzilla.redhat.com/show_bug.cgi?id=1094865. Since SWITCHYARD-2351 covers most other things in camel, have to check if all the BZs associated with 1094865 is covered. If not 2124 needs some rework. Will update soon.
I confirmed that the replicator attached here works.
I will send a PR removing the 2124 commits. Please let me know if any more issues after removing the commits.