[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1969) updatedMessage, deletedMessage and createdMessage in framework.Home cause NPE if getEntityClass is overridden
[ http://jira.jboss.com/jira/browse/JBSEAM-1969?page=comments#action_12380145 ]
Pete Muir commented on JBSEAM-1969:
-----------------------------------
Sure, I understand the bug.
I don't understand what you are talking about here
"However, there is one question. The @Create method calls getEntityClass(), which
must be non-null and establishes the value of the entityClass private field. That begs the
question, should subclasses be forced to call setEntityClass() in the getEntityClass()
override?"
and
"However, the same problem will come up if you try to override getId(). I think in
that case it is okay to enforce the call to setId() since that is a very special
property."
updatedMessage, deletedMessage and createdMessage in framework.Home
cause NPE if getEntityClass is overridden
-------------------------------------------------------------------------------------------------------------
Key: JBSEAM-1969
URL: http://jira.jboss.com/jira/browse/JBSEAM-1969
Project: JBoss Seam
Issue Type: Bug
Components: Framework
Environment: Mac OSX 10.4.8, Jboss 4.2.1, Seam 1.3.0
Reporter: Damian Harvey
Assigned To: Dan Allen
Priority: Trivial
Fix For: 2.0.1.GA
Attachments: HomeTest.java, JBSEAM-1969-v1.txt, SimpleEntity.java
I am extending an existing class (BookingHome) that extends EntityHome. My BookingHome
class needs to override getEntityClass. Doing this then results in a NPE as
updatedMessage, deletedMessage and createdMessage refer to entityClass rather than
getEntityClass.
--
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