Hello Jon,
Its not a fix for the string lookup problem, so though the fix for 2492 it
allows you to pass in a string property for the datasource, doing so will
result in the same issue on Tomcat. But it does allow passing in a
datasource object, which allows you to work around the lookup issue (2498)
by allowing you to look it up properly and pass it in.
This fix for 2492 didn't make it into buld 37 - missed it by a day. I'm not
that familar with the build process, but it looks like build 38 is scheduled
for tonight, which then should include the fix.
I can't comment on the Issue tracker list" link being complete as I'm not up
on all the bugs checked in. I suspect that it picks up bugs based on the
target milestone being set for that build, so it might be that a few have
the target set wrong. let me know if you find any missing and I'm sure
someone can look into it further.
Best Regards,
Chris
----- Original Message -----
From: "Jon Miller" <jemiller_at_uchicago.edu>
To: <persistence_at_glassfish.dev.java.net>
Sent: Wednesday, March 07, 2007 1:35 PM
Subject: Re: non-jta-data-source doesn't work with Tomcat 5.5?
> Chris,
>
> It looks like this fix has been resolved? One thing that I've been
> wondering is that the "Issue tracker list" link next to each Java
> Persistence API download doesn't seem to list all the issues that were
> fixed? I'm wondering if the fix is included with build 37? I'm also
> wondering if the Tomcat fix is included? Do you have to lookup the
> DataSource yourself and then pass that in, or, does passing a string work
> now?
>
> Jon
>
> ----- Original Message -----
> From: "Christopher Delahunt" <christopher.delahunt_at_oracle.com>
> To: <persistence_at_glassfish.dev.java.net>
> Sent: Monday, February 26, 2007 4:34 PM
> Subject: Re: non-jta-data-source doesn't work with Tomcat 5.5?
>
>
>> Hi Jon, Tom,
>>
>> Actually, the fix for 2492 might help, as I was planning on implementing
>> it to allow taking in either a string that can be used to lookup a
>> datasource, or a datasource object itself. So effectively you could
>> lookup the datasource yourself and pass it in as a property avoiding this
>> issue.
>>
>> I hope to have it check in within the next day or two.
>>
>>
>> Best regards,
>> Chris
>>
>>
>> ----- Original Message -----
>> From: "Tom Ware" <tom.ware_at_oracle.com>
>> To: <persistence_at_glassfish.dev.java.net>
>> Sent: Monday, February 26, 2007 5:07 PM
>> Subject: Re: non-jta-data-source doesn't work with Tomcat 5.5?
>>
>>
>>> Hi Jon,
>>>
>>> We're glad you are happy with the product and that you are rewarded for
>>> participating in the community. That is our goal.
>>>
>>> I have a bit of bad news, however. I just talked to the person that is
>>> fixing bug 2492, and he does not think it is going to solve your issue
>>> on Tomcat. I have entered an enhancement to allow this configuration to
>>> occur more easily. Unfotunately, I think the short answer is to use the
>>> customizer as suggested in the forum.
>>>
>>> Here is the enhancement:
>>>
>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=2498
>>>
>>> Sorry for the inconvenience,
>>> Tom
>>>
>>> Jon Miller wrote:
>>>
>>>>Thanks Tom. I've been meaning to thank all of the people on this list
>>>>that have taken the time to answer my questions. The answers have been
>>>>very much appreciated. Also, I want to say thanks for creating such a
>>>>great product. Object relational mapping is pretty revolutionary IMHO.
>>>>It's great that it's part of the core Java platform. I think great now
>>>>and it'll only get better. Good job guys.
>>>>
>>>>Jon
>>>>
>>>>----- Original Message -----
>>>>From: "Tom Ware" <tom.ware_at_oracle.com>
>>>>To: <persistence_at_glassfish.dev.java.net>
>>>>Sent: Monday, February 26, 2007 1:47 PM
>>>>Subject: Re: non-jta-data-source doesn't work with Tomcat 5.5?
>>>>
>>>>
>>>>
>>>>>Hi Jon,
>>>>>
>>>>> We're hoping to that some changes we make for this bug will solve your
>>>>> JNDI issues.
>>>>>
>>>>>-Tom
>>>>>
>>>>>Jon Miller wrote:
>>>>>
>>>>>
>>>>>>Thanks Tom. Yes, that property will come in handy. That's pretty much
>>>>>>exactly what I need. Currently, there seems to be something that
>>>>>>doesn't work with the JNDI naming itself though (when used with Tomcat
>>>>>>(unless I'm doing something wrong)).
>>>>>>
>>>>>>Jon
>>>>>>
>>>>>>----- Original Message -----
>>>>>>From: "Tom Ware" <tom.ware_at_oracle.com>
>>>>>>To: <persistence_at_glassfish.dev.java.net>
>>>>>>Sent: Monday, February 26, 2007 9:23 AM
>>>>>>Subject: Re: non-jta-data-source doesn't work with Tomcat 5.5?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Hi Jon,
>>>>>>>
>>>>>>>There is some work on the way that may help you with two of your
>>>>>>>issues:
>>>>>>>
>>>>>>>https://glassfish.dev.java.net/issues/show_bug.cgi?id=2492*
>>>>>>>
>>>>>>>*
>>>>>>>
>>>>>>>* *Hopefully this will solve your issue of using a data source in
>>>>>>>Java SE.
>>>>>>>
>>>>>>> In addition, allowing the datasources information to be specified as
>>>>>>> properties should allow you to determine when you create your JavaSE
>>>>>>> EntityManagerFactory which datasource you want to connect to.
>>>>>>>
>>>>>>>-Tom**
>>>>>>>
>>>>>>>Jon Miller wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>No one knows the answer to this? I'm not looking forward to having
>>>>>>>>to restart my app everytime the database goes down, so, I'm hoping
>>>>>>>>to get GP working with Tomcat's connection pool which I've used with
>>>>>>>>Hibernate in the past without problem. While it may be the case that
>>>>>>>>Tomcat's JNDI implementation isn't what it should be, I believe it's
>>>>>>>>important that GP work with it because a lot of users will probably
>>>>>>>>try to use it that way. I wasn't able to get it to work using the
>>>>>>>>latest build of GP. This IMHO isn't something you shouldn't have to
>>>>>>>>use a customizer to get working.
>>>>>>>>
>>>>>>>>Jon
>>>>>>>>
>>>>>>>>----- Original Message -----
>>>>>>>>From: "Jon Miller" <jemiller_at_uchicago.edu>
>>>>>>>>To: "Glassfish Persistence List"
>>>>>>>><persistence_at_glassfish.dev.java.net>
>>>>>>>>Sent: Tuesday, February 20, 2007 4:53 PM
>>>>>>>>Subject: non-jta-data-source doesn't work with Tomcat 5.5?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Hi all,
>>>>>>>>>
>>>>>>>>>I'm using GP V2 B36 with Java 1.5.0_09 and Tomcat 5.5.17. I've been
>>>>>>>>>having problems with Glassfish Persistences built-in connection
>>>>>>>>>pool not handling broken connections correctly. Specifically, it
>>>>>>>>>seems to have problems dealing with the fact that MySQL times out
>>>>>>>>>connections after 8 hours. So, I decided to try to use the
>>>>>>>>>non-jta-data-source setting instead and use Tomcat's connection
>>>>>>>>>pool. However, I can't seem to get it to work. I found the
>>>>>>>>>following article which indicates it doesn't work unless you use a
>>>>>>>>>customizer. Can anyone confirm whether this is the case?
>>>>>>>>>
>>>>>>>>>http://forums.java.net/jive/thread.jspa?messageID=189962
>>>>>>>>>
>>>>>>>>>Jon
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>--
>>>>>>>
>>>>>>>
>>>>>>>
>>>
>>> --
>>> Tom Ware
>>> Principal Software Engineer
>>> Oracle Canada Inc.
>>>
>>> Direct: (613) 783-4598
>>> Email: tom.ware_at_oracle.com
>>>
>>
>