On 29 May 2009, at 00:12, Denis Forveille wrote:
Upgrading to Hibernate 3.3.1 will force to add slf4j libs and having
both sl4fj and commons-logging jars with the current version of Seam.
So if Seam is packaged with Hibernate 3.3.1, why not updating Seam
to use slf4j instead of commons-logging?
Seam doesn't use commons-logging, so I don't quite see the problem (it
uses log4j, and if not available, JUL).
You're probably thinking of richfaces or something...
I am currently using seam 2.1.2 + hibernate 3.3.1 + slf4j + log4j +
jcl-over-slf4j.jar (just for seam...) and everything works fine.
Would be cool to drop jcl-over-slf4j.jar ..
Pete Muir wrote:
> Right, we should do this update?
>
> Sanne, do you want to submit a patch to a JIRA?
>
> On 28 May 2009, at 22:38, Sanne Grinovero wrote:
>
>> Hi,
>> about library versions I'm wondering why doesn't Seam bundle the
>> latest hibernate 3.3.x ?
>>
>> I guess it was a good thing to keep the same version as JBoss AS
>> 4.2,
>> but since 5 is out these reason could be reconsidered.
>>
>> Hibernate Search 3.1.0 is available since months and has many
>> improvements over 3.0.1, but it requires an up-to-date hibernate
>> core.
>>
>> Sanne
>>
>> 2009/5/28 Dan Allen <dan.j.allen(a)gmail.com>:
>>>
>>>>
>>>>> There was also
>>>>> question, if we can upgrade the spring integration to 2.5.x
>>>>> instead of
>>>>> 2.0.x.
>>>
>>> I've been using Seam together with Spring 2.5 for a long time.
>>> There really
>>> is no conflicts...and what is nice is that you get the Spring
>>> ELResolver
>>> (instead of the VariableResolver) in your hands for tighter
>>> integration.
>>>
>>> -Dan
>>>
>>> --
>>> Dan Allen
>>> Senior Software Engineer, Red Hat | Author of Seam in Action
>>>
>>>
http://mojavelinux.com
>>>
http://mojavelinux.com/seaminaction
>>>
http://in.relation.to/Bloggers/Dan
>>>
>>> NOTE: While I make a strong effort to keep up with my email on a
>>> daily
>>> basis, personal or other work matters can sometimes keep me away
>>> from my email. If you contact me, but don't hear back for more
>>> than a week,
>>> it is very likely that I am excessively backlogged or the message
>>> was
>>> caught in the spam filters. Please don't hesitate to resend a
>>> message if
>>> you feel that it did not reach my attention.
>>>
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/seam-dev
>
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev