January 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4757) update ICEfaces version to 1.8.2

by judy guglielmin (JIRA)

update ICEfaces version to 1.8.2 --------------------------------- Key: JBSEAM-4757 URL: https://issues.jboss.org/browse/JBSEAM-4757 Project: Seam Issue Type: Feature Request Components: Build Affects Versions: 2.2.1.CR3 Environment: jsf1.2 Reporter: judy guglielmin Priority: Critical Fix For: 2.2.1.Final ICEfaces version 1.8.2 (and all subsequent general releases) will now be available for maven2 access from central repository. All scripts doing maven calls for ICEfaces (examples and seam-gen) should now refer to this version -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-16) Forge should be able to view/modify beans.xml as a Plugin, not only as a Facet

by Lincoln Baxter III (JIRA)

Forge should be able to view/modify beans.xml as a Plugin, not only as a Facet ------------------------------------------------------------------------------ Key: SEAMFORGE-16 URL: https://issues.jboss.org/browse/SEAMFORGE-16 Project: Seam Forge Issue Type: Feature Request Components: Brainstorming Reporter: Lincoln Baxter III The ability to re-order, add, or remove interceptors / decorators for example. Adding/removing beans - seam config support, etc. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-35) Add combined JAR to build

by Dan Allen (JIRA)

Add combined JAR to build ------------------------- Key: SEAMCATCH-35 URL: https://issues.jboss.org/browse/SEAMCATCH-35 Project: Seam Catch Issue Type: Task Components: Build Infrastructure Affects Versions: 3.0.0.Alpha2 Reporter: Dan Allen Assignee: Dan Allen Fix For: 3.0.0.Alpha3 Add the combined JAR build. Ensure that the JAR depends only on other combined JARs, not individual JARs. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-33) Setup Hudson job for Seam Catch

by Dan Allen (JIRA)

Setup Hudson job for Seam Catch ------------------------------- Key: SEAMCATCH-33 URL: https://issues.jboss.org/browse/SEAMCATCH-33 Project: Seam Catch Issue Type: Task Components: Build Infrastructure, Test Suite Affects Versions: Alpha2 Reporter: Dan Allen Assignee: Jason Porter Fix For: Alpha3 The Hudson job should run a full build. mvn clean install Also include a job to publish the reference guide, API docs and Maven snapshots on a nightly basis. Project information here: http://seamframework.org/Seam3/CatchModule -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

5
13
0 / 0

[JBoss JIRA] Created: (SOLDER-52) Add methods to AnnotationIntrospector that operate on Annotated (from CDI)

by Dan Allen (JIRA)

Add methods to AnnotationIntrospector that operate on Annotated (from CDI) -------------------------------------------------------------------------- Key: SOLDER-52 URL: https://issues.jboss.org/browse/SOLDER-52 Project: Seam Solder Issue Type: Feature Request Reporter: Dan Allen The AnnotationIntrospector works on java.lang.reflect.AnnotatedElement types. However, in an extension, you are most often dealing with an Annotated. Therefore, the AnnotationIntrospector should provide parallel utilities for retrieving/checking an annotation on Annotated or any stereotype on Annotated. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
8
0 / 0

[JBoss JIRA] Issue Comment Edited: (SEAMCATCH-4) Include the ability to filter stack traces

by Jason Porter (JIRA)

