Hi, With the change in 5.0.16 that means it fails fast if you have both @Property and getter and setter for a field we have removed quite a few @Property annotations as we realize some fields were silently ignoring the existing getters and setters (which sometimes have a tiny bit of logic in).
The odd thing is that now we are getting an exception. Does @Parameter transform a field into a final field now? I don't see any reference to same in the release notes. The exception has at its root: "Caused by: org.apache.tapestry5.ioc.internal.util.TapestryException: Binding LiteralBinding[cssClassName: slotCta] is read-only. at org.apache.tapestry5.internal.bindings.AbstractBinding.set(AbstractBindi ng.java:45) at org.apache.tapestry5.internal.structure.InternalComponentResourcesImpl.w riteParameter(InternalComponentResourcesImpl.java:329)" I am was advising the team in general not to use @Property any more due to the nature of the gotchas but this would rather put a hole in that. I prefer handcoded getters and setters to simplify unit testing... Any ideas? Many thanks is advance Russell
