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, It would be a pleasure for Tapestry users to find Tapestry going an extra mile to make their lives easier, that's why we are using Tapestry in the first place, Its awesome.
I personally don't see a reason why a "is" methods should support primitive boolean only. I won't be surprised if the specs change in the future to support Boolean objects too, but should we wait for that to happen to change how Tapestry works ?! *---------------------* *Muhammad Gelbana* http://www.linkedin.com/in/mgelbana On Fri, May 30, 2014 at 9:29 PM, Erich Gormann <e.gorm...@gormann.de> wrote: > Thanks Howard, > > we fixed the way CXF generates our webservice types and now we have the > desired getter. > Of course it was not compliant to the bean spec before, but I saw no way > to change the generation behavior. > > Regards > Eric > > Am 30.05.2014 18:43, schrieb Howard Lewis Ship: > > If you getter method is "is", not "get", prefixed then the type MUST be >> boolean, not Boolean. That's well defined in the Java Beans >> specification. >> >> >> On Thu, May 29, 2014 at 12:41 AM, Lance Java<lance.j...@googlemail.com> >> wrote: >> >> Eg: https://gist.github.com/uklance/0d461f9618b3a131ca3b >>> On 28 May 2014 12:43, "Lance Java"<lance.j...@googlemail.com> wrote: >>> >>> Another solution is to override / decorate BeanModelSource. The easiest >>>> solution is call the default implementation then add the extra >>>> PropertyModel(s) to the BeanModel. >>>> >>>> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
