Hi Emmanuel,
On Wed, Aug 21, 2013 at 4:52 PM, Emmanuel Bernard
emman...@hibernate.org wrote:
To me the real answer is to the programmatic API and add a
programmatic mapping factory to your configuration.
See Example 4.28. Use a mapping factory in
On 21 Jan 2013, at 12:17 AM, Guillaume Smet guillaume.s...@gmail.com wrote:
Hi Sanne,
On Thu, Jun 20, 2013 at 6:45 PM, Sanne Grinovero sa...@hibernate.org wrote:
Great, so maybe we should just do that.
Yep, looks like a good idea and would be far cleaner.
+1 once we use Jandex we can
I've actually found a flaw in my suggestion: a scan of all user
provided classes might not be desirable.
For one, someone might have some unintended dependencies which happen
to include such an @AnalyzerDef, which could conflict with some
definition name being used elsewhere and this is not
On Fri, Jun 21, 2013 at 2:35 PM, Hardy Ferentschik ha...@hibernate.org wrote:
Again, I still don't see the connection between @Entity and @AnalyzerDefs.
How does you library look like and what do you want to provide. Can you
provide
an example. Does your library contain an indexed type? Are
On 21 Jan 2013, at 2:26 PM, Guillaume Smet guillaume.s...@gmail.com wrote:
On Fri, Jun 21, 2013 at 12:17 PM, Sanne Grinovero sa...@hibernate.org wrote:
Guillaume, could you clarify the use case once more? I am assuming it
was all about a cleaner code organization; in that case wouldn't it be
Hi,
We would like to declare our global @AnalyzerDefs on a class which
isn't a specific entity.
For the @TypeDefs of Hibernate, we do it by declaring the @TypeDefs on
a class annotated with @MappedSuperClass but with @AnalyzerDefs, we
are forced to declare them on a concrete @Entity.
Is this an
Hi Guillame,
reusing a @MappedSuperClass annotated entity sounds like a workaround
rather than the proper solution.
But I see your point on defining the global analyzers in a centralized
place rather than have them scattered on entities; question is if we
can do better?
There is a property to
On 20 Jan 2013, at 6:39 PM, Sanne Grinovero sa...@hibernate.org wrote:
Hardy, while moving to Jandex would it be possible - and efficient -
for us to just find all @AnalyzerDefs on the user classpath (without
these necessarily needing to be mapped entities) ?
Absolutely!
--Hardy
Great, so maybe we should just do that.
BTW, slightly unrelated, but in the same style it always bothered me
that @NamedQuery definitions need to be specified on entities.
Granted they often relate to a specific entity, but not always, and in
some cases they are better maintained close to their
On 20 Jan 2013, at 6:22 PM, Guillaume Smet guillaume.s...@gmail.com wrote:
Hi,
We would like to declare our global @AnalyzerDefs on a class which
isn't a specific entity.
For the @TypeDefs of Hibernate, we do it by declaring the @TypeDefs on
a class annotated with @MappedSuperClass but
Hi Sanne,
On Thu, Jun 20, 2013 at 6:45 PM, Sanne Grinovero sa...@hibernate.org wrote:
Great, so maybe we should just do that.
Yep, looks like a good idea and would be far cleaner.
--
Guillaume
___
hibernate-dev mailing list
11 matches
Mail list logo
