RE: [Tomcat-jg-development] new feature

[Filip H. <ma...@fi...>]

this is not really a problem. All it means is that you will not be able to
manage the InMemoryReplicationManager
through a JMX admin tool.
It is a poor choice of the tomcat developers to hardcode the classes into a
XML file in the library path, instead of making this openly configurable.

Filip

~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
www.filip.net

>-----Original Message-----
>From: tom...@li...
>[mailto:tom...@li...]On Behalf Of
>Bela Ban
>
>
>Dude,
>
>can we do something about the problem below ? Should we include that
>file in our distribution as well ?
>
>
>By: jronan <http://sourceforge.net/users/jronan/> ( Jim Ronan )
>RE: session replication
><http://sourceforge.net/forum/message.php?msg_id=1749592>
>2002-11-08 12:35 I had the same problem with tomcat 4.1.12. I believe it
>is caused by internal changes within Tomcat that require classes like
>the session manager to be included in the mbeans-descriptors.xml file. I
>fixed it by extracting the mbeans-descriptors.xml file from
>$TOMCAT_HOME/server/lib/catalina.jar and saving it to
>$TOMCAT_HOME/server/classes/org/apache/catalina/mbeans. Next, I copied
>the section for the StandardManager, and renamed it
>InMemoryReplicationManager.
>
>This cleared the problem.
>
>good luck - jim
>
>--
>Bela Ban
>http://www.javagroups.com
>Cell: (408) 316-4459
>