Folks,
so, after all, despite all the small things outlined here yesterday and
today, as of today for the first time I managed to completely get our apps
deployed and running on gfv3-b64:
- Eventually figured out that, except for xercesImpl.jar, it's fine to dump
most of our libraries used to <domain>/lib/. Some xerces implementation
obviously seems to be around (JVM? Glassfish?) or just an "optional"
dependency, at least its absence didn't really cause problems.
- Worked around #9564[1] by creating the datasource and, after that,
stopping the domain and, in the corresponding <jdbc-connection-pool> element
in domain.xml, changing "driver-classname" to "datasource-classname".
- Figured out that, same as in GFv2, the jar containing the JDBC driver for
our database needs to go to <domain>/lib/ext/, putting it to
<domain>/lib/database/ failed with a ClassNotFoundException while trying to
do a ping to the connection.
- Worked around #9679[2] and #9680[3] by manually creating the required
listener using asadmin.
After these tweaks, deploying all our war files was pretty straightforward.
No special exceptions to report, by now things seem to work smoothly. Good
work so far everyone! :) Now to move forward and get things sorted out a
little... smaller modules, ejbs, all this stuff. :)
Cheers,
Kristian
[1]
https://glassfish.dev.java.net/issues/show_bug.cgi?id=9564
[2]
https://glassfish.dev.java.net/issues/show_bug.cgi?id=9679
[3]
https://glassfish.dev.java.net/issues/show_bug.cgi?id=9680
--
Dipl.-Ing.(BA) Kristian Rink * Software- und Systemingenieur
planConnect GmbH * Könneritzstr. 33 * 01067 Dresden
fon: 0351 215 203 71 * cell: 0176 2447 2771 * mail: rink_at_planconnect.de
Amtsgericht Dresden HRB: 20 015 * St.-Nr. FA DD I 201 / 116 / 05360
Geschäftsführer: Stefan Voß, Karl Stierstorfer