CommandLink behaviour

[Balaji Saranathan <ba...@wipro.com>]

Ok these are my findings, if it would help you in anyways. I don't know
if these behaviours are accepted by the Specification for compatibility
tests. A quick run through of the specification doesn't seem to mandate
any on these lines. But I may be wrong.

I had a simple CommandLink in both Sun RI and myfaces based application.

Scenario 1:

The command link are not enclosed in <h:form> tags.

Sun RI threw a null pointer exception.

My faces gave a empty blank page with a whole lot of html source but
there is no value between <a> </a> tag.

Scenario 2:

The command link are enclosed in <h:form> tags.

Sun RI renders properly and includes JavaScript on the onclick event.

MyFaces renders properly but has a whole lot of JavaScript generated
that includes clearing the dummy form, a JS function called getScrolling
etc.

I just changed the subject of the mail to reflect the problems with the
component.





Confidentiality Notice 

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.