May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1188) Using the Seam exception filter without JTA throws exception

by Mike Quilleash (JIRA)

Using the Seam exception filter without JTA throws exception ------------------------------------------------------------ Key: JBSEAM-1188 URL: http://jira.jboss.com/jira/browse/JBSEAM-1188 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Tomcat 6, no microcontainer Reporter: Mike Quilleash Upgraded to Seam 1.2.1 and the following exception gets printed to the logs when there is an exception. ERROR [org.jboss.seam.web.ExceptionFilter] [http-56000-1] (ExceptionFilter.java:136) - could not roll back transaction javax.naming.NamingException: Cannot create resource instance at org.apache.naming.factory.TransactionFactory.getObjectInstance(TransactionFactory.java:113) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at org.apache.naming.NamingContext.lookup(NamingContext.java:793) at org.apache.naming.NamingContext.lookup(NamingContext.java:140) at org.apache.naming.NamingContext.lookup(NamingContext.java:781) at org.apache.naming.NamingContext.lookup(NamingContext.java:153) at org.apache.naming.SelectorContext.lookup(SelectorContext.java:137) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.seam.util.Transactions.getUserTransaction(Transactions.java:153) at org.jboss.seam.util.Transactions.isUTTransactionActiveOrMarkedRollback(Transactions.java:122) at org.jboss.seam.util.Transactions.isTransactionActiveOrMarkedRollback(Transactions.java:50) at org.jboss.seam.web.ExceptionFilter.rollbackTransactionIfNecessary(ExceptionFilter.java:128) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:63) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) I don't have JTA/microcontainer installed as I just want to use the exception filter for redirecting on error, rolling back transactions should be disabled/skipped in a non JTA configuration. -- 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, 10 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1301) Bugs with MockServletContext.getResourcePaths()

by Michael Youngstrom (JIRA)

Bugs with MockServletContext.getResourcePaths() ----------------------------------------------- Key: JBSEAM-1301 URL: http://jira.jboss.com/jira/browse/JBSEAM-1301 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 1.3.0.BETA1 I've been doing some work with Seam integration testing lately and noticed getResourcePaths() wasn't working correctly. It appeared to never return anything beyond the webroot. So, I fixed that problem and enhanced getResourcePaths so that it could handle situations where a users directory structure may have multiple webroots (e.g. one for test and main). I changed from searching for webroot by looking for WEB-INF/web.xml files to only WEB-INF. If nobody has any objections to my implementation I'll go ahead and commit this. This is how I've rewritten getResourcePaths(): public Set getResourcePaths(String name) { Enumeration<URL> enumeration = null; try { enumeration = getClass().getClassLoader().getResources("WEB-INF"); } catch (IOException e) { throw new RuntimeException("Error finding webroot.",e); } Set<String> result = new HashSet<String>(); while(enumeration.hasMoreElements()) { URL url = enumeration.nextElement(); File rootFile = new File(url.getPath()).getParentFile(); File newFile = new File(rootFile.getPath()+name); File[] files = newFile.listFiles(); if(files != null) { addPaths( result, files, rootFile.getPath() ); } } return result; } private static void addPaths(Set<String> result, File[] files, String rootPath) { for (File file: files) { String filePath = file.getPath().substring( rootPath.length() ).replace('\\', '/'); if(file.isDirectory()) { result.add(filePath+"/"); } else { result.add(filePath); } } } -- 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, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-953) Don't create HttpSession until we *really* need it

by Gavin King (JIRA)

Don't create HttpSession until we *really* need it -------------------------------------------------- Key: JBSEAM-953 URL: http://jira.jboss.com/jira/browse/JBSEAM-953 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.1.GA This requires a thorough code audit. -- 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, 10 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1368) Document conversation propagation rules with partial page submit

by Gavin King (JIRA)

Document conversation propagation rules with partial page submit ---------------------------------------------------------------- Key: JBSEAM-1368 URL: http://jira.jboss.com/jira/browse/JBSEAM-1368 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.ALPHA -- 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, 10 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1353) SeamExpressionFactory breaks custom ExpressionFactories

