Hi Scott,
We also refactored Quercus in a major way for 3.1.0, so that's almost
certainly what you're running into. We should be able to split out
the interpreted half of Quercus as a standalone web-app (i.e. non-
Resin), so we can have non-Resin users working on Quercus too.
that is
The 1.4 EE API specified that maxInactiveInterval is an integer
specifying the number of seconds this session remains open between
client requests. In my development resin conf , when I set the
session-timeout configuration to 1 minute, session.maxInactiveInterval
came out as 6, but it should
We also refactored Quercus in a major way for 3.1.0, so that's almost
certainly what you're running into. We should be able to split out
the interpreted half of Quercus as a standalone web-app (i.e. non-
Resin), so we can have non-Resin users working on Quercus too.
that is great news. Are
Anyone consider integrating an ODBMS like db4o into Quercus (or even Resin)?
Using an ODBMS instead of MySQL/RDBMS with PHP 5 and Java seems to
have some nice advantages.
Frank
--
+==+
| Crossroads Technologies Inc. |
|
On Jan 3, 2007, at 10:18 AM, L Logue wrote:
Date: Wed, 3 Jan 2007 09:06:49 -0800
From: Scott Ferguson [EMAIL PROTECTED]
On Jan 3, 2007, at 7:23 AM, L Logue wrote:
The 1.4 EE API specified that maxInactiveInterval is an integer
specifying the number of seconds this session remains open
I have this rewrite rule:
rewrite-dispatch
forward
regexp=/here/.*/([0-9]+)\??(.*)
target=/there.jsp?id=$1amp;$2
/
/rewrite-dispatch
Which is supposed to do this:
when resin sees this:
/here/12345?x=1
it should forward to this:
/there.jsp?id=12345x=1
but actually it is
