[hibernate-dev] 3.5.0-CR-2 set up in JIRA

2010-02-16 Thread Steve Ebersole
Just wanted to point out to everyone that 3.5.0-CR-2 has been set up in JIRA ( http://opensource.atlassian.com/projects/hibernate/browse/HHH/fixforversion/11011 ) and tentatively scheduled for Feb 24 2010. I say tentatively because I am not sure I will wait that long; lets see how things go.

Re: [hibernate-dev] Message-Templates from multiple JARs

2010-02-16 Thread Gunnar Morling
I agree with Max, I think there should be some way for packaging message bundles within components containing constraint annotations, while offering the possibility to optionally override these with custom messages if required. With respect to large-scale enterprise apps, I guess it can become qui

Re: [hibernate-dev] Hibernate Search 421 [Exceptions happening in backend are unnoticed]

2010-02-16 Thread Emmanuel Bernard
Hello Amin, Have you had a chance to work on this? Emmanuel On 9 janv. 2010, at 15:59, Amin Mohammed-Coleman wrote: > Hi Sanne > > Thanks for the advice! I'll take a look at it. > > > Cheers > Amin > > On Sat, Jan 9, 2010 at 1:34 PM, Sanne Grinovero > wrote: > >> Hi Amin, >> I've been looki

Re: [hibernate-dev] Message-Templates from multiple JARs

2010-02-16 Thread Emmanuel Bernard
On 16 févr. 2010, at 09:58, Max Rydahl Andersen wrote: > > - "Emmanuel Bernard" wrote: > >> I don't see i18n as something that should necessarily be packaged >> inside a component. Resource keys are generally grouped in one or two >> files for the overall application (so that fixing a typo

Re: [hibernate-dev] Message-Templates from multiple JARs

2010-02-16 Thread Max Rydahl Andersen
- "Emmanuel Bernard" wrote: > I don't see i18n as something that should necessarily be packaged > inside a component. Resource keys are generally grouped in one or two > files for the overall application (so that fixing a typo is quick). You must be developing small or monolith applications

Re: [hibernate-dev] Message-Templates from multiple JARs

2010-02-16 Thread Emmanuel Bernard
I don't see i18n as something that should necessarily be packaged inside a component. Resource keys are generally grouped in one or two files for the overall application (so that fixing a typo is quick). If you have to dig into individual or even third party components, it becomes a pain point.