Do the right thing, even if it means breaking existing tests. Ultimately, that will be better in the long run. Just my $0.02.
-- Jeff -----Original Message----- From: Pedro Nevado [mailto:[EMAIL PROTECTED] Sent: Thursday, November 11, 2004 12:39 PM To: Cactus Users List Subject: RE: FilterRedirector does not initialize sessions. - IS THIS A BUG ?? Hi there, As far as I remember, the problem is not only with the default mecanism to associate a session to the request in the client side. Even if you explicitly set automatic session to true in the client side, this statement is ineffective in the server side. In my test with filters I bypass this limitation dealing with the session in the server side. A midway would be just to patch the code to allow instatiating a session if explicitly said in the webrequest. That way, there would not be, I think, any effect on existing tests wich counts on the present default mecanism. Please, let me now what you finally conclude about this point. Regards, Pedro -----Mensaje original----- De: Kazuhito SUGURI [mailto:[EMAIL PROTECTED] Enviado el: jueves, 11 de noviembre de 2004 17:14 Para: [EMAIL PROTECTED] Asunto: Re: FilterRedirector does not initialize sessions. - IS THIS A BUG ?? Hi Vincent, In article <[EMAIL PROTECTED]>, Thu, 11 Nov 2004 14:03:04 +0100, "Vincent Massol" <[EMAIL PROTECTED]> wrote: vmassol> What strategy would you like us to follow to align the behaviors of vmassol> FilterTestCase and ServletTestCase? To align... Is this means that FilterTestCase and ServletTestCase should have same behavior of its default setAutomateSession()? If so, I think it's impossible without breaking existing TestCases. Of cource, it might be more trifling problem than I think. Why don't we wait for reactions from other users of this list? # How do you think, Pedro? vmassol> BTW, do you have any idea why I decided to enable session creation by vmassol> default for ServletTestCase? I can't recall... ;-) I'm not sure since it had already been so when I used Cactus for the first time. But I can guess some: 1. Servlet uses a session object in many cases, then, it's user friendly if the session object is prepared by default. 2. if method under test uses a session object, a TestCase 'there is no session object available' is needed only once, however, there are other many 'when the session object has XYZ' TestCases. 3. if method under test does not use any session object, the default behavior of the session creation can not be a problem. Regards, ---- Kazuhito SUGURI mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions USA, Inc. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
