Upayavira wrote: > > 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? > I haven't thought about it yet and have not too much knowledge of the flow stuff, but however it will be implemented the contract of the existing interfaces cannot be changed, so for example we cannot change the Request interface etc.
Now (without thinking about performance etc) I guess writing wrappers is one way to go, so you could write a FOMRequestWrapper that only provides the allowed methods. This wrapper forwards everything to the Request object that does the real work. Carsten
