February 2011 - seam-issues - Jboss List Archives

[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 2/19/11 2:27 PM: --------------------------------------------------------------- Here are some examples. 1. Drop all frames in NoDefClassFoundError {code:java} public class NoClassFoundStackFrameFilter implements ExceptionStackFrameFilter<NoClassDefFoundError> { @Override public StackFrameFilterResult process(StackFrame frame) { return StackFrameFilterResult.BREAK; } } {code} 2. Truncate frames after a threshold (though no indication we did that we did) {code:java} public class TruncateExceptionStackFilter implements ExceptionStackFrameFilter<Throwable> { @Override public StackFrameFilterResult process(StackFrame frame) { if (frame.getIterationStatus().getIndex() >= 20) { return StackFrameFilterResult.DROP_REMAINING; } return StackFrameFilterResult.INCLUDE; } } {code} 3. Remove noise in between fire event and invoke observer {code:java} public class InvokeObserverStackFrameFilter implements ExceptionStackFrameFilter<Throwable> { @Override public StackFrameFilterResult process(StackFrame frame) { StackTraceElement el = frame.getStackTraceElement(); if (frame.isMarkSet("event.firing")) { if (isReflectionInvoke(el)) { frame.clearMark("event.firing"); return StackFrameFilterResult.DROP; } else { return StackFrameFilterResult.DROP; } } else if (el.getClassName().contains(".BeanManager") && el.getMethodName().equals("fireEvent")) { frame.mark("event.firing"); return StackFrameFilterResult.INCLUDE; } return StackFrameFilterResult.INCLUDE; } private boolean isReflectionInvoke(StackTraceElement candidate) { return candidate.getClassName().equals(Method.class.getName()) && candidate.getMethodName().equals("invoke"); } } {code} 4. Flatten reflections invoke into a single line {code:java} public class ReflectionInvokeStackFrameFilter implements ExceptionStackFrameFilter<Throwable> { @Override public StackFrameFilterResult process(StackFrame frame) { if (frame.isMarkSet("reflections.invoke")) { if (frame.getStackTraceElement().getMethodName().startsWith("invoke") || frame.getStackTraceElement().getClassName().contains("_WeldClientProxy")) { return StackFrameFilterResult.DROP; } else { frame.clearMark("reflections.invoke"); } } return StackFrameFilterResult.INCLUDE; } } {code} was (Author: dan.j.allen): Here are some examples. 1. Drop all frames in NoDefClassFoundError public class NoClassFoundStackFrameFilter implements ExceptionStackFrameFilter<NoClassDefFoundError> { @Override public StackFrameFilterResult process(StackFrame frame) { return StackFrameFilterResult.BREAK; } } 2. Truncate frames after a threshold (though no indication we did that we did) public class TruncateExceptionStackFilter implements ExceptionStackFrameFilter<Throwable> { @Override public StackFrameFilterResult process(StackFrame frame) { if (frame.getIterationStatus().getIndex() >= 20) { return StackFrameFilterResult.DROP_REMAINING; } return StackFrameFilterResult.INCLUDE; } } 3. Remove noise in between fire event and invoke observer public class InvokeObserverStackFrameFilter implements ExceptionStackFrameFilter<Throwable> { @Override public StackFrameFilterResult process(StackFrame frame) { StackTraceElement el = frame.getStackTraceElement(); if (frame.isMarkSet("event.firing")) { if (isReflectionInvoke(el)) { frame.clearMark("event.firing"); return StackFrameFilterResult.DROP; } else { return StackFrameFilterResult.DROP; } } else if (el.getClassName().contains(".BeanManager") && el.getMethodName().equals("fireEvent")) { frame.mark("event.firing"); return StackFrameFilterResult.INCLUDE; } return StackFrameFilterResult.INCLUDE; } private boolean isReflectionInvoke(StackTraceElement candidate) { return candidate.getClassName().equals(Method.class.getName()) && candidate.getMethodName().equals("invoke"); } } 4. Flatten reflections invoke into a single line public class ReflectionInvokeStackFrameFilter implements ExceptionStackFrameFilter<Throwable> { @Override public StackFrameFilterResult process(StackFrame frame) { if (frame.isMarkSet("reflections.invoke")) { if (frame.getStackTraceElement().getMethodName().startsWith("invoke") || frame.getStackTraceElement().getClassName().contains("_WeldClientProxy")) { return StackFrameFilterResult.DROP; } else { frame.clearMark("reflections.invoke"); } } return StackFrameFilterResult.INCLUDE; } } > 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.CR1 > > > 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

14 years, 8 months

1
0
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 2/19/11 2:25 PM: --------------------------------------------------------------- I played around with some ideas and we may even be able to use this for the exception mapping as well. Here are some prototype APIs. {code:java} /** * A filter for processing the stack frames of a single exception (type parameter allows us to focus on a specific exception type) */ public interface ExceptionStackFrameFilter<T extends Throwable> { public StackFrameFilterResult process(StackFrame frame); } public interface StackFrame { StackElement getStackElement(); StackTraceElement getStackTraceElement(); void mark(String tag); StackFrame getMarkedFrame(String tag); boolean isMarkSet(String tag); void clearMark(String tag); void setStackTraceElement(StackTraceElement element); IterationStatus getIterationStatus(); } public enum StackFrameFilterResult { /** * Include this frame */ INCLUDE, /** * Drop this frame */ DROP, /** * Include this frame, but skip any remaining frames in this cause */ DROP_REMAINING, /** * Drop this frame and any remaining frames in this cause */ BREAK, /** * Stops processing any remaining frames or causes */ TERMINATE, /** * Include this frame, then stop processing any remaining frames or causes */ TERMINATE_AFTER } /** * A filter for processing the chained exceptions (i.e., the causes) */ public interface ExceptionStackFilter { public StackFilterResult process(StackElement element); } public interface StackElement { Throwable getThrowable(); void setThrowable(Throwable throwable); IterationStatus getIterationStatus(); } public enum StackFilterResult { /** * Include this throwable */ INCLUDE, /** * Drop this throwable, go to next in chain (if any) */ DROP, /** * Drop any remaining throwables in the chain */ DROP_REMAINING, /** * Drop throwable and any remaining in the chain */ TERMINATE } {code} was (Author: dan.j.allen): I played around with some ideas and we may even be able to use this for the exception mapping as well. Here are some prototype APIs. /** * A filter for processing the stack frames of a single exception (type parameter allows us to focus on a specific exception type) */ public interface ExceptionStackFrameFilter<T extends Throwable> { public StackFrameFilterResult process(StackFrame frame); } public interface StackFrame { StackElement getStackElement(); StackTraceElement getStackTraceElement(); void mark(String tag); StackFrame getMarkedFrame(String tag); boolean isMarkSet(String tag); void clearMark(String tag); void setStackTraceElement(StackTraceElement element); IterationStatus getIterationStatus(); } public enum StackFrameFilterResult { /** * Include this frame */ INCLUDE, /** * Drop this frame */ DROP, /** * Include this frame, but skip any remaining frames in this cause */ DROP_REMAINING, /** * Drop this frame and any remaining frames in this cause */ BREAK, /** * Stops processing any remaining frames or causes */ TERMINATE, /** * Include this frame, then stop processing any remaining frames or causes */ TERMINATE_AFTER } /** * A filter for processing the chained exceptions (i.e., the causes) */ public interface ExceptionStackFilter { public StackFilterResult process(StackElement element); } public interface StackElement { Throwable getThrowable(); void setThrowable(Throwable throwable); IterationStatus getIterationStatus(); } public enum StackFilterResult { /** * Include this throwable */ INCLUDE, /** * Drop this throwable, go to next in chain (if any) */ DROP, /** * Drop any remaining throwables in the chain */ DROP_REMAINING, /** * Drop throwable and any remaining in the chain */ TERMINATE } > 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.CR1 > > > 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMREST-33) Unable to deploy recent snapshot

