January 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Updated: (SEAM-17) Switch to JBoss Community coding style

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAM-17?page=com.atlassian.jira.plugin.sy... ] Dan Allen updated SEAM-17: -------------------------- Summary: Switch to JBoss Community coding style (was: Switch to JBoss code style to modules) Description: For reasons people can no longer even remember, Seam uses a very non-conventional code style. This complicates patches, impacts documentation and generally swims upstream against Java conventions. By adopting the JBoss Community coding style (specifically the code style used in AS 7 [1], one of the newest projects at JBoss), it simplifies things on the one hand while providing the appearance of JBoss projects working together on the other. This change would be made in the process of preparing a candidate release of the Seam stack. We'll also need to update the reference guides. The JBoss convention closely parallels the Java convention with a few exceptions. We believe that these exceptions are corrections to poor choices in the Java convention, so we could call it the Java convention 2.0. Those differences are as follows: AS 7 vs Java convention 1. Spaces vs mixed tabs and spaces (a strange default) 2. Single block indent for continued lines vs double block indent for continued lines 3. 128 line width vs 80 4. indent switch statements vs don't indent switch statements 5. indent size 4 vs indent size 8 6. minor javadoc differences [1] https://github.com/jbossas/jboss-as/raw/master/ide-configs/eclipse/as7for... was: For reasons people can no longer even remember, Seam uses a very non-conventional code style. This complicates patches, impacts documentation and generally swims upstream against Java conventions. By adopting the JBoss code style (specifically the code style used in AS 7 [1], one of the newest projects at JBoss), it simplifies things on the one hand while providing the appearance of JBoss projects working together on the other. This change would be made in the process of preparing a candidate release of the Seam stack. We'll also need to update the reference guides. The JBoss convention closely parallels the Java convention with a few exceptions. We believe that these exceptions are corrections to poor choices in the Java convention, so we could call it the Java convention 2.0. Those differences are as follows: AS 7 vs Java convention 1. Spaces vs mixed tabs and spaces (a strange default) 2. Single block indent for continued lines vs double block indent for continued lines 3. 128 line width vs 80 4. indent switch statements vs don't indent switch statements 5. indent size 4 vs indent size 8 6. minor javadoc differences [1] https://github.com/jbossas/jboss-as/raw/master/ide-configs/eclipse/as7for... > Switch to JBoss Community coding style > -------------------------------------- > > Key: SEAM-17 > URL: https://issues.jboss.org/browse/SEAM-17 > Project: Seam 3 > Issue Type: Task > Components: Release tasks > Reporter: Dan Allen > > For reasons people can no longer even remember, Seam uses a very non-conventional code style. This complicates patches, impacts documentation and generally swims upstream against Java conventions. > By adopting the JBoss Community coding style (specifically the code style used in AS 7 [1], one of the newest projects at JBoss), it simplifies things on the one hand while providing the appearance of JBoss projects working together on the other. > This change would be made in the process of preparing a candidate release of the Seam stack. We'll also need to update the reference guides. > The JBoss convention closely parallels the Java convention with a few exceptions. We believe that these exceptions are corrections to poor choices in the Java convention, so we could call it the Java convention 2.0. Those differences are as follows: > AS 7 vs Java convention > 1. Spaces vs mixed tabs and spaces (a strange default) > 2. Single block indent for continued lines vs double block indent for continued lines > 3. 128 line width vs 80 > 4. indent switch statements vs don't indent switch statements > 5. indent size 4 vs indent size 8 > 6. minor javadoc differences > [1] https://github.com/jbossas/jboss-as/raw/master/ide-configs/eclipse/as7for... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-3) Support multiple to addresses

by Pete Muir (JIRA)

Support multiple to addresses ----------------------------- Key: SEAMMAIL-3 URL: https://jira.jboss.org/browse/SEAMMAIL-3 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-2) Testing infrastructure

by Pete Muir (JIRA)

Testing infrastructure ---------------------- Key: SEAMMAIL-2 URL: https://jira.jboss.org/browse/SEAMMAIL-2 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMWICKET-23) Seam Catch integration

by Jason Porter (JIRA)

