I?m new to FUSE and trying to develop some use cases using FID 1.2.1 / EIP projects.
Can someone tell me, what are the external JARs that I should add to the build path for each camel processor, endpoints?
cxf-manifest.jar from fuse-services-framework installation
Stax.jar from fuse-message-broker installation.
Jaxb-impl.jar from fuse-message-broker installation.
And also we add the project if the service implementation is available in different project.
FTP Endpoint: you have to add commons-net-2.0.jar
HTTP Endpoint you have to add the below jars
commons-io.jar from fuse-esb installation
commons-httpclient.jar from fuse-services-framework installation
commons-codec.jar from fuse-services-framework installation
camel-http.jar from fuse-mediation-router installation
To deploy the EIP in the FUSE ESB Server we don't have exact jars to be added.It depends on the route we build.
But to work with some patterns like CBR, Aggregator etc in FUSE ESB 4.x version we need to add below jars
activemq-all.jar from fuse-message-broker installation.
spring-2.5.5.jar from fuse-services-framework installation
I installed Fuse ESB and Fuse IDE.
I'm trying to add activemq-all.jar to my buildpath in order to use a jms-endpoint.
Maybe a stupid question, but where can I find this jar? Do I need to install Fuse Message Broker, just to have this file?
Other question, I installed Fuse Message Broker and I'm trying to add the jar that I found here? Is it just by adding an external jar to the project doing "> Configure Build Path > Libraries > Add External Jar"?
Do I need to do something else so that this jar is added to my bundle or does it refresh automatically on the fuse server?
The camel-mina component provides for the tcp, udp, mcast, multicast and vm protocols, so you have picked the correct Camel component jar. This component depends on Apache Mina, so you should also include the mina-core jar on the classpath.
2, 3 & 4 were not present in any of the FUSE installation (ESB, MQ, CXF & Router). Copying of such libraries (not present in FUSE installation) is expected?
This is a side-effect of using Maven as the core building mechanism for the FUSE software. Since Maven is smart enough to go and find the correctly versioned dependencies, we don't ship them by default. This keeps your download size smaller.
Yes, it can be a nuisance at times, but in most cases (so far) it has been ok.