| JSP version mismatch using WTP with BEA? [message #204144] |
Fri, 09 November 2007 15:57  |
Eclipse User |
|
|
|
I'm having a problem getting a JSF web project to build on Europa JEE.
The odd thing is, in my JSP page, the auto-complete brings up the
"deferredSyntaxAllowedAsLiteral" as a valid attribute of a <%@ page, but
once its there, I get a warning that seems to indicate that the build
process doesn't think its valid:
Undefined attribute name (deferredSyntaxAllowedAsLiteral)
Similar problem in my web.xml file: auto-complete will bring up a
deferred-syntax-allowed-as-literal tag, but I get the following "Problem":
cvc-complex-type.2.4.a: Invalid content was found starting with element
'deferred-syntax-allowed-as-literal'. One of
'{"http://java.sun.com/xml/ns/javaee":description,
"http://java.sun.com/xml/ns/javaee":display-name,
"http://java.sun.com/xml/ns/javaee":icon,
"http://java.sun.com/xml/ns/javaee":url-pattern}' is expected.
ProjectName/WebContent/WEB-INF web.xml line 30
It almost looks like auto-complete is JSP version 2.1 (or higher) and the
build is 2.0 (or lower).
Can this be fixed? Why the version mismatch?
Thanks in advance!
|
|
|
|
|
| Re: JSP version mismatch using WTP with BEA? [message #204275 is a reply to message #204267] |
Mon, 12 November 2007 13:59  |
| Eclipse User |
|
|
|
Mev wrote:
> Are you asking if the error was from the Web Page Editor's UI? I'm
> assuming it would be some sort of background build process in Eclipse
> that would generate the warning message, but I'm not sure how a source
> page could generate a warning -- I would think it would be some else
> that generates a warning based on a source page.
> I must not be understanding what you are asking for.
I meant the "autocomplete." The source page doesn't know about that
attribute.
--
Nitin Dahyabhai
Structured Source Editing
|
|
|
Powered by
FUDForum. Page generated in 0.03636 seconds
Home