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.

Markus
begin:vcard
fn:Markus KARG
n:KARG;Markus
org:QUIPSY QUALITY GmbH;Entwicklung / R & D
adr:;;Stuttgarter Strasse 23;Pforzheim;Baden-Wuerttemberg;75179;Bundesrepublik Deutschland
email;internet:[EMAIL PROTECTED]
title:Staatl. gepr. Inf.
tel;work:+49-7231-9189-52
tel;fax:+49-7231-9189-59
note:QUIPSY(R) Entwicklung / R & D
x-mozilla-html:TRUE
url:http://www.quipsy.de
version:2.1
end:vcard

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to