February 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-812) encoding issues

by Piotr Czekaj (JIRA)

encoding issues --------------- Key: JBSEAM-812 URL: http://jira.jboss.com/jira/browse/JBSEAM-812 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 1.1.6.GA Reporter: Piotr Czekaj It would be great to have some option to set encoding for text, without it it's impossible to display for example polish national characters -- 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

17 years, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-846) SeamTest setField() not recognize fields in super classes.

by Mariusz Smykula (JIRA)

SeamTest setField() not recognize fields in super classes. ---------------------------------------------------------- Key: JBSEAM-846 URL: http://jira.jboss.com/jira/browse/JBSEAM-846 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.6.GA Reporter: Mariusz Smykula Attachments: setField.txt Seam 1.1.6 CVS (14.02.2007) -- 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

17 years, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-848) TransactionPropagationType.isNewTransactionRequired() logic is incorrect for MANDATORY and NEVER

by Mike Quilleash (JIRA)

TransactionPropagationType.isNewTransactionRequired() logic is incorrect for MANDATORY and NEVER ------------------------------------------------------------------------------------------------ Key: JBSEAM-848 URL: http://jira.jboss.com/jira/browse/JBSEAM-848 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash The existing code looks like this... case REQUIRED: return !transactionActive; case SUPPORTS: return false; case MANDATORY: if ( !transactionActive ) { throw new IllegalStateException("No transaction active on call to MANDATORY method"); } case NEVER: if ( transactionActive ) { throw new IllegalStateException("Transaction active on call to NEVER method"); } default: throw new IllegalArgumentException(); Will fall-through on the second two cases and throw an incorrect exception. Probably needs just needs "return false" in both cases. -- 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

17 years, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-803) Query: getLastFirstResult possible raises an exception

by Carsten H?hne (JIRA)

Query: getLastFirstResult possible raises an exception ------------------------------------------------------ Key: JBSEAM-803 URL: http://jira.jboss.com/jira/browse/JBSEAM-803 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 1.1.6.GA Reporter: Carsten H?hne I do have implemented the pagination control (Chapter 10.3 from the docu. This peace of code does not function: <s:link view="/listUser.xhtml" rendered="#{myUserList.nextExists}" value=" last "> <f:param name="firstResult" value="#{myUserList.lastFirstResult}"/> </s:link> When rendering the page an exception is thrown: 2:13:28,734 DEBUG org.jboss.seam.core.Events: Processing event:org.jboss.seam.postSetVariable.myUserList 12:13:28,750 DEBUG org.jboss.util.NestedThrowable: org.jboss.util.NestedThrowable.parentTraceEnabled=true 12:13:28,750 DEBUG org.jboss.util.NestedThrowable: org.jboss.util.NestedThrowable.nestedTraceEnabled=false 12:13:28,750 DEBUG org.jboss.util.NestedThrowable: org.jboss.util.NestedThrowable.detectDuplicateNesting=true 12:13:28,750 ERROR org.hibernate.util.JDBCExceptionReporter: Transaction is not active: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=null:1171019559906/10, BranchQual=null:1171019559906, localId=0:10]; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=null:1171019559906/10, BranchQual=null:1171019559906, localId=0:10]) 09.02.2007 12:13:28 com.sun.facelets.FaceletViewHandler handleRenderException SCHWERWIEGEND: Error Rendering View[/listUser.xhtml] javax.faces.el.EvaluationException: /listUser.xhtml @67,73 value="#{myUserList.lastFirstResult}": Exception getting value of property lastFirstResult of base of type : org.jboss.seam.framework.HibernateEntityQuery$$EnhancerByCGLIB$$9d3287a at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:60) at javax.faces.component.UIParameter.getValue(UIParameter.java:68) at org.jboss.seam.ui.HtmlLink.getParameterString(HtmlLink.java:208) at org.jboss.seam.ui.HtmlLink.encodeBegin(HtmlLink.java:115) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249) After removing this piece of code the pagination works for first,last and next. -- 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

