Please reply to your original thread if you solve your problem.

Because we care but are busy, and don't want to write unnecessary emails. ;-)

Cheers,
Nick.


Jean-Philippe Steinmetz wrote:
Thanks for the response. I actually was able to solve my own problem after
some very lengthy troubleshooting. I'm using Tomcat as my web server so
context.xml is what it uses for resource definitions. Anyway, I was missing
mysql-connector and commons-jdbc jars from my war package.

Jean-Philippe

-----Original Message-----
From: Fidel Chavarria [mailto:[EMAIL PROTECTED]
Sent: Friday, September 07, 2007 2:53 PM
To: users@tapestry.apache.org
Subject: RE: Context.xml



Hi,

 What is context.xml...  Are you using Spring ?
 What framework are you using to access your database ?

you need to post more explicit details ...





Jean-Philippe Steinmetz-2 wrote:
Btw.... I'm  using tapestry 5.

-----Original Message-----
From: Jean-Philippe Steinmetz [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 06, 2007 4:16 PM
To: 'Tapestry users'
Subject: Context.xml

I've discovered a new problem of mine that concerns the context.xml
file.


I access a mysql database in my framework that is referenced by my
context.xml file as a resource. I have my context.xml in the correct
directory src/main/webapp/META-INF but for some reason I keep getting
an
error when I do a lookup for the resource. Is Tapestry using its own
context
file I'm not aware of? How do I add my resource to the correct context
file
so that I can get my database connection? Thanks in advance.



Jean-Philippe Steinmetz



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
View this message in context: http://www.nabble.com/Context.xml-
tf4395210.html#a12563929
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to