transactionListener component should be implemented like Hibernate TMLookup
---------------------------------------------------------------------------
Key: JBSEAM-664
URL: http://jira.jboss.com/jira/browse/JBSEAM-664
Project: JBoss Seam
Issue Type: Bug
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.1.5.GA
It would be MUCH better if we did not have an EJB sitting in jboss-seam.jar.
--
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
Consider integrating jBPM Identity modulewith Security
-------------------------------------------------------
Key: JBSEAM-1465
URL: http://jira.jboss.com/jira/browse/JBSEAM-1465
Project: JBoss Seam
Issue Type: Feature Request
Components: BPM, Security
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.3.0.GA
Maybe we can use that as our identity model....
--
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
Integration with JBoss SSO
--------------------------
Key: JBSEAM-1032
URL: http://jira.jboss.com/jira/browse/JBSEAM-1032
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 1.2.0.GA
Reporter: Shane Bryzak
Assigned To: Shane Bryzak
We should provide integration of Seam Security with JBoss SSO.
--
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
Support X509 certificates
-------------------------
Key: JBSEAM-744
URL: http://jira.jboss.com/jira/browse/JBSEAM-744
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Reporter: Gavin King
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 1.2.0.BETA1
I have no idea what these things are, but apparently people want to get them. Supposedly, they are nothing to do with certificates you get when you win something like a spelling competition in primary school. 'Cos if they were, we could have used Norman's PDF stuff. So anyway we can just steal code from Acegi. Then I can tell people "we've got a certificate for X509" in talks, and they will think I know what it is.
--
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
URL authorization
-----------------
Key: JBSEAM-740
URL: http://jira.jboss.com/jira/browse/JBSEAM-740
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Reporter: Gavin King
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 1.2.0.BETA1
Probably, for completeness, we need the SecurityFIlter after all, to allow GET/PUT/POST/DELETE authorization for URLs.
--
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
Create a web service test page for seam-gen
-------------------------------------------
Key: JBSEAM-1543
URL: http://jira.jboss.com/jira/browse/JBSEAM-1543
Project: JBoss Seam
Issue Type: Feature Request
Components: WS
Reporter: Shane Bryzak
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 1.3.0.GA
It would be extremely cool to be able to use the web service test page from the seambay example in all apps, not just in this one example. I need to investigate how we can include this in a seam-gen application or easily be able to add it to any seam app, ala the debug page.
--
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
<param> node in <exception> in pages.xml is not used
----------------------------------------------------
Key: JBSEAM-1625
URL: http://jira.jboss.com/jira/browse/JBSEAM-1625
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.BETA1
Environment: jboss 4.2, seam 2.0.0.B1
Reporter: Zalder R
The param option in an exception node in pages.xml is not used :
<exception class="org.my.Exception">
<redirect view-id="/mypage.xhtml">
<param name="u" value="#{user.username}"/>
<message severity="warn">#{messages['MSG.ERROR.MAX_TEXT_REACHED']}</message>
</redirect>
</exception>
When the exception is triggered : redirect is done to mypage.xhtml ... not mypage.xhtml?u=whatever
--
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
Application-level log
---------------------
Key: JBSEAM-1505
URL: http://jira.jboss.com/jira/browse/JBSEAM-1505
Project: JBoss Seam
Issue Type: Feature Request
Components: Wiki
Reporter: Christian Bauer
Assigned To: Christian Bauer
Priority: Minor
Create a persistent LogEvent and raise a Seam event whenever anything interesting happens in the app (user registered, document deleted, notification stopped because of bounces, and so on). Show log in the admin interface and allow admin to set log level and clear the log.
--
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