Can Camel Jetty proxy URL share the webapplication context
- by user1750353
I am struggling with Camel Jetty Proxy Routes. At times, the routes exhibits inconsistent behavior.
My Proxy app deployed with context root "Proxy", however, if give that as the context path for my proxy URL I get service not found error.
If change the Proxy to an arbitrary context such as "Dummy" then the route works. Is that how camel jetty component works?
From Path:
jetty:http://0.0.0.0:6080/Proxy/PurchaseOrder/?matchOnUriPrefix=true&disableStreamCache=true&traceEnabled=true
To Path:
jetty:http://localhost:7001/Provider/PurchaseOrder/?bridgeEndpoint=true&throwExceptionOnFailure=false
Another issue i noticed with jetty is
If deploy both Proxy and Provider on the same app container(same listening port), then the route completely stops working saying "Provider/PurchaseOrder/" service not found.
The only way the routes work is, both routes have to run different ports and the from route shouldn't share the webcontext path.
I have requirement that if required I should be a able run both Proxy and Provider on the same container.
Any help appreciated.
Thanks,
