For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 6 replies, 4 voices, and was last updated 18 years, 6 months ago by
.
-
Posts
-
Hi,
I’m testing Eclipse 3.3/MyEclipse 6.0M1/Java6 on Windows XP.
I noticed that for several of my files, MyEclipse gives some bogus warnings. In one of those files I use JSF, but also just JSTL and the $ syntax. The editor gives the following warnings:
For the construct ${bundle[‘operations.begin’]}, it gives the warning: “El Syntax Error”. This is not true, the page runs fine in Tomcat 5.5 using MyFaces 1.1.5.
For the construct ${period.startday}, it gives the warning “The word ‘startday’ is not correctly spelled”. I’m not really sure if the spellchecker should give this kind of message. I would rather see something like: “According to the JavaBeans convention, ‘startday’ should be ‘startDay’ instead.” (or something like that).
Inside template text I have the entity € which should be legal according to the doctype of the page (the doctype is included in the page using a JSP include). However, the warning I get is: “The word ‘&&;euro;’ is not correctly spelled”. Just to be sure, I build the following example page and validated it through the w3c validator. It gives no errors or warnings:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head><title>test</title></head> <body> This is a € </body> </html>These warnings were given right after I did a fresh checkout of my project from the SVN repository. I found out that for many of my jsf files, validation was set to disabled (on a per-file basis, the global setting was enabled). When I enabled it and run validation manually, MyEclipse gave many, many more bogus warnings.
Among others, for every dynamic attribute on a taglib tag the warning: “Undefined attribute name (attributeName)” is given. I think it should detect that the tag declares it is accepting dynamic attributes, but fails to do this.
If I use the jsp attribute syntax for passing text or xml fragments to tags, everything between them is flagged as a warning. I.e. when I use XML tags, the editor gives a warning “Unknown tag (tag)” for each of them.
E.g.
Suppose I have a tag Foo in the ns x, with a property bar, then the following is legal JSP:
<x:Foo> <Foo:bar> <someTag> some text </someTag> </Foo:bar> </x:Foo>In this case, “<someTag> some text </someTag>” is just a string that the bar property will be set to. It makes no sense at all to validate this in the context of the JSP file.
Worse is that none of managed beans are recognized at all!
This used to work in MyEclipse 5.5, but now seems to be broken. Inside an #{} expression I can use auto-completion, but MyEclipse only gives me a choice of “FacesContext, view, a4j, a4jskin, applicationScope, cookie, header, etc”.
This all are standard beans or ones defined in META-INF/faces-context.xml files (as is the case of the a4j bean). My managed beans on the other hand are defined in separate files, which are mentioned using javax.faces.CONFIG_FILES in web.xml. The editor seems to ignore these.
In understand that a milestone release is often a little rough on the edges and I hope you’ll be able to use my feedback to improve matters for the 6.0GA release.
It has been exactly a month; MyEclipse 6.0GA should probably arrive in at most a few weeks (according to your roadmap even sooner 😉 ). Could you give feedback on whether any of the issues I reported above have in fact been addressed?
Thanks in advance
Hi henk,
Sorry for the delay on this one. The currency issue has been taken care of in ME 6.0 GA. The *managed bean* issue has also been address. Let me know if the problems persist.I am using Eclipse 3.3 and MyEclipse 6.0 GA. In my JSF editor when editting my faces-config.xml, I am getting “com is not spelled correctly” and “jsp is not spelled correctly”.
In the excerpt below, all ‘jsp’s are misspelled according to the editor.<navigation-rule>
<from-view-id>/userLogin.jsp</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/BillList.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>failure</from-outcome>
<to-view-id>/userLogin.jsp</to-view-id>
</navigation-case>
</navigation-rule>
