I am testing Helios 3.6 since M2 release.
The Content Assist in xhtml for primefaces and others don´t work for element attribute with XHTML file. This problem don´t occur if it´s a JSP file. Please, take a look at the following post. If a understand correctely, there is some problem with taglib configuration for primefaces and others.
I gave an richfaces example, but the same happens with primefaces and icefaces, etc.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=315892
I don´t believe this is an JSF vendor problem with taglib.
CA in xhtml don´t work for elem attribute with XHTML file
Try JBoss Tools for Eclipse please. Here is the link http://www.jboss.org/tools. With the last releases of JBoss Tools you have almost fully JSF 2 support and CA as well.
PrimeFaces Cookbook (2. edition): http://ova2.github.io/primefaces-cookbook/ Learning Angular UI Development with PrimeNG: https://github.com/ova2/angular-develop ... th-primeng Blog: https://medium.com/@OlegVaraksin
-
- Prime
- Posts: 18616
- Joined: 05 Jan 2009, 00:21
- Location: Cybertron
- Contact:
Taking a look at page 372 of user's guide might help.
Cagatay, the workaround in the user´s guide don´t work anymore in Helios.
In Helios, this caused cyclical dependency. They provided a fix for this since Helios CR2:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=314030
With this fix, this workaround don´t work anymore.
We can´t use JBoss tools because we are not allowed (don´t ask me why
I think a lot of people will complain about this in the final release of helios.
Thanks for the help.
In Helios, this caused cyclical dependency. They provided a fix for this since Helios CR2:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=314030
With this fix, this workaround don´t work anymore.
We can´t use JBoss tools because we are not allowed (don´t ask me why
I think a lot of people will complain about this in the final release of helios.
Thanks for the help.
-
- Prime
- Posts: 18616
- Joined: 05 Jan 2009, 00:21
- Location: Cybertron
- Contact:
I see, we should wait for a stable helios as it seems.
The Eclipse TEAM will to take a look at the taglib declaration in Primefaces to see there is something wrong.
I recommended Primefaces 2.0.2.
I still think that is a Helios issue, not primefaces (richfaces, Icefaces, etc). By the way, as soom I have an answer I will post here.
Helios release date is in 23 july and this issue need to be fixed before it´s release.
If you want to take a look in what is going on, follow this link
https://bugs.eclipse.org/bugs/show_bug.cgi?id=315892
I recommended Primefaces 2.0.2.
I still think that is a Helios issue, not primefaces (richfaces, Icefaces, etc). By the way, as soom I have an answer I will post here.
Helios release date is in 23 july and this issue need to be fixed before it´s release.
If you want to take a look in what is going on, follow this link
https://bugs.eclipse.org/bugs/show_bug.cgi?id=315892
I found this https://bugs.eclipse.org/bugs/show_bug. ... 315892#c15:
Thanks Tai
So is this a PrimeFaces problem?Correct. If you look at prime faces as an example, here's an example of a tag
definition for the accordian panel:
<tag>
<tag-name>accordionPanel</tag-name>
<component>
<component-type>org.primefaces.component.AccordionPanel</component-type>
<renderer-type>org.primefaces.component.AccordionPanelRenderer</renderer-type>
</component>
</tag>
So they have not provided us any information about the attributes. Compare
this to the tag libs that are provided for the built-in h:outputText tag...
Thanks Tai
-
- Prime
- Posts: 18616
- Joined: 05 Jan 2009, 00:21
- Location: Cybertron
- Contact:
Why helios doesn't read the attributes from the tld, that's what other IDEs do as I know.
-
- Information
-
Who is online
Users browsing this forum: No registered users and 49 guests