Integrating 3rd party transport library

[domenico <do...@credit-suisse.com>]

I have now come to a stage where I need to connect my route to a 3rd party
transport library. This library consists of 70+ jar files. Soem of them are
propietary, some are just standard stuff such as xalan.jar etc. The jar
files reference each other and even worse, they use config files, XML files,
signatures that should be relative to the jar file.

I have managed to create a nice little component for the transport with a
producer. But now I struggle with all the dependencies. I have started
creating poms for some of the jars, but this is not coming to an end. But
the most critical question is, how do I get all the extra files into the
dependency tree at the right place?

Did I choose the right path here? Do I really need to mavenize the entire
3rd party transport library file by file?

many thanks for any advice.



--
View this message in context: http://camel.465427.n5.nabble.com/Integrating-3rd-party-transport-library-tp5723832.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Integrating 3rd party transport library

[Claus Ibsen <cl...@gmail.com>]

On Mon, Dec 10, 2012 at 11:38 AM, domenico
<do...@credit-suisse.com> wrote:
> I have now come to a stage where I need to connect my route to a 3rd party
> transport library. This library consists of 70+ jar files. Soem of them are
> propietary, some are just standard stuff such as xalan.jar etc. The jar
> files reference each other and even worse, they use config files, XML files,
> signatures that should be relative to the jar file.
>
> I have managed to create a nice little component for the transport with a
> producer. But now I struggle with all the dependencies. I have started
> creating poms for some of the jars, but this is not coming to an end. But
> the most critical question is, how do I get all the extra files into the
> dependency tree at the right place?
>
> Did I choose the right path here? Do I really need to mavenize the entire
> 3rd party transport library file by file?
>
> many thanks for any advice.
>

If the 3rd party is not Maven or OSGi bundles already.
You can also consider putting it all together in a big uber JAR with
all of them.

>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Integrating-3rd-party-transport-library-tp5723832.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen