You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Walter Mourão <wa...@gmail.com> on 2011/08/30 13:12:48 UTC

[Trinidad] Fwd: [Bug 315892] In xhtml pages, content assist for elements attributes worksonly for JSF 2 base library.

Hi folks,
the text below refers to code completion in Eclipse.

Does Trinidad have such 'attribute definitions in their *.taglib.xml
descriptors' ?

Walter Mourão
http://waltermourao.com.br
http://arcadian.com.br
http://oriens.com.br



---------- Forwarded message ----------
From: <bu...@eclipse.org>
Date: Mon, Aug 29, 2011 at 8:26 PM
Subject: [Bug 315892] In xhtml pages, content assist for elements attributes
worksonly for JSF 2 base library.
To: walter.mourao@gmail.com


https://bugs.eclipse.org/bugs/show_bug.cgi?id=315892
Product/Component: Java Server Faces / core

--- Comment #32 from Ian Trimble <ia...@oracle.com> 2011-08-29
19:26:48 EDT ---
It has been explained several times in this bug report why there is a
difference. When dealing with JSF 2.0 and *.taglib.xml descriptors, a
different
mechanism is used to determine the available attributes. If the author of
such
a library has not provided the attribute information, it is not correct to
assume that any available TLD is appropriate to describe the tag library -
there could be good reason that a TLD and *.taglib.xml files describe
different
attributes and it would be wrong for us to assume these two descriptor
methods
are interchangeable.

That said, there is no simple solution that can address this anyway; a
factory
has been chosen to provide the content model before element information is
requested. There is no way to determine the validity of a factory based on
what
arbitrary attribute information it is provided. That is, the factory can not
be
determined to be invalid at the point where the factory is registered, and
when
the factory is asked to provide element information, it is too late to "swap
in" another factory based on some heuristic that decides which is more
appropriate.

PrimeFaces 2.2.1 and RichFaces 4.0.0 now have attribute definitions in their
*.taglib.xml descriptors; I doubt this was done for the fun of it, the
definitions should have been there all along and the authors have rectified
the
problem. I believe this to be the correct resolution for this issue; library
authors need to provide the expected attribute definitions with their
libraries.

--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are a voter for the bug.
You are on the CC list for the bug.