MyEclipse :: View topic - JSF 1.2 With Facelets

MyEclipse: JSF 1.2 With Facelets

jfrosch - Nov 09, 2007 - 05:40 PM
Post subject: JSF 1.2 With Facelets

I have a JEE 5 project using JSF 1.2 with Facelets. The MyEclipseIDE JSF Designer source editor flags the JSF 1.2 attributes as errors; i.e. the label attribute on an h:inputText element is flagged as unknown attribute.

When creating a new JEE 5 project with JSP, the JSF 1.2 attributes are not flagged as errors so I suspect I have a configuration problem with the JSF XML schema files.

The html opening element is specified as follows:

Code:

Any ideas on what I need to do to get the JSF 1.2 XML schemas to be used?

Thanks.

Jack[/code]

support-nipun - Nov 14, 2007 - 07:50 AM
Post subject: RE: JSF 1.2 With Facelets

In your designer window, add the TextInput from the palette under "JFS HTML". Is it still marked as an unknown attribute ?

rwryme - Nov 15, 2007 - 05:57 PM
Post subject: RE: JSF 1.2 With Facelets

I posted the identical problem under the topic "Post subject: Apparently bogus errors on JSP files ". Nipun responded with a screen clip showing the label tag without the error. I assumed it must be my configuration problem, but I can create a new JEE5, JSF, Facelets application from scratch as Nipun purported to do and I get the error.

I just tried adding from the palette under JFS-H and I get the error.

I no longer believe this is a configuration problem, I think it is an intermittent bug, because I use this tag/label consistently. Normally the first time I add it to an xhtml file, I get the line flagged as an error. But after some time the marker may go away. I have multiple files in the same project, some of which exhibit the failure some not. Once the flag goes away it does not seem to come back but I can't find any pattern as to what causes it, or causes it to clear up.

jfrosch - Nov 15, 2007 - 11:16 PM
Post subject: Re: RE: JSF 1.2 With Facelets

support-nipun wrote:

In your designer window, add the TextInput from the palette under "JFS HTML". Is it still marked as an unknown attribute ?

Yes it is.

I dragged the TextInput control onto the design canvas and got an opening and closing h:inputText element. I added the attribute, label="Name: ", and the attribute was flagged as being an unknown attribute. Ditto for converterMessage, requiredMessage, etc.

All the JSF 1.2 attributes are unrecognized, even though my build path includes the JEE 5 library with (presumably) JSF 1.2 jars. The following entry is from my .classpath file:

Code:

It's not a huge issue at this moment, but I'd sure like to figure out why I can use JSF 1.2 in a JSP, but not in a Facelets XHTML page.

Thanks for any help.

support-rkalla - Nov 21, 2007 - 06:28 PM
Post subject: RE: Re: RE: JSF 1.2 With Facelets

Guys, thanks for your patience. It looks like a bug on our end with the Facelets editor not recognizing the 1.2 taglibs. I am filing it ASAP.

jfrosch - Nov 21, 2007 - 10:39 PM
Post subject: RE: Re: RE: JSF 1.2 With Facelets

Excellent. Thanks!

To everyone in the USA - have a happy Thanksgiving.

frweisma - Dec 13, 2007 - 04:57 PM
Post subject: RE: Re: RE: JSF 1.2 With Facelets

I having the same problem. But it is not only restricted to the jsf 1.2 taglib. Every additional taglib is ignored by the content assistant.
I have as additonal tag libs the richfaces included. The designer add the taglibs correctly in the header. But the contant assistant takes
no notice of this.

support-rkalla - Dec 13, 2007 - 06:39 PM
Post subject: RE: Re: RE: JSF 1.2 With Facelets

frweisma,
The facelets editor, due to how facelets taglibs are designed, cannot pickup the validation and content-assist definitions for the taglibs on the fly, it's a process we have to support and include in the editor at this time.

frweisma - Dec 15, 2007 - 12:49 PM
Post subject: RE: Re: RE: JSF 1.2 With Facelets

