WebMacro adds some difficulty in that it searches the
classpath for its
properties. I am guessing that as long as you have a webmacro.jar and
properties file per zone everything will be okay. (This is
something that
needs to be fixed in WM, unless I am misreading the situation.)
I just want to be clear on this, so let me ask a couple of dumb
questions-
1. Can you run more than 1 Turbine application per VM?
2. If not, couldn't this be a serious drawback for using Turbine?
3. Should we be concerned with a remedy for this?
--
dave
[EMAIL PROTECTED]
nt: Monday, July 03, 2000 5:13 PM
Subject: Clarification on Turbine per VM
I just want to be clear on this, so let me ask a couple of dumb
questions-
1. Can you run more than 1 Turbine application per VM?
2. If not, couldn't this be a serious drawback for using Turbine?
3. Should we be
on 7/3/2000 5:13 PM, "dave bryson" [EMAIL PROTECTED] wrote:
1. Can you run more than 1 Turbine application per VM?
I don't see why not.
One issue with this is namespaces with regards to the way that the packages
are found.
For example:
module.package=org.apache.jyve, org.tigris.scarab
If
on 7/3/2000 5:52 PM, "Jon Stevens" [EMAIL PROTECTED] wrote:
I could see doing a hack where you took the last bit of the package name and
appended it to the beginning of the search path so that the above URL
examples would work transparently without having code things that way.
For example:
