cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From oceatoon <t.katelb...@systheo.com>
Subject Re: WishFull thinking JX and SessionContext Authentication
Date Sat, 22 Jan 2005 11:43:18 GMT
Carsten Ziegeler wrote:

> Leszek Gawron wrote:
>> Carsten Ziegeler wrote:
>> 
>>> oceatoon wrote:
>>>
>>>> This is wishfull thinking and probably no news to those refactoring
>>>> JX. But
>>>> access to the session context object like the session-context input
>>>> module
>>>> would be great (like for example with the authentication context). I
>>>> have
>>>> found other post asking about and for this sort of functionality. it
>>>> would
>>>> smoothen quite a bit the access to such inportant elements as the
>>>> ones in
>>>> session-context (like authentication data).
>>>>
>>> Yes, this should be possible, I agree. I hope that the refactored
>>> version will be pluggable to plug-in some kind of adapter to access
>>> "own data" like the authentication context etc.
>> 
>> 
>> Wouldn't it be better if JXTG supported input modules with syntax like:
>> 
>> {im:moduleName:valueName}
>> 
>> ?
Yes that would be even better

> Don't know :) Sure, this is one solution - my idea is a little bit
> different:
> we could provide a pluggable object model and then use this object model
> in jxtg,
> but also in input modules - so in fact you would only need one input
> module and can use the same syntax there as in jxtg. I'm not sure if
> this makes sense, but if it does, we wouldn't need input modules anymore.
do you mean input modules would be pluggable objects and we could create our
own object to be used ? but in that case why not simply create another IM?
And IM are quite usefull all over cocoon, don't you think?

Tibor



Mime
View raw message