by Mike Quilleash (JIRA)

SeamExpressionFactory breaks custom ExpressionFactories ------------------------------------------------------- Key: JBSEAM-1353 URL: http://jira.jboss.com/jira/browse/JBSEAM-1353 Project: JBoss Seam Issue Type: Bug Components: EL Affects Versions: 1.3.0.ALPHA Environment: Any Reporter: Mike Quilleash Trying out the current CVS and the modifications to the SeamExpressionFactory have broken my application. In the old version SeamExpressionFactory used to wrap the ExpressionFactory facelets would've created by default (getApplication().getExpressionFactory()) but now it just wraps a jboss EL ExpressionFactory. I have a custom ExpressionFactory which i need to create custom ValueExpressions in certain circumstances. The above change circumvents my ExpressionFactory when facelets is compiling. -- 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, 10 months

2
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1282) Refactor Exception Handling definition parsing into Pages component

by Chris Rudd (JIRA)

Refactor Exception Handling definition parsing into Pages component ------------------------------------------------------------------- Key: JBSEAM-1282 URL: http://jira.jboss.com/jira/browse/JBSEAM-1282 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Chris Rudd Currently I am using the fix I proposed for JBSEAM-715. This allows me to manage and pass additional pages.xml files to the Pages component. The problem is that for the exception definition the Exceptions component only looks at the WEB-INF/pages.xml. I propose either refactoring the processing of the exception nodes into the Pages component so that any pages.xml that is processed can define exception handlers. An alternate implementation would be to have the Pages component to notify the Exceptions component of each pages.xml it processes. This way the specific can still be encapsulated in the Exceptions compoent, but it is fed the pages.xml files to use. -- 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, 10 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1092) s:fileUpload throws MissingResourceException

by Jonas Erma (JIRA)

s:fileUpload throws MissingResourceException -------------------------------------------- Key: JBSEAM-1092 URL: http://jira.jboss.com/jira/browse/JBSEAM-1092 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Environment: JBoss-4.0.5, JSF RI 1.2_02, Facelets, Ajax4JSF 1.0.7 Reporter: Jonas Erma Please see forum messages. -- 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, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1373) QuartzDispatcher

by Gavin King (JIRA)

QuartzDispatcher ---------------- Key: JBSEAM-1373 URL: http://jira.jboss.com/jira/browse/JBSEAM-1373 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.3.0.ALPHA Reporter: Gavin King People like Quartz. -- 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, 10 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1361) sessionId cookie: man-in-the-middle attack

by fguerzoni (JIRA)

sessionId cookie: man-in-the-middle attack ------------------------------------------ Key: JBSEAM-1361 URL: http://jira.jboss.com/jira/browse/JBSEAM-1361 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.2.1.GA Environment: general feature Reporter: fguerzoni I noticed that sessionId cookie sent to client before authentication remains the same even after login succedeed. This could lead to a man-in-the-middle attack because pre-login sessionId could be easily sniffed. So, it would be very nice if it should be possible to do a session switching on server side forcing a pre-login session invalidation and a new session creation (request.getSession(true)) as soon as client authenticates. Old session data should then be copied to new session. In this case a new sessionId cookie will be sent to client: client will use this ticket during next requests. This mechanism collides with the actual Seam implementations where Lifecycle.endSession is called after a session.invalidate I think that Seam should automatically execute this task during the authentication phase. -- 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, 10 months

4
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1374) Document JBoss EL

by Gavin King (JIRA)

Document JBoss EL ----------------- Key: JBSEAM-1374 URL: http://jira.jboss.com/jira/browse/JBSEAM-1374 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Gavin King Assigned To: Norman Richards Priority: Critical Fix For: 1.3.0.ALPHA The whole "elenhancements" chapter needs a rewrite. -- 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, 10 months

2
2
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 May 2007