Peter Bright <[EMAIL PROTECTED]> wrote on 02/04/2004 11:51:47 PM: > > Just out of curiosity, what is the stupid thing that the 1.4 > > ear plugin > > does with ear.bundle? > Not stick them into application.xml. It doesn't stick things into > application.xml with the result that projects that previously worked cease > to do so.
It's not supposed to. That's the issue that cropped up. Somehow people are/were using the <java> element in application.xml to get things on their 'classpath' for WARs and EJBs in the EAR. This is just plain wrong. > > People had been using these for things like commons-logging, > > which was > > clearly wrong. > The flip-side is it appears to be more reliable than setting classpaths in > the parts that /are/ modules (AFAIK the "proper" way of doing this). This > is quite a compelling feature; reliable and wrong is generally better than > unreliable and notionally "correct". So placing the jars in MANIFEST.MF using Class-Path doesn't work for some containers? What's their preferred way of specifying the classpath for a WAR or EJB then??? -- dIon Gillard, Multitask Consulting
