Enhydra: Migrating from Jserv to Enhydra

[Ben Ricker <bricker@xxxxxxxxx>]

I have a servlet based web application that I want to test with Enhydra.
I have been able to setup all the examples and what have you, but I
cannot get an existing application to be run under Enhydra. There are
two possible complications which may be spoiling the broth.

First a few words about specs. I am running Redhat 6.2 with Sun JDK1.2.2
and Enhydra 3.1.

The two complications are that the app is a bunch of class files within
a jar file and we have our own built-in connection pool.

On the first complication: not only do we have the classes within the
jar, under Jserv we set up a ton of package aliases which allow the
calling of the class by its name rather then its full package. How does
one migrate those aliases so the URLs will work? 

Secondly, we can leave the connection pool option off so that our own
pool does the job, I would assume? Is there any reason why the Enhydra
connection pool is superior? We utilize Oracles JDBC drivers for the
pool as well as the access to the pool (sending the SQL, etc.).

Thanks for the assistance,

Ben Ricker
Senior Web Administrator
US-Rx, Inc.
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@xxxxxxxxxxx
with the text "unsubscribe enhydra" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-enhydra@xxxxxxxxxxxx