Problem deploying an EAR

[Massimiliano Ziccardi]

Hi all.

I've some problem deploying on Geronumo an EAR that works beautifully
with jBoss.

The EAR is composed this way:
EAR
   - UTILITY1.jar
   - UTILITY2.jar
   - UTILITY3.jar
   - WEBMODULE.war

The WEBMODULE.war classpath configured inside the WEBMODULE.war
manifes points to the UTILITY jar files with a row like the following:

Manifest-Version: 1.0
Built-By: nandana
Build-Jdk: 1.5.0_08
Class-Path: UTILITY1.jar
 UTILITY2.jar
 UTILITY3.jar
Created-By: Apache Maven
Archiver-Version: Plexus Archiver

The whole EAR is created by Eclipse (the utility projects are simple
Java Projects, added to J2EE module dependencies of EAR and configured
as dependencies for the WAR file).

Geronimo keep on complaining that the manifest is not correct, with a
message like the following:

  org.apache.geronimo.common.DeploymentException: Manifest class path
entries must be a valid jar file, or if it is a directory, all the
files with jar suffix in it must be a valid jar file (JAVAEE 5 Section
8.2):  resolved to targetURI= UTILITY1.jar

Have you any idea?

Thanks,
Massimiliano

[djencks]

That doesn't look like a valid manifest entry for Class-Path... how is  
it generated?

thanks
david jencks

On Oct 14, 2009, at 2:03 AM, Massimiliano Ziccardi wrote:

> Hi all.
>
> I've some problem deploying on Geronumo an EAR that works beautifully
> with jBoss.
>
> The EAR is composed this way:
> EAR
>   - UTILITY1.jar
>   - UTILITY2.jar
>   - UTILITY3.jar
>   - WEBMODULE.war
>
> The WEBMODULE.war classpath configured inside the WEBMODULE.war
> manifes points to the UTILITY jar files with a row like the following:
>
> Manifest-Version: 1.0
> Built-By: nandana
> Build-Jdk: 1.5.0_08
> Class-Path: UTILITY1.jar
> UTILITY2.jar
> UTILITY3.jar
> Created-By: Apache Maven
> Archiver-Version: Plexus Archiver
>
> The whole EAR is created by Eclipse (the utility projects are simple
> Java Projects, added to J2EE module dependencies of EAR and configured
> as dependencies for the WAR file).
>
> Geronimo keep on complaining that the manifest is not correct, with a
> message like the following:
>
>  org.apache.geronimo.common.DeploymentException: Manifest class path
> entries must be a valid jar file, or if it is a directory, all the
> files with jar suffix in it must be a valid jar file (JAVAEE 5 Section
> 8.2):  resolved to targetURI= UTILITY1.jar
>
> Have you any idea?
>
> Thanks,
> Massimiliano

[Massimiliano Ziccardi]

I've solved the problem.

Inside my EAR there was some jars that needs bouncycastle jars...
It seems that Geronimo has some problem when there are signed jars (at
least it had problems with bouncycastle, however I'll indagate
further).

However, now I've a new problem: my web app (deployed inside an EAR)
depends on axis2.
Axis2 depends on commons-fileupload : I always get an

2009-10-15 10:44:49,253 ERROR [WarBasedAxisConfigurator]
org/apache/commons/fileupload/FileUploadException
org.apache.axis2.deployment.DeploymentException:
org/apache/commons/fileupload/FileUploadException
        at org.apache.axis2.deployment.AxisConfigBuilder.processMessageBuilders(AxisConfigBuilder.java:623)
        at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:186)
        at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:615)
        at org.apache.axis2.deployment.WarBasedAxisConfigurator.<init>(WarBasedAxisConfigurator.java:146)
        at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500)
        at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
        at org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.java:54)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1064)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4051)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)
        at org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:63)
        at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:398)
        at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
        at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:251)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)

any idea?

Thanks,
Massimiliano

On Thu, Oct 15, 2009 at 12:26 AM, David Jencks <david_jencks@...> wrote:

> That doesn't look like a valid manifest entry for Class-Path... how is it
> generated?
>
> thanks
> david jencks
>
> On Oct 14, 2009, at 2:03 AM, Massimiliano Ziccardi wrote:
>
>> Hi all.
>>
>> I've some problem deploying on Geronumo an EAR that works beautifully
>> with jBoss.
>>
>> The EAR is composed this way:
>> EAR
>>  - UTILITY1.jar
>>  - UTILITY2.jar
>>  - UTILITY3.jar
>>  - WEBMODULE.war
>>
>> The WEBMODULE.war classpath configured inside the WEBMODULE.war
>> manifes points to the UTILITY jar files with a row like the following:
>>
>> Manifest-Version: 1.0
>> Built-By: nandana
>> Build-Jdk: 1.5.0_08
>> Class-Path: UTILITY1.jar
>> UTILITY2.jar
>> UTILITY3.jar
>> Created-By: Apache Maven
>> Archiver-Version: Plexus Archiver
>>
>> The whole EAR is created by Eclipse (the utility projects are simple
>> Java Projects, added to J2EE module dependencies of EAR and configured
>> as dependencies for the WAR file).
>>
>> Geronimo keep on complaining that the manifest is not correct, with a
>> message like the following:
>>
>>  org.apache.geronimo.common.DeploymentException: Manifest class path
>> entries must be a valid jar file, or if it is a directory, all the
>> files with jar suffix in it must be a valid jar file (JAVAEE 5 Section
>> 8.2):  resolved to targetURI= UTILITY1.jar
>>
>> Have you any idea?
>>
>> Thanks,
>> Massimiliano
>
>

[Massimiliano Ziccardi]

Just to share my solution with you all.

The problem was that geronimo-tomcat already contains an AXIS2
runtime: using the geronimo-jetty bundle everything went ok.