April 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1075) Documentation enhancement for injecting Logger (make clear when static is required)

by Arjan van Bentem (JIRA)

Documentation enhancement for injecting Logger (make clear when static is required) ----------------------------------------------------------------------------------- Key: JBSEAM-1075 URL: http://jira.jboss.com/jira/browse/JBSEAM-1075 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Optional The documentation of @Logger in "3.6 Logging" states at http://fisheye.jboss.com/browse/JBoss/jboss-seam/doc/reference/en/modules... It doesn't matter if you declare the log variable static or not—it will work either way. I think this should be enhanced to read, for example: It doesn't matter if you declare the log variable static or not—it will work either way, except for entity beans which needs the logger to be static. ...maybe followed by an example: @Entity @Name("member") @Table(uniqueConstraints = @UniqueConstraint(columnNames = "membername")) public class Member implements Serializable { @Logger private static Log log; : public void setMemberName(String memberName) { log.info("setting memberName"); this.memberName = memberName; } : } At least, that's what I've found; when not declaring it static it will not get injected or is lost (I'm not sure which), and thus would yield a NullPointerException upon usage. Likewise, "22.2. Annotations for bijection" at http://fisheye.jboss.com/browse/JBoss/jboss-seam/doc/reference/en/modules... now states Specifies that a component field is to be injected with an instance of org.jboss.seam.log.Log. ...but maybe this could be extended to read: Specifies that a component field is to be injected with an instance of org.jboss.seam.log.Log. Remember that for entity beans the actual variable needs to be declared static. Cheers, Arjan. -- 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

18 years, 1 month

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-866) Ajax4JSF integration for Wiki

by Gavin King (JIRA)

Ajax4JSF integration for Wiki ----------------------------- Key: JBSEAM-866 URL: http://jira.jboss.com/jira/browse/JBSEAM-866 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King The following features should use Ajax4JSF instead of navigation or full page submits. * Preview panel should be dynamically rendered as user types in the edit box * Edit page and edit directory should use an ajax include instead of navigation * The operations in the edit directory box should use partial submit/render * Login should be implemented using a partial submit/render -- 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

18 years, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1224) Consider integration of security with App Framework

by Pete Muir (JIRA)

Consider integration of security with App Framework --------------------------------------------------- Key: JBSEAM-1224 URL: http://jira.jboss.com/jira/browse/JBSEAM-1224 Project: JBoss Seam Issue Type: Feature Request Components: Core, Security Affects Versions: 1.2.1.GA Reporter: Pete Muir Assigned To: Shane Bryzak >From the forums: 'One down side to using EntityHome for generic crud is lack of built in security. One needs to be careful when using Homes for crud operations that allow or require RequestParameters. You need to ensure the operation on this ID is valid. You don't want to expose information you shouldn't and you definitely don't want to modify or destroy information you shouldn't. For example, you don't want a user to update or delete another user's entity just by changing an ID in the URL and hitting return. Seam supports entity level security and you can probably extend a Home to double check access restrictions prior to operations. Likewise, you don't want private information available on lets say a user profile screen, to be available to anyone able to modify a URL.' -- 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

18 years, 2 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-895) Support re-setting the principal in identity without relogin

by Christian Bauer (JIRA)

Support re-setting the principal in identity without relogin ------------------------------------------------------------ Key: JBSEAM-895 URL: http://jira.jboss.com/jira/browse/JBSEAM-895 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Christian Bauer Assigned To: Shane Bryzak Priority: Minor I'm allow my users to change passwords and usernames while they are logged in. After such a change of credentials, I need to replace the principal in the identity component. This can currently only be done through logout() and login(), manually by the user. I want to do this automatically, and I don't want to destroy the session for that. -- 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

18 years, 2 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1145) "javax.persistence.TransactionRequiredException: no transaction is in progress" thrown during flush of a transient entity in a @Transactional POJO

by Alex Savitsky (JIRA)

