Re: [Exist-development] Need Guidance :: Change to xmldb:remove()

[Adam R. <ad...@ex...>]

Erm, Are you sure that is the case?

XMLDB module functions should call the xmldb either local or remote
implementation, but at some point that code has to enter into the
internal API which is where the trigger should be effected from?

On 12 May 2011 22:41, Patrick Bosek <pat...@jo...> wrote:
> Hello dev team,
>
> I'm making good progress on my upgrade to the triggers in eXist, but I've
> hit a bump and need some guidance. I've found that xmldb:remove uses
> "org.xmldb.api.base.Collection" to remove the resource, there by never
> hitting the trigger code. So, after looking through it I figured I'd change
> the xmldb:remove to use the remove functions in
> org.exist.collections.Collection. Is this ok? Or is there another method you
> would prefer I use?
>
>
> Cheers,
>
> --
> Patrick Bosek
> Jorsek Software
> Cell (585) 820 9634
> Office (585) 239 6060
> Jorsek.com
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb