Orion's JMS is really buggy, it fails almost all the compatibility tests for
JMS.
We did a similar thing that you are experimenting with, only the MDB
response queue is a queue on OpenJMS. I believe our first attempts to do
this on Orion completely failed. I haven't tried it with 1.5.4, but
I came across this exact problem. In the mailing archives the
recommendation is to remove the action=j_security_check from the login
form.
Here's what I did to implement the system:
1. created a index.jsp in the non protected folder. It contains a redirect
Second try:
I came across this exact problem. In the mailing archives the
recommendation is to remove the action=j_security_check from the login
form.
Here's what I did to implement the system:
1. created a index.jsp in the non protected folder. It contains a redirect
I can't seem to find a mapping that will allow me to do
ResultSet.getTimestamp or ResultSet.getDate from a MS SQL Server DB using
the MS JDBC driver and Orion.
I've tried the following mappings:
type-mapping type=java.sql.Timestamp name=datetime /
type-mapping type=java.sql.Date
I sent this to support but maybe someone on this list has already come
across this problem:
I'm having problems getting the UserTransaction for external clients. The
following is basically how I'm trying to get at it:
env.put(Context.PROVIDER_URL,"ormi://localhost/app");
Context ctx = new