Re: Enhydra: Re: Enhydra: tomcat vs. enhydra

David Li <[email protected]> wrote:

>The implementation includes write to disk and write to DB for 
>fail-over. Tomcat's session manager is basic. I am not talking about 
>interface difference but implementation difference.

I can see your point of view...


>Are you using XMLC 2.2? It's pretty straight forward to use XMLC 2.2 
>with Tomcat. In fact, Tomcat is used as the development environment of 
>XMLC 2.2. ;) There is an example in 2.2 distribution.

No, i'm stuck with the xmlc that comes with enhydra (now 5.1beta7), i've
looked at 2.2alpha4 but never tried it in a production stage probably
cause i was scared by the 'alpha' stage.
As i can read the only thing changed is the xerces now packaged
differently... right ?


>More XMLC 2.2 promotion here:
>
>http://debian-sf.objectweb.org/projects/xmlc

Definitely i'll look at it more deeper... I think there's no problem
replacing xmlc jars within 5.1beta7 with the ones from xmlc2.2alpha4, am
i wrong ? Are you aware of problems with this configuration ?

>I thought the 5.0 has made that easy. There was a patch needed for 3.x 
>which I have posted here. I think that's integrated into 5.x already.

I'm doing it right now and i'm having problem with log4j configuration.
I still haven't found where to put log4j.xml file for
HttpPresentationServlet.configureLogger to find it.

>According to Madl Alfred, that's the direction of Enhydra 6.0.

That's would be a great boost in enhydra value!

Regards,
Thelmo