cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Upayavira" ...@upaya.co.uk>
Subject Finishing FOM (was RE: Release Plan for 2.1)
Date Fri, 13 Jun 2003 13:20:09 GMT
> > > AFAIK, the only real thing missing for 2.1 is the FOM
> > > implementation. The question is now, is someone already working on
> > > it resp. should we wait for the release until it's finished?
> > 
> > What is actually required to fix the FOM implementation? Is it just
> > refactoring some of the main Cocoon classes to follow the FOM? If it
> > isn't too hard, I might try to find time for some of it.
> >  
> I think its refactoring and adding some functionality. As a starting
> point you can look at this thread:
> http://marc.theaimsgroup.com/?t=105401789500001&r=1&w=2

I remember reading that. What I wanted to know is exactly how one would go about 
updating the FOM. 

If all it requires is refactoring some of Cocoon's classes, e.g. 
o.a.c.environment.http.HttpCookie (the one I've just used), then that's not so hard. 
But how about when we need to restrict access to a method in the FOM that we want 
to be accessible in the class otherwise?

Has anyone worked out how this might be done?

Upayavira

Mime
View raw message