On Thu 2014-02-06 21:52, Hardy Ferentschik wrote:
>
> On 6 Jan 2014, at 15:10, Steve Ebersole wrote:
>
> > On Thu, Feb 6, 2014 at 6:46 AM, Emmanuel Bernard
> > wrote:
> >
> > Configuration.getreflectionManager (optional)
> >>
> >
> > We do not use commons-annotations anymore at all (yaay!).
On 6 Jan 2014, at 15:10, Steve Ebersole wrote:
> On Thu, Feb 6, 2014 at 6:46 AM, Emmanuel Bernard
> wrote:
>
> Configuration.getreflectionManager (optional)
>>
>
> We do not use commons-annotations anymore at all (yaay!). If you need
> access to this type of functionality, I have been think
On 06 Feb 2014, at 15:10, Steve Ebersole wrote:
>
> On Thu, Feb 6, 2014 at 6:46 AM, Emmanuel Bernard
> wrote:
>
> Configuration.getreflectionManager (optional)
>
> We do not use commons-annotations anymore at all (yaay!). If you need access
> to this type of functionality, I have been thi
On 06 Feb 2014, at 14:52, Steve Ebersole wrote:
>
> On Thu, Feb 6, 2014 at 7:01 AM, Emmanuel Bernard
> wrote:
> For OGM the impact is less but in
> Integrator.integrate
> we use Configuration to be able to conditionally add a naming strategy
> configuration.setNamingStrategy().
> See this ac
With HHH-8893[1] I am working on building the unified XSD for mapping
information. I have mentioned this a few times. HHH-8894[2] is related to
this.
Part of HHH-8894 is this idea to handle legacy hbm.xml documents as if they
were defined using this new XSD. Initially I had planned on using XSL
On Thu, Feb 6, 2014 at 6:46 AM, Emmanuel Bernard wrote:
Configuration.getreflectionManager (optional)
>
We do not use commons-annotations anymore at all (yaay!). If you need
access to this type of functionality, I have been thinking about passing
along access to the Jandex index we use.
> The
On Thu, Feb 6, 2014 at 7:01 AM, Emmanuel Bernard wrote:
> For OGM the impact is less but in
> Integrator.integrate
> we use Configuration to be able to conditionally add a naming strategy
> configuration.setNamingStrategy().
>
See this actually illustrates the problems with Configuration, so thank
For OGM the impact is less but in
Integrator.integrate
we use Configuration to be able to conditionally add a naming strategy
configuration.setNamingStrategy().
Not sure what to do here either in the
ntegrate(MetadataImplementor, SessionFactoryImplementor,
SessionFactoryServiceRegistry)
case.
I have looked at Search and identified the elements that use
Configuration and it's access to mapping.
During bootstrap via an Integrator, we use
Configuration.getProperties()
Configuration.getreflectionManager (optional)
cfg.getClassMappings()
The properties are used to bootstrap Hibernate Sear
