December 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSERVLET-22) Test Seam Servlet in an EAR with multiple web apps

by Dan Allen (JIRA)

Test Seam Servlet in an EAR with multiple web apps -------------------------------------------------- Key: SEAMSERVLET-22 URL: https://issues.jboss.org/browse/SEAMSERVLET-22 Project: Seam Servlet Issue Type: Feature Request Components: Compliance, Producers, Test Suite Affects Versions: 3.0.0.Alpha2 Reporter: Dan Allen Assignee: Dan Allen We want to verify that we haven't broken any assumptions, such as whether the correct ServletContext is injected. Should be relatively easy to solve with Arquillian. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-6) Ensure exception handling is well tested

by Pete Muir (JIRA)

Ensure exception handling is well tested ---------------------------------------- Key: SEAMMAIL-6 URL: https://jira.jboss.org/browse/SEAMMAIL-6 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1279) use ExceptionFilter in Remoting

by Keith Naas (JIRA)

use ExceptionFilter in Remoting ------------------------------- Key: JBSEAM-1279 URL: http://jira.jboss.com/jira/browse/JBSEAM-1279 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Affects Versions: 1.2.1.GA Reporter: Keith Naas Assigned To: Shane Bryzak Currently, the Remoting resource class swallows all exceptions. Because of this, it is not possible to gracefully handle security restrictions in WebRemote methods from the client. Two ideas: # Simply bubble the Exception all the way up through the ResourceServlet. If the ResourceServlet throws the exception, the ExceptionFilter should pick up on it. The XHR would then receive the proper error code as defined in the pages.xml and could properly redirect the user to the correct login page. # Have the ResourceServlet trap for NotLoggedInException's or NotAuthorizedException's and return the respective HTTP status code. The XHR would then receive the error code and be able to redirect the user to the correct login 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

13 years, 3 months

5
12
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-17) Separate core and client sub-modules within remoting project

by Shane Bryzak (JIRA)

Separate core and client sub-modules within remoting project ------------------------------------------------------------ Key: SEAMREMOTING-17 URL: https://issues.jboss.org/browse/SEAMREMOTING-17 Project: Seam Remoting Issue Type: Task Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3188) ConcurrentModificationException on flush of ServerConversationContext

by Sanne Grinovero (JIRA)

ConcurrentModificationException on flush of ServerConversationContext --------------------------------------------------------------------- Key: JBSEAM-3188 URL: https://jira.jboss.org/jira/browse/JBSEAM-3188 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.3.CR1 Environment: 2.0.3.CR1, JBoss 4.2.2, JDK 5 Reporter: Sanne Grinovero As confirmed by other people on the forum at http://seamframework.org/Community/ConcurrentModificationExceptionAfterPr... It is possible for ServerConversationContext to iterate on an EntrySet which is modified in the iteration block. I couldn't understand exactly in which scenarios it happens, but it's easy to patch the code to iterate on a copy instead (I'll attach the patch). I can't say if it's correct to make a copy, or if you should actually avoid the changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (SEAMFACES-46) @End should probably not throw exceptions if a conversation could not be ended because it does not exist

by Lincoln Baxter III (JIRA)

@End should probably not throw exceptions if a conversation could not be ended because it does not exist -------------------------------------------------------------------------------------------------------- Key: SEAMFACES-46 URL: https://jira.jboss.org/browse/SEAMFACES-46 Project: Seam Faces Issue Type: Feature Request Components: Conversations Affects Versions: 3.0.0.Alpha4 Reporter: Lincoln Baxter III The @End annotation calls conversation.end() without first checking conversation.isTransient(). This results in exceptions when invoking the method on a transient conversation. This should either be a configuration option of the annotation, or should not occur: @End(ConversationPropagation.REQUIRED) @End(ConversationPropagation.OPTIONAL) Etc... something like that(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

6
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4464) <totalPages>-tag for pdf generation

by Robert Becker (JIRA)

<totalPages>-tag for pdf generation ----------------------------------- Key: JBSEAM-4464 URL: https://jira.jboss.org/jira/browse/JBSEAM-4464 Project: Seam Issue Type: Feature Request Reporter: Robert Becker When creating official documents it is often required to add something like "Page X of Y" to the footer. The p:pageNumber-tag provides the first value whereas a totalPages-tag is missing. Márcio Dantas created and published a wokarround for this under http://seamframework.org/Community/SeamPdfPageXOfY but this approach is somewhat "dirty". I see that it culd be problematic to provide the number of total pages while rendering the document so perhaps a placeholder could be used and altered when onCloseDocument in UIDocument is called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-15) Warnings should be issued when @Dependent scoped Validators and Converters are registered

by Lincoln Baxter III (JIRA)

Warnings should be issued when @Dependent scoped Validators and Converters are registered ----------------------------------------------------------------------------------------- Key: SEAMFACES-15 URL: https://jira.jboss.org/jira/browse/SEAMFACES-15 Project: Seam Faces Issue Type: Feature Request Components: JSF CDI Integration Affects Versions: 3.0.0.Alpha2 Reporter: Lincoln Baxter III When users attempt to register a Faces Converter and use @Inject support without registering the converter in a normal @Scope (Request, Session, Flash, Application, Etc...) Seam Faces should print a warning at boot time using: ProcessBean extension -- check for Converter/Validator interfaces and warn if @Dependent or isNormalScope() == false. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-65) Should be able to disable deploy-time halt on detection of java.faces.bean.ManagedBean annotated classes

by Lincoln Baxter III (JIRA)

Should be able to disable deploy-time halt on detection of java.faces.bean.ManagedBean annotated classes -------------------------------------------------------------------------------------------------------- Key: SEAMFACES-65 URL: https://issues.jboss.org/browse/SEAMFACES-65 Project: Seam Faces Issue Type: Feature Request Reporter: Lincoln Baxter III Priority: Minor Some users may find this behavior overly restrictive, particularly when migrating existing applications. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMFACES-52) Add JSF EL resolvers to WeldExtensions EL

by Pete Muir (JIRA)

Add JSF EL resolvers to WeldExtensions EL ----------------------------------------- Key: SEAMFACES-52 URL: https://jira.jboss.org/browse/SEAMFACES-52 Project: Seam Faces Issue Type: Feature Request Reporter: Pete Muir Register the JSF ELResolvers with Weld Extensions (for each resolver to register, create a bean with type ELResolver and qualifier @Resolver) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2010