I think you need to set the content type for your response. Try something like:
res.setContentType(text/html);
where res is the HttpServletResponse.
Jay
-Original Message-
From: Jörg Lindner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 01, 2005 12:26 PM
To:
I too am not sure what the problem is, though I've got this working on
Windows at least. Couple of comments:
First, what is the need for the second factory definition in the URL
i.e. socketFactory=com.mysql.jdbc.NamedPipeSocketFactory? You've
already defined a factory in the Resource definition
Oops. Haven't had my coffee yet. I read MySQL but thought SQL Server.
Obviously my DB is different than yours, so that may explain our
differences.
But either way, my previous post might still help.
Jay
-Original Message-
From: Merrill Cornish [mailto:[EMAIL PROTECTED]
Sent:
I forgot whether your original post showed it or not, but how are you
trying to acquire the resource in your code? It should look something
like:
Context initialContext = new InitialContext();
Context envContext = (Context) initialContext.lookup(java:comp/env);
this.dataSource = (DataSource)
The J2EE tutorial is one place that talks about the context naming
scheme:
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/Resources2.html
And just to be 100% sure, my example below actually has a minor
cut-and-paste error--there's a space after TimesheetsDB in the second
lookup(). If you
I really hope you can get this figured out, as I'm out of ideas.
But I do concur with Adam's suggestion about looking for multiple
contexts, as I ran into a similar problem when my context.xml was there
twice--once in my .WAR, and once as a result of my Ant deploy task
putting it manually into
lost on redeploy
That's a really nice write up, Jay. Would it be convenient for you to
post a simple project that does this with a build file? Sounds like
something that could make it into the FAQ. If that's too much trouble I
can produce a project zip perhaps.
Burgess, Jay S wrote:
Having just
Having just gone through this headache last week, I can provide a
solution that works for me (for TC5 only!).
First, create a file called context.xml and put it in a directory called
META-INF at the same level in your source hierarchy as WEB-INF.
context.xml should contain your Context and
I'm not much of a UNIX person, but I remember reading about the
allowLinking attributes in Context and DefaultContext. Not sure that
they're applicable, but I figured I'd mention them in case they were and
you hadn't seen them.
Jay
-Original Message-
From: Milt Epstein [mailto:[EMAIL
Having just gone through a similar issue last week, I can recommend
searching the archives (and maybe the bug database). You'll probably
find your solution.
If you're getting this error when you start up Tomcat, then it's
probably fixable (you may have a JAR in the wrong place, etc.) If
you're
I'm obviously missing something important with regards to moving our
database/JDBC connectivity to use JNDI DataSource/DBCP. I've read and
re-read the docs, looked at every related message in the archive, and
Google'd every set of keywords I can think of, but still no luck.
Here's the issue:
. Leaving the /hal
out of my request meant it never saw the /hal stuff in server.xml
which is where my DataSource stuff lives.
I cleaned up my URL in links/forms etc. and seemed to get on okay.
Hope it helps a bit.
Best regards
Chris
-Original Message-
From: Burgess, Jay S [mailto
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 28, 2004 11:36 AM
To: Tomcat Users List
Subject: Re: JDBC/DBCP problems
Hi!
Burgess, Jay S wrote:
Thanks for the feedback. Maybe my problem does have something to do
with context visibility, but since I'm defining the resource within
You've identified part of my problem, I think. From what I found, none of the
documentation that talks about DataSource configuration mentions that ResourceLink
is required (e.g. JNDI Datasource HOW-TO). They talk about using resource-ref in
WEB.XML instead. I assumed that if you had a
14 matches
Mail list logo
