Christian,

Do you have any examples?

Ralph

> -----Original Message-----
> From: Christian Haul [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 10, 2003 2:00 AM
> To: [EMAIL PROTECTED]
> Subject: Re: output-modules
> 
> 
> On 10.Oct.2003 -- 10:33 AM, Frederic Gaus wrote:
> > Hi! 
> > 
> > I would like to use output-modules. But I just can not find 
> out how to
> > use them. It's very clear and easy to use input-modules, just like
> > variables. But how do I have to use the output-modules? 
> Thanks for all
> > your hints. 
> 
> Concept is very similar. If you plan to store data somewhere, an
> output module gives an additional indirection. This way it is easy to
> switch eg. between storing data in a session or as request
> attributes. Maybe it should not be stored as attributes directly but
> hash map entries in a session attribute. Well, there's a module for
> that as well. Other needs could be accomodated as well. For example,
> there is no reason that would prevent storing data in a database
> (could use OJB or Hibernate here) or write to a file.
> 
> Difference to storing data directly is, that output modules *should*
> support a weak transactional behaviour. So, when finished handing data
> to the output module, either "rollback" or "commit" should be
> called. Some modules support optionally to have some isolation and new
> values are not visible before "commit" is called.
> 
> Please do follow up if you have more questions / problems regarding
> the use of those modules.
> 
>       Chris.
> -- 
> C h r i s t i a n       H a u l
> [EMAIL PROTECTED]
>     fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to