The ACC wants to find connector classes in the classpath, what it a showstopper
for us. We are an ISV and ship one EAR that shall run on all applications
servers, so there should be no vendor specific work arounds in the EAR. But
without such a workaround (which btw bloats up the Client.jar by far and makes
performance of ACC startup a mess) our correct EAR will not run on GlassFish.
Since GlassFish is the RI for Java EE 5, we want to please Sun Microsystems to
provide a fix ASAP, since currently the RI just proofs that it does not behave
like the spec wants it to be.
Especially see this answer:
With the workaround (putting the RA's implementation into the client.jar) the
ACC needs so long to start up (due to the lots of additional classes) that it
makes really no more fun to work with.
To express how severe this problem is for us, we have marked it as P1.
We understand that Sun Microsystems cannot provide a real fix in short term, but
we expect that there is a real solution that makes the workaround obsolete to be
published FAR BEFORE GlassFishv3.
We want to distribute GlassFish (and service contracts from Sun Microsystems) to
our enterprise customers, but we cannot do that as long as the product is not
behaving according to the spec.