In LazyInitializationException's constructor, we do log as error the exception
and its stack trace. While not extremely common[1][2], there are cases in
Hibernate Search engine where we catch the exception and ignore it on purpose.
These ERROR level logs are scaring and polluting.
Question,
Answering my own question, Integrator integrates and disintegrates seem to be
the counterparts.
On 5 juil. 2011, at 17:30, Emmanuel Bernard wrote:
Hey,
Hibernate 3.6 had the notion of EventListeners's Initializable and
Destructible lifecycles.
What is the new way of doing it in Hibernate
Hey,
Hibernate 3.6 had the notion of EventListeners's Initializable and Destructible
lifecycles.
What is the new way of doing it in Hibernate Core 4?
I apologize of we have discussed it but my memory tells me I've no idea ;)
Emmanuel
___
hibernate-dev
http://java.net/projects/jax-rs-spec/pages/Validation
Can you guys have a look at it a give me your feedback. The JAX-RS expert group
has created this draft and looks for feedback.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
What I have done in the past is append to the title of the bug report the
contributor name in parenthesis.
eg
HHH-1234 Write new query optimization (John Doe)
On 27 juin 2011, at 10:40, Strong Liu wrote:
as an open source project, we have been getting lots of help from community,
many
Hello Tom,
If such person existed, that would be awesome :)
Here are the steps.
Most if not all operations to the datastore are hidden behind the GridDialect
interface. But there are a few steps towards complete success
1. Finish to abstract away GridDialect from Infinispan's Cache API
Could it be some thread concurrency visibility?
Since it's a concurrent hashmap, I'd venture it's accessed concurrently :)
Try and make the variable final (or volatile) to ensure proper visibility
across threads.
On 22 juin 2011, at 02:44, Scott Marlow wrote:
I'm not sure if we will see this
WorkerFactory
QueueingProcessor
Emmanuel
On 10 mai 2011, at 19:29, Emmanuel Bernard wrote:
I've started the work to split classes between API, SPI and private classes.
Some areas went very well, some are more problematic but that was to be
expected. Anyways it did generate a couple of questions
FYI I've created
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-778 to gather
this need.
On 1 juin 2011, at 12:42, Sanne Grinovero wrote:
2011/6/1 Emmanuel Bernard emman...@hibernate.org:
I dislike orm as it's too generic, we don't want to imply to support any
orm
2. Specific issues:
o org.hibernate.search.batchindexing.impl.Executors is used by
MutablefactoryTest
should we keep executors as private or should we consider it an actual API
or SPI?
I don't think exposing this as SPI is very useful to people, but at
some point in future it's
I am very pleased to announce the first public alpha of Hibernate OGM.
Hibernate OGM stands for Object Grid Mapping and its goal is to offer a
full-fledged JPA engine storing data into NoSQL stores.
Read the rest at http://goo.gl/NVkX5
___
+1 for separate sub packages
On 16 juin 2011, at 16:50, George Gastaldi wrote:
Hello !
I am working on HV-491 (Support the validation using MOD11 algorithm)
that is used on validation of several personal identification
documents (including Brazil).
I was talking with Hardy about adding
Hello Sanne and Davide.
First of all awesome job :)
I've added a few comments in the pull request, here are a couple more.
The package should be something.something.impl as it's not meant to be
published to users.
org.hibernate.search.util.logging.impl is fine by me.
We might want to adjust
FYI, my big change just made it (sorry about the delay).
On 13 mai 2011, at 16:16, Alex Snaps wrote:
On Thursday 12 May 2011 at 17:17, Emmanuel Bernard wrote:
I've significantly improved the GridDialect in my quest to use Atomic Maps
for entity and associations. Unfortunately the change
I always die a little when I see someone using HashtableCacheProvider.
What do you think of removing it entirely. Worse case, we could provide an
implementation that is backed by ConcurrentHashMap but even with that, we would
get no eviction policy etc.
On 7 juin 2011, at 21:58, Sanne Grinovero wrote:
I agree that we should not include it, but are there viable
alternatives to deploy a Seam2 application?
People would need to embed the lib in their apps.
Also given the nice classloader isolation AS7 provides, if we really
need to have it
Moving it to the hibernate-testing module seems like a good idea to me.
On 8 juin 2011, at 15:02, Steve Ebersole wrote:
The only use case I am really interested in for simple map based caching is
the test suite. Its the whole reason I did not do the things Strong and I
discussed on the
Guys I'm considering releasing the specification document as a Git repository.
I am wondering if the document should share the same Git repo as
beanvalidation-api or if these two should be kept separated. In other words, do
these share the same release / tag cycle all the time?
WDYT?
Note that
Because somehow we need people to be able to index the id of embedded objects.
And at the time, I decided that automatically indexing them was harmless.
Either we stay as is or we add a specific annotation to ask for id indexing in
embedded objects
Emmanuel
On 3 juin 2011, at 14:42, Sanne
yep that's fine. I suspect this setting will be quite useful in Hibernate OGM's
search engine though.
On 6 juin 2011, at 12:27, Sanne Grinovero wrote:
2011/6/6 Emmanuel Bernard emman...@hibernate.org:
That's a backward compatible change so it needs to be done in 4.0
That's why I'm proposing
I mean this setting being set to true (RE OGM).
On 6 juin 2011, at 12:31, Emmanuel Bernard wrote:
yep that's fine. I suspect this setting will be quite useful in Hibernate
OGM's search engine though.
On 6 juin 2011, at 12:27, Sanne Grinovero wrote:
2011/6/6 Emmanuel Bernard emman
On 6 juin 2011, at 16:41, Emmanuel Bernard wrote:
On 6 juin 2011, at 14:34, Sanne Grinovero wrote:
2011/6/6 Emmanuel Bernard emman...@hibernate.org:
I mean this setting being set to true (RE OGM).
I'm wondering how you would use that, and especially if you wouldn't
need the class type
Because
- core does not have support for injecting custom constraints on generators
today
- I find this feature useless and this has been confirmed by no real user
asking for it for the last 5 years :)
Emmanuel
On 3 juin 2011, at 18:14, Strong Liu wrote:
On 23 mai 2011, at 17:00, Sanne Grinovero wrote:
Hi Davide,
today I've downloaded the hibernate-search sources and my eclipse has
a problem importing the maven projects because the parent folder has
the same name as one of the sub-folders:
what was the problem? I personally never had
Hi guys,
I've setup @hibernate_dev on Twitter and made GitHub to push commit messages to
the account.
If you are interested in the commit messages, just follow this account.
And of course, you can follow @hibernate which is Hibernate team's twitter
account (low traffic).
, Emmanuel Bernard wrote:
I'd say I like the current approach better than using spi / internal as
top
level.
The only think I would change is rename internal to some shorter
version:
- impl
- private
- hidden
- ?
Another discussion we had on HSearch is whether or not use internal
We discussed this with Steve,
The ReflectionManager layer still uses TCCL so if for some reason it is not
properly set, then we can't find the package-info class. Another possibility is
that the lower level (Concurrent)Classloader does not support package-info.java.
Emmanuel
On 16 mai 2011, at
yes git cherry-pick will be your friend to clean the mess
On 13 mai 2011, at 16:16, Alex Snaps wrote:
On Thursday 12 May 2011 at 17:17, Emmanuel Bernard wrote:
I've significantly improved the GridDialect in my quest to use Atomic Maps
for entity and associations. Unfortunately the change
and relational (who remember that a database CAN be non
relational ?) and than Cache which seems to retrictive in my point of view.
Regards,
Niko
2011/5/12 Emmanuel Bernard emman...@hibernate.org
Let me summarize,
GridMap is the equivalent of Cache, right?
I agree that Map is not the right
Back up after I've contacted the Contegix guys.
On 12 mai 2011, at 04:46, Strong Liu wrote:
JIRA Startup Failed
You cannot access JIRA at present. Look at the table below to identify the
reasons
Description
The jira.home directory
On 11 mai 2011, at 18:46, Sanne Grinovero wrote:
Hello,
To conclude this thread, there are still three notes being discussed
on the wiki:
http://community.jboss.org/wiki/PlansforHibernateSearch4
1) assume exclusive_index_use=true as default
That was my proposal, I'm not sure we're all
In which case do you recommend people to write something like that?
Is that related to any use of Hibernate Search?
Also it seems not all methods as they are make sense, for example display
pushing to log is not likely going to be something users want in this form
necessarily.
On 11 mai 2011,
property level.
On 12 mai 2011, at 16:54, Emmanuel Bernard wrote:
In which case do you recommend people to write something like that?
Is that related to any use of Hibernate Search?
Also it seems not all methods as they are make sense, for example display
pushing to log is not likely
Let me summarize,
GridMap is the equivalent of Cache, right?
I agree that Map is not the right representation, plus
MapKey,MapString,Object is ugly. So +1 for a dedicated object.
I think we could use:
- Cache
- Database
- Bucket
Note a fan of GridMap as it won't make sense for the post
I've significantly improved the GridDialect in my quest to use Atomic Maps for
entity and associations. Unfortunately the change is not ready to be shared
yet. I hope to get that out next week Entity are using atomic maps but not
associations yet.
Also, I've see you've used merge to sync your
[1]
@AnalyzerDef(name = entityAnalyser,
tokenizer = @TokenizerDef(factory = StandardTokenizerFactory.class),
filters = { @TokenFilterDef(factory = StandardFilterFactory.class),
@TokenFilterDef(factory = LowerCaseFilterFactory.class),
I've started the work to split classes between API, SPI and private classes.
Some areas went very well, some are more problematic but that was to be
expected. Anyways it did generate a couple of questions from philosophical to
concrete. Please try and chime in.
1.
API vs SPI:
I agree with you.
Today, if you do not / forgot to specify javax.persistence.sharedCache.mode,
you're up for a long debugging ride before figuring it out.
So +1 for ENABLE_SELECTIVE.
That is the default if people use hbm.xml files + SessionFactory anyways.
Emmanuel
On 2 mai 2011, at 15:55,
While working on OGM, I found the need to override some of the default values
of some Hibernate Core settings, namely:
- TransactionFactory (defaults to JDBCTransactionFactory)
- TransactionManagerLookup (defaults to null)
What do you thing of the idea of having a DefaultValueProvider class
(gist),
but I was getting so confused, it's at least helped me to get things straight.
- Original Message -
From: Steve Ebersole st...@hibernate.org
To: Emmanuel Bernard emman...@hibernate.org
Cc: hibernate-dev@lists.jboss.org
Sent: Tuesday, April 26, 2011 11:47:12 AM
Subject: Re
On 22 avr. 2011, at 19:22, Juraci Paixao Krohling wrote:
On 04/22/2011 06:43 PM, Emmanuel Bernard wrote:
I've been working on Hibernate OGM documentation. I am still very unhappy
with what I have but that's a start.
You can read it at
http://docs.jboss.org/hibernate/ogm/3.0/reference/en
Please use the user forum http://forum.hibernate.org
This mailing list is about theHibernate projects developments.
On 26 avr. 2011, at 15:51, Faraz Fallahi wrote:
hi
im trying to create a simple one-to-one mapping in my hbm files.
For Example:
one-to-one name=account
with this metadata builder which is
more semantically correct. But this is a bit verbose for today since I can
only think of naming strategy as falling into this bucket.
On 04/22/2011 03:37 AM, Emmanuel Bernard wrote:
My preference would go to a MetadataSources#setMetadata(NamingStrategy)
My
emmanuel: hello everyone
gbadner: hi
emmanuel: have you guys started the meeting?
jpav: you just did I think
hardy: seems like it
sannegrinovero: hi emmanuel, no not yet
jpav: no one started the bot yet
emmanuel: #startmeeting
jpav: I don't think the bot is even running
emmanuel: maxandersen:
, serviceRegistry.get(
SearchFactoryImplementor.class ) );
}
(or even simpler if SessionImplementor makes it possible to retrieve
services )
Regards,
Sanne
On 04/06/2011 09:28 AM, Emmanuel Bernard wrote:
yes as is indeed better.
On 6 avr. 2011, at 13:29, Steve Ebersole wrote:
A phrase I see
have been contemplating is:
new MetadataSources( reg ).buildMetadata( new MyNamingStrategy() )
I am open to other suggestions. I really am trying to keep in mind the scope
in which stuff is needed/useful/valid.
On 04/21/2011 03:11 AM, Emmanuel Bernard wrote:
On 21 avr. 2011, at 05
Hi all
I've been working on Hibernate OGM documentation. I am still very unhappy with
what I have but that's a start.
You can read it at
http://docs.jboss.org/hibernate/ogm/3.0/reference/en-US/html_single/
You can contribute to it by forking on github
https://github.com/hibernate/hibernate-ogm
insert the
proposals which survived in the wiki JIRA.
(needles to say, no objections on your proposals)
Cheers,
Sanne
2011/4/20 Emmanuel Bernard emman...@hibernate.org:
Hi,
We have had in our road map an Hibernate Search 3.5 before Hibernate 4.
Hibernate 4 is the release where
I don't have any strong opinion.
I'd be tempted to say you are right. It seems to be somebody expecting a non
indexable path would not be hurt if the Path structure returned an indexable
version. Can you also create a BVAL issue so that the spec gets clarified.
On 21 avr. 2011, at 00:11, Gunnar
On 21 avr. 2011, at 05:43, Steve Ebersole wrote:
I think this new API for creating a SessionFactory is starting to firm
up, so I wanted to put out another call for feedback before we get too
close to Alpha3. So at a high level there are 2 pieces of information
needed to build the
Hi,
We have had in our road map an Hibernate Search 3.5 before Hibernate 4.
Hibernate 4 is the release where the following should happen:
- split packages into API, SPI and private packages
- use JBoss Logging
- be compliant with Core 4
- break whatever contract we need to break to open up
For info, I've made public the page describing the log recommendations for
JBoss projects
http://community.jboss.org/wiki/HowtologinJBossprojects
It seems that the FATAL-INFO level with named categories and class based
categories for DEBUG-TRACE fits nicely.
Note that i18n debug and trace
We are pleased to announce our latest baby: Hibernate Search 3.4.
The big new feature is faceting: this is what you see on Amazon when you do a
query and they propose the matching list of brands, price range etc.
The other big trend is performance improvement thanks to our users / customers
Surely they are serializable in XML ;)
(Sorry, could not resist)
On 13 avr. 2011, at 00:44, Steve Ebersole wrote:
Hm, if we move to jaxb are those generated binding classes serializable?
On 04/12/2011 02:41 PM, Hardy Ferentschik wrote:
On Apr 12, 2011, at 21:26, Steve
In preparation for landing, I've moved Hibernate OGM's repository to the
Hibernate organization ie from https://github.com/emmanuelbernard/hibernate-ogm
to https://github.com/hibernate/hibernate-ogm . Sanne and I have push access.
I've also created a forum
https://gist.github.com/903302#file_1_method_configuration.java
seems the one that makes most sense by far to me. The other options tend to
make method a super concept that is not symmetric with .property()
What does
//this version doesn't break the compatibility
means on other versions?
On 8 avr. 2011, at 11:09, Hardy Ferentschik wrote:
On Fri, 08 Apr 2011 10:47:37 +0200, Emmanuel Bernard emman...@hibernate.org
wrote:
What does
//this version doesn't break the compatibility
means on other versions?
I also prefer https://gist.github.com/903302
Make sure you write a client of this API, I suspect Class?... parameterTypes
might not be what you want.
On 8 avr. 2011, at 13:41, Kevin Pollet wrote:
On vendredi 8 avril 2011 at 13:13, Gunnar Morling wrote:
Hi,
I also like https://gist.github.com/903302#file_1_method_configuration.java
On 8 avr. 2011, at 17:16, Kevin Pollet wrote:
On vendredi 8 avril 2011 at 15:54, Emmanuel Bernard wrote:
Make sure you write a client of this API, I suspect Class?...
parameterTypes might not be what you want.
On 8 avr. 2011, at 13:41, Kevin Pollet wrote:
What do you mean ?
Have you
yes as is indeed better.
On 6 avr. 2011, at 13:29, Steve Ebersole wrote:
A phrase I see a lot here is as:
session.as( AuditReader.class ).someEnversSpecificMethod()
or
session.as( FullTextSession.class )...
On 04/06/2011 06:26 AM, Adam Warski wrote:
On Apr 6, 2011, at 1:20 PM,
In JPA and other Java specs, there is a pattern emerging where one could unwrap
some objects from a common API
interface EntityManager {
T unwrap(ClassT type);
}
We typically let a Session be extracted from an EntityManager
Session session = entityManager.unwrap(Session.class);
I wonder if
+1 but you've realized that you've volunteered yourself.
On 4 avr. 2011, at 00:08, Sanne Grinovero wrote:
Hello,
I'm sure you all have heard all the noise about the Lucene 3.1
release, it has indeed some interesting changes [1]; it's almost
drop-in compatible with Lucene 3.0.x but providing
What's you actual use case. This explicit separation is something I've always
appreciated to limit clever package-level visibility usages.
Let's discuss tomorrow on IRC
.
On 4 avr. 2011, at 21:43, Sanne Grinovero wrote:
Hi,
it's sometimes useful from the test packages to be able to get
For info, I like #2 the best
ConnectionOptions can deal in the future with:
- schema based diff
- user based diff ala Oracle VPD
interface ConnectionOptions {
TenantType getTenantType();
String getDefaultSchema();
String getUser() //is that how VPD filters out?
..some more
HEM uses them. As @Entity are EJBs, they do need to do some authorization
checks.That's unfortunately more a legacy from EJB 2 than anything else.
On 18 mars 2011, at 20:08, Steve Ebersole wrote:
Is anyone using or aware of uses of the JACC stuff in org.hibernate.secure?
I'd like to remove
:
VPD is really the same notion as a tenant. So the ConnectionProvider having
access to the tenant already solves that
On Tuesday, March 29, 2011, at 10:31 am, Emmanuel Bernard wrote:
For info, I like #2 the best
ConnectionOptions can deal in the future with:
- schema based diff
- user
info.
Emmanuel
On 29 mars 2011, at 18:30, Steve Ebersole wrote:
The connection provider is different yes. The information needed is the same.
For VPD you issues an ALTER SESSION command on the connection to tell it the
tenant
On Tuesday, March 29, 2011, at 11:22 am, Emmanuel Bernard
+1 to move all the remaining projects to the new scheme.
Commons annotations cannot be ingested by core. It's a HSearch dependency and
HSearch is moving towards no runtime dependency on Core.
On 19 mars 2011, at 18:43, Steve Ebersole wrote:
I moved Core, Java Persistence API and Metamodel
On 27 mars 2011, at 19:36, Scott Marlow wrote:
We just discussed Hibernate 4.0 annotation scanning the other day and I
wanted to add to the conversation (which was about using
https://github.com/jbossas/jandex).
As a workaround for https://issues.jboss.org/browse/JBAS-9141, I'll
On 28 mars 2011, at 14:32, Scott Marlow wrote:
Another point to consider is that the
org.hibernate.ejb.packaging.Scanner is not covering all Hibernate
integration points, but only the AS JPA integration (as far as I
currently understand it).
AFAIK that's the only area where where we need
On 28 mars 2011, at 15:35, Scott Marlow wrote:
On 03/28/2011 09:04 AM, Emmanuel Bernard wrote:
On 27 mars 2011, at 19:36, Scott Marlow wrote:
We just discussed Hibernate 4.0 annotation scanning the other day and I
wanted to add to the conversation (which was about using
https
On 28 mars 2011, at 16:23, Emmanuel Bernard wrote:
On 28 mars 2011, at 15:35, Scott Marlow wrote:
On 03/28/2011 09:04 AM, Emmanuel Bernard wrote:
On 27 mars 2011, at 19:36, Scott Marlow wrote:
We just discussed Hibernate 4.0 annotation scanning the other day and I
wanted to add
I'd say I like the current approach better than using spi / internal as top
level.
The only think I would change is rename internal to some shorter version:
- impl
- private
- hidden
- ?
Another discussion we had on HSearch is whether or not use internal on the
package name that is always
No more nasty @Persister annotations on your entities, they now look like plain
old ones.
When using JPA and as long as you use a TransactionManager (ie JTA support),
the configuration is very simple
persistence xmlns=http://java.sun.com/xml/ns/persistence;
And I've added a small page on how to set up JBoss TransactionManager in
standalone
http://community.jboss.org/wiki/HowtouseJBossJTAstandaloneTransactionManager
On 18 mars 2011, at 16:39, Emmanuel Bernard wrote:
No more nasty @Persister annotations on your entities, they now look like
plain
we can come up with more, let's see if it's worth the
complexity and other problems. I'd propose it for version 4, a nice
breaking change :)
Cheers,
Sanne
2011/3/15 Emmanuel Bernard emman...@hibernate.org:
On 15 mars 2011, at 18:24, Emmanuel Bernard wrote:
On 15 mars 2011
On 15 mars 2011, at 16:43, Sanne Grinovero wrote:
I guess we should prevent the indexing of ids in secondary elements?
If the associated element is an entity, it's perfectly valid to index its id
and query by it
//return all books when the author's id is 2
author.id:2
On 15 mars 2011, at 18:24, Emmanuel Bernard wrote:
On 15 mars 2011, at 16:43, Sanne Grinovero wrote:
I guess we should prevent the indexing of ids in secondary elements?
If the associated element is an entity, it's perfectly valid to index its id
and query by it
//return all books
On 14 mars 2011, at 11:46, Sanne Grinovero wrote:
What you are loosing by query.getFacets( facetName ) is the ability to
iterate over the
enabled facets. At the very least you have to take care yourself of which
facet names are set.
In intermediate step would be to get rid of
On 14 mars 2011, at 12:03, Emmanuel Bernard wrote:
On 14 mars 2011, at 11:46, Sanne Grinovero wrote:
What you are loosing by query.getFacets( facetName ) is the ability to
iterate over the
enabled facets. At the very least you have to take care yourself of which
facet names are set
As you guys know I've not been comfortable with the idea of reusing Filter as
an implementation as it seem to be it is an implementation detail that we might
change down the road and that is of no interest to the user.
Instead of bitching abstractly, I've decided to implement a CDI style bean
)
.createFacetRequest();
Same for range, which might be even more useful.
BTW what's the facet.value() for a range facet?
On 14 mars 2011, at 15:29, Emmanuel Bernard wrote:
As you guys know I've not been comfortable with the idea of reusing Filter as
an implementation as it seem
On 14 mars 2011, at 16:33, Hardy Ferentschik wrote:
- move Facet methods hosted on FTQuery to a FacetManager interface and do
ftQuery.getFacetManager().enableFacet(cdscds);
no sure about this one. What other benefits does this approach have except
the reuse for the JPA query?
My concerns
On 14 mars 2011, at 16:33, Hardy Ferentschik wrote:
On Mon, 14 Mar 2011 15:43:20 +0100, Emmanuel Bernard emman...@hibernate.org
wrote:
Note that another benefit of option 2 is that we can down the road (post
3.4) implement a way to pre-select which facet element is enabled (say you
an exception.
On 11 mars 2011, at 12:42, Sanne Grinovero wrote:
ah, that looks impressively similar to this post I just answered last night:
https://forum.hibernate.org/viewtopic.php?f=1t=1009976
I actually planned to ask you about it.
2011/3/11 Emmanuel Bernard emman...@hibernate.org
We (as in not me for once) are having a bad experience with massive amounts of
merge conflicts. Git is great but there is only so much magic can get you at.
We were discussing how to limit these kind of bad experiences in IRC and I've
added a few more advices I could think of.
Try to separate
Hi guys,
I have finished the migration of Hibernate OGM to its new separated Git
repository. I've kept the history (that was fun).
The new home is now here https://github.com/emmanuelbernard/hibernate-ogm
This is a multi module project with a single module so far: hibernate-ogm-core.
But we
1. I think I'm fine with that. I never really trusted Hibernate to properly
implement this anyways :)
2. is there a isStarted() method or something equivalent for someone to guard
against subsequent begin calls?
3. I am neutral. I tend to like b for it's simplicity but a would not bother me
It seems that the engine package content is entirely related to query and
should move somewhere under o.h.search.query.
Any opinion or objection? Most are non API non SPI classes anyways.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
Which part specifically?
I can't really finish HSEARCH-687 without it.
On 2 mars 2011, at 23:24, Sanne Grinovero wrote:
fine for me, but we could postpone such a change?
I believe both Hardy and me have many pending changes to integrate in
the same area.
2011/3/2 Emmanuel Bernard emman
I am thinking about moving:
EntityInfo
AbstractLoader
DocumentExtractor
Loader
LoaderHelper
MultiClassesQueryLoader
ObjectLoaderHelper
ProjectionLoader
QueryLoader
On 2 mars 2011, at 23:19, Emmanuel Bernard wrote:
It seems that the engine package content is entirely related to query
of the SessionFactoryImplementor contracts.
On 2 mars 2011, at 23:40, Sanne Grinovero wrote:
ok, you don't have conflicts with Hardy either:
https://github.com/hibernate/hibernate-search/pull/50/files
2011/3/2 Emmanuel Bernard emman...@hibernate.org:
I am thinking about moving:
EntityInfo
Hi Hardy,
Nice job.
Here are a few comments in random order:
To avoid the problem of Constructor multiplications and still use immutable
objects use a builder to collect the information and create the object out of
it. The constructor can even be package private
My initial reaction was that
Awesome feedback :)
Let's make sure we can support these sue cases in the API or know how to extend
the API to cover them in the future. Once we are safe here we can iterate over
the underlying implementation.
On 28 févr. 2011, at 19:56, Marc Schipperheyn wrote:
My two cents:
* Most of the
Looks fine to me. I was concerned about passing Method around as well.
On 1 mars 2011, at 00:29, Gunnar Morling wrote:
Hi,
I pretty much finished the implementation of the meta data API related to
method level constraints for Hibernate Validator (see
On 23 févr. 2011, at 23:37, Sanne Grinovero wrote:
I'm not a big fan for this feature, so for the moment I ported all the
rest and all tests are green by just
returning a non-lazy iterator:
https://github.com/Sanne/infinispan/tree/ISPN-952
Options:
- drop the feature
- expose a
It kinda like the declarative aspect of it though there are a lot of nasty
strings all around :). The rest is not really new so all old school issues
apply.
As usual for higher level caching you need to manually handle data eviction
which is likely be a source of bugs.
They also don't say if
On 23 févr. 2011, at 18:13, Sanne Grinovero wrote:
I've been trying to port current work in progress as dependency of
Infinispan Query,
I'm wishing for these changes:
1) TimeoutManager should throw specific exceptions directly, depending
on the framework being used
(see the pull request
That's the expected behavior.
A seems reasonable to me. Abstract it behind HibernateHelper calls.
On Feb 22, 2011, at 5:08 PM, Sanne Grinovero wrote:
Hi all,
I'm needing some advice about HSEARCH-689 - MassIndexer throwing
LazyInitializationException on associated collections.
MassIndexer
On Feb 19, 2011, at 1:41 AM, Sanne Grinovero wrote:
great, thank you. Pulled this so I can have a look tomorrow, when I'll
have 10h train.
Are you only looking for feedback, or do you think something should be
merged already?
This will probably be merged within a week or two.
What is
801 - 900 of 1482 matches
Mail list logo
