Never mind, I answered my own question: just config the servlet container.. I keep thinking you could describe the port and allow the container to listen and manage connections on that port for the specific servlet. Either I'm dreaming, or that was the old way of doing it way back with v1.0 of the Java Web Server or JSDK or something..
James > -----Original Message----- > From: James Higginbotham > Sent: Thursday, January 02, 2003 10:34 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] Non-HTTP Servlets? > > > > Yes, this is quite standard. Use GenericServlet as your base class. > > That's cool.. You or anyone else remember if there is a > deployment descriptor to indicate the port to bind to? Its > been a looong time since I've looked at anything but > HTTPServlets, but this thread sparked my interest once again.. > > James > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/j> boss-user > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
