Moreover, if you are separating things per server, you already have the
server.id EL variable to play with.
For example, we use it to define different home directories per server
instante:
web-app id=/ root-directory=${resin.home}/webapps/${server.id}//
so...
resin:import
If there is agreement that this is a bug, and the fix can be rolled into a
snapshot, I can test further to find out where the next gotcha is with large
valued contentLengths.
Thanks,
Aaron
From: resin-interest-boun...@caucho.com
[mailto:resin-interest-boun...@caucho.com] On Behalf
On 10/20/2011 08:25 AM, Aaron Freeman wrote:
If there is agreement that this is a bug, and the fix can be rolled
into a snapshot, I can test further to find out where the next gotcha
is with large valued contentLengths.
Thanks. I've filed this as http://bugs.caucho.com/view.php?id=4819.
Okidoke, no problem.
- Aaron
From: resin-interest-boun...@caucho.com
[mailto:resin-interest-boun...@caucho.com] On Behalf Of Scott Ferguson
Sent: Thursday, October 20, 2011 11:58 AM
To: resin-interest@caucho.com
Subject: Re: [Resin-interest] Possible Bug Fix?
On 10/20/2011 08:25 AM,
Hi Scott,
I used to bundle JUEL 2.1.x in my webapp and it run fine with resin 4.0.x.
After I upgrade to JUEL 2.2.3, some of the el expressions in jsp file
threw exceptions.
The error method invocation expressions is like:
${myBean.myMethod()}
it will produce
javax.el.MethodNotFoundException:
On 10/20/2011 11:59 AM, Wesley Wu wrote:
Hi Scott,
I used to bundle JUEL 2.1.x in my webapp and it run fine with resin 4.0.x.
After I upgrade to JUEL 2.2.3, some of the el expressions in jsp file
threw exceptions.
The error method invocation expressions is like:
${myBean.myMethod()}
it
