On 11/03/2011 19:17, David Calavera wrote:
Hi Mark,
could you remember to release the maven artifacts, I've seen the last
version released was 7.0.8.
7.0.11 Maven deploy started now. It'll take a couple of hours to
complete and it'll need to sync to Maven central. I've never checked
just how
Aureliusz R. wrote:
Borut,
thanks again. You were correct, it was lazy initialization. Pretty
much at this point I got the spring part working.
I've encountered yet another issue with mapping requests from apache2
web server to tomcat. It seems to have something to do with SSL, as I
don't have
The docBase for my app is /usr/local/jsp/
I've placed my spring test JSP in /usr/local/jsp/testSpring/testSpring.jsp
You probably want your's app docBase to be something like
/usr/local/myapp, and then have your jsp's in a directory
/usr/local/myapp/WEB-INF/jsp/ - eg.
I've thought about that, but I would think I would be maxing out the cpu
if tomcat's processing were the limit. I'm running only about 8% cpu
usage across all 4 cpu's.
On 3/11/2011 4:23 PM, Tony Anecito wrote:
Hi David,
I recently ran performance tests against version 7 and during that
On 3/11/2011 6:04 AM, Jess Holle wrote:
On 3/11/2011 3:22 AM, Mark Thomas wrote:
The obvious difference is that Tomcat 6 compilation targets Java 5
whereas Tomcat 7 targets Java 6. For a simple test JSP:
Tomcat 6 (1.5) - 3,488
Tomcat 7 (1.5) - 3,530 +1%
Tomcat 7 (1.6) - 3,668 +6%
The 1% will
Nevermind -- I examined other classes produced with 1.5 specified.
These were compiled for 1.5 (version 49.0 byte code).
On another ugly JSP, I note:
* Tomcat 6 - JDT targeting 1.5: 93K
* Tomcat 7 - JDT targeting 1.6: 149K
* Tomcat 7 - JDT targeting 1.5: 133K
* Tomcat 7 - javac
On 11 March 2011 20:02, David kerber dcker...@verizon.net wrote:
I've already checked my connection bandwidth, and that still has some
headroom, though not a lot.
What's not a lot? If latency across the connection is starting to
increase due to congestion, that could increase the time to
I'm running Tomcat 6.0.24 on Ubuntu 10.04.2 LTS. I'm trying to
configure WebDav and limit access to a single folder, a subdirectory of
my applications www folder... i.e. www/myapp/subdir. I want to limit
access only to subdir and disable the clients ability to create any new
directories.
Hi Mark,
Thanks a lot for your response. I did agree with Charles regarding the
usually bad idea about just replacing JARs, but in this specific case
(7.0.10 to 7.0.11) I suspected it could be done just replacing JARs.
I will try it definitely.
On Fri, Mar 11, 2011 at 12:40 PM, Mark Thomas
Well, first of all, I'm using the 2004 Struts version. Why didn't I upgraded
that over all these years? Because in the first years I thought I was going
to migrate to JSF, and recetly I'm thinking that maybe I should go with
Spring. For that reason, I didn't want to invest time upgrading to the
2011/3/12 Christopher Schultz ch...@christopherschultz.net:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50883
- From your bug report, this stack trace does not look right at all
(...)
- From that stack trace, it appears that
ApplicationHttpRequest.setAttribute is calling
Hi Mark,
I have been thinking about this issue, and I have some thoughts and
questions.
My web.xml file doesn't mention the TLDs, but I have confirmed that the
Struts JAR does contain them. That is the reduncancy. I tried removing the
TLDs from my WEB-INF directory, and the the info message was
12 matches
Mail list logo
