These look like very handy additions (especially the first);  +1.

-- Adam


On 8/8/06, Gabrielle Crawford <[EMAIL PROTECTED]> wrote:

 Hi,

 I'm proposing two new methods for ClientConverter and ClientValidator in
issue 17. Please let me know if there are comments or objections?

 https://issues.apache.org/jira/browse/ADFFACES-117

 Thanks,

 Gabrielle

-------------------------------------------------------------


I would like to add these method to ClientConverter and ClientValidator,
which should allow getting rid of InternalClientConverter and
InternalClientValidator, which are in impl.

 The first method is used to load a custom js lib.


   /**
    * Gets the URI specifying the location of the js lib resource.
    * Only the first reference to a library will result in its being
imported.
    */
   public String getClientLibrarySource(
    FacesContext context);


 Th method below is used to load built-in js scripts, and should return the
same information that would be used in the importScript's "names" attribute
component. See
http://incubator.apache.org/adffaces/tagdoc/af_importScript.html

   /**
    * Supports importing the built-in scripts provided by ADF Faces.
    * It can be used to ensure that a Javascript function is available
    * before using it in a Javascript handler.
    * Only the first reference to a script will result in its being
imported.
    * @return a collection of function names
    */
   public Collection<String> getClientImportNames();


  Description


   I would like to add these method to ClientConverter and ClientValidator,
which should allow getting rid of InternalClientConverter and
InternalClientValidator, which are in impl. The first method is used to load
a custom js lib.     /**    * Gets the URI specifying the location of the js
lib resource.    * Only the first reference to a library will result in its
being imported.    */   public String getClientLibrarySource(
   FacesContext context); This method is used to load built-in js scripts,
and should return the same information that would be used in the
importScript's "names" attribute component. See
http://incubator.apache.org/adffaces/tagdoc/af_importScript.html
    /**    * Supports importing the built-in scripts provided by ADF Faces.
   * It can be used to ensure that a Javascript function is available    *
before using it in a Javascript handler.    * Only the first reference to a
script will result in its being imported.    * @return a collection of
function names    */   public Collection<String> getClientImportNames();

 Show ยป



Reply via email to