I've created https://issues.apache.org/jira/browse/TOMAHAWK-164 to track this issue. I may take a look at EqualsValidator after I'm done if it isn't too difficult.
On 2/28/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > On 2/28/06, Rogers Reilly <[EMAIL PROTECTED]> wrote: > > 3) a tangent, but related- if you find yourself trying to get Tomahawk & > > ADF components working together, you may find this example helpful. The > > Tomahawk EqualsValidator won't work if you're comparing the component to > > an ADF component, and here's why: > > UIInput foreignComp = (UIInput) uiComponent.getParent().findComponent(_for); > > in EqualsValidator (line 72) is casting the "compare to" component to > > UIInput, but ADF input components don't extend UInput. You can create a > > custom ADFEqualsValidator by replacing the above with: > > UIXEditableValue foreignComp = (UIXEditableValue) > > uiComponent.getParent().findComponent(_for); > > or, of course, create an overarching EqualsValidator that tries both casts. > > Ok. I'm probably not going to try to fix EqualsValidator as > CompareToValidator in the sandbox supercedes it. > > Do ADF input components implement EditableValueHolder? I have gotten > CompareToValidator to a compilable state by replacing UIInput and > UIOutput typecasts to EditableValueHolder. > > I still need to do some testing, though. >
