I'm -0.5 on throwing an exception.
The doc of the session module is very clear, "The module does not create a new session" So, in fact, this is a bug which should simply be fixed as proposed. Everyone relying on the fact, that a session is created by the module did not read the docs :) And from my understanding, I would rather expect that the module doesn't return a value if no session exists than throwing an exception.
If we put this change into the status.xml, everyone will see the change.
I agree with Carsten.
Vadim
Carsten
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] Behalf Of Jorg Heymans Sent: Wednesday, January 14, 2004 10:06 AM To: [EMAIL PROTECTED] Subject: Re: [BUG] SessionModule creates sessions on default
<snipped>
no value is found I think "null" is returned. Maybe we should throw an
exception in the case of no existing session because if you use an input
module you want to read out data, not more and not less.
If anything will be changed then I would prefer it like this. This way it's more obvious that the change was made and it won't go by unnoticed in developer code. Changing the underlying call "silently" to getSession(false) can cause all sorts of weird behaviour in seemingly unrelated parts of the code.
ReinhardJorg
