>
> public class ClassUnitInterceptor extends DbEventInterceptorSupport2 {
> public void preInsert (InterceptorParameters iparms) {...}
> }
>
> The advantage is I can add things to InterceptorParameters
> without breaking existing code. My changes introduce
> DbEventInterceptorSupport2, so old Interceptors don't break.
>
> I plan on adding a setData(Object x) and getData() method to
> InterceptorParameters to be used to pass info between preX()
> and postX() methods. The current method of putting things in
> the session seems a little kludgey.
>
>
> I'm not sure if this is useful enough to introduce into the
> main branch of DbForms. what do you think ?
Yes it's a good idea to put this into the main trunc.
The idea of setData/getData to transport data is great.
But it's a little bit work because each time the interceptors are invoked
they are created new.
But that should be no problem
We have had this discussion sometime ago.
With the result that we should'nt break backward compatibility. And i have
had the idea how to:
Just change the interfaces. Implement the new interfaces in the default
implementation classes. There you make an tranformation between the old and
the new interfaces and call just empty procedures with the old interface.
So everybody can use it's old code - the methods will be called through
overriding.
One other point: We should dicuss ideas like this public. In the moment
there seems to be only few interested people (Luca, Shawn where are you??)
- but i think it'S worth to do this public.
Cheers,
Henner
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
