4 Replies Latest reply on Sep 27, 2008 4:01 AM by Adam Warski

    Handling of custom UserTypes

    MÃ¥ns af Klercker Newbie


      We are currently evaluating using Envers in our app, and it's looking pretty good so far. One problem is that we use a custom UserType. It's pretty simple (it maps the type to a string and stores state as XML), so it should *really* be no problem to version a property of this type. There are of course also alternative ways to implement the mapping, so everything is not lost anyway.

      What are the issues with supporting custom UserTypes, and could there be ways of going around the current limitation at least for simpler implementations of UserType? We've noticed that Envers already supports two custom types, so there are obviously gray areas where perhaps we could contribute?