× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I'm not sure where you are at based on version levels, but there could be
a potential compatibility issue with RichFaces and JSP since JSP has been
deprecated as the view technology for JSF 2.0+ and replaced by Facelets.
Newer versions of RichFaces may be designed to work with the latter. Just
thought I'd throw that out there...

Blake



date: Tue, 13 Mar 2012 12:41:31 -0500
from: "Hockchai Lim" <lim.hock-chai@xxxxxxxxxxxxxxx>
subject: Re: [WEB400] richfaces3.1.6GA causes duplicate ID error on
MyFaces1.1.9 and Tomahawk1.1.11

Well, yes, sort of.

In the jsp, I've a hidden field that looks like this => <t:inputHidden
forceId="true" id="leaderPA"
value="#{carbonCopyAndForwardingUpdateBean.leaderPhoneNumber.areaCode}"/>.
and a hidden field in a datatable that looks like this: <t:inputHidden
forceId="true" id="leaderPA"
value="#{item.leaderPhoneNumber.areaCode}"></t:inputHidden>.
The id name is the same for these two hidden fields. But, since the
second
one is in a datatable, tomahwak will auto append a sequential # after the
id
name of leaderPA, which makes them unique (No duplicate that is).

This jsp is an existing jsp and is running fine in production. But if I
add
richfaces jars in the lib folder and add richfaces filter setup in
web.xml,
it error out with duplicate ID. I'm thinking, the problem might be
because
richfaces filter does not understand how tomahawk datatable forceID
attribute work.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.