July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1009) optionally login-require in a more specific page should be able to override a wildcard login-require

by Leo Baschy (JIRA)

optionally login-require in a more specific page should be able to override a wildcard login-require ---------------------------------------------------------------------------------------------------- Key: JBSEAM-1009 URL: http://jira.jboss.com/jira/browse/JBSEAM-1009 Project: JBoss Seam Issue Type: Patch Components: Security Affects Versions: 1.2.0.GA Environment: all Reporter: Leo Baschy This should be optional to switch on, so no one's existing expectations of security get broken. The point is about having a generic wildcard <page view-id="*" scheme="http" login-required="true"> to secure the whole site, and then allowing specific pages or specific wildcards to have login-required="false". E.g. for a registration (with preview) section as one cannot be logged in if one isn't registered yet. Some may suggest instead forcing pages into dedicated secure and not-secure directories, but in reality if there are multiple reasons to force pages into directories different ways (security, hyperlink management, publishability of URLs, etc.), one cannot serve all of them. -- 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, 1 month

6
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1384) Support for Eclipse WTP in seam-gen projects

by Mariusz Smykula (JIRA)

Support for Eclipse WTP in seam-gen projects -------------------------------------------- Key: JBSEAM-1384 URL: http://jira.jboss.com/jira/browse/JBSEAM-1384 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness, Tools Affects Versions: 1.2.1.GA Reporter: Mariusz Smykula Auto deploy system and support for web application in Eclipse WTP is simple, easy and fast. This is much better solution than deploying with ant. Eclipse WTP 2.0 is comming in near time, so I think better support for WTP will be good. Now, users of WTP cant use Dynamic Web Project for working with application. -- 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, 1 month

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1596) Unique Constraint Validator

by Pete Muir (JIRA)

Unique Constraint Validator --------------------------- Key: JBSEAM-1596 URL: http://jira.jboss.com/jira/browse/JBSEAM-1596 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Priority: Blocker We could have a generic unique constrain validator as part of the model validation. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059691#4059691 -- 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, 1 month

8
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1277) ServerConversationContext does not process removals / additions when an exception propagates up

by Chris Rudd (JIRA)

ServerConversationContext does not process removals / additions when an exception propagates up ----------------------------------------------------------------------------------------------- Key: JBSEAM-1277 URL: http://jira.jboss.com/jira/browse/JBSEAM-1277 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA Reporter: Chris Rudd I have an Stateful EJB Component that throws an exception (this is expected, im testing that the system can recover from that error). This causes the component to be removed from the seam contexts (via the RemoveInterceptor). Then the exception floats up and is caught by the ExceptionFilter, and is redirected to a new view. All that works correctly. BUT when I return to the conversation that contained the EJB component, the component is still in it (even though the RemoveInterceptor removed it). Ive traced it down to this : ServerConversationContext.remove -- this adds the removal to the removals list, but does not update the session.attributes (the real storage for the context). ServerConversationContext.flush -- this applies the removals / additions to the session attributes map. The problem is that flush is never called when an exception propagates out. Thus the changes to that context are never flushed to the session attributes. -- 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, 1 month

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-808) StatckOverflowError if factory specifies it's component

by John Ray (JIRA)

StatckOverflowError if factory specifies it's component ------------------------------------------------------- Key: JBSEAM-808 URL: http://jira.jboss.com/jira/browse/JBSEAM-808 Project: JBoss Seam Issue Type: Bug Environment: Latest from CVS Reporter: John Ray I accidently specified the name of my component instead of a context variable and this resulted in a StatckOverflowError. For example @Stateful @Name("foo") @Scope(ScopeType.EVENT) public class FooAction implements Foo { @Out("bar") private String bar; @Factory("foo") public void initBar() { ... } } I'd sugest changing the code in org.jboss.seam.Component at line 490 to include an if/throw. I highlighted the 2 new lines with an asterisk if ( method.isAnnotationPresent(org.jboss.seam.annotations.Factory.class) ) { Init init = (Init) applicationContext.get( Seam.getComponentName(Init.class) ); //can't use Init.instance() here 'cos of unit tests String contextVariable = toName( method.getAnnotation(org.jboss.seam.annotations.Factory.class).value(), method ); * if (contextVariable.equals(name)) * throw new IllegalStateException("@Factory method can not be for it's own component: " + name); init.addFactoryMethod(contextVariable, method, this); } -- 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, 1 month

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1653) excetpion handling in pageflow and end-conversation

