[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
17 years, 4 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
17 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1278) Recent EL changes seems to break SeamTest
by Stuart Robertson (JIRA)
Recent EL changes seems to break SeamTest
-----------------------------------------
Key: JBSEAM-1278
URL: http://jira.jboss.com/jira/browse/JBSEAM-1278
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1.GA
Environment: Seam from CVS, Facelets, Jboss 4.2.0CR2
Reporter: Stuart Robertson
I'm seeing the following:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at org.jboss.seam.jsf.SeamApplication.getExpressionFactory(SeamApplication.java:104)
at org.jboss.seam.core.Expressions.getExpressionFactory(Expressions.java:41)
at org.jboss.seam.core.Expressions$1.createExpression(Expressions.java:67)
at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:71)
at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1688)
at org.jboss.seam.Component.getInstance(Component.java:1637)
at org.jboss.seam.Component.getInstance(Component.java:1614)
at org.jboss.seam.Component.getInstance(Component.java:1608)
at org.jboss.seam.jsf.SeamELResolver.getValue(SeamELResolver.java:49)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44)
at org.jboss.el.parser.AstValue.getTarget(AstValue.java:34)
at org.jboss.el.parser.AstValue.setValue(AstValue.java:83)
at org.jboss.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249)
at org.jboss.seam.util.UnifiedELValueBinding.setValue(UnifiedELValueBinding.java:44)
at org.jboss.seam.mock.SeamTest$Request.setValue(SeamTest.java:373)
at com.fb.core.test.catalog.RegisterAndLoginTest$LoginFacesRequest.updateModelValues(RegisterAndLoginTest.java:386)
at org.jboss.seam.mock.SeamTest$Request.run(SeamTest.java:475)
at com.fb.core.test.catalog.RegisterAndLoginTest.registerTest(RegisterAndLoginTest.java:68)
at org.jboss.seam.jsf.SeamApplication.getExpressionFactory(SeamApplication.java:100)
... 39 more
Caused by: java.lang.UnsupportedOperationException
at javax.faces.application.Application.getExpressionFactory(Application.java:766)
... 44 more
... Removed 26 stack frames
which seems to be because the RI ExpressionFactory isn't being set when using SeamTest. I pulled in a bunch of updates from CVS just prior to this showing up, and many of them were related to MessageBinding/Expression. Wonder if that is related.
The expression it's throwing on is:
setValue("#{identity.username}", userName);
--
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
17 years, 4 months