[
https://jira.jboss.org/jira/browse/JBSEAM-4422?page=com.atlassian.jira.pl...
]
deanhiller commented on JBSEAM-4422:
------------------------------------
my bad, can we open a bug on not having the name of entityManager configured in so many
different locations. That leads to exactly this problem. (ie. tomcat does not have you
configure the port in 3 different locations to work). It would be nice if there was a
component that held the name of the entityManager or something so it was only configured
once which would avoid users spending alot of time here.
thanks,
Dean
cannot rename entityManager if using selectOneMenu with
convertEntity
---------------------------------------------------------------------
Key: JBSEAM-4422
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4422
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.2.CR2, 2.1.2.GA, 2.2.0.CR1, 2.2.0.GA
Reporter: deanhiller
Assignee: Pete Muir
If you are using h:selectOneMenu along with convertEntity, then in the components.xml
file, renaming entityManager to mgr or anything else breaks. It results in a
NullPointerException because JpaEntityLoader in seam-ui returns a hardcoded
"entityManager" to have looked up which does not exist because I had renamed it.
I had to go through all my code and rename mgr back to entityManager because this was
hardcoded.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira