0 Replies Latest reply on Apr 26, 2011 10:22 PM by geschtli

    Here is a heavy workarround required

    geschtli Newbie



      The command  '<a4j:command' from Richfaces, so i have tested,

      has many bottlenecks and bug's.


      The command itself does not, for what it was foreseen.

      I think, it needs a good workarround.


      - First, holding an accurate Link over some rendering pages does not correct work.


      - Second, calling methods to send datas (eg. table-datas converted to csv-files)

      doesn't also not work.


      This all does work with '<h:commandLink', but not with '<a4j:commandLink'


      Where 'h' and 'a4j' is:

      xmlns:h="http://java.sun.com/jsf/html" (from Apache MyFaces jsf 2.0)

      xmlns:a4j="http://richfaces.org/a4j" (from Richfaces 4.0)


      I can give examples to this.


      What has driven the richfaces-developer, to layout such a

      awfull, garstly and time consuming command?


      With it, i must write separate servlet's to do the same, what

      i can do with '<h:commandLink' , that calls only simple backing bean methods!! 


      Also i found, setting the background-color for a header dataTable and dataScroller-

      elements, are 'nightmares' and needs a workarround!