Re: instance has been stopped. could not loadoracle.toplink.essentials...

2009-03-02 Thread Thufir
On Sun, 01 Mar 2009 21:46:30 -0600, Caldarale, Charles R wrote: >> From: news [mailto:n...@ger.gmane.org] On Behalf Of Thufir Subject: Re: >> instance has been stopped. could not loadoracle.toplink.essentials... >> >> Glad you saw that. It seems like toplink is required f

RE: instance has been stopped. could not loadoracle.toplink.essentials...

2009-03-01 Thread Caldarale, Charles R
> From: news [mailto:n...@ger.gmane.org] On Behalf Of Thufir > Subject: Re: instance has been stopped. could not > loadoracle.toplink.essentials... > > Glad you saw that. It seems like toplink is required for JPA? Got no idea; what I said was mostly a joke, like mixing oil and

Re: instance has been stopped. could not loadoracle.toplink.essentials...

2009-03-01 Thread Thufir
On Sun, 01 Mar 2009 09:24:08 -0600, Caldarale, Charles R wrote: > (Mixing anything from Oracle with MSSQL? That's gutsy.) > > - Chuck Glad you saw that. It seems like toplink is required for JPA? Do you have suggestion beyond "don't use mssql" because mssql is what my school uses, so I ha

Re: instance has been stopped. could not loadoracle.toplink.essentials...

2009-03-01 Thread Thufir
On Sun, 01 Mar 2009 09:24:08 -0600, Caldarale, Charles R wrote: >> From: news [mailto:n...@ger.gmane.org] On Behalf Of Thufir Subject: >> instance has been stopped. could not loadoracle.toplink.essentials... > >> I can't quite predict with certainty when this error wil

RE: instance has been stopped. could not loadoracle.toplink.essentials...

2009-03-01 Thread Caldarale, Charles R
> From: news [mailto:n...@ger.gmane.org] On Behalf Of Thufir > Subject: instance has been stopped. could not > loadoracle.toplink.essentials... > I can't quite predict with certainty when this error > will occur: And we can't predict what Tomcat version you're runni