by Jozef Hartinger (JIRA)

Unable to deploy recent snapshot -------------------------------- Key: SEAMREST-33 URL: https://issues.jboss.org/browse/SEAMREST-33 Project: Seam REST Issue Type: Bug Reporter: Jozef Hartinger Assignee: Jozef Hartinger Stack trace: http://pastebin.com/3TeT5udB http://pastebin.com/VUfkkQnK Libraries used within the application: http://rapidshare.com/files/448504431/seam_jars.zip -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
10
0 / 0

[JBoss JIRA] Updated: (SEAMINTL-16) Implement an interpolator for strings containing expressions

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/SEAMINTL-16?page=com.atlassian.jira.plugi... ] Ken Finnigan updated SEAMINTL-16: --------------------------------- Fix Version/s: 3.1.0.Alpha1 (was: 3.0.0.CR1) > Implement an interpolator for strings containing expressions > ------------------------------------------------------------ > > Key: SEAMINTL-16 > URL: https://issues.jboss.org/browse/SEAMINTL-16 > Project: Seam International > Issue Type: Task > Components: Messages > Reporter: Dan Allen > Fix For: 3.1.0.Alpha1 > > > Since Weld Extensions has adopted the EL expression resolver, it's fitting that it also provides an interpolator for strings containing EL expression. > Provide an interpolator that resolves EL expressions and position parameters in strings. This feature was available in Seam 2 [1]. Since it's not provided yet in Seam 3, we see it showing up as a utility in various modules, including the International [2] and REST [3] modules. We should consolidate this to a single, authoritative source. > It should probably be made an interface with implementations that process specific expression languages, such as EL. For instance, one implementation might interpret MVEL. Just an idea. > [1] http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2/src/main/... > [2] https://github.com/seam/international/raw/master/impl/src/main/java/org/j... > [3] https://github.com/seam/rest/raw/master/impl/src/main/java/org/jboss/seam... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (SEAMJMS-16) Event to JMS to Event mapping behavior

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/SEAMJMS-16?page=com.atlassian.jira.plugin... ] Pete Muir reopened SEAMJMS-16: ------------------------------ Reopening, I don't understand what is spec required about this? Also, this is certainly fixable in JBoss AS, even if we have to do something complex to get there. > Event to JMS to Event mapping behavior > -------------------------------------- > > Key: SEAMJMS-16 > URL: https://issues.jboss.org/browse/SEAMJMS-16 > Project: Seam JMS > Issue Type: Bug > Reporter: John Ament > > While working on seam jms, I've noted the following behavior. > java.lang.IllegalStateException: Singleton not set for BaseClassLoader@3479404a{vfs:///apps/jboss/jboss-6.0.0.Final/server/all/conf/jboss-service.xml} > at org.jboss.weld.integration.provider.JBossSingletonProvider$EarSingleton.get(JBossSingletonProvider.java:59) [:6.0.0.Final] > at org.jboss.weld.Container.instance(Container.java:58) [:6.0.0.Final] > at org.jboss.weld.resolution.ResolvableBuilder.checkQualifier(ResolvableBuilder.java:209) [:6.0.0.Final] > at org.jboss.weld.resolution.ResolvableBuilder.addQualifier(ResolvableBuilder.java:174) [:6.0.0.Final] > at org.jboss.weld.resolution.ResolvableBuilder.addQualifierIfAbsent(ResolvableBuilder.java:184) [:6.0.0.Final] > at org.jboss.weld.manager.BeanManagerImpl.resolveObserverMethods(BeanManagerImpl.java:464) [:6.0.0.Final] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:604) [:6.0.0.Final] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:598) [:6.0.0.Final] > at org.jboss.seam.jms.bridge.IngressMessageListener.onMessage(IngressMessageListener.java:45) > at org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91) [:6.0.0.Final] > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final] > at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final] > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final] > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > This exception occurs when trying to fire an event with the contents of a JMS message. The message listener in this case is instantiated from the portable extension and receives the bean manager as an argument in the constructor. I am able to get as far as reading the data from JMS, but when firing the second event the above exception occurs. I'm not certain that this is a Weld problem, but it seem slike a good place to start based on the packages shown. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

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

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-63?page=com.atlassian.jira.plug... ] Brian Leathem resolved SEAMFACES-63. ------------------------------------ Resolution: Done > 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: Brian Leathem > Fix For: 3.0.0.CR1 > > > 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

