@Transactional(REQUIRED|REQUIRES_NEW|SUPPORTS|....)
---------------------------------------------------
Key: JBSEAM-595
URL: http://jira.jboss.com/jira/browse/JBSEAM-595
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.1.1.GA
Why not just support this stuff for JavaBean components, its easy anyway.
--
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
read-only transactions
----------------------
Key: JBSEAM-601
URL: http://jira.jboss.com/jira/browse/JBSEAM-601
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.1.1.GA
If we let the user specify that a txn is pure read-only, then we can safely put the EM/Session in FlushMode.NEVER as a performance optimization.
--
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
processing events after the transaction
---------------------------------------
Key: JBSEAM-572
URL: http://jira.jboss.com/jira/browse/JBSEAM-572
Project: JBoss Seam
Issue Type: Feature Request
Components: Core, Examples
Affects Versions: 1.1.0.GA
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.GA
Currently the booking example refreshes the booking list in a new txn that is processed before the end of the current txn. This is actually incorrect, so we need a way to delay event processing until after the current txn is complete.
--
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
Seam logging does not report correct line number/class name/method name under Log4J or JDK1.4 logging
-----------------------------------------------------------------------------------------------------
Key: JBSEAM-581
URL: http://jira.jboss.com/jira/browse/JBSEAM-581
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.CR2
Environment: Java 1.5.0_06
Windows XP Pro
Tomcat 6.0.0
Reporter: Mike Quilleash
Seam uses a wrapper around commons logging to allow it to evaluate EL expressions as part of the log string. However this adds an extra level to the call stack which the commons logging library is unaware of so the reporting of line numbers/class name/method name in log output always reports the line number in the Seam logging implementation rather than the calling code above it.
This affects Log4J (line numbers/class name/method name) and JDK1.4 logging (class name/method name).
--
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
METHOD context
--------------
Key: JBSEAM-600
URL: http://jira.jboss.com/jira/browse/JBSEAM-600
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.1.1.GA
A METHOD context is useful, since it lets you easily do a temporary override of components in other scopes.
--
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
workspace management + nested conversations broken in 1.1
---------------------------------------------------------
Key: JBSEAM-593
URL: http://jira.jboss.com/jira/browse/JBSEAM-593
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.GA
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.1.1.GA
In the issue tracker, select a project, create an issue, create a comment, try to navigate to the project from the breadcrumbs
--
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
seam-gen should let the user define a schema to use
---------------------------------------------------
Key: JBSEAM-598
URL: http://jira.jboss.com/jira/browse/JBSEAM-598
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 1.1.0.GA
Reporter: Gavin King
Fix For: 1.1.1.GA
Esp. for reverse engineering where we should set hibernate.default_schema in build.properties.
--
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
ELResolver for Collection and DataModel
---------------------------------------
Key: JBSEAM-478
URL: http://jira.jboss.com/jira/browse/JBSEAM-478
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.1.0.CR1
It is amazing that you can't do:
collection.size
datamodel.size
datamodel.empty
in EL.
We can solve this with an ELResolver
--
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
org.jboss.seam.core.Validation.validate() method does not work for alternative property expression format: #{entity[fieldName]}
-------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-580
URL: http://jira.jboss.com/jira/browse/JBSEAM-580
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.CR2
Environment: JBoss 4.0.5, Seam 1.1.0.CR, Windows XP Professional
Reporter: Andrew Pople
The Validation.validate is hard coded to look for propertyExpressions of the form "#{entity.property}. It throws: "java.lang.RuntimeException: not an attribute value binding: #{entity[property]} when given the alternative square-bracket syntax for retrieving bean properties.
--
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
precedence="..." in components.xml
----------------------------------
Key: JBSEAM-597
URL: http://jira.jboss.com/jira/browse/JBSEAM-597
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.GA
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.1.1.GA
has multiple bugs
--
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