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
ajax4jsf a:commandLink stops working if page is defined in pages.xml with an action, or if page is opened from s:link
---------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-632
URL: http://jira.jboss.com/jira/browse/JBSEAM-632
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.1.0.GA
Environment: any
Reporter: Dan Liu
Priority: Critical
a4j a:commandLink stops working in following two situations:
1. If the containing page is defined in pages.xml with an action defined, the action method defined in pages.xml is always triggered and a:commandLink specified method is never triggered.
2. If the containing page is bookmarkable and is opened through s:link, the a:commandLink in this page would stop working.
--
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
iText support should allow .pdf and .html file extensions
---------------------------------------------------------
Key: JBSEAM-677
URL: http://jira.jboss.com/jira/browse/JBSEAM-677
Project: JBoss Seam
Issue Type: Feature Request
Affects Versions: 1.1.5.GA
Reporter: Norman Richards
It should be possible to to use the iText support with urls like myDocument.pdf. This will work better with browsers, work better when the user saves the document and look much nicer.
--
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
@Observer doesn't work in components that use @Unwrap
-----------------------------------------------------
Key: JBSEAM-673
URL: http://jira.jboss.com/jira/browse/JBSEAM-673
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
If a component uses @Unwrap and @Observer at the same time, Events.instance().raiseEvent() attempts to invoke the observer method on the unwrapped object, which usually causes a NoSuchMethodException exception.
--
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 calling of org.jboss.seam.core.redirect.execute() in pages.xml
--------------------------------------------------------------------
Key: JBSEAM-690
URL: http://jira.jboss.com/jira/browse/JBSEAM-690
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Priority: Minor
Instead of <redirect> I'd like to call redirect.execute() to jump to some saved location. This is useful eg. after Delete:
<page view-id="/docEdit.xhtml">
<navigation from-action="#{documentHome.delete}">
<end-conversation before-redirect="true"/>
<redirect-to-captured-request/>
</navigation>
...
--
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
seam-gen should create a Hibernate Console configuration for the "prod" database
--------------------------------------------------------------------------------
Key: JBSEAM-648
URL: http://jira.jboss.com/jira/browse/JBSEAM-648
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Reporter: Gavin King
Assigned To: Max Andersen
Fix For: 1.1.1.GA
ie. Hibernate Console should work ootb with a seam-gen'd app.
--
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
Spring integration
------------------
Key: JBSEAM-696
URL: http://jira.jboss.com/jira/browse/JBSEAM-696
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Norman Richards
The Spring integration package will support:
(1) injection of Seam components into Spring beans, using beans.xml
(2) injection of Spring beans into Seam components using @In
(3) access to Spring beans via EL
(4) use of Seam-managed PC from Spring DAOs
We'll probably even go as far as:
(5) The ability to treat a Spring bean as a Seam STATELESS JAVA_BEAN component, with a full stack of Seam interceptors
--
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