Still, the main issue that remains is the jsp's.
We have three options here:
- Creating symlinks: this solves the problem in linux. In windows we
would have to copy manually or through a build script/maven extension
the content from outside the project to inside the war. Always a risk
to have
---
HARBOR: http://coolharbor.100free.com/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
Making the Java dream come true.
---
HARBOR: http://coolharbor.100free.com/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
Making the Java dream come true.
Hummm, right, I haven't thought of it. But this would make the whole
deployment process awkward. The generation of the war and it's
expansion would have to be done manually, but it's one more option.
Thanks
Emerson
On 26/02/2008, Johnny Kewl [EMAIL PROTECTED] wrote:
Well, i don't really see the difference regarding security of having
the jsp's separated or not. Even with the JSP's inside the war, once
expanded you could change a JSP without that been detected anyway.
On 20/02/2008, Ralph Goers [EMAIL PROTECTED] wrote:
Right.
The only way access to your
Well, I said at the beginning that I'm not a big fan of this approach,
but I understand the reasons behind it and the difficulties it would
have to change it.
Other reason for using this approach is when you have a great amount
of static content, like images. An update of the war would have to
It got rolled back due to some vetos. (Hence the if your brave comment).
See the dev list for details.
The patch itself works fine.
-Tim
emerson cargnin wrote:
Thanks Tim.
Do you know if this will be included on next release of tomcat6?
regards
emerson
On 19/02/2008, Tim Funk [EMAIL
From: emerson cargnin [mailto:[EMAIL PROTECTED]
Subject: Re: Mapping JSP's to outside of the war or expanded folder
Other reason for using this approach is when you have a great amount
of static content, like images.
One would normally package a large amount of static information in a
We put a proxy in front of Tomcat. It serves all the static content.
emerson cargnin wrote:
Well, I said at the beginning that I'm not a big fan of this approach,
but I understand the reasons behind it and the difficulties it would
have to change it.
Other reason for using this approach is
We use windows on the dev workstatios and unix (SunOS 5.10
Generic_120011-14 sun4v sparc SUNW,Sun-Fire-T200) on dev/qa/production
servers.
We use Java 5 and we are migrating to tomcat 5.5 or 6.
Ralph, why do you say it's dangerous? Even if it doesn't have java
code, it would have tagslibs.
emerson cargnin wrote:
We use windows on the dev workstatios and unix (SunOS 5.10
Generic_120011-14 sun4v sparc SUNW,Sun-Fire-T200) on dev/qa/production
servers.
We use Java 5 and we are migrating to tomcat 5.5 or 6.
Ralph, why do you say it's dangerous? Even if it doesn't have java
code, it
This is not really an issue for me, as the access to the servers are
totally strict
and... any idea on how to map to the jsp's outside?
Nobody ever need it? how do people migrate from resin then?
On 19/02/2008, Ralph Goers [EMAIL PROTECTED] wrote:
emerson cargnin wrote:
We use windows on the
From: emerson cargnin [mailto:[EMAIL PROTECTED]
Subject: Re: Mapping JSP's to outside of the war or expanded folder
and... any idea on how to map to the jsp's outside?
Nobody ever need it? how do people migrate from resin then?
Nobody needs it because it's a clear violation of the servlet
If you are brave ... you can apply this patch:
http://svn.apache.org/viewvc?view=revrevision=575332
-Tim
emerson cargnin wrote:
This is not really an issue for me, as the access to the servers are
totally strict
and... any idea on how to map to the jsp's outside?
Nobody ever need it? how do
Right.
The only way access to your servers is totally strict is if they have
no network connection and no human input devices connected. However, in
the spirit in which you probably meant this, I will have to point out
that if your web apps are running on the internet then what you are
Once the .war is expanded why would you want to map to JSPs outside of the file
system package?
emerson cargnin wrote ..
Hi there
We use resin here in my work. Resin allows in its web.xml an element like:
path-mapping
url-pattern/jsp/*/url-pattern
In the future to get the gurus to reply supply more info about your systems
overall (OS, JDK, TC version, hardware, network topology, etc.). If you are
running a NIX box you could possibly create some soft links in the directories
you have named below. I have not tried something like that nor
We also do this with Velocity (we use Spring MVC rather than JSP) and point our
Velocity ResourceLoader to somewhere else on the filesystem (away from any
Apache document root so they aren't accessible). This brings benefits of being
able to do hot-deploy of content/templates for urgent copy
18 matches
Mail list logo
