Joao Pedro Clemente wrote:

If we are talking Jetty (JBossWeb) - 2 things :

You need to be running the 'all' configuration
The distributable support is improved in 3.0.4


Thank you Jules.
We are talking about Jetty. I think that it's impossible to use
distributable in 3.0.3, as I've searched some more in Jboss forum and saw
that some other people had the same problem: at deployment time, a null
pointer exception.

I was yesterday trying to get a simple servlet to work with 3.0.4 and I
was able to deploy it without a problem. However, I think I've seen
"locks" when a group changed, as I got stuck with no reply from that
servlet (after acessing it some times sucessfully, and then unplug a
network cable from one of the servers)

Yet on more tought: You state taht we NEED to be running the all config.
I saw that by trying... but I somehow disagree on what I've seen, and
please, comment on what you think it's correct:

Supose you have a package "myDistributableServlet.war".
I tought I could deploy if both in 'all' and in 'default' and teh
difference would be that 'default' would ignore the <distributable/> tag.
That's not true as 'default' is unable to deploy the package, stating an
error...

What do you think? Thank you



-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

There is no semantic difference between the configurations. Only differences in what classes/apps are deployed/available and their configuration.

If you want 'default' to support distributable, copy the javagroups.jar from 'all' into it. HttpSession distribution will work, but JBoss clustering won't. 'default' is a custom configuration for people who aren't running a cluster, 'all' is a config for people who are. There is no point in Jetty trying to check the name of the config as you could make up your own and do anything you like with it. All I can do is check Class or Service availability - but if I had to do that for every class I use the overhead would be onerous, so I assume (just like all the JBoss clustering code) a certain amount of knowledge on the part of my users......

Does that help...


Jules




________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________


-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to