-
1. Re: Testing RichFaces
sergeysmirnov Sep 18, 2007 3:28 PM (in response to jwnorma)I do not understand your statement about "RichFaces generates it's own ids for components". RichFaces does nothing over that the standard JSF does.
-
2. Re: Testing RichFaces
sergeysmirnov Sep 18, 2007 3:36 PM (in response to jwnorma)We use Shale Test framework (with our extensions) and HtmlUnit on our side to test the developing components. However, it is more suitable for testing component rather than the web applications.
-
3. Re: Testing RichFaces
jwnorma Sep 18, 2007 5:56 PM (in response to jwnorma)Thanks for the quick response!
I meant that RichFaces takes a tag like
<rich:inputText id="text1" value="#{bean.input}" />
and
creates html:
<input type="text" id="blah:j_id24:text1" ...}
is it possible to force the id like in MyFaces Tomahawk? -
4. Re: Testing RichFaces
sergeysmirnov Sep 18, 2007 6:12 PM (in response to jwnorma)richfaces has no rich:inputText component
-
5. Re: Testing RichFaces
jwnorma Sep 19, 2007 9:03 AM (in response to jwnorma)I was using that merely as an example.
The question is the same, regardless of the component.
Can you force id's, or is there some other mechanism by which to uniquelty identify components once they are rendered. -
6. Re: Testing RichFaces
maksimkaszynski Sep 22, 2007 1:53 PM (in response to jwnorma)No, we don't force ids.
We follow JSF naming standards. -
7. Re: Testing RichFaces
maksimkaszynski Sep 22, 2007 1:55 PM (in response to jwnorma)Components could be easily located by their client ids.
<h:form id="f">
<a4j:commandButton id="b">
document.getElementById('f:b') will succeed