You don't need an application server for this.
For connection pooling, take a look at http://jakarta.apache.org/commons/dbcp/.
For passing objects around you could:
* Pass each object when you create the thread; and pass those around as needed.
This has the advantage of clearly defining the
You could store the files in a directory external to the web app (and to the
JBoss installation entirely).
You'll then need to configure the web-app with the path to the external
directory. You could define a initialization parameter in your web.xml to
specify this.
Unfortunately this would
When you say main JBoss execution window, do you mean a console window
displaying output?
Are you running this on Windows? Are you sure you aren't clicking your mouse
in the console window, thus causing it to enter Select mode? When in Select
mode, it will block. Pressing Escape, CTRL+C or
Define a resource reference in web.xml, then map that to the JBoss jndi name in
jboss-web.xml and look it up (using the name defined in web.xml) from the container
java:comp/env context.
web.xml:
resource-ref
| res-ref-namejdbc/myDS/res-ref-name
|
That method is only available in JMS 1.1 which is only included with J2EE 1.4.
JBoss 3.x supports J2EE 1.3, which includes the JMS 1.0.2 APIs. ConnectionFactory has
no methods in that version.
I'd suggest reviewing the J2EE 1.3 javax.jms API docs and make sure if you're
following any
The entire JMS specification consists of interfaces. Therefore, to write and compile
a an application that makes use of the JMS api, you only need to add a JAR containing
the interfaces to your classpath. The jboss-j2ee.jar contains all the JMS interfaces.
The actual JBoss implementations of