14 years, 8 months

1
0
0 / 0

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

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-63?page=com.atlassian.jira.plug... ] Brian Leathem reopened SEAMFACES-63: ------------------------------------ Assignee: Brian Leathem (was: Jason Porter) > 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: Brian Leathem > Fix For: 3.0.0.CR1 > > > 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (SEAMJMS-16) Event to JMS to Event mapping behavior

by John Ament (JIRA)

[ https://issues.jboss.org/browse/SEAMJMS-16?page=com.atlassian.jira.plugin... ] John Ament closed SEAMJMS-16. ----------------------------- Resolution: Rejected Rejecting issue. This is apparently as defined by spec, so cannot be fixed. > Event to JMS to Event mapping behavior > -------------------------------------- > > Key: SEAMJMS-16 > URL: https://issues.jboss.org/browse/SEAMJMS-16 > Project: Seam JMS > Issue Type: Bug > Reporter: John Ament > > While working on seam jms, I've noted the following behavior. > java.lang.IllegalStateException: Singleton not set for BaseClassLoader@3479404a{vfs:///apps/jboss/jboss-6.0.0.Final/server/all/conf/jboss-service.xml} > at org.jboss.weld.integration.provider.JBossSingletonProvider$EarSingleton.get(JBossSingletonProvider.java:59) [:6.0.0.Final] > at org.jboss.weld.Container.instance(Container.java:58) [:6.0.0.Final] > at org.jboss.weld.resolution.ResolvableBuilder.checkQualifier(ResolvableBuilder.java:209) [:6.0.0.Final] > at org.jboss.weld.resolution.ResolvableBuilder.addQualifier(ResolvableBuilder.java:174) [:6.0.0.Final] > at org.jboss.weld.resolution.ResolvableBuilder.addQualifierIfAbsent(ResolvableBuilder.java:184) [:6.0.0.Final] > at org.jboss.weld.manager.BeanManagerImpl.resolveObserverMethods(BeanManagerImpl.java:464) [:6.0.0.Final] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:604) [:6.0.0.Final] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:598) [:6.0.0.Final] > at org.jboss.seam.jms.bridge.IngressMessageListener.onMessage(IngressMessageListener.java:45) > at org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91) [:6.0.0.Final] > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final] > at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final] > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final] > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > This exception occurs when trying to fire an event with the contents of a JMS message. The message listener in this case is instantiated from the portable extension and receives the bean manager as an argument in the constructor. I am able to get as far as reading the data from JMS, but when firing the second event the above exception occurs. I'm not certain that this is a Weld problem, but it seem slike a good place to start based on the packages shown. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-4782) beans.xml is now empty in seam-persistence-3.0.0.Beta4.jar

by Emeric Kwemou (JIRA)

beans.xml is now empty in seam-persistence-3.0.0.Beta4.jar ---------------------------------------------------------- Key: JBSEAM-4782 URL: https://issues.jboss.org/browse/JBSEAM-4782 Project: Seam Issue Type: Bug Reporter: Emeric Kwemou Priority: Optional this was not the case in prior version of seam persistence. now one have to explicitely declare interceptors : org.jboss.seam.persistence.transaction.TransactionInterceptor. Please clearly state if users have to declare the interceptor themselve. Thank you Emeric -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4783) Seam Remoting fails to generate valid XML if object has a field without a getter.

by Nadim Rafehi (JIRA)

Seam Remoting fails to generate valid XML if object has a field without a getter. --------------------------------------------------------------------------------- Key: JBSEAM-4783 URL: https://issues.jboss.org/browse/JBSEAM-4783 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.2.1.Final Environment: Windows 7 running Seam 2.2.1 Final on JBoss 6.0.0 Final. Reporter: Nadim Rafehi Assignee: Shane Bryzak When trying to serialize a list (possibly also a single object) which has a field with no getter method, the XML serializer will create an opening tag but will not put in anything in the body nor will it close the tag. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2011