Using non-EJB classes with Sockets/non-servlet communication

[orange80]

Hey guys,

I am starting to fool around with JBoss AS 5, and have a (probably) silly question. I would like starting experimenting with JTS, JNDI, and JMS, using a simple app that just uses ordinary Java sockets or Apache HttpClient rather than servlet communication. So my questions are

1. Will JBoss AS allow me to open up sockets within a class or does this violate a security restriction or something else like that?

2. Does JBoss AS only work with EJBs or can I use regular Java classes that tie into the App Server's services such as JTS, JNDI, etc.

Thanks,
Jamie

[peterj]

Why not simply use EJBs? They (session beans and message-driven beans) should give the capabilities you are looking for without having to write your own plumbing code.