August 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMMAIL-20) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SEAMMAIL-20 URL: https://issues.jboss.org/browse/SEAMMAIL-20 Project: Seam Mail Issue Type: Task Reporter: Jason Porter There are some classes (or perhaps all classes) which need to be updated to the new code formatting guidelines, please see https://github.com/seam/build/blob/master/formatting.README for more information -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-11) root pom.xml is not correct regarding distribution profile

by Martin Gencur (JIRA)

root pom.xml is not correct regarding distribution profile ---------------------------------------------------------- Key: SEAMMAIL-11 URL: https://issues.jboss.org/browse/SEAMMAIL-11 Project: Seam Mail Issue Type: Bug Reporter: Martin Gencur Fix For: 3.0.0.Beta1 The root pom.xml should contain corrent submodule definition in "distribution" profile. There is a <module>examples/sendmail</module> but should be <module>examples/seam-mail-examples-sendmail</module> instead. Thus, the distribution build is failing. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
2
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

14 years, 5 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

14 years, 6 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

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-58) Typos in documentation

by Jozef Hartinger (JIRA)

Typos in documentation ---------------------- Key: SEAMPERSIST-58 URL: https://issues.jboss.org/browse/SEAMPERSIST-58 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Priority: Minor Fix For: 3.0.1.CR1 persistence-general.xml: spell check failed on 'intercepter' persistence-general.xml: spell check failed on 'loosly' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMWICKET-41) EJB and Seam Wicket result in NotSerializableException

by Thierry Peng (JIRA)

EJB and Seam Wicket result in NotSerializableException ------------------------------------------------------ Key: SEAMWICKET-41 URL: https://issues.jboss.org/browse/SEAMWICKET-41 Project: Seam for Apache Wicket Issue Type: Enhancement Affects Versions: 3.0.0.Final Environment: Wicket 1.4.17, Glassfish 3.1 and Glassfish 3.1.1 Reporter: Thierry Peng Fix For: Future Injection of EJBs with Seam for Apache Wicket does not work properly. Wicket tries to serialize all injected references once the page/component changes its version. The culprit is the org.glassfish.weld.ejb.SessionObjectReferenceImpl.ejbRef which is not serializable, see the forum reference for the stacktrace. There are few discussions about this problem, one mentioned, that the spec doesn't require that an ejb must be serializable, which is true. Because this is a Problem which mainly affects wicket and its way to serializable the component tree, I suggest that we solve it in this module. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
5
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

14 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (SEAMREPORTS-8) Change API to benefit from Seam Render

by George Gastaldi (JIRA)

Change API to benefit from Seam Render -------------------------------------- Key: SEAMREPORTS-8 URL: https://issues.jboss.org/browse/SEAMREPORTS-8 Project: Seam Reports Issue Type: Enhancement Affects Versions: 3.0.0.Alpha1 Reporter: George Gastaldi Fix For: The Future The API could benefit from Seam Render SPI. This issue was created to check if that´s a good idea. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-43) develop, not master, should be the default branch

by Marek Schmidt (JIRA)

develop, not master, should be the default branch ------------------------------------------------- Key: SEAMREMOTING-43 URL: https://issues.jboss.org/browse/SEAMREMOTING-43 Project: Seam Remoting Issue Type: Bug Reporter: Marek Schmidt Assignee: Shane Bryzak All other modules that switched to the "git flow" have `develop' as a default branch, `master' is still appear to be the default in https://github.com/seam/remoting, also note that there is a commit in master that is not in develop (legal, but suspicious) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
1
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 August 2011