• New Feature
  • Status: Closed
  • 3 Minor
  • Resolution: Fixed
  • SpringRuntime
  • ekulesho
  • Reporter: ekulesho
  • January 18, 2007
  • 0
  • Watchers: 0
  • July 27, 2012
  • February 05, 2007


Currently we always include execution stack trace into synthetic id generated for Spring app context. This is done to allow scenario like this:

ctx1 = new ClasspathXmlApplicationContext(new String[] {“ctx.xml”}); ctx2 = new ClasspathXmlApplicationContext(new String[] {“ctx.xml”});

So, ctx1 and ctx2 won’t be linked together as a clustered context and will stay unrelated, though instance of ctx1 or ctx2 can be still clustered with context created at the same location on different node.

However there are scenarios when this logic may not be what user would expect and we need to support that.

The idea is to disable stack trace inclusion by default and add an option to tc-config.xml to allow to enable it. Meaning of that option is something like “include location info into the generated context id”.


Steve Harris 2007-01-19

So the default will be for autoid to be off. Lets brain storm on some names.

auto id stack based id dynamic id

any other ideas?

Eugene Kuleshov 2007-01-19

generate id with location generate id with stacktrace

Eugene Kuleshov 2007-02-05

Added element to the . By default stack trace is not added, but can be enabled back by adding:

true ... </div>