I see that jaxen.jar is not included in AS50. Therefore the current jbpem-bpel.sar (1.1.0-Beta4) which also does not include jaxen anymore but depends on it does not run in AS50 What other component uses jaxen? If there is none, then jbpem-bpel.sar should include jaxen.jar More generally, I suggest we radically remove all thirdparty jars that are not referenced from component-info.xml and make it a requirement that a component declares its dependencies. This should avoid the problem of carrying over stale thirdparty jars that nobody knows what they are used for. In other words, to answer the question: What component uses jar X? I only need to scan the component-info.xml(s) for X cheers -thomas

jdom also has a dependency on jaxen, although it depends on which features of jdom you use (specifically jdom uses jaxen for xpath stuff, although its a weird inter-dependency thing from what i recall). Anyway, Hibernate requires jdom; however, Hibernate itself does not use any of the jaxen-related capabilities of jdom and thus does not require jaxen be present on the classpath for its own use... Thomas Diesler wrote: > I see that jaxen.jar is not included in AS50. Therefore the current > jbpem-bpel.sar (1.1.0-Beta4) which also does not include jaxen anymore > but depends on it does not run in AS50 > > What other component uses jaxen? If there is none, then jbpem-bpel.sar > should include jaxen.jar > > More generally, I suggest we radically remove all thirdparty jars that > are not referenced from component-info.xml and make it a requirement > that a component declares its dependencies. This should avoid the > problem of carrying over stale thirdparty jars that nobody knows what > they are used for. > > In other words, to answer the question: What component uses jar X? I > only need to scan the component-info.xml(s) for X > > cheers > -thomas > >

Alejandro Guizar wrote: > dom4j also uses jaxen to provide xpath features. Don't know if any > other component in AS uses xpath, tough. > > Re: declaring dependencies, how far a component should go? jbpm-bpel > uses hibernate. In turn, hibernate uses cglib (among other stuff). > jbpm-bpel does not use cglib directly, but will not run if cglib is > not present. Should jbpm-bpel declare cglib? > What I think Thomas is suggesting is that jbpm-bpel declare hibernate and hibernate declare cglib. This is how it works in the RPM world by the way. Fernando > -Alejandro > > Steve Ebersole wrote: >> jdom also has a dependency on jaxen, although it depends on which >> features of jdom you use (specifically jdom uses jaxen for xpath >> stuff, although its a weird inter-dependency thing from what i >> recall). Anyway, Hibernate requires jdom; however, Hibernate itself >> does not use any of the jaxen-related capabilities of jdom and thus >> does not require jaxen be present on the classpath for its own use... >> >> Thomas Diesler wrote: >>> I see that jaxen.jar is not included in AS50. Therefore the current >>> jbpem-bpel.sar (1.1.0-Beta4) which also does not include jaxen anymore >>> but depends on it does not run in AS50 >>> >>> What other component uses jaxen? If there is none, then jbpem-bpel.sar >>> should include jaxen.jar >>> >>> More generally, I suggest we radically remove all thirdparty jars that >>> are not referenced from component-info.xml and make it a requirement >>> that a component declares its dependencies. This should avoid the >>> problem of carrying over stale thirdparty jars that nobody knows what >>> they are used for. >>> >>> In other words, to answer the question: What component uses jar X? I >>> only need to scan the component-info.xml(s) for X >>> >>> cheers >>> -thomas >>> >>> > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Not always that simple. For example, everyone here is assuming that hibernate should just declare cglib as a direct dependency. But the truth is that for hibernate, cglib is an "optional" dependency (to borrow the Maven terminology) depending on the features of hibernate you use. In fact, within AS y'all use the javassist-based provider for bytecode services and thus cglib is not really a hibernate dependency at all as AS uses it. At any rate, I was originally simply pointing out that there are other dependency paths for jaxen... Dimitris Andreadis wrote: > Is quite simple actually: every component declares all it's direct > dependencies and whatever tool is used can validate the whole graph. > > Fernando Nasser wrote: _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Alejandro Guizar wrote: > dom4j also uses jaxen to provide xpath features. Don't know if any other > component in AS uses xpath, tough. > > Re: declaring dependencies, how far a component should go? jbpm-bpel > uses hibernate. In turn, hibernate uses cglib (among other stuff). > jbpm-bpel does not use cglib directly, but will not run if cglib is not > present. Should jbpm-bpel declare cglib? > What I think Thomas is suggesting is that jbpm-bpel declare hibernate and hibernate declare cglib. This is how it works in the RPM world by the way. Fernando > -Alejandro > > Steve Ebersole wrote: >> jdom also has a dependency on jaxen, although it depends on which >> features of jdom you use (specifically jdom uses jaxen for xpath >> stuff, although its a weird inter-dependency thing from what i >> recall). Anyway, Hibernate requires jdom; however, Hibernate itself >> does not use any of the jaxen-related capabilities of jdom and thus >> does not require jaxen be present on the classpath for its own use... >> >> Thomas Diesler wrote: >>> I see that jaxen.jar is not included in AS50. Therefore the current >>> jbpem-bpel.sar (1.1.0-Beta4) which also does not include jaxen anymore >>> but depends on it does not run in AS50 >>> >>> What other component uses jaxen? If there is none, then jbpem-bpel.sar >>> should include jaxen.jar >>> >>> More generally, I suggest we radically remove all thirdparty jars that >>> are not referenced from component-info.xml and make it a requirement >>> that a component declares its dependencies. This should avoid the >>> problem of carrying over stale thirdparty jars that nobody knows what >>> they are used for. >>> >>> In other words, to answer the question: What component uses jar X? I >>> only need to scan the component-info.xml(s) for X >>> >>> cheers >>> -thomas >>> >>> > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >