cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: Monitor.timestamp() could be non-private??
Date Wed, 10 May 2000 17:35:00 GMT
> Graeme Rimmer wrote:
> 
> I've only been using Cocoon for a couple of days and am trying to
> write my own Producer based on a resource which is neither a File nor
> a URI.
> 
> I was hoping to use the Monitor class to work out if the Document has
> been updated.  Looking at the source code for it, it appears that I
> would only have to override timestamp() to return a meaningful
> timestamp for my resource and the rest would do everything I need.
> 
> Unfortunately, timestamp() is private so I can't subclass Monitor in
> the way I'd want.  Is there a reason I am unaware of that timestamp()
> was made private??
> 
> My apologies if this should have gone to the users forum, given that I
> tracked down what I wanted to do in the source code, I guessed this
> was the most appropriate forum for it.
> 
> Graeme

Probably I didn't think it was useful outside Cocoon internals... but if
you believe so, I don't have problems in making it public.

Anyone else?

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------



Mime
View raw message