You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by to...@gi-de.com on 2010/09/10 08:57:24 UTC
Maven *.ear build for SAP Web AS
Hi,
actually we´re trying to get our *.ear built by Maven to be deployable und
executable on SAP Web Application Server.
We run into problems, caused by a classpath in (for example)
<groupId>javax.xml.soap</group>
<artifactId>saaj-api</artifactId>
<version>1.3</version>
This jar has a MANIFEST.MF containing
Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
The application server is complaining about this classpath because Maven
puts the *.jars with their version names into it,
that means jaxp-api-1.4.jar (for example)
=> Is there a way to come around this? Do I have to customize all my
module filenames?
Torsten
RE: Antwort: Re: RE: Maven *.ear build for SAP Web AS
Posted by Martin Gainty <mg...@hotmail.com>.
Torsten
I just took a quick glance at the cargo deployment containers and noticed SAP was missing
Directory of $m2_home/src/main/java/cargo/trunks/core/containers:
geronimo
glassfish
jboss
jetty
jonas
orion
resin
tomcat
weblogic
3,948 pom.xml
apparently SAP container was not considered during the initial development of cargo
if you could file a JIRA we could gauge the work involved to add SAP Container
https://jira.codehaus.org/browse/CARGO
thanks
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> To: users@maven.apache.org
> Subject: Antwort: Re: RE: Maven *.ear build for SAP Web AS
> From: torsten.reinhard@gi-de.com
> Date: Mon, 18 Oct 2010 14:26:04 +0200
>
> that´s our opinion too:-)
> But the problem still exists and the only way to fix that is using a
> sequence of ANT Tasks to manually "repairt" that......
>
> Thanx anyway,
>
> Torsten
>
>
>
>
> Wayne Fay <wa...@gmail.com>
> 10.09.2010 16:06
> Bitte antworten an
> "Maven Users List" <us...@maven.apache.org>
>
>
> An
> Maven Users List <us...@maven.apache.org>
> Kopie
>
> Thema
> Re: RE: Maven *.ear build for SAP Web AS
>
>
>
>
>
>
> > Here´s some more detailed information, where the same problem has
> > appeared:
> >
> > http://forums.sdn.sap.com/message.jspa?messageID=4753421
>
> I've run into this with SAP Web AS (among with a great number of other
> "issues" in wars and ears that otherwise deploy with zero issues on
> all the other major app servers in the market) and all I can say is...
> don't use SAP Web AS unless you have a lot of time and patience to
> deal with these kinds of problems manually.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Antwort: Re: RE: Maven *.ear build for SAP Web AS
Posted by to...@gi-de.com.
that´s our opinion too:-)
But the problem still exists and the only way to fix that is using a
sequence of ANT Tasks to manually "repairt" that......
Thanx anyway,
Torsten
Wayne Fay <wa...@gmail.com>
10.09.2010 16:06
Bitte antworten an
"Maven Users List" <us...@maven.apache.org>
An
Maven Users List <us...@maven.apache.org>
Kopie
Thema
Re: RE: Maven *.ear build for SAP Web AS
> Here´s some more detailed information, where the same problem has
> appeared:
>
> http://forums.sdn.sap.com/message.jspa?messageID=4753421
I've run into this with SAP Web AS (among with a great number of other
"issues" in wars and ears that otherwise deploy with zero issues on
all the other major app servers in the market) and all I can say is...
don't use SAP Web AS unless you have a lot of time and patience to
deal with these kinds of problems manually.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: RE: Maven *.ear build for SAP Web AS
Posted by Wayne Fay <wa...@gmail.com>.
> Here´s some more detailed information, where the same problem has
> appeared:
>
> http://forums.sdn.sap.com/message.jspa?messageID=4753421
I've run into this with SAP Web AS (among with a great number of other
"issues" in wars and ears that otherwise deploy with zero issues on
all the other major app servers in the market) and all I can say is...
don't use SAP Web AS unless you have a lot of time and patience to
deal with these kinds of problems manually.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Antwort: RE: Maven *.ear build for SAP Web AS
Posted by to...@gi-de.com.
Hi,
at first thanx to all replies until now!
Here´s some more detailed information, where the same problem has
appeared:
http://forums.sdn.sap.com/message.jspa?messageID=4753421
In our environment we see:
com.sap.engine.services.library_container.deploy.LCDeploymentException:
[ERROR CODE DPL.LIB.103] Class-path entry jaxb-api.jar specified in
/usr/sap/GZG/J00/j2ee/cluster/server0/temp/deploy/kvkams-ear-SAP.ear1283962052624/lib/jaxb-impl-2.1.9.jar/META-INF/MANIFEST.MF
file cannot be resolved.]
Thanx, Torsten
Martin Gainty <mg...@hotmail.com>
10.09.2010 12:54
Bitte antworten an
"Maven Users List" <us...@maven.apache.org>
An
<us...@maven.apache.org>
Kopie
Thema
RE: Maven *.ear build for SAP Web AS
can you display the error you see when Application Server encounters
Version-specific jars jaxp-api-VERSION.jar jax-qname-VERSION.jar
activation-VERSION.jar servlet-VERSION.jar
does your filesystem accept alpha, dash and numeric characters in jar
filename?
gruss
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
dient lediglich dem Austausch von Informationen und entfaltet keine
rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> To: users@maven.apache.org
> Subject: Maven *.ear build for SAP Web AS
> From: torsten.reinhard@gi-de.com
> Date: Fri, 10 Sep 2010 08:57:24 +0200
>
> Hi,
>
> actually we´re trying to get our *.ear built by Maven to be deployable
und
> executable on SAP Web Application Server.
>
> We run into problems, caused by a classpath in (for example)
>
> <groupId>javax.xml.soap</group>
> <artifactId>saaj-api</artifactId>
> <version>1.3</version>
>
> This jar has a MANIFEST.MF containing
>
> Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
>
> The application server is complaining about this classpath because Maven
> puts the *.jars with their version names into it,
> that means jaxp-api-1.4.jar (for example)
>
> => Is there a way to come around this? Do I have to customize all my
> module filenames?
>
> Torsten
>
RE: Maven *.ear build for SAP Web AS
Posted by Martin Gainty <mg...@hotmail.com>.
can you display the error you see when Application Server encounters Version-specific jars jaxp-api-VERSION.jar jax-qname-VERSION.jar activation-VERSION.jar servlet-VERSION.jar
does your filesystem accept alpha, dash and numeric characters in jar filename?
gruss
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> To: users@maven.apache.org
> Subject: Maven *.ear build for SAP Web AS
> From: torsten.reinhard@gi-de.com
> Date: Fri, 10 Sep 2010 08:57:24 +0200
>
> Hi,
>
> actually we´re trying to get our *.ear built by Maven to be deployable und
> executable on SAP Web Application Server.
>
> We run into problems, caused by a classpath in (for example)
>
> <groupId>javax.xml.soap</group>
> <artifactId>saaj-api</artifactId>
> <version>1.3</version>
>
> This jar has a MANIFEST.MF containing
>
> Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
>
> The application server is complaining about this classpath because Maven
> puts the *.jars with their version names into it,
> that means jaxp-api-1.4.jar (for example)
>
> => Is there a way to come around this? Do I have to customize all my
> module filenames?
>
> Torsten
>
Re: Maven *.ear build for SAP Web AS
Posted by João Ferreira <jt...@gmail.com>.
I think this is his problem...
http://maven.apache.org/plugins/maven-war-plugin/examples/file-name-mapping.html
The ear plugin also has the same option(fileNameMapping) I think:
http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html
2010/9/10 Anders Hammar <an...@hammar.net>:
> No, I believe his problem is that the jar file names in the manifest of that
> jar doesn't match with the actual jar file names on the app server. Not sure
> how to fix this other than patch the saaj-api.jar.
>
> However, I'm somewhat surprised that the app server complains about this as
> I don't think that the classpath in the manifest should be used for Java EE.
> However, I could be wrong...
>
> /Anders
>
> On Fri, Sep 10, 2010 at 09:19, per-henrik hedman <ph...@gmail.com> wrote:
>
>> If I understand you correctly, you are building ear-file and you want
>> to remove certain jars from that ear?
>>
>> You could do that by:
>>
>> <dependency>
>> <groupId>javax.xml.soap</group>
>> <artifactId>saaj-api</artifactId>
>> <version>1.3</version>
>> <exclusions>
>> <exclusion>
>> <groupId>{groupId for jaxp-api}</groupId>
>> <artifactId>jaxp-api.jar</artifactId>
>> <version>1.4</version>
>> </exclusion>
>> </exclusions>
>> </dependency>
>>
>> Cheers,
>> Per-Henrik
>>
>> Don't thi
>> On Fri, Sep 10, 2010 at 8:57 AM, <to...@gi-de.com> wrote:
>> > Hi,
>> >
>> > actually we´re trying to get our *.ear built by Maven to be deployable
>> und
>> > executable on SAP Web Application Server.
>> >
>> > We run into problems, caused by a classpath in (for example)
>> >
>> > <groupId>javax.xml.soap</group>
>> > <artifactId>saaj-api</artifactId>
>> > <version>1.3</version>
>> >
>> > This jar has a MANIFEST.MF containing
>> >
>> > Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
>> >
>> > The application server is complaining about this classpath because Maven
>> > puts the *.jars with their version names into it,
>> > that means jaxp-api-1.4.jar (for example)
>> >
>> > => Is there a way to come around this? Do I have to customize all my
>> > module filenames?
>> >
>> > Torsten
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven *.ear build for SAP Web AS
Posted by Anders Hammar <an...@hammar.net>.
No, I believe his problem is that the jar file names in the manifest of that
jar doesn't match with the actual jar file names on the app server. Not sure
how to fix this other than patch the saaj-api.jar.
However, I'm somewhat surprised that the app server complains about this as
I don't think that the classpath in the manifest should be used for Java EE.
However, I could be wrong...
/Anders
On Fri, Sep 10, 2010 at 09:19, per-henrik hedman <ph...@gmail.com> wrote:
> If I understand you correctly, you are building ear-file and you want
> to remove certain jars from that ear?
>
> You could do that by:
>
> <dependency>
> <groupId>javax.xml.soap</group>
> <artifactId>saaj-api</artifactId>
> <version>1.3</version>
> <exclusions>
> <exclusion>
> <groupId>{groupId for jaxp-api}</groupId>
> <artifactId>jaxp-api.jar</artifactId>
> <version>1.4</version>
> </exclusion>
> </exclusions>
> </dependency>
>
> Cheers,
> Per-Henrik
>
> Don't thi
> On Fri, Sep 10, 2010 at 8:57 AM, <to...@gi-de.com> wrote:
> > Hi,
> >
> > actually we´re trying to get our *.ear built by Maven to be deployable
> und
> > executable on SAP Web Application Server.
> >
> > We run into problems, caused by a classpath in (for example)
> >
> > <groupId>javax.xml.soap</group>
> > <artifactId>saaj-api</artifactId>
> > <version>1.3</version>
> >
> > This jar has a MANIFEST.MF containing
> >
> > Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
> >
> > The application server is complaining about this classpath because Maven
> > puts the *.jars with their version names into it,
> > that means jaxp-api-1.4.jar (for example)
> >
> > => Is there a way to come around this? Do I have to customize all my
> > module filenames?
> >
> > Torsten
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven *.ear build for SAP Web AS
Posted by per-henrik hedman <ph...@gmail.com>.
If I understand you correctly, you are building ear-file and you want
to remove certain jars from that ear?
You could do that by:
<dependency>
<groupId>javax.xml.soap</group>
<artifactId>saaj-api</artifactId>
<version>1.3</version>
<exclusions>
<exclusion>
<groupId>{groupId for jaxp-api}</groupId>
<artifactId>jaxp-api.jar</artifactId>
<version>1.4</version>
</exclusion>
</exclusions>
</dependency>
Cheers,
Per-Henrik
Don't thi
On Fri, Sep 10, 2010 at 8:57 AM, <to...@gi-de.com> wrote:
> Hi,
>
> actually we´re trying to get our *.ear built by Maven to be deployable und
> executable on SAP Web Application Server.
>
> We run into problems, caused by a classpath in (for example)
>
> <groupId>javax.xml.soap</group>
> <artifactId>saaj-api</artifactId>
> <version>1.3</version>
>
> This jar has a MANIFEST.MF containing
>
> Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
>
> The application server is complaining about this classpath because Maven
> puts the *.jars with their version names into it,
> that means jaxp-api-1.4.jar (for example)
>
> => Is there a way to come around this? Do I have to customize all my
> module filenames?
>
> Torsten
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org