Michael Brennan wrote: > As a convenience, I also > support a bit of syntactic sugar for Java components added to the form > as variables. Top-level accessible methods on that object are exposed as > function with no namespace whose name starts with "<variable name>.". > For example, a method called "bar()" on a component assigned to > variable "foo" would be exposed as a function "foo.bar()".
Oops. I need to make a minor correction to that "no namespace" statement. The function will be in the same namespace as the variable name. So a variable "ns:foo" containing a Java object with a method "bar()" would result in a function exposed as "ns:foo.bar()". The variable name can also contain periods, e.g. the function "foo.one.bar()" would map to the method "bar()" on the variable "foo.one" (if it exists). Any explicitly registered function takes precedence over this automatic function resolution. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jaxen-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxen-interest
