After quickly reading the J2EE 1.4 spec, section "J2EE.8.2 Optional
Package Support", page 121, a JAR (jar/war/rar) can have a Class-Path
entry in the META-INF/MANIFEST.MF file that refers to other JARs.
So AFAIK, this should be supported. It would be worth checking that any
relative paths specified in your Class-Path entry are actually valid
when your application is deployed (the spec says the deployment tool
should install JAR files in a way that preserves relative references).
In other words, check whether hello-utility.jar is in the same directory
as the war file that is refering to it in the deployed files (under
geronimo\repository\yourGroupId\.....) . If you didn't specify a
groupId in your deployment plan, then look under
geronimo\repository\default\.....
Regards,
John
toby cabot wrote:
Hi Folks,
I'm fooling around with a 1.1 build and trying to get my little
"hello, world" application to deploy and run. It mostly does (much
thanks to the plan conversion utility) but one feature doesn't seem to
work as it used to.
My EAR has (among other stuff) a webapp in a war, and a jar with some
utility classes in it. In 1.0 I could put the utility jar name in the
war's manifest.mf file like so:
Class-Path: hello-utility.jar
... and the classes in hello-utility.jar would be visible to the
servlets in the war. In 1.1 this doesn't seem to work (I get
NoClassDefFoundError exceptions at deploy-time).
Now I'm not sure if what I was doing was J2EE-kosher to begin with so
if not that's cool. But if it's *supposed* to work I'm not sure that
it does anymore.
Thanks,
Toby
