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? Cheers, Gabriel ------------------------------------------------------------------------------ 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
