On Sat, 31 May 2014 07:51:56 -0300, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
I don't see a reason why Tapestry doesn't support such a case. Unless
Tapestry uses a 3rd party library that strictly complies with the java
beans specifications to read getters\setters,
Tapestry doesn't use a 3rd party library. It uses the classes in the
java.beans package. That's a 1st party library in the Java world. Classes
from Java itself. So the source code generator is actually wrong (at least
in the configuration that generated isXXX() methods returning Boolean).
In this very specific case, I think the JavaBeans specification is
correct: Boolean isn't actually a boolean type, because it has three
values: true, false and null. So it doesn't make any sense an isXXX()
method which can return something which isn't true nor false.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
