The PostgreSQL driver is not a legitimate part of the EAR. In theory, an
EAR should be deployable on any EJB platform regardless of the back-end
database. One of the main goals of EJB is to hide stuff like that from
your application. I am not sure why the error would be "no such file,"
but I cannot see how this could work even if the file were to be found.
The JAR file in question is loaded during mbean initialization as jBoss
starts up. By the time deployment happens, it is too late.
Furthermore, there would be substantial practical problems with putting
such a driver into the EAR which would make it undesirable to do. For
example, your EAR would only work with a specific version of PostgreSQL;
if the back-end database were upgraded to a new version, everything would
break. So this is a really not a good idea.
-- Mike
On 2001-06-25 at 20:06 -0500, G.L. Grobe wrote:
> I'm trying to get rid of the following error when I startup with
> ./run_with_tomcat.sh.
>
> [J2EE Deployer Default] couldnt add ./jdbc7.0-1.2.jar to common classpath:
> /u/public/JBoss-2.2.2_Tomcat-3.2.2/jboss/deploy/jdbc7.0-1.2.jar (No such
> file or directory)
* * *
> Chapter 3 (JDBC) of the docs say I must copy the driver file
> (jdbc7.0-1.2.jar) to the lib/ext directory in the JBoss distribution.
> Because I'm trying to get my J2EE app in a format to where it will
> distribute w/ one EAR file that I can give to my customers and will work
> accross several servers, I'd like to not have to pull the driver out and
> place it into the ~/lib/ext dir.
>
> Anyway this will work w/o doing that?
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
