[
http://jira.jboss.com/jira/browse/JBSEAM-3135?page=comments#action_12418709 ]
Nicklas Karlsson commented on JBSEAM-3135:
------------------------------------------
Actually I have them both, planning on finishing the second edition now on my vacation
;-)
But was I wrong in terminology or categorically wrong, should my original request have
been for a check against a key equality implementation? As defined in the old wiki
SeamProblemsFAQ and
http://seamframework.org/Documentation/IGetValueIsNotAValidOptionWhenUsin...
Or does a long running conversation and SMPC take care of everything?
I know this is the wrong forum for this but just to make sure I don't recommend it
anymore to people with similar problems...
warning for non-overridden hashcode/equals when using
s:convertEntity
---------------------------------------------------------------------
Key: JBSEAM-3135
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3135
Project: Seam
Issue Type: Feature Request
Components: JSF Controls
Reporter: Nicklas Karlsson
Considering the largish number of posts on the forum where "convertEntity
doesn't work" or "the value doesn't stay selected", it could be
nice to have a log.warn statement if s:convertEntity encounteres an entity without
overridden equals/hashcode. If doable, that is.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira