With stuff like this the usually the trick is to make sure your not
clustering anything that doesn't need to really be shared across
JVM. The other trick is to make sure you include the classes for
instrumentation that need it. This is usually not to hard
but each framework has it's nuances so hard to say if their will be
any trouble. Once you have the includes and stuff
done the best thing you can do for the community is create a TIM http://www.terracotta.org/web/display/docs/Terracotta+Integration+Modules+Manual
on
the forge http://forge.terracotta.org. That way the next person will
have it easy.
Cheers,
Steve Harris
"Terracotta. It's ten pounds of awesome in a five pound sack."
On Jan 11, 2009, at 12:44 PM, Philip S. Constantinou wrote:
Not knowing anything about running Terracotta, but having experience
running Stripes in a clustered Tomcat environment, there's two
things I'd watch for.
You're going to need session replication which I imagine Terracotta
does well since it's common in the Java Servlet environment.
When you set up the stripes make sure to configure
Stripes.EncryptionKey
By default Stripes generates a random number at startup which it
uses as the secret to create a signature that's generated by the
stripes:form tag and submitted to prevent browser HTML tampering.
Unless the configuration is the same, failover between two nodes
will makes some form submissions issues errors to the user. By
configuring the Stripes.EncryptionKey you override the random number
with a shared secret.
Good luck!
<!-- Declarations for Stripes to operate as a web filter -->
<filter>
<filter-name>StripesFilter</filter-name>
<filter-class>net.sourceforge.stripes.controller.StripesFilter</
filter-class>
....
<init-param>
<param-name>Stripes.EncryptionKey</param-name>
<param-value>somerandomsecretstring</param-value>
</init-param>
On Sun, Jan 11, 2009 at 10:13 AM, mh <[email protected]> wrote:
Does it mean that it would not be a good idea to proceed with Stripes
assuming that it will work just work on top of Terracotta before this
integration happens? One of the Terracotta's promises is that it's
transparent
and does not require any specific changes to app code but at the
same time there
are TIMs... It's a bit confusing...
mh
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