So this means that you have completly different implementations between JSP and XHTML. Because when i design a JSP site,
all properties of foreign taglibs are supported.

support-rkalla - Dec 15, 2007 - 03:24 PM
Post subject: RE: Re: RE: JSF 1.2 With Facelets

JSP, XHTML and Facelets are all similar in structure/syntax highlighting, but if you are asking about grammars for the languages and content-assist/taglib support, they are all very different.

jfrosch - Jan 29, 2008 - 03:44 PM
Post subject: RE: Re: RE: JSF 1.2 With Facelets

Quote:

Guys, thanks for your patience. It looks like a bug on our end with the Facelets editor not recognizing the 1.2 taglibs. I am filing it ASAP.

Has there been any progress on this?

support-rkalla - Jan 29, 2008 - 06:45 PM
Post subject: RE: Re: RE: JSF 1.2 With Facelets

No, we haven't had a release since it was filed. I am going to push for it to get fixed in 6.5 or 7.0 later this year.

jfrosch - Jan 29, 2008 - 07:49 PM
Post subject: Re: RE: Re: RE: JSF 1.2 With Facelets

support-rkalla wrote:

No, we haven't had a release since it was filed. I am going to push for it to get fixed in 6.5 or 7.0 later this year.

Ouch! I truly hope the fix is sooner than later.

IMO, one of the biggest advantage of JSF 1.2 is the introduction of time-saving, code-saving attributes on the HTML tags.

For instance, in JSF 1.1, one had to create a separate h:message element for each input field, but JSF 1.2 allows one to specify the message value, and even Severity level styles, on the same element. This not only saves coding an extra element, but when the form is composed in a 2-column gridPanel, I usually wrap the input field and h:message element into an h:panelGroup to keep the message rendered close to the field. Being able to have a 2-column, label/field table without the extra h:panelGroup is an additional time savings.

Of course, there's much more in JSF 1.2 that saves times and makes coding easier.

So not having JSF 1.2 support in the Facelets editor isn't just inconvenient; it's causing a lot of extra code to be written while we await this important fix.

If the code for this editor is open source, perhaps we can all take a look to see if there's a way to slipstream in a fix before the next big release?

Thanks for your understanding.

anthonyestelita - Feb 14, 2008 - 04:20 PM
Post subject: RE: Re: RE: Re: RE: JSF 1.2 With Facelets

vote +6 (we have 6 licenses) to get this fix/addressed sooner. :-)

We too are using JSF 1.2 and we currently have to live with the validation errors. And we have to manually type in the new JSF 1.2 attributes/tags. Not much of a big deal, just some times a pain (it gets hard to see real bugs in your code when your problems tab has 20+ items about invalid tags/attributes).

Hopefully we don't have to wait till the end of this year for this!

Anthony

support-rkalla - Feb 14, 2008 - 04:40 PM
Post subject: RE: Re: RE: Re: RE: JSF 1.2 With Facelets

Quote:

IMO, one of the biggest advantage of JSF 1.2 is the introduction of time-saving, code-saving attributes on the HTML tags.

I just want to clarify, we support JSF 1.2 with standard JSP pages, but not in Facelets yet. (I realize your request is for Facelets, I just want to clarify for anyone running through the thread and reading it quickly)

Quote:

We too are using JSF 1.2 and we currently have to live with the validation errors.

anthonyestelita - Feb 14, 2008 - 06:00 PM
Post subject: RE: Re: RE: Re: RE: JSF 1.2 With Facelets

