I would appreciate if any one has deal with similar issue as above. I would appreciate your input.
Thanks, Bhavesh On Tue, Jun 16, 2015 at 11:55 AM, Bhavesh Mistry <mistry.p.bhav...@gmail.com > wrote: > Adding Dev group to see how I can achieve this. > > Thanks, > > Bhavesh > > On Mon, Jun 15, 2015 at 2:56 PM, Bhavesh Mistry < > mistry.p.bhav...@gmail.com> wrote: > >> Hi All, >> >> >> >> I am new to Apache Camel and trying to solve following problem with >> routing: >> >> >> >> I have CXF JAX-RS based REST Service implemented and deployed in same JVM >> (end-point). >> >> >> >> I have another set of REST Service that is not within same Java Process >> it is in (python or any other Process but on same host). >> >> >> >> >> >> We have unified port to access both services, for example, >> >> >> >> Client call ----> HTTP Rest call (*8080*) ----- Camel Route( >> if(“/java_api/” >> ----> to(http://localhost:*9090*) else { to (http://localhost:9091 (OLD >> Services)} >> >> >> >> >> >> <cxf:rsServer id="javaRestServer" address=" >> http://localhost:9090/java_api" >> >> loggingFeatureEnabled="true" >> >> serviceClass="…." > >> >> <cxf:providers> >> >> <ref bean="jaxbProvider" /> >> >> <ref bean="jsonProvider" /> >> >> </cxf:providers> >> >> <cxf:serviceBeans> >> >> <ref bean="myService"/> >> >> </cxf:serviceBeans> >> >> </cxf:rsServer> >> >> >> >> >> >> The problem with this approach is there is unnecessary http call for Java >> API(java_api) route since it is already locally hosted and we do not want >> to incur HTTP call. >> >> >> >> This has been done to set-up all the CXF context and be able to server >> REST service. >> >> >> >> So, my questions are: >> >> >> >> 1) 1) Is there any way to setup route to call cxf local binding JAX-RS >> (direct call) rather then http call for Java API ? >> >> 2) 2) How can I configure route such a way so HTTP Proxy headers (e.g >> *X-Forwarded-For >> *) gets passed to old Service API ? Since, Java Layer is indeed acting >> as proxy server. >> >> >> Thanks in advance for your help ! >> >> >> Thanks, >> >> >> >> Bhavesh >> >> >> > >