J2EE Design Question
I'm presently working on a messaging server using JMS internally to parse/route/store/etc. messages. Clients don't connect directly to the JMS system, and instead make a connection to a gateway which handles conversion between their protocol and JMS.
I think I'm happy with that design, but, being relatively new to J2EE, I'm not sure how best to go implementing the gateway. Presently it's a standalone Java app that sits outside the J2EE server (JBoss), manages connections, and translates messages to/from the server. It works, but I get the feeling I'd be better off if the gateway could reside inside the app server.
Anyone with a little more J2EE experience have any suggestions on how this could be accomplished? I keep thinking that maybe it's something I could do with a session bean, but I'm not sure it's something I should do with one. Thoughts?
Update: I've been looking at servlets, and I'm thinking that they might be what I want. Does this seem like something you'd use a servlet to do?
I think I'm happy with that design, but, being relatively new to J2EE, I'm not sure how best to go implementing the gateway. Presently it's a standalone Java app that sits outside the J2EE server (JBoss), manages connections, and translates messages to/from the server. It works, but I get the feeling I'd be better off if the gateway could reside inside the app server.
Anyone with a little more J2EE experience have any suggestions on how this could be accomplished? I keep thinking that maybe it's something I could do with a session bean, but I'm not sure it's something I should do with one. Thoughts?
Update: I've been looking at servlets, and I'm thinking that they might be what I want. Does this seem like something you'd use a servlet to do?
