Jules,
thanks again and sorry when I was rude.
likewise
The one that I pointed you two in the second message in this thread.
Ok, my mistake again. I only saw this as FAQ wrt url-rewriting.
The SessionManager that *you* have asked for by specifying that your webapp is <distributable/>
<deploymentdescriptor servletspec="2.3" distributable="false" sessiontimeout="30" />
Got this one too now
How do you decide you are in a cluster if :
1). The jar that contains the clustering implementation is not available (which it isn't in the default config - javagroups.jar)
Wouldn't it be the other way around: if javagroups.jar is not present, then fall back to single node?
2). you are the first node to come up.
Ok, this one is trickier ;-)
My approach is that the developer should know what they are doing. If they ask Jetty to do something that it cannot do, it should error - behaviour after that is undefined. If Jetty pretended to be
You are probably right here. On the other hand, as tomcat which is seen by some as sort of reference implementation, acts differently this is confusing at least.
TC can only be the RI for stuff that is specced - clustering is not.
Yes the error messages could be better, and will be on the next development iteration.
What about: running jetty in 'default' as single node instance and only putting clustering in 'all' or create a fourth config which has clustering etc., but not all (e.g. no corba ..)?
At the moment Jetty installation is identical for all configs. Tailoring Jetty for each installation would take more time away from items higher on my todo list..
Your points are all noted.
Cheers,
Jules
Thank you for your patience
Heiko
------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