Yes we are seeing these validation errors in our xhtml pages. ;-(

TobyDyer - Apr 21, 2008 - 11:28 AM
Post subject:

Any update on when support for JSF 1.2 with Facelets will be added? Is this something we can expect in the near future (i.e. weeks) or is it not on the current roadmap? I would love to use MyEclipse on my current project but without this support it's not an option.

support-rkalla - Apr 21, 2008 - 06:59 PM
Post subject:

TobyDyer,
I think you'll be seeing some nice updates for JSF/Facelets in our 6.5 release.

jwcard - Dec 11, 2009 - 03:45 PM
Post subject: Facelets editor not recognizing JSF 1.2 taglibs

I am currently use MyEclipse 8.0 GA and this problem still exists. Are there any workarounds / patches etc...or plans to fix this is a future release?

Any info would be appreciated...

support-shalini - Dec 14, 2009 - 06:22 AM
Post subject: RE: Facelets editor not recognizing JSF 1.2 taglibs

jwcard,
I could not replicate this at my end. Attribute label="Name: " is no longer tagged as invalid. Can you give some more information?
1. Can you copy paste your installation details from MyEclipse > Installation Summary > Installation Details?
2. Can you send us some code/file to replicate this issue. You can use the PM button at the end of the post.

jwcard - Dec 14, 2009 - 01:48 PM
Post subject: RE: Facelets editor not recognizing JSF 1.2 taglibs

Here is the installation details report:

Code:

*** Date:
Monday, December 14, 2009 8:22:06 AM EST

** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 8.0
Build id: 8.0-20091120

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 8.0
Build id: 8.0-20091120

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse 8.x Latest\myeclipse.exe
-name
Myeclipse
--launcher.library
C:\Program Files\Genuitec\MyEclipse 8.x Latest\../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519\eclipse_1206.dll
-startup
C:\Program Files\Genuitec\MyEclipse 8.x Latest\../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
C:/Program Files/Genuitec/MyEclipse 8.x Latest
-configuration
configuration
-vm
C:/Program Files/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll

Here is a block of sample code. In this block MyEclipse highlights 'requiredMessage' as unknown attribute

Code:

<h:selectOneMenu value="{LoginBean.loginOrganization}" requiredMessage="Organization Required" tabindex="3">
<f:selectItems value="#{LoginRS.orgs}"/>
<f:converter converterId="OrganizationConverter"/>
</h:selectOneMenu>

Hope this helps...

j

support-shalini - Dec 15, 2009 - 08:30 AM
Post subject: RE: Facelets editor not recognizing JSF 1.2 taglibs

jwcard,
Thank you for the details. I shall escalate this to the dev team.

fabio.imperioli - Dec 15, 2009 - 04:35 PM
Post subject: RE: Re: RE: Re: RE: JSF 1.2 With Facelets

[quote="support-rkalla"]

Quote:

IMO, one of the biggest advantage of JSF 1.2 is the introduction of time-saving, code-saving attributes on the HTML tags.

Quote:

We too are using JSF 1.2 and we currently have to live with the validation errors.

Anthony, do you mean JSF in straight JSP pages, or Facelets/XHTML pages? Our JSP editor will correctly parse the updated definitions from the TLDs for JSF 1.2 in Java EE 5, so you shouldnHi All,

I need to use jsf 2.0 in order to use the ajax functionality in jsf.
Is this new version implemented in MyEclipse professional 8.x ?
Or there is another way to use ajax in version 1.2 in my eclipse 7.5 ?

best regards,

Fabio

fabio.imperioli - Dec 15, 2009 - 04:35 PM
Post subject: RE: Re: RE: Re: RE: JSF 1.2 With Facelets

I need to use jsf 2.0 in order to use the ajax functionality in jsf.
Is this new version implemented in MyEclipse professional 8.x ?
Or there is another way to use ajax in version 1.2 in my eclipse 7.5 ?

best regards,

Fabio

support-nipun - Dec 15, 2009 - 10:27 PM
Post subject: RE: Re: RE: Re: RE: JSF 1.2 With Facelets

We don't support JSF 2.0/Java EE 6 yet -- its' going to be part of our 9.x release series next year.

hb - Jun 10, 2010 - 09:13 PM
Post subject: RE: JSF 1.2 With Facelets

Quote:

Here is a block of sample code. In this block MyEclipse highlights 'requiredMessage' as unknown attribute
Code:

Code:

Hope this helps...

Any progress on this? Seems this is still a bug in 8.5. Myeclipse flags "requiredMessage" as error but not "requireMessage" (but that won't work).

I would try to add the missing "d" if someone could point me to the right file.

Support-Brian - Jun 11, 2010 - 07:55 AM
Post subject:

hb,

I believe we did fix this bug in 8.5 but I will ask the team to take another look at it now. If you invoke auto complete inside the h:selectOneMenu element (after deleting require[d]Message) you should be prompted with the attribute from autocompletion.

Are you prompted with requireMessage or requiredMessage?

hb - Jun 11, 2010 - 06:31 PM
Post subject:

Quote:

Are you prompted with requireMessage or requiredMessage?

that's the Problem: Autocomplete gives me the wrong "requireMessage" and the right one is flagged as error (at h:inputText btw)

support-joy - Jun 14, 2010 - 08:30 AM
Post subject:

hb,

Thank you for your feedback. I shall escalate your findings to the dev team.

Best.

MWThomson - Jan 24, 2011 - 07:57 PM
Post subject: Any update?

support-joy wrote:

hb,

Thank you for your feedback. I shall escalate your findings to the dev team.

Best.

Any update as to when this will be fixed? We still see this issue in 8.6.

Version: 8.6.1
Build id: 8.6.1-20101117

support-swapna - Jan 27, 2011 - 06:30 AM
Post subject: RE: Any update?

MWThomson,

I could not replicate this issue with the Version and Build id you specified.
Can you answer some questions for me?

1. When you invoke the autocomplete does it prompt for 'RequireMessage' or 'RequiredMessage' ?
2. Do you see it for < h:selectOneMenu> or <h:inputText> ?
3. Does the validator highlight 'RequireMessage' as unknown attribute?
4. Do you get suggestions when you delete the 'RequireMessage' and invoke the autocomplete?

MWThomson - Jan 27, 2011 - 04:06 PM
Post subject:

Note that it does work correctly at runtime.

1) auto complete does not show it

2) it does show up for <h:selectOneMenu /> and <h:inputText />

