Keith Chapman wrote: > While looking into https://wso2.org/jira/browse/CARBON-781 I noticed > that dropping the quickfixj jars into lib/extensions does not get FIX to > work correctly. It fails to start the FIX transport with a class not > found (Couldnt track whcih class its missing yet). The reason here is > because some jar the quickfixj depends on is not in the system > classpath, I'm sure that its available within some OSGI bundle though. > > This raises the question as to whether we should create a orbit project > for quickfixj and drop these OSGI bundles into carbon instead of > dropping in the plain old jars into lib/extensions. Creating OSGI > bundles is the cleaner solution. > Well, if you happen to drop these jars on to the lib/extensions you will have to put everything required by QFJ to the lib/extensions even things like commons-logging if required by QFJ. So this could be a good solution, may be we can bundle all the required libraries (which are not yet orbit bundles inside carbon) by the QFJ together and export them within a single orbit bundle for the simplicity. I know it is not the proper way of componentizing :-( .
The optimal solution to this is that we automatically make these jars into bundles when you put some legacy jar into a given folder so that they are available for the bundles with DynamicImport-Package header. I guess you have done something along this line isn't it? Thanks, Ruwan > WDYT? Shall I go ahead down that path? > > Thanks, > Keith. > > _______________________________________________ > Carbon-dev mailing list > [EMAIL PROTECTED] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > _______________________________________________ Esb-java-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
