It looks like the problem has to do with the extension of the jsp
source file. It doesn't have the jsp extension, it's got a jspf
extension.
I have about 4 of them, and they all have the same problem.
Now I just have to figure out how to tell Tomcat to treat a .jspf
file as a .jsp file.
Sho
More good news. It appears that it's really only one page that has
this problem!! (Or one that I've found so far.)
I'm amazed that I didn't see this at first. Now I have to figure out
what's wrong with that page.
On Jul 5, 2006, at 12:23 PM, Pid wrote:
Can you execute an arbitrary JSP script
I have some good news. I'm deploying an ear that contains a war that
has this problem.
I have another war that depends on some of the code that's in the
ear. I thought I'd wait until I got the ear working before trying the
war.
I decided on a lark to see what happens with the war. It works fi
I'm going to finish what I'm doing with jars and then find out the
answer to this question.
On Jul 5, 2006, at 12:23 PM, Pid wrote:
Can you execute an arbitrary JSP scriptlet in the page, or does
that get
ignored too?
Pid wrote:
And the taglibs are definitely being imported on the page in
2.4
On Jul 5, 2006, at 12:34 PM, Mark Sutton wrote:
What version of the servlet API are you specifying in the web.xml
of the
application?
Mark
On 05/07/06, Pid <[EMAIL PROTECTED]> wrote:
Can you execute an arbitrary JSP scriptlet in the page, or does
that get
ignored too?
Pid wrote:
>
Yes. Definitely.
As I said, the code works in JBoss 4.0.1 with Jetty 5.1.4.
I'm thinking that there's some kind of conflict with a jar file
somewhere. Some class loader issue at run-time. It would be nice if
some of the software would let me know about it.
I'm just trying to check all of the j
What version of the servlet API are you specifying in the web.xml of the
application?
Mark
On 05/07/06, Pid <[EMAIL PROTECTED]> wrote:
Can you execute an arbitrary JSP scriptlet in the page, or does that get
ignored too?
Pid wrote:
> And the taglibs are definitely being imported on the page i
Can you execute an arbitrary JSP scriptlet in the page, or does that get
ignored too?
Pid wrote:
> And the taglibs are definitely being imported on the page in question?
>
> Richard Doust wrote:
>> Config files are straight out of the box as Tomcat is deployed under
>> JBoss 4.0.4.
>> The web.xml
And the taglibs are definitely being imported on the page in question?
Richard Doust wrote:
> Config files are straight out of the box as Tomcat is deployed under
> JBoss 4.0.4.
> The web.xml file for the application has the obligatory:
>
>
>http://java.sun.com/jsp/jstl/c
Config files are straight out of the box as Tomcat is deployed under
JBoss 4.0.4.
The web.xml file for the application has the obligatory:
http://java.sun.com/jsp/jstl/core
http://java.sun.com/jsp/j
Does not work means that the tags don't get processed.
There are no error logs.
The tags show up in the html page that's delivered to the client.
On Jul 5, 2006, at 10:38 AM, Pid wrote:
error logs?
config files?
define "does not work" with some more precision and we might be
able to
help...
error logs?
config files?
define "does not work" with some more precision and we might be able to
help...
Richard Doust wrote:
> I need help getting Tomcat to process JSTL tags when an ear is deployed
> to JBoss 4.0.4 with Tomcat 5.5.17.
> The same application that works with JBoss 4.0.1 and Je
I need help getting Tomcat to process JSTL tags when an ear is
deployed to JBoss 4.0.4 with Tomcat 5.5.17.
The same application that works with JBoss 4.0.1 and Jetty 5.1.4 does
not work with JBoss 4.0.4 with Tomcat 5.5.17. JSTL tags are sent to
the client's browser unprocessed.
Tomcat does no
13 matches
Mail list logo
