Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Newcomers » Is there a way to hide the debug lines wildfly uses when calling interface methods?(wildfly, eclipse debug)
Is there a way to hide the debug lines wildfly uses when calling interface methods? [message #1821205] Fri, 07 February 2020 07:54 Go to next message
Péter Forgács is currently offline Péter ForgácsFriend
Messages: 1
Registered: February 2020
Junior Member
So when I call the method of an interface, there are a bunch of lines between the calling class and the called class that I do not care about. Is there a way to omit them from the debug call stack? If A class X method calls B interface Y method and C implements B, I would like to see only these two lines:

A.X

C.Y

example of such lines:

InterceptorContext.proceed() line: 340
InterceptorContext$Invocation.proceed() line: 437
Jsr299BindingsInterceptor.doMethodInterception(InvocationContext, InterceptionType, WeldInterceptorInstances, InterceptorBindings) line: 82
Jsr299BindingsInterceptor.processInvocation(InterceptorContext) line: 93
UserInterceptorFactory$1.processInvocation(InterceptorContext) line: 63
InterceptorContext.proceed() line: 340
ExecutionTimeInterceptor.processInvocation(InterceptorContext) line: 43
InterceptorContext.proceed() line: 340
SBInvocationInterceptor.processInvocation(InterceptorContext) line: 47
InterceptorContext.proceed() line: 340
InterceptorContext$Invocation.proceed() line: 437
EjbRequestScopeActivationInterceptor(AbstractEJBRequestScopeActivationInterceptor).aroundInvoke(InvocationContext) line: 64
EjbRequestScopeActivationInterceptor.processInvocation(InterceptorContext) line: 83
InterceptorContext.proceed() line: 340
ConcurrentContextInterceptor.processInvocation(InterceptorContext) line: 45
InterceptorContext.proceed() line: 340
InitialInterceptor.processInvocation(InterceptorContext) line: 21
InterceptorContext.proceed() line: 340
ChainedInterceptor.processInvocation(InterceptorContext) line: 61
ComponentDispatcherInterceptor.processInvocation(InterceptorContext) line: 52
InterceptorContext.proceed() line: 340
PooledInstanceInterceptor.processInvocation(InterceptorContext) line: 51
InterceptorContext.proceed() line: 340
CMTTxInterceptor.invokeInCallerTx(InterceptorContext, Transaction, EJBComponent) line: 254
CMTTxInterceptor.required(InterceptorContext, EJBComponent, int) line: 329
CMTTxInterceptor.processInvocation(InterceptorContext) line: 239
InterceptorContext.proceed() line: 340
CurrentInvocationContextInterceptor.processInvocation(InterceptorContext) line: 41
InterceptorContext.proceed() line: 340
WaitTimeInterceptor.processInvocation(InterceptorContext) line: 47
InterceptorContext.proceed() line: 340
SecurityContextInterceptor.processInvocation(InterceptorContext) line: 100
InterceptorContext.proceed() line: 340
StartupAwaitInterceptor.processInvocation(InterceptorContext) line: 22
InterceptorContext.proceed() line: 340
ShutDownInterceptorFactory$1.processInvocation(InterceptorContext) line: 64
InterceptorContext.proceed() line: 340
LoggingInterceptor.processInvocation(InterceptorContext) line: 67
InterceptorContext.proceed() line: 340
NamespaceContextInterceptor.processInvocation(InterceptorContext) line: 50
InterceptorContext.proceed() line: 340
AdditionalSetupInterceptor.processInvocation(InterceptorContext) line: 54
InterceptorContext.proceed() line: 340
ContextClassLoaderInterceptor.processInvocation(InterceptorContext) line: 64
InterceptorContext.proceed() line: 340
InterceptorContext.run() line: 356
WildFlySecurityManager.doChecked(PrivilegedExceptionAction<T>) line: 636
AccessCheckingInterceptor.processInvocation(InterceptorContext) line: 61
InterceptorContext.proceed() line: 340
InterceptorContext.run() line: 356
PrivilegedWithCombinerInterceptor.processInvocation(InterceptorContext) line: 80
InterceptorContext.proceed() line: 340
ChainedInterceptor.processInvocation(InterceptorContext) line: 61
ViewService$View.invoke(InterceptorContext) line: 198
ViewDescription$1.processInvocation(InterceptorContext) line: 185
InterceptorContext.proceed() line: 340
Re: Is there a way to hide the debug lines wildfly uses when calling interface methods? [message #1821247 is a reply to message #1821205] Sat, 08 February 2020 05:50 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 30892
Registered: July 2009
Senior Member
It's probably better to ask on the JDT forum:

https://www.eclipse.org/forums/index.php/f/13/

If there is a way, it would be accomplished using the "Use Step Filters" toolbar button. The behavior is configured by Preferences -> Java -> Debug -> Step Filtering.
Previous Topic:Getting an error in Mac OS
Next Topic:Can't find the download button for the installer
Goto Forum:
  


Current Time: Thu Feb 20 15:06:35 GMT 2020

Powered by FUDForum. Page generated in 0.05648 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top