[
https://issues.apache.org/jira/browse/MTOMCAT-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852324#comment-13852324
]
Josh Chaitin-Pollak commented on MTOMCAT-250:
---------------------------------------------
To clarify, this patch / Pull Request is NOT specific to any specific Session
Manager implementation, it simply allows the user to specify a factory class to
construct a session manager on startup. I'm sure a more sophisticated solution
could be devised, but the existing Tomcat7RunnerCli is pretty basic in its
configuration abilities anyway. I am open to enhancing the patch if there are
recommended implementations.
> Pull Request: Support Alternate Session Managers in Standalone War Bootstrap
> ----------------------------------------------------------------------------
>
> Key: MTOMCAT-250
> URL: https://issues.apache.org/jira/browse/MTOMCAT-250
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Reporter: Josh Chaitin-Pollak
> Priority: Minor
> Fix For: 3.0
>
>
> Hello,
> I have created a pull request on GitHub to allow the standalone war
> bootstrapper to use a factory to create an alternate session manager.
> https://github.com/apache/tomcat-maven-plugin/pull/5
> I am using this with a modified version of the memcached-session-manager
> project to allow my standalone war project to use that session manager.
> I think this would be of utility to more people. Here is the MSM pull request
> for reference: https://github.com/magro/memcached-session-manager/pull/33
> And here is an example of how you would use this patch:
> {code}
> java -Dmsm.memcachedNodes="n1:localhost:21211" -jar standalone.jar \
> -sessionManagerFactory
> de.javakaffee.web.msm.MemcachedBackupSessionManagerFactory
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
