NetWeaver jar versioning handling

Question

Hi
While trying to deploy my application on netwaver 7.1 i'm getting errors that indicates that app server cant handle a version number in a jar file name.
For instance an error:
"Class-path entry activation.jar specified in (...) MANIFEST.MF file cannot be resolved."
although activation-1.1.jar exists on the class path. Once the the version suffix is removed it doesn't complain.
is there any solution for that, besides changing jar names?
Br
PF

Answer 1

Hi
I think the problem lays somewhere else.
My application works fine under jboss, but its because it doesn't check manifests recursively - in other words, the class-path entries located in the jars, which are in the ear below the top level are ignored.
To make things more clear
my-app.ear
    META-INF/application.xml
    my-ejb.jar
        META-INF/MANIFEST.MF Class-Path: ext/lib1.jar
        tld/domain/MyEJB.class
        tld/domain/MyEJBRemote.class
        tld/domain/MyEJBRemoteHome.class
        ext/lib1.jar
           META-INF/MANIFEST.MF Class-Path: lib2.jar
            tld/domain/A.class
         ext/lib2-1.0.jar
            tld/domain/B.class
Neither the j2EE or the ejb spec talks about recursively
solving all jar dependencies, therfore jboss only checks my-ejb.jar/maniifest.mf (top level - as stated before).
However netwevaer does smth. different - checks them all.
Most of the jars contains a manifest that reffers through a class-path entries to other jars without a version suffix - and here is the root cause of my problem.
How can i avoid this recursive check?
Br
PF