[ https://issues.jboss.org/browse/SEAMCATCH-4?page=com.atlassian.jira.plugi... ] Jason Porter edited comment on SEAMCATCH-4 at 1/3/11 7:33 PM: -------------------------------------------------------------- This is really different than what is in the chat log. At first it seems like we were talking about the ExceptionStack event (which is in HEAD currently), then we moved into the actual issue, which I agree should be part of Catch, but it's like a side API that can be used outside of any handlers. We also need something that will print the stack trace, either it'll print a string, or take an PrintStream and print to it. was (Author: lightguard): This is really different than what is in the chat log. At first it seems like we were talking about the ExceptionStack event (which is in HEAD currently), then we moved into the actual issue, which I agree should be part of Catch, but it's like a side API that can be used outside of any handlers. We also need something that will print the stack trace, either it'll print a string, or take an OutputStream and print to it. > Include the ability to filter stack traces > ------------------------------------------ > > Key: SEAMCATCH-4 > URL: https://issues.jboss.org/browse/SEAMCATCH-4 > Project: Seam Catch > Issue Type: Feature Request > Reporter: Jason Porter > Assignee: Jason Porter > Fix For: 3.0.0.Alpha4 > > > Catch should draw from ideas such as: > - http://www.docjar.org/html/api/org/apache/commons/lang/exception/Nestable... > - http://stackoverflow.com/questions/2504647/bash-how-to-filter-java-except... > - http://squirrelsewer.blogspot.com/2010/03/filter-your-stack-traces.html > - http://pastebin.com/p8aCSeuu -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (SEAMCATCH-4) Include the ability to filter stack traces

by Jason Porter (JIRA)

[ https://issues.jboss.org/browse/SEAMCATCH-4?page=com.atlassian.jira.plugi... ] Jason Porter commented on SEAMCATCH-4: -------------------------------------- This is really different than what is in the chat log. At first it seems like we were talking about the ExceptionStack event (which is in HEAD currently), then we moved into the actual issue, which I agree should be part of Catch, but it's like a side API that can be used outside of any handlers. We also need something that will print the stack trace, either it'll print a string, or take an OutputStream and print to it. > Include the ability to filter stack traces > ------------------------------------------ > > Key: SEAMCATCH-4 > URL: https://issues.jboss.org/browse/SEAMCATCH-4 > Project: Seam Catch > Issue Type: Feature Request > Reporter: Jason Porter > Assignee: Jason Porter > Fix For: 3.0.0.Alpha4 > > > Catch should draw from ideas such as: > - http://www.docjar.org/html/api/org/apache/commons/lang/exception/Nestable... > - http://stackoverflow.com/questions/2504647/bash-how-to-filter-java-except... > - http://squirrelsewer.blogspot.com/2010/03/filter-your-stack-traces.html > - http://pastebin.com/p8aCSeuu -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-37) Unwrap SQLExceptions

by Jason Porter (JIRA)

Unwrap SQLExceptions -------------------- Key: SEAMCATCH-37 URL: https://issues.jboss.org/browse/SEAMCATCH-37 Project: Seam Catch Issue Type: Feature Request Components: Core Implementation Affects Versions: 3.0.0.Alpha3, 3.0.0.Alpha2, 3.0.0.Alpha1 Reporter: Jason Porter Assignee: Jason Porter Fix For: 3.0.0.Alpha4 Look at http://download.oracle.com/javase/6/docs/api/java/sql/SQLException.html Hey, instead of wrapping exceptions like EVERYONE ELSE in Java, let's do it differently *grumble, grumble, grumble* Now we need to see if it's an SQLException and get the iterator and put those exceptions into the causes somewhere. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-20) Document what happens when a handler throws an exception

by Dan Allen (JIRA)

Document what happens when a handler throws an exception -------------------------------------------------------- Key: SEAMCATCH-20 URL: https://jira.jboss.org/browse/SEAMCATCH-20 Project: Seam Catch Issue Type: Task Components: Documentation Affects Versions: Alpha2 Reporter: Dan Allen Assignee: Jason Porter Priority: Minor Fix For: Alpha3 The documentation should be more clear as to what happens when a handler throws an exception (even if its discouraged). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-32) untangle processing of exceptions in stack

by Dan Allen (JIRA)

untangle processing of exceptions in stack ------------------------------------------ Key: SEAMCATCH-32 URL: https://issues.jboss.org/browse/SEAMCATCH-32 Project: Seam Catch Issue Type: Task Components: Core Implementation Affects Versions: Alpha2 Reporter: Dan Allen Assignee: Jason Porter Fix For: Alpha3 Currently, the exceptions in the stack are being handled in tandem. All the breadth-first type visiting is happening for each exception in the stack, then all the depth-first type visiting is happening. Each exception should be processed in turn. Consider this case: The following exception chain is thrown: E1 -> E2 -> E3 (where "X -> Y" means X is caused by Y). Also, E3S is a superclass of E3. Let's assume there are handlers for all four exception types for both traversal modes (breadth-first and depth-first). The expected order of execution is as follows: E3S handler in the breadth-first traversal mode E3 handler in the breadth-first traversal mode E3 handler in the depth-first traversal mode E3S handler in the depth-first traversal mode E2 handler in the breadth-first traversal mode E2 handler in the depth-first traversal mode E1 handler in the breadth-first traversal mode E1 handler in the depth-first traversal mode We process the exceptions in the stack in the order E3, E2, E1 because we assume the cause, E3 is the most important exception. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

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