-- Adam
On 8/24/06, Thomas Spiegl <[EMAIL PROTECTED]> wrote:
I started to work on Trinidad and tomahawk incompatibilities.
Problem #1 (fixed partly)
When using the ADF form, tomahawk links won't work. The reason for
this: Tomahawk links are bound to the MyFaces form component.
This problem I could partly solve. I started off using an environment,
which is typical for users creating an ADF project with JDeveloper.
Sun RI 1.1_02
ADF Faces
Tomahawk 1.1.5
Tomahawk links can now be used in conjunction with anADF form. In this
case the ADF form will be detected, and the links onclick method will
be rendered the ADF way. The name of the hidden input will be
different than the one MyFaces uses. This fact is considered when
extracting the request parameter in the link renderers decode method.
Restriction (not solved by now)
Tomahawk links are not working using h:form, because the Sun RI Form
is not compatible with the MyFaces form. I have in mind that Martin
recently resolved this issue, but it did not seem to work for me.
Some components using links may still have problems (JSCookMenu was
one of this candidates).
Problem #2 (needs to be solved)
Environment:
MyFaces implementation
ADF Faces
Tomahawk 1.1.5
The hidden parameter "jsf-sequence" will not be rendered when using an
ADF form.
Possible solution: A new tomahawk component (myfacesParams), renders
all hidden input fields needed by the MyFaces implementation, eg the
jsf-sequence param. This artificial component must then be added to
every ADF form. This approach will work, but it's fault-prone. Any
ideas?
Thomas
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