by Michael Kozak (JIRA)

excetpion handling in pageflow and end-conversation --------------------------------------------------- Key: JBSEAM-1653 URL: http://jira.jboss.com/jira/browse/JBSEAM-1653 Project: JBoss Seam Issue Type: Bug Reporter: Michael Kozak The problem has been discussed <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&t=112982">here</a> I included sample application to reproduce the bug. I tested the application with IE as it behaves very badly with it. Try to invoke the action which throws exception multiple times using back button. The behaviour of seam is diffrent every time. Sometimes it ends coversation and sometimes it throws a lot of exceptions. -- 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, 1 month

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1428) Seam PDF does't do alignment inside cell

by Mikhail Grushinskiy (JIRA)

Seam PDF does't do alignment inside cell ---------------------------------------- Key: JBSEAM-1428 URL: http://jira.jboss.com/jira/browse/JBSEAM-1428 Project: JBoss Seam Issue Type: Bug Components: PDF Affects Versions: 1.3.0.ALPHA, 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA, 1.3.1.GA Reporter: Mikhail Grushinskiy verticalAlignment, horizontalAlignment ignored -- 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, 2 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1747) SeamPhaseListener transaction debug log statements are misleading/confusing

by Matt Drees (JIRA)

SeamPhaseListener transaction debug log statements are misleading/confusing --------------------------------------------------------------------------- Key: JBSEAM-1747 URL: http://jira.jboss.com/jira/browse/JBSEAM-1747 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: 20070727.1142 Reporter: Matt Drees Priority: Trivial Debug logs from SeamPhaseListener look something like this on a non-faces request: DEBUG 31-07 11:34:31,467 (org.jboss.seam.jsf.SeamPhaseListener:begin:573) beginning transaction prior to phase: RESTORE_VIEW 1 DEBUG 31-07 11:34:31,560 (org.jboss.seam.jsf.SeamPhaseListener:commitOrRollback:589) committing transaction after phase: RESTORE_VIEW 1 DEBUG 31-07 11:34:31,560 (org.jboss.seam.jsf.SeamPhaseListener:begin:573) beginning transaction prior to phase: RENDER_RESPONSE 6 DEBUG 31-07 11:34:31,576 (org.jboss.seam.jsf.SeamPhaseListener:commitOrRollback:589) committing transaction after phase: INVOKE_APPLICATION 5 DEBUG 31-07 11:34:31,592 (org.jboss.seam.jsf.SeamPhaseListener:begin:573) beginning transaction prior to phase: INVOKE_APPLICATION 5 DEBUG 31-07 11:34:33,731 (org.jboss.seam.jsf.SeamPhaseListener:commitOrRollback:589) committing transaction after phase: RENDER_RESPONSE 6 It's misleading. For one thing, there is no "INVOKE_APPLICATION" phase; but that phaseid is used for logging before and after page actions. For another, the "before" and "after" statements are backwards (semantically). -- 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, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1183) Allow custom ExceptionHandler implementations to be inserted

by Mike Quilleash (JIRA)

Allow custom ExceptionHandler implementations to be inserted ------------------------------------------------------------ Key: JBSEAM-1183 URL: http://jira.jboss.com/jira/browse/JBSEAM-1183 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Currently you can only configure a small subset of actions to occur on an exception (redirect, http-error etc). Enhancing the exception configuration xml to allow pluggable ExceptionHandler implementations would make this a lot more flexible. e.g. pages.xml <pages>  <exception class="javax.persistence.EntityNotFoundException"> <http-error error-code="404"/> </exception>  <exception handlerClass="com.xxx.seam.CustomExceptionHandler"/> </pages> These should probably have higher precedence than standard configure-by-exception-class handlers. -- 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, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1485) Configure Default Interceptors

by Bruno E. Grossi (JIRA)

Configure Default Interceptors ------------------------------ Key: JBSEAM-1485 URL: http://jira.jboss.com/jira/browse/JBSEAM-1485 Project: JBoss Seam Issue Type: Feature Request Components: Core Environment: Linux with only Tomcat, not JBoss Reporter: Bruno E. Grossi Create an configuration option to disable some default interceptors that there are never used, improving the application's performance. On some systems there are no necessity of some interceptors, for example, the transactional ones (RollbackInterceptor, TransactionInterceptor and ManagedEntityIdentityInterceptor) that degrade 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

17 years, 3 months

3
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2007