Now that I have a small bit of time to return to this...
Correct me if I'm wrong, but assuming ESQL is being invoked, the
following XSP page should return either an error, or no output at
all:
---
?xml version=1.0?
xsp:page
xmlns:xsp=http://apache.org/xsp;
I'm trying a different approach, and now I'm getting Java
exceptions in Tomcat's logs.
Here is my XSP. Switching to dbpool doesn't change the
exception.
?xml version=1.0?
xsp:page
xmlns:xsp=http://apache.org/xsp;
xmlns:esql=http://apache.org/cocoon/SQL/v2;
esql:connection
I'm trying to convert a simple XSP application from AxKit to
Cocoon, and ESQL isn't being interpreted.
In my original application, the uninterpreted XML shows up in my
output documents. To simplify my testing, I tried two things:
1) Running a simple example from the request taglib to make sure
