On 1 Jan 2014, at 16:36, Emmanuel Bernard <emman...@hibernate.org> wrote:
> ## Handling duplicates > > I had in mind the following logic. > > Prevent custom bridge providers to offer bridges in the same situation. What do you mean with "in the same situation”? You mean there cannot be two bridge providers for the same return type (assuming no dedicated bridge annotation) > That would be an error at start up time as the alternative of picking up one > of them does not seem very attractive. How do you determine bridge providers providing bridges for the “same situation”? > Sanne questioned the idea of built-in bridge and would rather have all > bridges handled equally and not allow duplication. > It seems that the current set of bridges cannot support that approach. When I > developed the code, I realised that there is an ordering to respect. If I put > the TikeBridgeProvider logic before the date and calendar bridgeProviders, > then the DSLTest fails. I could not find why but it shows that we have some > interdependencies at the moment. I think it would be a good idea to fine out what’s going on first. —Hardy _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