3) Problems view:
Unknown attribute (requiredMessage) userInformation.xhtml /<appname>/web/secure/administration L/<appname>/web/secure/administration/userInformation.xhtml Facelets Problem (JSF)

4) I do get suggestions, including "required", but not "requiredMessage" or even "requireMessage"

Our namespace:

Code:

<ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:c="http://java.sun.com/jstl/core" xmlns:f="http://java.sun.com/jsf/core" xmlns:ice="http://www.icesoft.com/icefaces/component" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:ice-cc="http://www.icesoft.com/icefaces-composite-comps">

Support-Brian - Jan 28, 2011 - 03:07 PM
Post subject:

Thanks for the detailed explanation with screenshots; as you can see, we did fix this issue with for the regular HTML prefix but not for the ICEfaces prefix which escaped us. I'll try to get this fixed in the upcoming 9.0 GA release, thanks again for the report.

MWThomson - May 27, 2011 - 05:48 PM
Post subject:

Support-Brian wrote:

Any word on when this will be fixed? It is still a problem in 9.0 (Build id:9.0-20110318).

Support-Brian - May 30, 2011 - 09:35 AM
Post subject:

MWThomson,

Thanks for reminding us. I've put this out as a high priority item for 9.0.1 due in a couple of weeks. My team is looking at the problem right now and may have a few questions for you shortly.

Support-Brian - Jun 07, 2011 - 08:57 PM
Post subject:

MWThomson,

We took this up with the ICEfaces team and the issue will be fixed in the upcoming 1.8.3 and 2.1 releases of ICEfaces. Once these versions of ICEfaces are publicly available, updating your libraries to use that version will fix the problem.

See here for more details: http://jira.icefaces.org/browse/ICE-6930

Appreciate your support.