> I would suggest using an aggregator and avoiding the document() function within > Cocoon. Cocoon will not know that you have referred to an external document, and > thus will not take this into account when deciding whether to serve a cached page or > not. Thus your employeeNames.xml file might change, but Cocoon wouldn't notice, > and thus would serve the cached version - not good. Therefore, the advice is avoid > document() and use an aggregator.
We're thinking that you're a god (lol), because you're just telling us the problem we just had discovered, so we're thinking that you're a mindreader.... :) kidding :) Actually, we we're empty the temporary internet files everytime we wanted to check if he was merging the files lolol But incredibly it is really working :) So, we're thinking that in the end, cocoon isn't to bad as we thought... We'll change to the aggregate function, as you said. Thanks once again Joao Cesar [EMAIL PROTECTED] Computer Science Student's @ University of Lisboa, PORTUGAL --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
