Hi Fernando,
By default Terracotta for Spring is naming those roots using synthetic
name derived from the matching web application name and matching spring
config names. There is a FAQ entry about that in the "Troubleshooting
Guide" linked from the on Terracotta home page. See
https://terracotta.org/confluence/display/wiki/Troubleshooting+Guide#TroubleshootingGuide-TerracottaforSpring...
So you can override that root name in your tc-config.xml using
<root-name> element:
...
<application>
<spring>
<jee-application>
<application-contexts>
<application-context>
<root-name>myClusteredSpringContext</root-name>
...
regards,
Eugene Kuleshov
PS: it feels like I am the only one answering all the questions today,
but by strange coincidence those happens to be from my area of expertise
Fernando Padilla wrote:
> I want to run my webapp through tomcat, jetty and mvn jetty:run, but
> when I did, I noticed that terracotta was generating unique roots for
> different ways that I launch the web application; and for each different
> context path that I launch my webapp under.. ( so developers can't share
> roots )
>
> This is very disappointing. How can I get this working?
>
> -------
> tc:spring_info.appName is coming up with different things:
>
> fbracket
> Jetty.path=/fbracket
> Jetty.path=/fannetwork
>
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users
