The first version of the spec specifically disallowed supporting such setters afaik, but I seem to recall a discussion about an errata on the spec maybe related to that? Any information ? It seems our implementation does not like setters which have a non void return value, just wanted to check if that was still a mandated behavior or not.
-- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
