This is what you should use from now on.
Cheers
On Thu, Jul 19, 2018 at 9:08 PM Laurent Almeras <lalmeras(a)gmail.com> wrote:
Mistake on my side. As I configure programmaticaly Hibernate, I use
<class>.class.getName() code to populate my Hibernate properties. So I
directly stepped into a class not found error when I update.
I just modify my code to use strings provided in documentation and it
works as expected. So not sure any modification is needed in documentation
on a deprecated feature and a corner-case (use of classes in code whereas
it is not needed or advised in document) even thought this
qualified-classname-like notation may be error prone.
Sorry for the noise
Le 19/07/2018 à 10:19, Guillaume Smet a écrit :
By the way, did you have an error using the old names?
Because they should still be supported.
On Thu, Jul 19, 2018 at 10:16 AM Guillaume Smet <guillaume.smet(a)gmail.com>
wrote:
> Hi Laurent,
>
> Good catch. The classes have been moved to an internal package and we
> should now use the short names instead.
>
> Created
https://hibernate.atlassian.net/browse/HHH-12829, will fix right
> away.
>
> --
> Guillaume
>
> On Wed, Jul 18, 2018 at 11:43 PM Laurent Almeras <lalmeras(a)gmail.com>
> wrote:
>
>> Hi,
>>
>> Sorry to bother you on a deprecated feature subject, but I think the
>> package names provided in documentation are broken :
>>
>>
https://docs.jboss.org/hibernate/stable/orm/userguide/html_single/Hiberna...
>>
>> Do we agree that the correct names are
>> org.hibernate.cache.ehcache.internal.SingletonEhCacheRegionFactory and
>> org.hibernate.cache.ehcache.internal.EhCacheRegionFactory ? Not sure I'm
>> right because of the .internal package; I spontaneously understand it as
>> « private, do not touch » package.
>>
>> If I'm not wrong, I can open a Jira and propose a PR.
>>
>>
>> --
>> Laurent Almeras
>>
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>