"javax.persistence.TransactionRequiredException: no transaction is in progress" thrown during flush of a transient entity in a @Transactional POJO -------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1145 URL: http://jira.jboss.com/jira/browse/JBSEAM-1145 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: Tomcat + Microcontainer (has also been tried on Tomcat + JOTM, Tomcat + Atomikos, Tomcat + JBoss Transactions, all with the same result) Seam-managed Tx and PC, long-running conversations with manual flush Reporter: Alex Savitsky When persisting a transient entity during manual flush, an exception "javax.persistence.TransactionRequiredException: no transaction is in progress" is thrown, unless getEntityManager().joinTransaction() is executed prior to flush() - despite declaring the POJO as @Transactional and using Seam-managed transactions and persistence contexts. When persisting a managed entity, however, no exceptions are thrown and update completes normally. -- 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

18 years, 2 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1034) Usage of jBPM core:process-definitions needs clarification

by Arjan van Bentem (JIRA)

Usage of jBPM core:process-definitions needs clarification ---------------------------------------------------------- Key: JBSEAM-1034 URL: http://jira.jboss.com/jira/browse/JBSEAM-1034 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Minor The Seam documentation for "21.6. Configuring jBPM in Seam" describes how to add jBPM process definitions to components.xml: <core:jbpm> <core:pageflow-definitions> <value>createDocument.jpdl.xml</value> <value>editDocument.jpdl.xml</value> <value>approveDocument.jpdl.xml</value> </core:pageflow-definitions> <core:process-definitions> <value>documentLifecycle.jpdl.xml</value> </core:process-definitions> </core:jbpm> Nice, but as a side-effect a new copy is inserted into the database each time JBoss AS is started, even if the deployed EAR has not changed. This, of course, can only be noticed if in the example hibernate.cfg.xml from the DVD Store example the line <property name="hbm2ddl.auto">create-drop</property> is changed into <property name="hbm2ddl.auto">update</property> Apparently using <core:pageflow-definitions> is considered to be a developers tool: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98430 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90206 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103819 I think this needs some clarification in the documentation, but unfortunately (right now) I would not know what is the preferred way to deploy processes in Seam on a production machine. The third topic might include some ideas from others on that. Arjan. -- 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

18 years, 2 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-652) Allow use of EHCache with <s:cache/>

by Gavin King (JIRA)

Allow use of EHCache with <s:cache/> ------------------------------------ Key: JBSEAM-652 URL: http://jira.jboss.com/jira/browse/JBSEAM-652 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Priority: Minor -- 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

18 years, 2 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-650) <s:formattedText value="#{post.body}" highlight="#{word}"/>

by Gavin King (JIRA)

<s:formattedText value="#{post.body}" highlight="#{word}"/> ----------------------------------------------------------- Key: JBSEAM-650 URL: http://jira.jboss.com/jira/browse/JBSEAM-650 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.5.GA Seam needs to support wikitext ootb. -- 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

18 years, 2 months

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-671) Add an inheritance mechanism for themes

by Bill Wallace (JIRA)

Add an inheritance mechanism for themes --------------------------------------- Key: JBSEAM-671 URL: http://jira.jboss.com/jira/browse/JBSEAM-671 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.GA Reporter: Bill Wallace It would be very nice to have an item in a theme that allowed one to indicate which theme to inherit from, eg: default theme - no inheritance: printable.properties: org.jboss.seam.theme.inherit default accessible.properties: org.jboss.seam.theme.inherit default accessible-printable.properties org.jboss.seam.theme.inherit printable accessible ... Thus, the accessible-printable version would inherit first from printable, then from accessible. Assuming they could in fact co-exist, that might work out nicely to produce an accessible-printable version. It would also be nice to allow inheritance from generic property files that are NOT explicit themes - that way, you can put portions of a theme in another file, and just inherit from all the required themes. Note that the Java API makes this relatively easy, just be creating a chain of inheritance. (Note that only accessible would chain to default, a new printable would be needed that only inherited from accessible, not from anything else.) -- 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

18 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-911) endAndRedirect() in jBPM pageflow

by Gavin King (JIRA)

endAndRedirect() in jBPM pageflow --------------------------------- Key: JBSEAM-911 URL: http://jira.jboss.com/jira/browse/JBSEAM-911 Project: JBoss Seam Issue Type: Feature Request Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.8 GA Currently all jbpm pageflows and at a specific page. We want to be able to end the flow at the page of the parent conversation, by introducing something like an end-state element. Perhaps we should also have the ability to return to the starting page even when there was no parent conversation. -- 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

18 years, 2 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2007