Andreas Pålsson wpt2...@hotmail.com wrote:
I have been thinking about this issue all day, and I think the
specification needs more work on this area.
There is certainly no need for a container to wade through hundreds
maybe even thousands of classes in search of something that does not
exist.
On 01/08/2012 02:53, andreas palsson wrote:
Good morning.
After upgrading to 7.0.29, one of my larger webapps could no longer be
deployed due to OutOfMemoryError.
As far as I know, this is related to the new feature of annotation scanning
which was enabled in v7.0.29 (see the stack
Thank you Mark for explaining this.
I'll see if I can get my hands on a 7.0.30 and see how it works out.
One thing though, would it be possible to allow Tomcat to _only_ scan for SCI's
in WEB-INF/classes and exclude WEB-INF/lib (even for parent classes inherited
in the former)?
It would be
On 01/08/2012 09:35, andreas palsson wrote:
Thank you Mark for explaining this. I'll see if I can get my hands on
a 7.0.30 and see how it works out.
You'll need to wait until all the issues have been fixed and then build
from trunk. Keep an eye on the dev list.
One thing though, would it be
Mark Thomas wrote:
On 01/08/2012 02:53, andreas palsson wrote:
Good morning.
After upgrading to 7.0.29, one of my larger webapps could no longer be deployed due to
OutOfMemoryError.
As far as I know, this is related to the new feature of annotation scanning
which was enabled in v7.0.29 (see
On 01.08.2012 09:51, Mark Thomas wrote:
On 01/08/2012 02:53, andreas palsson wrote:
Good morning.
After upgrading to 7.0.29, one of my larger webapps could no longer be deployed due to
OutOfMemoryError.
As far as I know, this is related to the new feature of annotation scanning
which was
I have been thinking about this issue all day, and I think the
specification needs more work on this area.
There is certainly no need for a container to wade through hundreds
maybe even thousands of classes in search of something that does not exist.
It is an unnecessary task which consumes both
On 01.08.2012 18:10, Andreas Pålsson wrote:
I have been thinking about this issue all day, and I think the
specification needs more work on this area.
There is certainly no need for a container to wade through hundreds
maybe even thousands of classes in search of something that does not exist.
On 01.08.2012 18:52, Rainer Jung wrote:
Mark, is there a way we can influence the EG to change this?
I'm not Mark and don't want to preempt any answer from him, but there is
the following public discussion available:
http://java.net/jira/browse/SERVLET_SPEC-36
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 8/1/12 5:55 AM, André Warnier wrote:
Without for a minute questioning the technical competence and
intellectual brilliance of the actors involved, for me the above
perfectly illustrates a phenomenon that is common in the computer
Good morning.
After upgrading to 7.0.29, one of my larger webapps could no longer be deployed
due to OutOfMemoryError.
As far as I know, this is related to the new feature of annotation scanning
which was enabled in v7.0.29 (see the stack trace below).
Have anyone else experienced the same
11 matches
Mail list logo
