[jbpm-issues] [JBoss JIRA] Created: (JBPM-2556) identify minimal runtime library dependencies

identify minimal runtime library dependencies --------------------------------------------- Key: JBPM-2556 URL: https://jira.jboss.org/jira/browse/JBPM-2556 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.x feedback from a customer: " after trying hard today, I got jBPM4 running in OSGi equinox. I only tested a little functionality with a simple persistent jPDL workflow using HSQL in-memory db. The problem was that the SAXFactory provider could not be configured properly and resulted in a classloader violation exception. Solution was actually simple: I removed all 3rd party libraries that have something to do with XML (e.g. xml-apis.jar) and ship with jBPM4 and from the bundle-classpath. Now I wonder, if the JBPM4 team has an overview of the necessary smallest dependency set for 3rd-party libs in order to OSGi-tify jBPM and these dependend-jars and get the unnecessary rubbish out of the classpath. Hope they can provide some feedback about that. ------------------ I forgot to send you my current MANIFEST which is working with the small example: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: WFTEST Bundle-SymbolicName: WFTEST Bundle-Version: 1.0.0.qualifier Bundle-Activator: wftest.Activator Bundle-ActivationPolicy: lazy Bundle-RequiredExecutionEnvironment: JavaSE-1.6 Import-Package: org.osgi.framework;version="1.3.0" Bundle-ClassPath: lib/activation.jar, lib/antlr.jar, lib/avalon-framework.jar, lib/commons-collections.jar, lib/commons-logging.jar, lib/dom4j.jar, lib/ejb3-persistence.jar, lib/hibernate-annotations.jar, lib/hibernate-cglib-repack.jar, lib/hibernate-commons-annotations.jar, lib/hibernate-core.jar, lib/hibernate-entitymanager.jar, lib/hsqldb.jar, lib/idm-api.jar, lib/idm-common.jar, lib/idm-core.jar, lib/idm-hibernate.jar, lib/idm-spi.jar, lib/javassist.jar, lib/jaxb-api.jar, lib/jaxb-impl.jar, lib/jboss-common-core.jar, lib/jboss-j2ee.jar, lib/jboss-logging-spi.jar, lib/jbosscache-core.jar, lib/jbpm-console-form-plugin.jar, lib/jbpm-console-graphView-plugin.jar, lib/jbpm-console-integration.jar, lib/jbpm-console-reports.jar, lib/jbpm-examples-tests.jar, lib/jbpm-jboss4.jar, lib/jbpm-jboss5.jar, lib/jbpm-spi.jar, lib/jbpm-test-db-tests.jar, lib/jbpm-tomcat6.jar, lib/jbpm.jar, lib/jgroups.jar, lib/jta.jar, lib/jtds.jar, lib/juel-engine.jar, lib/juel-impl.jar, lib/juel.jar, lib/junit.jar, lib/livetribe-jsr223.jar, lib/log4j.jar, lib/logkit.jar, lib/mail.jar, lib/mysql-connector-java.jar, lib/postgresql.jar, lib/servlet-api.jar, lib/slf4j-api.jar, lib/slf4j-jdk14.jar, lib/slf4j-log4j12.jar, lib/standalone-compiler.jar, lib/subethasmtp-smtp.jar, lib/subethasmtp-wiser.jar, . I guess several of these jars could be removed and the remaining could be wrapped in OSGi-Bundle jars. ------------------ " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira