Scott M Stark wrote:
You don't have to worry about the port or interface as these are attributes of the
web server context the servlet is deployed to.
Okay the default container listens on 8080 from what you're saying
there's no need to listen on 8083 anymore. I'm not sure how you'd map
the WebServer replacement servlet in the web.xml if the port is not
exclusive - perhaps a filter to check each call or something but that's
a fair bit of overhead. So what I think is needed here are 2 Tomcat
Connectors/Jetty Adapters to one to bind to 8080 and another to bind to
8083 - the 8083 connector/adapter can be setup as part of the servlet
containers config.
You don't have to worry about class loaders. Just use the thread context class
loader.
Sorry I wasn't clear on this - WebServer has the following method
/** Add a class loader to the web server map and return the URL that
should be used as the annotated codebase for classes that are to be
available via RMI dynamic classloading. The codebase URL is formed by
taking the java.rmi.server.codebase system property and adding a subpath
unique for the class loader instance.
@see #getClassLoaderKey(ClassLoader)
@param cl, the ClassLoader instance to begin serving download requests for
@return the annotated codebase to use if java.rmi.server.codebase is set,
null otherwise.
*/
public URL addClassLoader(ClassLoader cl)
And it's called by WebService's
/**
* @jmx:managed-operation
*/
public URL addClassLoader(ClassLoader cl)
{
return server.addClassLoader(cl);
}
Hope this clarifies my original points
James
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "James Cooley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 07, 2003 3:08 AM
Subject: Re: [JBoss-dev] Remote class loading servlet
Hi Dain,
I had a look at the class and it looks like it should be pretty easy
to do this in a servlet but the deployment may be an issue. The API
includes setPort, setBindAddress, etc. Is there an abstract factory to
create a Tomcat Connector/Jetty Adapter (or whatever the container may
be) at runtime? If not is is okay to just default to 8083 and configure
the port in the service xml config file?
The problem is also complicated by the fact that we need to add and
remove ClassLoaders dynamically and WebService will no longer hold the
instance of WebServer (unless there is an abstract factory).
You were looking for a volunteer and you get an essay :)
James
Dain Sundstrom wrote:
We have a small project open for a volunteer. In Jboss 2 and 3 we have
a custom lightweight web server (port 8083) that returns java class
files from the classLoader.getResouceAsStream to RMI clients (this is
how remote class loading happens). I talked to Scott at JBoss Boot Camp
and we think it is a good idea to replace this with a plain old Servlet
for JBoss 4.0 so it can work with regular security, pooling and such.
This is a fairly simple piece of code and shouldn't take longer then a
day or two. If you are interested the code can be found in
jboss-head/server/src/main/org/jboss/web/WebServer.java
-dain
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
