So far so good, I _could_ live with TransactionPlugin instead of a more convoluted TransactionListener, but the problem is that the only kind of post events sent to TransactionListener/Plugin.dataStoreChange, POST_UPDATE, does not come with a "source". All other events (PRE_INSERT/UPDATE/DELETE) have the TransactionEvent.getSource() property set (and being the EObject representing the transaction element: InsertElementType, etc).
Is there a reason for pos-update events not having the source property set? I'd really really need it. Cheers, Gabriel On Aug 19, 2010, at 11:27 AM, Gabriel Roldan wrote: > I didn't implement TransactionPlugin instead because... I didn't even know > about it, believe it or not :) > > Sounds like a perfect match, thanks for the info Andrea. > > Gabriel > > On Aug 19, 2010, at 8:47 AM, Andrea Aime wrote: > >> Gabriel Roldan ha scritto: >>> Hey all, >>> I'm in the process of avoiding GWC to whip out the whole layer cache upon >>> every transaction. >>> To that end, I need to make good use of transaction events, but to make >>> _good_ use of them I'd need two things: >>> - first, currently only update transactions issue post events. Insert, >>> update and delete issue pre events. >>> - second, it'd be great that post events were always thrown. I think the >>> rationale behind not issuing post events for insert and delete is that the >>> affected features won't change. But still id't be good to have a sense of >>> whether a given transaction succeeded or failed. So a >>> reasonForFailure():Exception property in TransactionEvent would be great, >>> provided post events are always thrown, both upon success and upon failure. >>> Thoughts? may I add post events to insert and delete transactions, and >>> before throwing a service exception? >> >> As you realized the reason for post and pre events is to give the >> transaction listener a service, changing that would be a regression. >> >> If you need to know about the transaction completion status why don't >> you just implement TransactionPlugin (a TransactionListener sub-interface), >> that gives you the transaction completion hooks? >> >> Cheers >> Andrea >> >> >> -- >> Andrea Aime >> OpenGeo - http://opengeo.org >> Expert service straight from the developers. > > Gabriel Roldan > [email protected] > Expert service straight from the developers > Gabriel Roldan [email protected] Expert service straight from the developers ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
