Francois,
There are a lot of dissimiliarities between JBoss and WAS when it comes to
deployment.

The first problem you have is that the application.xml contains jar
references which WAS balks at so you need to:
Modify the maven-ear-plugin\plugin.jelly file, commenting out the following
code:
 <!--             <j:when test="${dep.type=='jar'}">
                <x:element name="module">
                  <x:element name="java">${dep.getArtifact()}</x:element>
                </x:element>
              </j:when>
-->

If the code is commented out properly, this basically says if you see a
"jar" type to NOT include it in the application.xml

The spec actually makes it sound like only application client jars should
be included in the application.xml file, not just any jars.  You don't want
to remove the jars from the ear bundle, because you do want them there, you
just don't want them in the application.xml file.

What are you doing for the EJB RMI generated code?  WAS expects certain
classes, which you get with WSAD 5.x EJB generation.  Of course, if you are
not doing EJBs, it's not a problem.

Also, to actually tell maven to generate the application.xml, you need to
put this in the project.properties for the EAR project:
maven.ear.appxml.generate=true

- Tom



|---------+---------------------------->
|         |           "Francois Boccou"|
|         |           <francois.boccou@|
|         |           cgey.com>        |
|         |                            |
|         |           03/02/2004 08:47 |
|         |           AM               |
|         |           Please respond to|
|         |           "Maven Users     |
|         |           List"            |
|         |                            |
|---------+---------------------------->
  
>---------------------------------------------------------------------------------------------------------------------|
  |                                                                                    
                                 |
  |       To:       [EMAIL PROTECTED]                                                  
                            |
  |       cc:                                                                          
                                 |
  |       Subject:  From eclipse/maven to WS5.0                                        
                                 |
  
>---------------------------------------------------------------------------------------------------------------------|




Hello,

I have a problem to deploy an ear on websphere 5.0.
I use Eclipse, maven, jboss on my local pc and think goes well for testing
but the deployment to websphere 5.0 goes actually completly wrong and I
don't know where to lead my investigations.

Maven helped me create an ear files thats contains my web application, my
ejbs et some jars.

When I run AAT on this ear , I have the following error :
*** ERROR *** Mon Mar 01 18:10:19 CET 2004    caller:   at
com.ibm.etools.archive.impl.LoadStrategyImpl.openNestedArchive(LoadStrategyI

mpl.java:390)
    com.ibm.etools.archive.exception.OpenFailureException: IWAE0023E Unable
to open module file "vpc-donnees-1.0.jar" in EAR file
"/u04/product/vpc/vpcv2.7/vpc-ear-1.0.ear"
    Stack trace of nested exception:
    com.ibm.etools.archive.exception.OpenFailureException: IWAE0006E
Archive
is not a valid Application Client JAR File because the deployment
descriptor
can not be found (case sensitive): META-INF/application-client.xml

Ok, it seems that META-INF/application-client.xml is missing, but how to
generate this file, for what ?

If someone would show me the path ...

Thanks
François







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to