Hi Anissa
thanks very much.
Which ever way it goes, we need to verify if Toplink still works if any code
changes are made.
regards
Richard
2009/10/28 Anissa Lam <Anissa.Lam_at_sun.com>
>
>
> There seems to be confusion on where exactly the JDBC drivers should be
> installed in v3. Thanks for all the great suggestion on how to make the
> pool creation experience better.
> I have contacted the doc team so they are aware of the issues.
> Jagadish Ramu is the owner of the JDBC resource, I am cc'ing him so he can
> send his comment as well.
>
>
> thanks
> Anissa.
>
> Richard Kolb wrote:
>
>
> Some more work when you wake up :)
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=10628
>
> regards
> Richard
>
>
> 2009/10/28 Judy Tang <Judy.J.Tang_at_sun.com>
>
> Good point Richard. Will let Anissa sleep now and think about it tomorrow
> :-)
>
> Thanks !
> Judy
>
>
> Richard Kolb wrote:
>
> Hi Judy
>
> I think we have a more complex problem. The driver may need to be in
> lib/ext to make Oracle Toplink work.
> Personally I don't use toplink so I can't confirm this.
>
> Maybe a nice to have (and a quick one) is to add a README.TXT file in
> lib/ext and say what should and what should not be included there.
>
> regards
> Richard
>
>
> 2009/10/28 Judy Tang <Judy.J.Tang_at_sun.com>
>
> Hi Richard,
>
> Thanks for continue testing and report issues. It helps us to know where to improve.
>
> Checked with Yifeng she confirmed if put the driver in domain1/lib, it is working fine. Thanks Yifeng :-)
>
> Thanks Anissa, you are so fast, even looked into online Help and found an issue there.
>
> I have a suggestion and see if it is possible to add code to check under domain1/lib, if driver is not
> there, may be pop up an error message to suggest user to put the driver in the right place ?
>
>
>
> Judy
>
> Anissa Lam wrote:
>
>
> Hi Richard,
> I have looked at this and realized what is the problem.
> The location where you install the oracle driver is the issue. It should
> be placed under glassfishv3/glassfish/domains/domain1/lib (Note: NOT
> lib/ext).
> Once you put it there, and restart the driver, connector runtime is able
> to detect that and console presented the correct information.
> Attached is the list of property shown when i select "javax.sql.DataSource"
> as the resource type.
>
> I checked the current Online Help for creating the pool, the help did
> mention that lib/ext being an alternate location which is incorrect.
>
> * # Make the driver accessible to the common class loader.
> 1. Copy the JAR and ZIP files of the driver into the domain-dir/lib
> directory; or copy the class files into the domain-dir/lib/ext directory.
> 2. Restart the domain.
>
> *I will contact the doc team and ensure that this will be corrected.
> Again, thanks for drawing this to our attention and takeing the time to
> file the bug.
>
> thanks
> Anissa.
>
> Richard Kolb wrote:
>
> Hi Anissa
>
> No problem, just glad I saw it.
> Will copy the GF 2.1 setting.
>
>
> regards
> Richard
>
> 2009/10/28 Anissa Lam <Anissa.Lam_at_sun.com>
>
>
> Hi Richard,
> I will look into this. In the meantime, maybe you can work around the
> problem by adding rows in the Property table and fill in the Property name
> and value pair instead of relying GUI to provide the property list for you
> to fill in the value.
>
> Sorry for the inconvenience.
>
> thanks
> Anissa.
>
>
> Richard Kolb wrote:
>
>
> Can someone please confirm this (it's a bad one) :
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=10626
>
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net For
> additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>
> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>
>
>
>