[logback-user] turn off stack traces in one appender, leave them on in another

Given a configuration with two appenders, one file based and the other network-based, I would like to be able to code log statements with a throwable parameter in which the file-based one would append the stack-trace information contained in the throwable, but the network-based appender would not. The network-based appender is home-brewed, descending from JMSAppenderBase. Is there a hook in the appender hierarchy that would allow it to turn off appending of the stack trace for that appender while letting other appenders print the stack trace? Thanks.