Re: JSP Precompile and WebSphere
Hy Jerry,
this is my only war-Project in Workspace. I'ts the only maven-Project in
Workspace.
Robert
Jerry Thome schrieb:
> We have a simple web app. We test locally using Tomcat and then deploy
> through various lifecycles which run WebSphere 6.1. Our JSP precompile
> process doesn't do anything IBM / WAS specific. Some of our JSPs are very
> simple, and some are used by Spring.
>
> We followed the instructions exactly as outlined here:
> http://mojo.codehaus.org/jspc-maven-plugin/usage.html Well, we are using
> JDK 1.5 so we specify that via properties.
>
>
> org.codehaus.mojo
> jspc-maven-plugin
>
>
> jspc
>
> compile
>
>
> ${compileSource}
> ${compileSource}
> ${compileSource}
>
>
>
>
>
> org.apache.maven.plugins
> maven-war-plugin
>
> ${basedir}/target/jspweb.xml
>
>
>
>
> Then, depending on the J2EE spec you're using, you need to include the
> right dependencies. Make sure to include the jsp-runtime jar too.
>
>
>javax.servlet
>jsp-api
>2.0
>provided
>
>
> javax.servlet
> jstl
> 1.1.2
>
>
> taglibs
> standard
> 1.1.2
>
>
>
> tomcat
> jasper-runtime
> 5.5.15
>
>
> We didn't change the WAS deployment descripters either. Prior to using
> this precompile feature, we let WebSphere auto-compile.
>
> I won't guarantee this will work for you, but this is all that we did.
>
> Good luck.
>
>
>
>
>
> asokan02
>
> 04/07/2009 10:06 AM
> Please respond to
> "Maven Users List"
>
>
>
> To
> users@maven.apache.org
> cc
>
> Subject
> RE: JSP Precompile and WebSphere
>
>
>
>
>
>
>
> Hello Jerry
>
> Is it possible to precompile JSPs for WebSphere using the jspc-maven
> plugin without a WebSphere installation on the machine that the comipation
> is done on? We do not have WAS installed on the our continuum servers and
> hence have been stuck compiling JSPs at deployment time. IBM's response
> to our question was that the only option is to run the jspBatch compiler
> that comes with WAS6.1. Could you please post the details of how you got
> the jspc-maven plugin to precompile JSPs for WebSphere?
>
> Thanks
>
>
>
> BTW, thanks for the info Martin.
>
> To follow-up, we had to add a couple dependencies to the WAR in order for
> the precompiled JSPs to work under WebSphere. That's it. The JSP
> servlets generated from WebSphere were a bit different than what's
> generated by our Maven2 project. The source extends different classes.
> Since our classes now extend org.apache.jasper.runtime.HttpJspBase and not
>
> IBM HttpJspBase classes, we had to add the jasper-runtime dependency...
> and maybe 1 or 2 others.
>
> So, not a big deal. It makes sense, I just had to think through it.
>
> Thanks.
>
>
>
>
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: JSP Precompile and WebSphere
We have a simple web app. We test locally using Tomcat and then deploy
through various lifecycles which run WebSphere 6.1. Our JSP precompile
process doesn't do anything IBM / WAS specific. Some of our JSPs are very
simple, and some are used by Spring.
We followed the instructions exactly as outlined here:
http://mojo.codehaus.org/jspc-maven-plugin/usage.html Well, we are using
JDK 1.5 so we specify that via properties.
org.codehaus.mojo
jspc-maven-plugin
jspc
compile
${compileSource}
${compileSource}
${compileSource}
org.apache.maven.plugins
maven-war-plugin
${basedir}/target/jspweb.xml
Then, depending on the J2EE spec you're using, you need to include the
right dependencies. Make sure to include the jsp-runtime jar too.
javax.servlet
jsp-api
2.0
provided
javax.servlet
jstl
1.1.2
taglibs
standard
1.1.2
tomcat
jasper-runtime
5.5.15
We didn't change the WAS deployment descripters either. Prior to using
this precompile feature, we let WebSphere auto-compile.
I won't guarantee this will work for you, but this is all that we did.
Good luck.
asokan02
04/07/2009 10:06 AM
Please respond to
"Maven Users List"
To
users@maven.apache.org
cc
Subject
RE: JSP Precompile and WebSphere
Hello Jerry
Is it possible to precompile JSPs for WebSphere using the jspc-maven
plugin without a WebSphere installation on the machine that the comipation
is done on? We do not have WAS installed on the our continuum servers and
hence have been stuck compiling JSPs at deployment time. IBM's response
to our question was that the only option is to run the jspBatch compiler
that comes with WAS6.1. Could you please post the details of how you got
the jspc-maven plugin to precompile JSPs for WebSphere?
Thanks
BTW, thanks for the info Martin.
To follow-up, we had to add a couple dependencies to the WAR in order for
the precompiled JSPs to work under WebSphere. That's it. The JSP
servlets generated from WebSphere were a bit different than what's
generated by our Maven2 project. The source extends different classes.
Since our classes now extend org.apache.jasper.runtime.HttpJspBase and not
IBM HttpJspBase classes, we had to add the jasper-runtime dependency...
and maybe 1 or 2 others.
So, not a big deal. It makes sense, I just had to think through it.
Thanks.
--
View this message in context:
http://n2.nabble.com/JSP-Precompile-and-WebSphere-tp2534484p2599460.html
Sent from the maven users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient is strictly prohibited. All messages
sent to and from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with our internal policies
and to protect our business. E-mails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, lost or destroyed, or
contain viruses. You are deemed to have accepted these risks if you communicate
with us by e-mail.
RE: JSP Precompile and WebSphere
Hello Jerry Is it possible to precompile JSPs for WebSphere using the jspc-maven plugin without a WebSphere installation on the machine that the comipation is done on? We do not have WAS installed on the our continuum servers and hence have been stuck compiling JSPs at deployment time. IBM's response to our question was that the only option is to run the jspBatch compiler that comes with WAS6.1. Could you please post the details of how you got the jspc-maven plugin to precompile JSPs for WebSphere? Thanks BTW, thanks for the info Martin. To follow-up, we had to add a couple dependencies to the WAR in order for the precompiled JSPs to work under WebSphere. That's it. The JSP servlets generated from WebSphere were a bit different than what's generated by our Maven2 project. The source extends different classes. Since our classes now extend org.apache.jasper.runtime.HttpJspBase and not IBM HttpJspBase classes, we had to add the jasper-runtime dependency... and maybe 1 or 2 others. So, not a big deal. It makes sense, I just had to think through it. Thanks. -- View this message in context: http://n2.nabble.com/JSP-Precompile-and-WebSphere-tp2534484p2599460.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: JSP Precompile and WebSphere
BTW, thanks for the info Martin. To follow-up, we had to add a couple dependencies to the WAR in order for the precompiled JSPs to work under WebSphere. That's it. The JSP servlets generated from WebSphere were a bit different than what's generated by our Maven2 project. The source extends different classes. Since our classes now extend org.apache.jasper.runtime.HttpJspBase and not IBM HttpJspBase classes, we had to add the jasper-runtime dependency... and maybe 1 or 2 others. So, not a big deal. It makes sense, I just had to think through it. Thanks. "Martin Gainty" 03/25/2009 04:28 PM Please respond to "Maven Users List" To users@maven.apache.org cc Subject RE: JSP Precompile and WebSphere Here is what I found for Websphere documentation for JSPCBuild.xml /**WINDOWS***/ Windows: ant -Dwas.home=%WAS_HOME% -Dear.path=%EAR_PATH% -Dextract.dir=%EXTRACT_DIR% Windows: ant jspc2 -Dwas.home=%WAS_HOME% -Dapp.name=%APP_NAME% -Dwebmodule.name=%MOD_NAME% Windows: ant jspc3 -Dwas.home=%WAS_HOME% -Dapp.name=%APP_NAME% -Dwebmodule.name=%MOD_NAME% -Ddir.name=%DIR_NAME% /UNIX***/ Unix: ant -Dwas.home=$WAS_HOME -Dear.path=$EAR_PATH -Dextract.dir=$EXTRACT_DIR Unix: ant jspc2 -Dwas.home=$WAS_HOME -Dapp.name=$APP_NAME -Dwebmodule.name=$MOD_NAME Unix: ant jspc3 -Dwas.home=$WAS_HOME -Dapp.name=$APP_NAME -Dwebmodule.name=$MOD_NAME -Ddir.name=$DIR_NAME /*JSPCBuild.xml from websphere displayed for your edification**/ HTH Martin __ Disclaimer and confidentiality note This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided. > To: users@maven.apache.org > Subject: JSP Precompile and WebSphere > From: jerry.th...@hewitt.com > Date: Wed, 25 Mar 2009 14:15:30 -0500 > > I have a project where we need to precompile JSPs. I have followed the > instructions here: http://mojo.codehaus.org/jspc-maven-plugin/usage.html > > We are servlet spec 2.4, JDK 1.5. Works great. Deploys and runs under my > local Tomcat without problems. > > Under WebSphere however is where we encounter an issue. > > SRVE0206E: This error typically implies that the servlet was originally > compiled with classes which cannot be located by the server. > SRVE0187E: Check your classpath to ensure that all classes required by the > servlet are present.SRVE0210I: This problem can be debugged by recompiling > the servlet using only the classes in the application's runtime classpath > SRVE0234I: Application classpath=[...]... > > Unfortunately, it doesn't tell me what file it is missing. Right now, I'm > going down the route that the generated source is different than what > would have been generated by WebSphere. I'm trying to get a generated JSP > from our dev server from a prior deployment now to compare > > Generated from Maven2 project... > public final class error_jsp extends org.apache.jasper.runtime.HttpJspBase > implements org.apache.jasper.runtime.JspSourceDependent > > I'm suspecting I need to include a Jasper jar or somehow change what is > generated during the build process. > > While I'm in limbo, just thought I would reach out and see if anyone else > encountered this situation before. > > Thanks. > > > > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. > >
RE: JSP Precompile and WebSphere
Here is what I found for Websphere documentation for JSPCBuild.xml /**WINDOWS***/ Windows: ant -Dwas.home=%WAS_HOME% -Dear.path=%EAR_PATH% -Dextract.dir=%EXTRACT_DIR% Windows: ant jspc2 -Dwas.home=%WAS_HOME% -Dapp.name=%APP_NAME% -Dwebmodule.name=%MOD_NAME% Windows: ant jspc3 -Dwas.home=%WAS_HOME% -Dapp.name=%APP_NAME% -Dwebmodule.name=%MOD_NAME% -Ddir.name=%DIR_NAME% /UNIX***/ Unix: ant -Dwas.home=$WAS_HOME -Dear.path=$EAR_PATH -Dextract.dir=$EXTRACT_DIR Unix: ant jspc2 -Dwas.home=$WAS_HOME -Dapp.name=$APP_NAME -Dwebmodule.name=$MOD_NAME Unix: ant jspc3 -Dwas.home=$WAS_HOME -Dapp.name=$APP_NAME -Dwebmodule.name=$MOD_NAME -Ddir.name=$DIR_NAME /*JSPCBuild.xml from websphere displayed for your edification**/ HTH Martin __ Disclaimer and confidentiality note This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided. > To: users@maven.apache.org > Subject: JSP Precompile and WebSphere > From: jerry.th...@hewitt.com > Date: Wed, 25 Mar 2009 14:15:30 -0500 > > I have a project where we need to precompile JSPs. I have followed the > instructions here: http://mojo.codehaus.org/jspc-maven-plugin/usage.html > > We are servlet spec 2.4, JDK 1.5. Works great. Deploys and runs under my > local Tomcat without problems. > > Under WebSphere however is where we encounter an issue. > > SRVE0206E: This error typically implies that the servlet was originally > compiled with classes which cannot be located by the server. > SRVE0187E: Check your classpath to ensure that all classes required by the > servlet are present.SRVE0210I: This problem can be debugged by recompiling > the servlet using only the classes in the application's runtime classpath > SRVE0234I: Application classpath=[...]... > > Unfortunately, it doesn't tell me what file it is missing. Right now, I'm > going down the route that the generated source is different than what > would have been generated by WebSphere. I'm trying to get a generated JSP > from our dev server from a prior deployment now to compare > > Generated from Maven2 project... > public final class error_jsp extends org.apache.jasper.runtime.HttpJspBase > implements org.apache.jasper.runtime.JspSourceDependent > > I'm suspecting I need to include a Jasper jar or somehow change what is > generated during the build process. > > While I'm in limbo, just thought I would reach out and see if anyone else > encountered this situation before. > > Thanks. > > > > The information contained in this e-mail and any accompanying documents may > contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if this > message has been addressed to you in error, please immediately alert the > sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents of > this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure compliance > with our internal policies and to protect our business. E-mails are not > secure and cannot be guaranteed to be error free as they can be intercepted, > amended, lost or destroyed, or contain viruses. You are deemed to have > accepted these risks if you communicate with us by e-mail. > > _ Express your personality in color! Preview and select themes for Hotmail®. http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=TXT_MSGTX_WL_HM_express_032009#colortheme
Re: Jsp precompile
Stefanie, take a look at the mail headers (I'm certain , in particular In-Reply-To: In-Reply-To: <[EMAIL PROTECTED]> This tells mail clients "all of these emails are related, so you should organize them as such." You can see this data in the gmx.net web interface by clicking the little envelope in the top-right corner above ins Adressbuch which has the tooltip label Ausdruck der Header-Informationen, just below Hilfe. Please create a BRAND NEW email every time you want to start a new topic by simply creating a new email to the Maven Users list. DO NOT reply to another one, unless you want to continue that discussion. Wayne On 3/3/08, Martin Höller <[EMAIL PROTECTED]> wrote: > On Monday 03 March 2008 wrote [EMAIL PROTECTED]: > > > firstly, and again: Do NOT just reply to a random message from the > > > > > > mailing list when you start a new topic. Write a NEW MAIL to the > > > mailing list. > > > > I don't understand. I used the [EMAIL PROTECTED] mail adress, but I changed > > the topic. So it should be a new topic, shouldn't it?? > > No it shouldn't! Have a look at > http://www.nabble.com/how-do-i-generate-my-first-maven-2.x-project--to15773087s177.html > to see how most proper mail clients show this thread. > > > I can't image the > > mail adress would "remember" what it was last used to, right??? > > As Stefan wrote, there are mail header fields that reference previous mails > from this thread, so just don't use the reply button if you do not reply. > > thx, > - martin > -- > Martin Höller | [EMAIL PROTECTED] > *x Software + Systeme | http://www.xss.co.at/ > Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 > A-1100 Vienna, Austria | Fax: +43-1-6060114-71 > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jsp precompile
On Monday 03 March 2008 wrote [EMAIL PROTECTED]: > > firstly, and again: Do NOT just reply to a random message from the > > > > mailing list when you start a new topic. Write a NEW MAIL to the > > mailing list. > > I don't understand. I used the [EMAIL PROTECTED] mail adress, but I changed > the topic. So it should be a new topic, shouldn't it?? No it shouldn't! Have a look at http://www.nabble.com/how-do-i-generate-my-first-maven-2.x-project--to15773087s177.html to see how most proper mail clients show this thread. > I can't image the > mail adress would "remember" what it was last used to, right??? As Stefan wrote, there are mail header fields that reference previous mails from this thread, so just don't use the reply button if you do not reply. thx, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 signature.asc Description: This is a digitally signed message part.
Re: Jsp precompile
[EMAIL PROTECTED] wrote:
firstly, and again: Do NOT just reply to a random message from the
mailing list when you start a new topic. Write a NEW MAIL to the mailing
list.
I don't understand. I used the [EMAIL PROTECTED] mail adress, but I changed the topic. So
it should be a new topic, shouldn't it?? I can't image the mail adress would
"remember" what it was last used to, right???
--
Ok, I saw too late that the old "subject" line was wrong already.
Anyway, in most mail clients, when you "reply" to a message, a header
field "In-Reply-To" is set into the mail with either all (of this
thread) or the latest message ids of the message(s) you replied to.
Then again, the mail client looks into this header field to determine
whether the message should be displayed in the same thread or in a new
thread. Thus, you can change the subject but the mail client will still
think that it is the same thread because of the "In-Reply-To" header field.
In Thunderbird for example, you can click "View", "Sort By", "Threaded"
to see what I mean.
Your web.xml needs to be in
src/main/webapp/WEB-INF,
Well, as we are moving from Maven 1.1 I was told to first move the project as
it is - using the (legacy) project structure in this first migration step.
Therefore, I can't yet use src/main/webapp/WEB-INF. My web.xml
is in src/war/WEB-INF, and when it's copied to the target folder, it will be in
/target/MY_WAR_FILE_NAME/WEB-INF.
Ok, one questions: is the war assembled correctly (including web.xml)?
There must be some option to alter the default path, right??
You saw the text in jspc maven plugin doc:
${basedir}/target/jspweb.xml
...
There you can set the path. Anyway, you wrote you didn't want to let the
compiler plugin modify the web.xml IIUC? But then the compilation is not
in effect, because within the web.xml the /...jsp are mapped to the
compiled ones, so I think you will need to let that happen if you want
to use the precompiled JSPs.
--
best regards,
Stefan Seidel
software developer
VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail. [EMAIL PROTECTED]
web.www.vub.de
HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jsp precompile
firstly, and again: Do NOT just reply to a random message from the > mailing list when you start a new topic. Write a NEW MAIL to the mailing > list. I don't understand. I used the [EMAIL PROTECTED] mail adress, but I changed the topic. So it should be a new topic, shouldn't it?? I can't image the mail adress would "remember" what it was last used to, right??? -- >Your web.xml needs to be in > src/main/webapp/WEB-INF, Well, as we are moving from Maven 1.1 I was told to first move the project as it is - using the (legacy) project structure in this first migration step. Therefore, I can't yet use src/main/webapp/WEB-INF. My web.xml is in src/war/WEB-INF, and when it's copied to the target folder, it will be in /target/MY_WAR_FILE_NAME/WEB-INF. There must be some option to alter the default path, right?? Thanks in advance, Stefanie -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jsp precompile
[EMAIL PROTECTED] wrote: Hi, Hi, firstly, and again: Do NOT just reply to a random message from the mailing list when you start a new topic. Write a NEW MAIL to the mailing list. Trying to precompile Jsp's but can't get it to work. I tried the plugins: Maven jspc plugin: http://mojo.codehaus.org/jspc-maven-plugin/usage.html We're using that one too. Your web.xml needs to be in src/main/webapp/WEB-INF, and is from there on copied automatically to whatever you specify in the maven-war-plugin. Which version of the jspc-maven-plugin are you using? 1.4.6 works great here. regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jsp precompile with war overlay
franz see wrote: > > Good day to you, George, > > My guess is that maven got confused since you declared maven-war-plugin > twice in the build section. You may want to combine both execution under > one and differentiate one from the other by using an . > > Something like this... > > > [snip] > > > Cheers, > Franz > > That works perfectly! Many thanks Franz. A good day indeed! George -- View this message in context: http://www.nabble.com/jsp-precompile-with-war-overlay-tf3187860s177.html#a8875042 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jsp precompile with war overlay
Good day to you, George,
My guess is that maven got confused since you declared maven-war-plugin
twice in the build section. You may want to combine both execution under one
and differentiate one from the other by using an .
Something like this...
org.apache.maven.plugins
maven-war-plugin
build-directory-tree
process-resources
exploded
build-war
package
war
${basedir}/target/jspweb.xml
org.codehaus.mojo
jspc-maven-plugin
1.4.6
${basedir}/target/${artifactId}-${version}
compile
Cheers,
Franz
George Berger wrote:
>
>
> Jörg Schaible wrote:
>>
>>
>> Can't you simply exclude the web.xml from the overlay?
>>
>>
>> maven-war-plugin
>>
>>WEB-INF/web.xml
>>
>>
>>
>> - Jörg
>>
>>
>
> Hi Jörg -
>
> Thanks for the suggestion. I tried it but got the same result.
>
> What I want the plugin to do is use the web.xml file generated by jspc,
> which is what this configuration tries to do:
>
> maven-war-plugin
>
> ${basedir}/target/jspweb.xml
>
>
> I found that this works fine if I'm just doing the precompile and the war
> packaging -- the jspc-generated jspweb.xml file gets used as the web.xml
> in the packaged war. But when I add the additional declaration to the pom
> to run the war:exploded goal during the process-resources phase, the final
> packaging uses the web.xml from the src/main/webapp tree instead. Any
> idea why the above configuration works in the first case but not in the
> second?
>
> George
>
>
--
View this message in context:
http://www.nabble.com/jsp-precompile-with-war-overlay-tf3187860s177.html#a8869466
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: jsp precompile with war overlay
Jörg Schaible wrote:
>
>
> Can't you simply exclude the web.xml from the overlay?
>
>
> maven-war-plugin
>
>WEB-INF/web.xml
>
>
>
> - Jörg
>
>
Hi Jörg -
Thanks for the suggestion. I tried it but got the same result.
What I want the plugin to do is use the web.xml file generated by jspc,
which is what this configuration tries to do:
maven-war-plugin
${basedir}/target/jspweb.xml
I found that this works fine if I'm just doing the precompile and the war
packaging -- the jspc-generated jspweb.xml file gets used as the web.xml in
the packaged war. But when I add the additional declaration to the pom to
run the war:exploded goal during the process-resources phase, the final
packaging uses the web.xml from the src/main/webapp tree instead. Any idea
why the above configuration works in the first case but not in the second?
George
--
View this message in context:
http://www.nabble.com/jsp-precompile-with-war-overlay-tf3187860s177.html#a8867524
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: jsp precompile with war overlay
George Berger wrote on Wednesday, February 07, 2007 5:02 PM: > I'm trying to use the war overlay feature of maven-war-plugin > to include some > common JSPs (e.g. common header and footer files) in multiple > projects, but I also want to use jspc-maven-plugin to precompile the > project JSPs. [snip] > This works great, almost: the overlaid war directory gets > created, jspc > precompiles its JSPs, and the war plugin creates the final > war containing > all the precompiled JSP classes in its WEB-INF/classes directory. > > The only problem is that the war contains the original web.xml from > src/main/webapps/WEB-INF instead of the rewritten version > created by jspc, > even though the configuration to use the rewritten one still > exists in the > second maven-war-plugin declaration. > > Any ideas why this is happening or how to get around it? Can't you simply exclude the web.xml from the overlay? maven-war-plugin WEB-INF/web.xml - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