Seam Catch integration ---------------------- Key: SEAMWICKET-23 URL: https://issues.jboss.org/browse/SEAMWICKET-23 Project: Seam Wicket Issue Type: Feature Request Affects Versions: 3.0.0.Beta1 Reporter: Jason Porter Wicket I believe has some exception handling built in and the ability to extend it. The wicket module needs integration with Catch to allow Catch Handlers to work with wicket exception handling infrastructure. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMREST-16) Move jaxrs example from Catch to REST

by Jozef Hartinger (JIRA)

Move jaxrs example from Catch to REST ------------------------------------- Key: SEAMREST-16 URL: https://issues.jboss.org/browse/SEAMREST-16 Project: Seam REST Issue Type: Task Affects Versions: Alpha2 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: Alpha3 (04:19:53 PM) mojavelinux: super...perhaps you can create a small example that uses the java-based exception handling...in fact, you could just take the example from catch...perhaps trim it down to the bare bones (04:21:20 PM) mojavelinux: and just call it something like seam-example-rest-exceptions (04:21:40 PM) mojavelinux: very simple scope -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMREST-15) Adapt to WELD-796

by Jozef Hartinger (JIRA)

Adapt to WELD-796 ----------------- Key: SEAMREST-15 URL: https://issues.jboss.org/browse/SEAMREST-15 Project: Seam REST Issue Type: Task Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Blocker Since the ProcessAnnotatedType is no longer fired for AnnotatedTypes registered via beanManager.addAnnotatedType, the Seam Config module is no longer able to configure Seam REST. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMREST-12) Upgrade to Seam Catch Alpha3

by Jozef Hartinger (JIRA)

Upgrade to Seam Catch Alpha3 ---------------------------- Key: SEAMREST-12 URL: https://issues.jboss.org/browse/SEAMREST-12 Project: Seam REST Issue Type: Feature Request Reporter: Jozef Hartinger Assignee: Jozef Hartinger -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Commented: (SEAMFACES-63) Create a JSF bridge to Seam Catch

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-63?page=com.atlassian.jira.plug... ] Dan Allen commented on SEAMFACES-63: ------------------------------------ I made some follow-up tweaks to bring this feature inline w/ the latest Solder API. Can't wait to show it off! > Create a JSF bridge to Seam Catch > --------------------------------- > > Key: SEAMFACES-63 > URL: https://issues.jboss.org/browse/SEAMFACES-63 > Project: Seam Faces > Issue Type: Feature Request > Components: Exception Handling > Affects Versions: 3.0.0.Beta1 > Reporter: Jason Porter > Assignee: Jason Porter > Fix For: 3.0.0.Beta3 > > > We need a JSF2 bridge for Catch. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SEAMFACES-63) Create a JSF bridge to Seam Catch

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-63?page=com.atlassian.jira.plug... ] Dan Allen updated SEAMFACES-63: ------------------------------- Status: Resolved (was: Pull Request Sent) > Create a JSF bridge to Seam Catch > --------------------------------- > > Key: SEAMFACES-63 > URL: https://issues.jboss.org/browse/SEAMFACES-63 > Project: Seam Faces > Issue Type: Feature Request > Components: Exception Handling > Affects Versions: 3.0.0.Beta1 > Reporter: Jason Porter > Assignee: Jason Porter > Fix For: 3.0.0.Beta3 > > > We need a JSF2 bridge for Catch. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (SEAMFACES-63) Create a JSF bridge to Seam Catch

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-63?page=com.atlassian.jira.plug... ] Dan Allen updated SEAMFACES-63: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/seam/faces/pull/9 Pull request satisfying complete feature request available. > Create a JSF bridge to Seam Catch > --------------------------------- > > Key: SEAMFACES-63 > URL: https://issues.jboss.org/browse/SEAMFACES-63 > Project: Seam Faces > Issue Type: Feature Request > Components: Exception Handling > Affects Versions: 3.0.0.Beta1 > Reporter: Jason Porter > Assignee: Jason Porter > Fix For: 3.0.0.Beta3 > > > We need a JSF2 bridge for Catch. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2011