Hi,
I am using Apache in front of Resin with mod_cacho to give requests to
Resin. My problem is that Resin seems to answer for all requests, making
Apache ignore whatever Alias/RewriteRules I set up. This may be related
to the fact that we are having a ROOT web-app (by using context-root
/ in
Hi
I'm in the process of migrating an old configuration for Resin 2.1.2
to Resin 3.1. In the old setup, we were launching resin using the
wrapper.pl script, and in the process could pass any JVM arguments we
needed, for example -XX arguments to hotspot, on the command line (as
arguments to the
Hi,
Just a small follow-up. By using sections like this in a host block in
resin.conf, I can convince mod_caucho to let Apache respond for some
URLs instead of Resin:
web-app id='/multimedia' document-directory='/data/tmp/op/multimedia'
servlet-mapping url-pattern='/multimedia/*'
On Aug 27, 2008, at 9:29 AM, Scott Ferguson wrote:
On Aug 26, 2008, at 10:21 AM, Rob Lockstone wrote:
On Aug 26, 2008, at 09:40, Scott Ferguson wrote:
It should, though. The watchdog should be starting Resin with
DYLD_LIBRARY_PATH set to include the libexec directory, which should
be
On Aug 27, 2008, at 5:37 AM, Patrick Wright wrote:
Hi
I'm in the process of migrating an old configuration for Resin 2.1.2
to Resin 3.1. In the old setup, we were launching resin using the
wrapper.pl script, and in the process could pass any JVM arguments we
needed, for example -XX
Perfect. Thanks for the info, Scott.
Patrick
We normally recommend using jvm-arg for the -XX arguments. That
way, all of your configuration is in one file, not scattered across
multiple files.
___
resin-interest mailing list
Hi!
There isn't any guarantee on the servlet spec that the request
parameters should be given in any specific order. That's why the
getParameterMap-method returns a Map, i.e. not guaranteed to be
ordered. I really don't understand why you'd want to get the request
params in the order of their
