-
1. Re: JBoss as a Non-http Socket Server
starksm64 Nov 23, 2004 2:50 PM (in response to jamesa)You would have to write a custom invoker. Look at the socket based invoker in the codebase under jboss-x.y/server/src/main/org/jboss/invocation/pooled
directory as a starting point. -
2. Re: JBoss as a Non-http Socket Server
jamesa Nov 23, 2004 5:30 PM (in response to jamesa)Is it possible to use a servlet (instead of HttpServlet) that can handle the client connections ?
-
3. Re: JBoss as a Non-http Socket Server
starksm64 Nov 23, 2004 10:31 PM (in response to jamesa)Anything is possible. This would require a custom tomcat connector so I don't see that as being any easier.
-
4. Re: JBoss as a Non-http Socket Server
jamesa Nov 23, 2004 11:08 PM (in response to jamesa)Scott,
Okay. I will go with PooledInvoker. What classes or methods should I extend or override ? How do I integrate the newly created functionality into JBoss ? Are there other aspects that I have to keep in mind to use clustering ? What is your sense of the complexity for doing something like this given that I haven't messed around with the innards of JBoss but have been a user for a while ?
Thanks
Arthur -
5. Re: JBoss as a Non-http Socket Server
starksm64 Nov 24, 2004 9:06 PM (in response to jamesa)Just start with the PooledInvoker code and modify it to support messaging parsing for you custom socket protocol. It should be deployed as a sar. See chap 2 of the online admin/devel guide for info on creating sars.
-
6. Re: JBoss as a Non-http Socket Server
jamesa Nov 24, 2004 9:34 PM (in response to jamesa)Scott,
Thanks for the pointers.
Arthur