Markus KARG wrote on Wednesday, September 20, 2006 10:49 AM: >> Then all the Sun JRE's are buggy. Sorry, I am using exactly > this artifact for a long time now without ever noticing that > weird classpath entry. The only time it is respected is when > you start the jar as app: >> >> java -jar my.jar >> >> In this case your classpath theory applies. The situation is > different on app servers though ... but far from consistent. >> >> >> > Try using FOP as a dependency in a EJB, package it as an EAR, > and you'll > soon see that it complains about the missing JARs -- since > EJB packager > downloads the pom.xml dependencies while runtime uses the Class-Path > entries. Just read the J2EE 1.4 spec and you'll learn that > the Sun JRE > is not buggy but your use case is just one of many. Yours is working. > Nice. Mine is not.
As said, the situation is different on AppServers. Neither jBoss nor WebLogic complain. IONA's possibly would, but it's abandonned. WebLogic *does* respect the classpath entry of the EJB artifact itself though. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
