ManagedEntityIdentityInterceptor could keep state as a EntityBeans in conversation context
------------------------------------------------------------------------------------------
Key: JBSEAM-586
URL: http://jira.jboss.com/jira/browse/JBSEAM-586
Project: JBoss Seam
Issue Type: Task
Components: Core
Affects Versions: 1.1.0.GA
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.1.GA
This will improve the referential integrity handling and, potentially, the performance.
--
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/WS
-------
Key: JBSEAM-505
URL: http://jira.jboss.com/jira/browse/JBSEAM-505
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Blocker
Fix For: 1.2.0.BETA1
Seam/WS will allow Seam components to receive WS calls and:
* participate in a WS conversation which is
* orchestrated by jBPM
* recoverable, when services come back online
--
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
jBPM async calls and scheduling
-------------------------------
Key: JBSEAM-506
URL: http://jira.jboss.com/jira/browse/JBSEAM-506
Project: JBoss Seam
Issue Type: Feature Request
Components: BPM
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.2.0.BETA1
Extend the jBPM/Seam integration to async and scheduled processing.
--
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
Migrate back to seperate microcontainer/lib and embedded-ejb/lib distribution and create an ant/lib dir
-------------------------------------------------------------------------------------------------------
Key: JBSEAM-542
URL: http://jira.jboss.com/jira/browse/JBSEAM-542
Project: JBoss Seam
Issue Type: Task
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.2.0.BETA1
we should consider splitting this stuff back out again
--
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
Get CRUD messages out of components.xml and into resource bundles
-----------------------------------------------------------------
Key: JBSEAM-449
URL: http://jira.jboss.com/jira/browse/JBSEAM-449
Project: JBoss Seam
Issue Type: Feature Request
Components: Framework
Affects Versions: 1.1.0.BETA1
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.1.0.BETA2
update/delete/create messages don't belong in components.xml
--
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
API Documentation for the org.jboss.seam.ui.* classes
-----------------------------------------------------
Key: JBSEAM-614
URL: http://jira.jboss.com/jira/browse/JBSEAM-614
Project: JBoss Seam
Issue Type: Task
Components: Documentation
Affects Versions: 1.1.1.GA
Reporter: Todd Smart
This is related in some ways to http://jira.jboss.org/jira/browse/JBSEAM-301.
It is very difficult (without reviewing the source code) to understand the Seam UI class and tag libraries. At a minimum, the API should be included in the documentation IMO.
Regards,
Todd
--
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
Allow seam.properties to optionally be packaged in mete-inf directory.
----------------------------------------------------------------------
Key: JBSEAM-563
URL: http://jira.jboss.com/jira/browse/JBSEAM-563
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Brian Leonard
Priority: Minor
Fix For: 1.1.0.GA
Today, seam.properties must be packaged in the root of the ejb.jar file. This is ackward for tools like NetBeans where I need to write a custom Ant target to package it there. Ideally, seam.properties could exist in the meta-inf directory of the ejb.jar. Is this a possibility?
--
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
s:validateAll and Trinidad
--------------------------
Key: JBSEAM-501
URL: http://jira.jboss.com/jira/browse/JBSEAM-501
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Priority: Minor
Fix For: 1.1.0.GA
Trinidad uses org.apache.myfaces.trinidad.component.UIXInput as the superclass of input components. UIValidateAll should also look for this class (by reflection).
--
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
"stackable" Redirect
--------------------
Key: JBSEAM-604
URL: http://jira.jboss.com/jira/browse/JBSEAM-604
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Reporter: Gavin King
Assigned To: Gavin King
Priority: Minor
This would let the user redirect to login page, then redirect back. Keep a stack of viewIds + parameters.
--
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