17 years, 11 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-764) Roles based security without drools jars

by Piotr Walczyszyn (JIRA)

Roles based security without drools jars ---------------------------------------- Key: JBSEAM-764 URL: http://jira.jboss.com/jira/browse/JBSEAM-764 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Piotr Walczyszyn To limit number of required jars in cases when role based security is used [without permissions], drools jars could be excluded from required dependecies. -- 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

17 years, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-845) Allow configuration of which actions are restricted for entity security

by Shane Bryzak (JIRA)

Allow configuration of which actions are restricted for entity security ----------------------------------------------------------------------- Key: JBSEAM-845 URL: http://jira.jboss.com/jira/browse/JBSEAM-845 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Shane Bryzak Assigned To: Shane Bryzak Fix For: 1.1.7.GA We really need to be able to configure which entity actions are restricted (and which ones are not) for each restricted entity. I'm currently thinking of something along the lines of this: @Restrict @RestrictedActions({READ,DELETE}) @Name("account") public class Account { ... } This is necessary so that it's not required to provide security rules for entity actions that are not intended to be restricted. -- 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

17 years, 11 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-841) HibernateSecurityInterceptor hammers any user-defined interceptor

by Gavin King (JIRA)

HibernateSecurityInterceptor hammers any user-defined interceptor ----------------------------------------------------------------- Key: JBSEAM-841 URL: http://jira.jboss.com/jira/browse/JBSEAM-841 Project: JBoss Seam Issue Type: Bug Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.1.7.GA The HibernateSecurityInterceptor should wrap, not replace, any existing interceptor. -- 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

17 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-799) security documentation issues

by Stephan Bublava (JIRA)

security documentation issues ----------------------------- Key: JBSEAM-799 URL: http://jira.jboss.com/jira/browse/JBSEAM-799 Project: JBoss Seam Issue Type: Feature Request Components: Documentation, Security Affects Versions: 1.1.6.GA Reporter: Stephan Bublava Priority: Minor Some minor issues I stumbled upon while reading the documentation, which is quite excellent, btw. 1) Using your container's JAAS configuration (12.2.5.1) I believe the configuration example is wrong: "jaasConfigName" should be "jaas-config-name". In this case "authenticate-method" should not be present at all. 2) The @Restrict annotation (12.3.2.1.) The documentation does not mention which permission check will be invoked if @Restrict is placed on the class. (Is this equivalent to adding @Restrict to each method?) 3) Creating a security rules file (12.4.3) The security rule in this section differs from those in seamspace (no-loop, activation-group, modify(c)). I assume the last one is essential. 4) Since Seam 1.1.6 it's possible to redirect to the original page after login (JBSEAM-773). It would be great to have an example in the documentation. -- 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

17 years, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-837) <page login-required="true">

by Gavin King (JIRA)

<page login-required="true"> ---------------------------- Key: JBSEAM-837 URL: http://jira.jboss.com/jira/browse/JBSEAM-837 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.1.7.GA As a simpler alternative to <restrict>#{identity.loggedIn}</restrict> + <exception class="org.jboss.seam.security.NotLoggedInException">, we should allow you to use: <pages login-view-id="/login.xhtml"> <page view-id="/main.xhtml" login-required="true"> ... </page> ... <pages> Just like we have with conversation-required today. This would use special code in Page.enter(), instead of exception handling to do its work. It would also add a message to the FacesContext (just like Manager.noConversation() does today). -- 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

17 years, 11 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-836) Security interceptor should not be triggered for lifecycle methods

by Gavin King (JIRA)

Security interceptor should not be triggered for lifecycle methods ------------------------------------------------------------------ Key: JBSEAM-836 URL: http://jira.jboss.com/jira/browse/JBSEAM-836 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.6.GA, 1.1.5.GA Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.7.GA For lifecycle methods, especially @Destroy, class-level restrictions should be ignored. Currently the booking example stacktraces when you try to log out. Use Component.isLifecycleMethod(method) -- 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

17 years, 11 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2007