Hi there,
I have a uncommon error with the taglib.
When using jsp:attribute tags within FCK:editor my j2ee application server says
500: Internal Server Error
Cannot compile WEB-INF/jsp/editor.jsp
Invalid parent type for jsp:attribute: FCK:editor
Invalid parent type for jsp:attribute: FCK:editor
Invalid parent type for jsp:attribute: FCK:editor
Using the same code in jetty 6 everything works fine.
Is there an error in the taglib?
How can I define that jsp:attribut is a valid child of FCK:editor?
<?xml version="1.0" encoding="UTF-8"?> <jsp:root version="2.0" xmlns:jsp="http://java.sun.com/JSP/Page" xmlns:FCK="http://java.fckeditor1.net" xmlns="http://www.w3.org/1999/xhtml"> ... <div> <FCK:editor instanceName="editorDefault"> <jsp:attribute name="height">500px</jsp:attribute> <jsp:attribute name="value"> This is some <strong>sample text</strong>. You are using <a href="http://www.fckeditor.net">FCKeditor</a>. </jsp:attribute> <FCK:config CustomConfigurationsPath="/myconfig.js"/> </FCK:editor> </div> ... </jsp:root>
Re: FCKeditor Java Taglib Error
Your page is broken in may ways:
first, there is no:
namespace.
second, you have to supply at least
or nothing else will happen but seeing XML output.
Running this page on Tomat 5.5, Jetty 6.1, GlassFish V2 works perfectly:
All three respond:
Having this picture:
The problem must be your system!
Attachments:
Re: FCKeditor Java Taglib Error
Thanks Michael,
but my page isn't that broken.
I just posted an excerpt from my jsp file (marked by the 2 ellipsis).
In the original one, I do have a jsp:directive.page and also an jsp:output tag.
You are right with the definition of my taglib.
I tested my application with a local taglib, because my application is behind a proxy.
So, I'm sorry, I didn't changed that back to the original uri.
Here is an excerpt of my web.xml:
So everything seems to be ok, but I still get this strange error.
Maybe the jsp version of my application server (trifork T4) is too old.
Any other suggestions?
Re: FCKeditor Java Taglib Error
It should matter if you are behing a proxy or not. The namespace is just a unique identifier, it does not even has to exist. You app server ist not too old. Remove the taglib declaration from your web.xml it's not becessary since JSP 2.0 and try the lib as-is. Additionally, please provide the full stack trace.
Hopefully we can solve this issue somehow. Maybe the app server has a false implementation of the JSP interface.