Via the standard java.rmi.server.codebase system property. This is now set by the WebService if it is not already set.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Dain Sundstrom" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 07, 2003 10:59 AM Subject: Re: [JBoss-dev] Remote class loading servlet > Scott, > > I'm putting the question for you at the top, so you can see it. How do > we specify the code base for remote loading? If James writes this he > will need to change it to point to the servlet. > > > > James, > > You are way over thinking this. I suggest you just start coding. :D > > On Friday, February 7, 2003, at 10:40 AM, James Cooley wrote: > > > 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 create a war named say class-loader. Then we set the codebase for > remote stubs to be http://whatever:8080/class-loader [the question for > Scott above]. Then create a servlet that accepts all requests to the > context-root, convert the requested file (under your context-root) into > a class name, and return that class from the thread context class > loader. > > >> 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 > > You're sill trying too hard. All of that code is already handled by > the the Jetty or Tomcat web container in which your servlet is running. > It is really as simple as > Thread().currentThread().getClassLoader().getResourceAsStream(name); > > -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
