We are using JBOSS FUSE 6.0.0 and program it using Apache Camel routes.A new requirement has come to Proxy a CORBA service as below:
System 1 ---> sends CORBA Request to--> JBOSS Fuse <BR>
JBOSS FuseFuse -->Transforms to SOAP HTTP--> System 2 <BR>
System2 -->Responds in SOAP HTTP---? JBOSS Fuse <BR>
JBOSS Fuse -->Converts SOAP to CORBA --> System 1. <BR>
Just needed your advise ,does anybody tried to use JBOSS Fuse/ Apache Camel as a CORBA Service consumer ?
Current we don't have camel-corba component to access or provide the CORBA service.
If you still want to use camel you may need to let the CORAB implementation use the Camel ProducerTemplate API to send the message to the CamelContext.
Related
Does CXF 3.1.x really uses Apache HttpComponents - HttpClient for http transport? Maven dependencies does not list "Apache HttpComponents" as dependency nor do I see any HttpClient class in the CXF jars? However CXF JIRA CXF-6704 discusses about it?
I need access to HttpClient in CXF for NTLM support per connection basis which CXF by default relies on Java 6+ Authenticator which is set per JVM.
CXF has a decoupled runtime layer. Mostly they start with cxf-rt-*.
In the case of transports, cxf-rt-transports-*.
Take a look at this. I believe that this is the HTTP Components transport runtime.
EDIT: I think this is for asynchronous transport - (looked at the pom after I posted this).
EDIT2: I did a little more research on this and found this documentation. It says that the async client can be used for synchronous calls by setting use.async.http.conduit bus property to true. This also specifically refers to NTLM authentication.
We are trying to connect to MQ resource via activation specification. Referring some of old blog which points the camel JMS uses Spring JMS. Camel JMS have placeholder for messageListenerContainerFactoryRef which uses MessageListenerContainerFactory i.e., org.springframework.jms.listener.AbstractMessageListenerContainer.
We are able to make spring jms to use activation spec to connect to Websphere MQ using org.springframework.jms.listener.endpoint.JmsMessageEndpointManager. Refer Spring JMS and Websphere MQ.
Now I am unable to figure out the way to bridge JmsMessageEndpointManager with AbstractMessageListenerContainer implementation. Any direction regarding the same would be great help.
Do you think that a Spring destination resolver can help you here?
destinationResolver
null
A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).
I need to add the basic authentication for a camel web project, which I use the camel restlet component to expose the REST apis, from the camel documentation Restlet Endpoint with Authentication,
An approach is to use the "restletRealm" setting, I can pass the unit test actually, but encounter the problem when integrate it with the real application:
if I add the host/port in the route DSL, like <from uri="restlet:http://localhost:8080/securedOrders?restletMethod=post&restletRealm=#realm"/>
this will cause the Address already in use error when tomcat startup
If I configure the route DSL like <from uri="restlet:/securedOrders?restletMethod=post&restletRealm=#realm"/>, this will blocking the route process.
Another approach is use the SSL support after camel 2.15.0, but still have the issue about add the host/port to the route DSL.
Any help? Thanks in advance!
ENV:
Camel: 2.15.2
Camel-Restlet: 2.15.2
Spring: 3.2.10.RELEASE
Can Camel connect to Sonic ESB?
I could not find any camel-sonic integration specific example. That's why I am confused if it is possible at all.
Connecting ESBs in general does not require specific transports since ESBs are connectivity software packages. You could probably pick and choose which transport fits you best and get started.
I had a look at Sonic ESB as I have never worked with it. However I can see a couple of ways you can integrate camel routes with the ESB.
Web services: If you are hosting web services on the Sonice ESB camel is more than capable of calling these web services from a camel route.
JMS: If Sonic ESB can host a JMS route (I am sure it can but could be wrong) you can just send JMS messages from your Camel route to the JMS queues hosted by Sonic ESB.
The JBI Component: Some ESB's such as Apache ServiceMix and OpenESB is based on the JBI standard. IF Sonic ESB uses this standard you should be able to send JBI messages directly to the Sonic ESB system.
Hope this gives you some pointers to look at.
This might be obvious but i just still don't understand how i'd do it with ServiceMix :
An external web service http://mypartner.com/service/partnerService
My platform is for example http://myservicemix.com/
I'd like to use OSGI bundles
Is this what i need ? :
A cxfbc:provider (this is the one that talks to the remote service, just a wsdl in the bundle right ?)
A camel route and transformations to bridge the two
A jaxrs:server (i'd like to expose it as a REST service)
The cxfbc is a JBI component. JBI is essentially dead/legacy, so I suggest to not use that for new projects. You can read more about JBI is dead here: http://gnodet.blogspot.com/2010/12/thoughts-about-servicemix.html
So Apache ServiceMix is the server where you can host your Camel applications. So I suggest to look into how to do a webservice proxy with Camel.
For example there is an example with Camel
http://camel.apache.org/cxf-proxy-example.html
That example is OSGi ready and can be deployed in Apache ServiceMix.
Also check out some of the CXF examples that are shipped with Apache ServiceMix, in the examples directory
The Camel CXF component can do both REST and WS.
Also there is the camel-restlet component for REST support as well: http://camel.apache.org/restlet