[Frank Weber]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[Frank Weber]

This message has not been recovered.

[Frank Weber]

This message has not been recovered.

[Frank Weber]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[Frank Weber]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[Frank Weber]

thanks for your feedback. I will try the XML Editor route, but I would like to look into the JSP side again …

Well I mentioned JSP 2.0 because it is the current standard, but such JSP Documents (Facelets via XHTML) should work with JSP version 1.2 as well, shouldn’t they?

http://www.onjava.com/pub/a/onjava/2001/11/28/jsp_xml.html

Can the ME JSP Editor handle JSP 1.2 Documents?

Thanks in advance,

Frank

[Frank Weber]

I do have problems to define the right namespaces and xsd file associations for the XML editor to work with facelets. It would be great to get an example … as all other pages could be derived from there !

On the JSP Editor route I found a small example that seems to work for ME as well:
http://blog.exadel.com/?p=12

There is only one tricky issue, when I changed an existing jsp I got this error:
Unable to load tag handler class “null” for tag “ui:composition”.
NOTE: No JSP line number was avaliable so line 1 was used for the marker.

So I had to follow this procedure:
1) you need to create first a jsp with the given structure (see below)
2) save it
3) compose your Facelets / JSP logic

JSP structure:

 <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
        xmlns:ui="http://java.sun.com/jsf/facelets"
        xmlns:h="http://java.sun.com/jsf/html">
    <jsp:text>
    <ui:composition template="/template.jsp">

        </ui:composition>
    </jsp:text>
</jsp:root>

Frank

[Riyad Kalla]

Frank sorry for the delay in responding, thank you very much for posting this information for others as well as us to use as a test case. I would like to clarify that unless you create a new JSP page with the content above, you are saying the page get’s an error? (for example if you open an existing page and replace all the contents with the above) is this correct?

We are looking at a timeline of MyEclipse 5.0 to refresh our JSP editor against the latest WTP snapshot to hopefully correct some of these XHTML and JSP 2.0 issues, in the mean time we appologize for the inconvenience.

[Frank Weber]

I converted the demo application xhtml files straigth to jsp files. Then I tried to change the format to the JSP Structure above, but the mentioned error remained.

Please what is the perspective on the X/HTML Editor side. Facelets support xhtml mockups that can be extended via aliases that are translated during compile time. ..

You may remember our discussions on JSF’s caching problem, which force you to redeploy the web app to see the changes performed in the view. I guess the hot-sync will work earliest with JSF 1.2, right? Or do you have any new insights on this?

I looked into the ME roadmap and feature list, but I am not too clear when the JSP/JSF Editor/Previewer on Linux would be supported. Can you clearify this for me?

Frank

[Frank Weber]

According to my tests the faclets guess number demo application works and the hot-sync seems to work as well, which is great! I added an outputText and later style to it and commented it out – and all was updated correctly in the view. Need to test it with other tags …

However the mentioned error on some JSPs appears even with the outlined procedure. … and the syntaxt gets not validated when you save the jsp.

So I tried to validate the JSPs and got reported “The maximum number of errors have been exceeded”. .. even on this mentioned JSP structure when I changed the version to 1.2.

Any idea how to get this to work correctly in ME before 5.0 comes out?

Frank

[Frank Weber]

The autocompletion works correctely for all tags of the jsp document attached below in ME.
For xhtml and jsf/html related tags syntax errors are handled correctly. See code below.

However the facelet tag related syntax errors are not handled correctly. I suspect that their is some problem on what the facelets provides and what ME JSP editor requires. Any idea what might be missing?

I have the facelets.tld, html_basic.tld, jsf_core.tld in the WEB-INF dir.

This is located under guessnumber/web/WEB-INF/lib (and the build path)
commons-beanutils.jar commons-logging.jar jsf-api.jar
commons-collections.jar el-api.jar jsf-facelets.jar
commons-digester.jar el-ri.jar jsf-impl.jar

<jsp:root xmlns:jsp=”http://java.sun.com/JSP/Page&#8221; version=”1.2″
xmlns:ui=”http://java.sun.com/jsf/facelets&#8221;
xmlns:h=”http://java.sun.com/jsf/html”&gt;
<jsp:text>
<html>
<head>
<title>Simple JSP Document</title>
</head>
<body>
<h1>Hello World</h1>

<h:outputText value=”bla”/>

<ui:define name=”title”>
<h:outputText value=”my Title”/>
</ui:define>

</body>
</html>
</jsp:text>
</jsp:root>[/code]

[Riyad Kalla]

Any idea what might be missing?

I’m sorry, I really don’t know. I’ve asked another developer that primarily works on the JSP designer and right now we are waiting for WTP to stabalize their editors which is what we hope to resync with for their 1.0 release, we hope by that time full XHTML and JSP 2.0 support will be completed, until then I believe it’s just a matter of trying different things.

[Author]

Posts