[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1494) add javax.el.LocalStrings
by Matt Drees (JIRA)
add javax.el.LocalStrings
-------------------------
Key: JBSEAM-1494
URL: http://jira.jboss.com/jira/browse/JBSEAM-1494
Project: JBoss Seam
Issue Type: Bug
Components: EL
Affects Versions: 1.3.0.ALPHA
Environment: Seam cvs (june 18, 2007)
Reporter: Matt Drees
jboss-el sometimes throws exceptions with localized messages, but jboss-el-api.jar does not include the appropriate message bundle. The result is EL evaluations sometimes result in an exception like this:
javax.el.ELException: java.util.MissingResourceException: Can't find bundle for base name javax.el.LocalStrings, locale en_US
at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:329)
at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:338)
....
--
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
18 years, 3 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1487) Changes to entity converter requires selectable entities to be managed.
by Felix Ho?feld (JIRA)
Changes to entity converter requires selectable entities to be managed.
-----------------------------------------------------------------------
Key: JBSEAM-1487
URL: http://jira.jboss.com/jira/browse/JBSEAM-1487
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.3.0.ALPHA
Environment: JBOss AS 4.2.0.GA
Seam 1.3.0.ALPHA
Reporter: Felix Ho?feld
Priority: Blocker
Fix For: 1.3.0.GA
The refactoring of the entity converter requires entities to be managed. If they are not the following exception is thrown:
org.hibernate.TransientObjectException: The instance was not associated with this session.
For me this is an api regression and therefore a blocker because it may introduce very nasty bugs which will be hard to detect. While a work around exists (see below) it is not easy to refactor existing application accordingly. Therefore this may effectivly prevent many people from upgrading to JBoss 4.2.0/Seam 1.3.0. (This is just my personal opinion and sort - feel free to downgrade this bug!)
Would it be possible to catch the exception and fall back to the old behaviour?
--
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
18 years, 3 months