On 1 Jan 2013, at 8:46 AM, Emmanuel Bernard wrote:
> Of course my memory might be flawed but the problems I recall around
> isolating a piece of code for hv, search and later bean validation from core
> did not involve unused imports. Come to think of it, I have never seen an
> *unused* impor
On 1 Jan 2013, at 10:58 AM, Sanne Grinovero wrote:
> Let's relax this, the likelyhood of this introducing a real problem
> affecting the runtime is extremely low, and there are better ways to
> prevent that. I've reopened the issue.
Why? The few occasions where it happens a fully qualified clas
All the saucy details on in.relation.to - http://in.relation.to/24330.lace
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On 2 Jan 2013, at 9:17 PM, Guillaume Smet wrote:
> The SearchFactory.getIndexedTypes API looks nice.
Great.
> Would it be possible to also expose something like getRootIndexedTypes
> based on the magic done in MassIndexerImpl.toRootEntities?
TBH i am not completely sure I understand what the
On 5 Jan 2013, at 3:44 PM, Guillaume Smet wrote:
> (Hardy, sorry for the double post, forgot the list)
>
> On Mon, Aug 5, 2013 at 3:20 PM, Hardy Ferentschik wrote:
>> TBH i am not completely sure I understand what the method does. The docs
>> says:
>>
>> &
On 5 Jan 2013, at 4:02 PM, Guillaume Smet wrote:
> It's been a long time since the last release of JPA modelgen and we
> fixed a couple of annoying bugs, namely:
> https://hibernate.atlassian.net/browse/METAGEN-81
> https://hibernate.atlassian.net/browse/METAGEN-82
+1 We really need to get a re
On 5 Jan 2013, at 5:31 PM, Gunnar Morling wrote:
> I think I could help with doing with the release, if you, Hardy, don't get to
> it (assuming it's a common Maven release process as e.g. in HV).
Awesome. Let's sync tomorrow.
> Btw. there seems to be an issue with one failing test on master a
On 6 Jan 2013, at 6:09 PM, Guillaume Smet wrote:
> I took a look at the current 1.3.0 roadmap:
> https://hibernate.atlassian.net/browse/METAGEN-89?jql=project%20%3D%20METAGEN%20AND%20fixVersion%20%3D%20%221.3.0.Final%22%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
Awesome. I moved
The second release today of the Hibernate team. Details as usual on
in.relation.to - http://in.relation.to/24338.lace
--Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On 9 Jan 2013, at 5:49 PM, Guillaume Smet wrote:
> AFAICS in the pom.xml, Search is now compiled for Java 6.
>
> I think It would be a good idea to add the @Override annotation to the
> methods implemented from an interface, considering it's supported in
> Java 6.
+1
--Hardy
I am all for cleaning up. Aside the things discussed here I would like to
follow up on HSEARCH-933.
The database profiles defined in the parent pom have imo no business there.
They just create unnecessary noise.
Initially I thought we could use a separate settings.xml, but I think you
cannot ad
> Another use case may be Optional from JDK 8:
>
> @Size(min = 5)
> Optional name;
Is another upcoming change not "type annotations" which would allow
Optional<@Size(min = 5) String>? That would of course be the preferable
solution.
--hardy
On 3 Jan 2013, at 4:10 PM, Emmanuel Bernard wrote:
> Something like c makes sense.
> It similar to the notion of converter in JPA.
>
> But why not the following style of interfaces
>
>interface Convert {
>To convert(From);
>}
Going back to Emmanuel mentioning @Convert. I am
Right, maven release plugin. I guess the build could need some love, but as I
keep saying we would be better off phasing out its use.
--Hardy
On 4 Jan 2013, at 11:08 PM, Brett Meyer wrote:
> Last time I did it, I believe that was true -- Maven release plugin only.
>
> Although, I thought you
Interesting idea. We should at least have a Jira issue for that. Do you think
about some DSL support for that?
--Hardy
On 26 Jan 2013, at 5:26 PM, Emmanuel Bernard wrote:
> The elasticsearch guys have done something quite smart
>
> http://www.elasticsearch.org/blog/stop-stopping-stop-words-a-
On 11 Jan 2013, at 5:14 PM, Sanne Grinovero wrote:
> Some other projects use Hibernate Search - specifically the engine
> module - to bridge their domain model to a Lucene index and take
> advantage of its high performance low-level integration with Lucene.
> This is generally achieved by indexi
Seems to me like a very specific use case. I guess we could offer a contract as
you suggest, but it is not
high on my priority list. Worth creating a Jira issue for though.
--Hardy
On 19 Jan 2013, at 9:05 AM, Gunnar Morling wrote:
> Hi,
>
> On SO [1], a user asked whether it's possible to r
On 19 Jan 2013, at 9:44 AM, Emmanuel Bernard wrote:
> It seems that what this user really needs is a way to convert the
> Set into another format entirely, JSON in this case. I
> wonder if we could find a more generic approach than just the ability to
> change properties names.
Well, there
Here are my 0.02$ which need to be taken with a grain of salt since I am not so
familiar with the
procedure call stuff.
On 17 Jan 2013, at 6:15 PM, Steve Ebersole wrote:
> In my opinion, ideally the JPA spec would have defined a separate method
> to register a "function return". Luckily since
On 19 Jan 2013, at 3:46 PM, Steve Ebersole wrote:
> The trouble is that hints are valid on StoredProcedureQuery whether named or
> not. If we go the route of using hints for annotations, doesn't it make
> sense to be consistent and use that when building a StoredProcedureQuery too?
For me a
On 19 Jan 2013, at 5:15 PM, Sanne Grinovero wrote:
> Discussing about some hibernate-search-engine complexities with Hardy
> on IRC, we came to the agreement that the way @Similarity behaves
> today was a mistake, so we're proposing to deprecate it in 4.4.
>
> Reasoning follows.
>
> There is a
Hi,
I am currently working on HSEARCH-471 [1] - dynamic sharding. The work is built
on Emmanuel's prototype and you find the current code on my fork [2].
Right now I am wondering about how to configure (dynamic) sharding. Here is how
things worked prior to dynamic sharding. Basically there two
Hi,
here comes a follow up on my previous email regarding configuration of dynamic
sharding.
Now I would like to get some feedback on ShardIdentifierProvider. This
interface was added for dynamic sharding on
top of DynamicShardingStrategy. Gunnar and I had a discussion around it today
[1] and
On 23 Jan 2013, at 1:55 PM, Sanne Grinovero wrote:
>> Or I set a custom sharding strategy which does not care about the number of
>> shards?
>
> I think that's far fetched. The NBR_OF_SHARDS option defines the size
> of the array of indexes passed to the IndexShardingStrategy so it's
> hard to
On 24 Jan 2013, at 12:04 AM, Sanne Grinovero wrote:
> Correct me if I'm wrong, but trying to synthesize this discussion I
> think that we're fundamentally agreeing that dynamic sharding is a
> "better replacement" for static sharding.
It has the potential for a replacement I think, but I don't
On 24 Jan 2013, at 12:54 PM, Sanne Grinovero wrote:
>> We should for sure try to keep API's stable. On the other hand I don't see
>> why we should not be
>> able to change SPI contracts. With this super restrictive behaviour we are
>> seriously limiting
>> our ability to move the software forw
Cool, we seem to agree on almost everything now :-)
On 24 Jan 2013, at 2:30 PM, Sanne Grinovero wrote:
>> 5) rename 'getShardIdentifier' to 'getShardIdentifierForAddition'
>
> Is that needed? I thought that by removing the conflicting method
> there would be no further need to clarify the metho
On 24 Jan 2013, at 3:16 PM, Sanne Grinovero wrote:
> On 24 September 2013 13:46, Hardy Ferentschik wrote:
>> Cool, we seem to agree on almost everything now :-)
>
> +1 it's hard to get convergence when the thread explodes exponentially
> on several different subjects bu
Same here. I have no problems importing ORM into IntelliJ. But I still use the
'gradle idea' task. Is this what's failing for you as well?
--hardy
On 24 Sep 2013, at 19:29, Steve Ebersole wrote:
> Why/how? I do this routinely.
>
> On 09/24/2013 12:26 PM, Emmanuel Bernard wrote:
>> I am sti
On 24 Jan 2013, at 8:31 PM, Sanne Grinovero wrote:
> You might wonder why I like to wipe clean my workspaces?
> On projects I read mostly I tend to need to jump to different
> branches, often far in time, in which the source code organization is
> likely different, so I'd need to re-import proj
On 30 Jan 2013, at 11:00 PM, Sanne Grinovero wrote:
> I'm having a half-baked solution for HSEARCH-1270, and it looks like I
> can't do better than that without waiting for HHH-8577 to be included
> in ORM [JIRA links at the bottom].
Can you make a use case example. Clearing the queue makes onl
On 1 Jan 2013, at 8:09 PM, Sanne Grinovero wrote:
> On 1 October 2013 15:41, Hardy Ferentschik wrote:
>>
>> On 30 Jan 2013, at 11:00 PM, Sanne Grinovero wrote:
>>
>>> I'm having a half-baked solution for HSEARCH-1270, and it looks like I
>>> can&#
On 2 Jan 2013, at 2:46 PM, Emmanuel Bernard wrote:
> But then the JSON binding technology should be responsible for the
> property anme conversion too, right? After all that is the layer that
> does this change.
That would be my initially gut feeling as well.
--Hardy
_
On 2 Jan 2013, at 3:06 PM, Emmanuel Bernard wrote:
> Turning the problem upside down, I wonder if IndexShardingStrategy
> should be deprecated and have SharIdentifierProvider as the API a user
> would implement. It makes for simpler things. What would we lose feature
> wise?
That is exactly wha
On 7 Jan 2013, at 12:06 PM, Gunnar Morling wrote:
> It adds a bit to the
> index size, but I guess it's the safer/simpler option for the time being.
The index size difference is imo in this case negligible. I would not have been
comfortable with the
required changes in Search in case we had to
On 7 Jan 2013, at 5:03 PM, Sanne Grinovero wrote:
> I've tried hard to find an agreement on this, but it seems we're
> wasting time without making progress.
> I'm not happy in ignoring a strong recommendation from any of you,
> very hard choice :-(
In the end it is your call. I tried to give ar
On 8 Jan 2013, at 10:08 AM, Gunnar Morling wrote:
> I'm not sure whether it has been considered before, but maybe we could unify
> the methods and work with a parameter object as a middle ground:
It has been. I suggested before to combine the methods. I think it is a good
approach, but Sanne
On 8 Jan 2013, at 11:56 AM, Sanne Grinovero wrote:
> Having said that, let's try to find the best proposal possible by
> lunch time, as one of the approaches needs to be merged:
I think we very well could go w/ the current state right now and evolve in
future versions.
I would like to explore
On 8 Jan 2013, at 1:38 PM, Sanne Grinovero wrote:
> Guys let's put this into perspective.
> These arguments I'm hearing against adding a method in a power-user
> oriented SPI are way outbalancing the harm they do to the project in
> terms of release delays and our very own time, there are defini
On 9 Jan 2013, at 4:20 PM, Steve Ebersole wrote:
> OGM itself is new, but at the end of the day its a JPA provider which is
> not new. Basing on Java 7 will limit adaption from folks wanting to
> drop OGM in to their app as replacement for their JPA provider to give
> it a spin in certain en
On 13 Jan 2013, at 12:41 AM, Sanne Grinovero wrote:
> I'm working to replace the integration tests using the now outdated
> EAP Alphas with WildFly 8.0.0.Beta1, which also has the benefit to
> remove the need for the enterprise repository.
+100
> Java7 is needed as the Arquillian connectors fo
On 14 Jan 2013, at 3:16 PM, Gunnar Morling wrote:
> Actually I thought what you describe would already be the case.
Same here, I thought that it would be the case already.
--Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https:/
Good idea. I would like to get involved. Already collected some Forge
experience (unfortunately it was not a pleasant one).
Let's talk on the team meeting.
--Hardy
On 24 Jan 2013, at 12:24 PM, Emmanuel Bernard wrote:
> We probably should think about what it would mean to help people get
> star
Hi,
I pushed a branch [1] to my local ORM repo which integrates the metamodelgen
sources into ORM as per HHH-8483 [2].
The sources are under tooling/metamodel-generator and the commit history is
kept. I did, however, squash several commits.
This includes in particular the commits from the maven
On 25 Jan 2013, at 6:16 PM, Steve Ebersole wrote:
>
> On Oct 25, 2013 10:26 AM, "Hardy Ferentschik" wrote:
>
> > * What should be the next version of the annotation processor? I guess it
> > could just use the main ORM version, so
> > we would make a v
On 25 okt 2013, at 22:54, Gunnar Morling wrote:
> When importing the ORM Gradle project into IntelliJ or Eclipse, I'm getting
> the following error:
Importing how? Did you create the IDE project files via 'gradle eclipse' resp.
'gradle idea' or are you any sorts of plugins.
Not sure about Ec
Agreed, we need to rework the faceting approach and maybe offer multiple
alternatives.
The multi value field problem is now solvable (I think). However, we first need
the migration to Lucene 4. FieldCaches change in Lucene 4 afaik and that's how
the facet collector works.
For me faceting has
On 27 Jan 2013, at 11:06, Nicolas Helleringer
wrote:
> I think too that Lucene 4 migration is mandatory before having a look
> at Facets native / count issues.
+1 Anything else is atm wasted effort. Just need to move faster on Search 5
then ;-)
—Hardy
Steve, are you still looking for feedback on this? It seems the CI tests are
passing again
and I am not sure whether I ever wrote any locking tests. If so, I completely
forgot about it.
—Hardy
On 24 Jan 2013, at 15:46, Steve Ebersole wrote:
> I looked at this some more.
>
> The cause is tha
> How about
>
> d. Use an alias for all skip options:
>
> export mvnFast = "mvn -DskipITs -DskipDocs -DskipDistro”
instead of using a variable, just use an alias. I have several aliases
defined in my ~/.alias file which I source from .bashrc.
> This gives a quick build in one command and sti
On 2 Jan 2013, at 16:07, Steve Ebersole wrote:
> So I am also working on reverting the change to use -proc:both with a
> single compile phase. However, what we will end up with is still a
> single -proc:only phase no matter how many processors are run. They
> will output to a unified direc
On 2 Jan 2013, at 18:12, Steve Ebersole wrote:
> Well technically it is not valid according to the javac spec, which was
> David's point (which I assume who you are referring to).
What is against the spec? To run 'javac -proc:only’?
> And in fact we get a slew of errors from running `javac -
On 3 Jan 2013, at 13:29, Steve Ebersole wrote:
>>> And in fact we get a slew of errors from running `javac -proc:only`. We
>>> just happen to eat/ignore them.
>>
>> Sure, in some cases you might have to run the processors as part of the main
>> compile. Still, imo nothing wrong with the way
On 11 Jan 2013, at 13:51, Sanne Grinovero wrote:
> We need to align the 4.5 branch to latest ORM 4.3.
>
> Considering the main theme for 4.5 is to keep up with JPA 2.1 and
> latest WildFly, the branch is technically ready for a release.
+1 We should release asap
> Anything else that you would
I think Gunnar forgot to include Ales in the previous mail (unless he is on
hibernate-dev).
Anyways, just a few comments.
On 11 Jan 2013, at 17:44, Gunnar Morling wrote:
> Can you confirm that some static method is involved here (which was the
> case for HV-818)? I can't see one on your Email
On 11 Jan 2013, at 19:25, Scott Marlow wrote:
> On 12/11/2013 11:44 AM, Gunnar Morling wrote:
>> Ales,
>>
>> Can you confirm that some static method is involved here (which was the
>> case for HV-818)? I can't see one on your Email class but maybe there is
>> one on AbstractEntity?
>>
>> If so
Hi Ales,
could you try running against Hibernate Validator 5.0.2-SNAPSHOT.
I just deployed it and it would be interesting to see whether it fixes the
problem prior to creating a final release.
—Hardy
On 12 Jan 2013, at 11:26, Ales Justin wrote:
>> Can you confirm that some static method is
On 12 Jan 2013, at 21:54, Sanne Grinovero wrote:
> In Hibernate Search there is a Maven module responsible for running
> performance tests, which takes several minutes to run.
>
> Since it's quite annoying for day to day development, and especially
> during a release process as the process runs
On 12 Jan 2013, at 21:54, Sanne Grinovero wrote:
> In Hibernate Search there is a Maven module responsible for running
> performance tests, which takes several minutes to run.
>
> Since it's quite annoying for day to day development, and especially
> during a release process as the process runs
Hi,
>>> The fix to include documentation would probably need to wait migration
>>> to asciidoc.
>>
>> I am not quite following? Which fix for documentation?
>
> I was referring to the fact that the documention is also not built by
> default. I'm seeing the light on your suggestions now,
ahh, mu
Hi,
Given that we are moving to Search 5 and we made some recent adjustments, I am
wondering whether it would
not be time to remove the experimental status of the spatial Api now? Thoughts?
—Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jbo
Sent from my iPad
On 14 dec 2013, at 13:55, Sanne Grinovero wrote:
> While I hope the API won't need any change, the implementation will be
> different: for one some Lucene APIs changed which affect it
> significantly, and also Lucene 4 provides some of this functionality
> already.
>
> We'll b
On 16 Jan 2013, at 08:32, Emmanuel Bernard wrote:
> - spatial as a name is a bit fuzzy, should we change it? I tend to use
> geolocation maybe geoquery when I try to explain the notion.
not sure. IMO spatial is the right term. I find relocation less appealing, but
better than geoquery which
g
On 19 Jan 2013, at 13:13, Gunnar Morling wrote:
> 2013/12/19 Hardy Ferentschik
>
> On 16 Jan 2013, at 08:32, Emmanuel Bernard wrote:
>
> > - spatial as a name is a bit fuzzy, should we change it? I tend to use
> > geolocation maybe geoquery when I try to explain t
Hi,
IMO we should rethink how we describe the architecture of Search and especially
its extension points.
I think for Search 5 we will need to review/rewrite the documentation (maybe as
part of moving to asciidoc) and clear out some
of the ambiguities we have in the used terminology.
For exam
On 19 Jan 2013, at 18:17, Sanne Grinovero wrote:
> On 19 December 2013 15:19, Hardy Ferentschik wrote:
>> Hi,
>>
>> IMO we should rethink how we describe the architecture of Search and
>> especially its extension points.
>> I think for Search 5 w
On 14 Jan 2014, at 00:06, Sanne Grinovero wrote:
> as you might already know by following the WildFly developer's mailing
> list, most of the Hibernate Search jars and dependencies (Lucene) are
> now included in the application server as modules.
Right. Still not sure whether this is such a gre
On 14 Jan 2014, at 12:25, Sanne Grinovero wrote:
>> +1 Does this really need a separate module?
>
> It's probably not strictly needed, but I think it's preferable so that
> people can use a different version of it.
> Also, it's our tested configuration.
ok
>> Is there some info about “optiona
Hibernate Validator 5.1.0.Beta1is out. More info on in.relation.to -
http://in.relation.to/24788.lace
—Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>> I can do a release. Just wondering whether it should be a CR already?
>>> The main point of 4.5 was to give us ORM 4.3 compatibility, right? AFAIK we
>>> already upgraded now
>>> to 4.3.0.Final (just not released yet). So it would really be time to get
>>> 4.5.0.Final out.
>>> We could cut a
On 16 Jan 2014, at 13:42, Steve Ebersole wrote:
>> Part of the discussion that I had with Steve this morning, and the piece
>> that he particularly wanted to discuss here, is how to perform the
>> extraction and where to put it:
>>
>> * Is this standalone service registry its own project, sep
On 18 Jan 2014, at 12:12, Sanne Grinovero wrote:
> The new website is missing the migration guides; specifically I'm
> looking at Hibernate Search but since we probably want to keep a
> familiar structure across the various projects, I hope to get feedback
> from all.
I agree, we probably shoul
Hi Martin,
great that you like Hibernate Search and want to make it even easier to use.
On 3 Jan 2014, at 19:08, Martin Braun wrote:
> I am currently working on a new way to query in Hibernate Search. It's not
> finished, but
> it already works.
I had a quick look at the code, but for the sak
On 3 Jan 2014, at 22:22, Emmanuel Bernard wrote:
>>> - I don't think annotations are the best way to express queries but you
>>> probably
>>> have your reasons, so let's discuss them :)
>> Why? I think it's not hard to read an you have the query right with your
>> ParameterWrapper-class which
On 4 Jan 2014, at 10:24, Martin Braun wrote:
> Uhm. I totally forgot to add this functionality in my rewrite (I have
> rewritten most of the code last weekend)
> and I implemented a way to pass parameters into QueryTypes. You can even pass
> parameters that are dynamically
> determined by stat
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
Hi,
not sure whether this could work in your use case, but in Search we use a
SessionFactoryObserver.
We register the observer in Integrator#integrate with the
SessionFactoryImplementor.
Once the SessionFactory is completely build you get a callback into
SessionFactoryObserver#sessionFactoryCre
I think if you need to make sure the SessionFactory is fully initialised,
you’ll need an observer.
On 11 Jan 2014, at 12:55, Gunnar Morling wrote:
> No, at least not in the case of DatastoreProvider.
>
> I think it depends on the specific service and when it is requested for the
> first time.
On 17 Jan 2014, at 11:44, Sanne Grinovero wrote:
> I've manually re-triggered building of most projects last night, and
> some actually need a bit of attention now; for example
> hibernate-commons-annotations is being built with Maven but it's no
> longer a Maven build.. please don't ignore its
More info about $subject as always on in.relation.to -
http://in.relation.to/24874.lace
—Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On 18 Jan 2014, at 08:32, Steve Ebersole wrote:
> As we move to 5.0 and the new unified XML format I'd like to revisit the
> ways we have mapped certain things historically in hbm.xml and improve upon
> them when possible. At the moment I am looking at mapping of natural ids.
> In hbm.xml the f
On 18 Jan 2014, at 04:28, Steve Ebersole wrote:
> At the moment all of metamodel binding completely mis-handles
> MappedSuperclasses. The annotation source processor handles them somewhat,
> but in a very unusable way; it basically flattens all MappedSuperclass info
> into the nearest Entity.
Nice
On 24 Jan 2014, at 08:52, Gunnar Morling wrote:
> Hi,
>
> As I just noticed, GitHub allows since recently to view diffs in prose
> files (e.g. MarkDown or AsciiDoc) in a *rendered* fashion [1].
>
> Just click the "Rendered" button next to a diff in commits or pull requests
> as e.g. her
Got also got a bunch of failures in HV with JDK8. Luckily a big part seems to
be
related to author tags of the form:
@author name
I’ll fix this and the remaining issues up shortly. I never likes this form of
author syntax, especially
since it was not valid HMTL ;-)
Funny enough, we discusse
More information about Hibernate Validator 5.1.0.Final on in.relation.to -
http://in.relation.to/24979.lace
Enjoy!
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On 4 Jan 2014, at 18:05, Emmanuel Bernard wrote:
> Here are the meeting minutes.
> I did add a manual summary since I don’t know how to effectively use the bot
> to its full potential.
>
> ## Validator
>
> 5.1 is out and plan to push it to WildFly as soon as they permit.
I am ways ahead of y
On 4 Jan 2014, at 20:41, Scott Marlow wrote:
> On 03/04/2014 02:32 PM, Hardy Ferentschik wrote:
>>
>> On 4 Jan 2014, at 18:05, Emmanuel Bernard wrote:
>>
>>> Here are the meeting minutes.
>>> I did add a manual summary since I don’t know how to e
On 5 Jan 2014, at 18:40, Steve Ebersole wrote:
> Historically annotation binding within Hibernate made a huge assumption
> that AccessType and PropertyAccessor were the same thing. They aren't
> necessarily. AccessType is simply meant to dictate where to look for
> annotations relating to "per
Nice
On 10 Jan 2014, at 18:13, Emmanuel Bernard wrote:
> I finally resolve WEBSITE-95 and explained how to build the website.
> It is on the survival guide web page which is reachable from
> http://hibernate.org/README/.
>
> http://hibernate.org/survival-guide/#publishing-the-site
>
> Emmanue
On 9 Jan 2014, at 18:31, Steve Ebersole wrote:
> Then we had expanded the previous discussion to look at the more general
> case... interface based models. Imo, the best way to map the above model
> would be:
>
> @Entity
> interface Employee {
>...
> }
>
> Yes, this deviates from JPA whic
+100
On 20 Jan 2014, at 16:21, Sanne Grinovero wrote:
> The next minor release of Apache Lucene v. 4.8 will require Java7.
>
> The Lucene team has highlighted many good reasons for that, including
> some excellent improvements in sorting performance and reliability of
> IO operations: nice thin
Hi Guillaume,
nice job with this issue. I was about to comment on the pull request, but
now I do it here.
On 21 Jan 2014, at 11:10, Guillaume Smet wrote:
> So, my patch here [1] broke a test which checks that Criteria +
> restrictions mostly work - even if it's documented as not supported
> an
On 21 Jan 2014, at 13:41, Sanne Grinovero wrote:
> The question of being able to filter via Criteria or Hibernate Session
> Filters is a recurring feature request so we need to be cautious here.
The question is can we support it properly (most notably correctly).
> You make good points, and if
Hi there,
As part of my work for making Search OSGi ready [1], I am looking into
addressing HSEARCH-1560 [2] which is about
split packages which we have between some of our Search bundles (or modules to
use Maven lingo).
Basically a split package "is caused where two or more bundles export the
On 26 Jan 2014, at 05:13, Steve Ebersole wrote:
>> From the test
> org.hibernate.test.annotations.access.jpa.AccessMappingTest#testExplicitPropertyAccessAnnotationsWithHibernateStyleOverride
> we have the following:
>
>
> @Entity
> @Access(AccessType.PROPERTY)
> public class Course3 {
>pri
use
> @org.hibernate.annotations.AccessType...
>
>
> On Wed, Mar 26, 2014 at 2:01 PM, Hardy Ferentschik
> wrote:
>
> On 26 Jan 2014, at 05:13, Steve Ebersole wrote:
>
> >> From the test
> > org.hibernate.test.annotations.access.jpa.AccessMappingTest#testExplicitPropertyAccessAn
On 26 Jan 2014, at 20:16, Steve Ebersole wrote:
> Ok, but... its still a good spring board to discuss this topic which is
> strangely unclear and murky in terms of what we do and do not support.
Sure. I am just saying, we are discussing a wrong test. When I was implementing
the JPA @Access ru
On 26 Jan 2014, at 15:56, Sanne Grinovero wrote:
> But the original test represents a quite naturally looking example and
> it's hard to justify why that should be considered illegal;
Because it is against the rules for the placement of @Access.
At least in my interpretation of the spec.
> Ig
On 26 Jan 2014, at 13:55, Emmanuel Bernard wrote:
> I don't have a full grasp of the consequences, I'll need to think about
> it.
:-) There might be a couple of other package changes which would make sense
(unrelated to the
split package problem). I guess now is the time to discuss and apply
On 26 Jan 2014, at 20:52, Sanne Grinovero wrote:
> The classes in the ORM module are extremely widely used by our primary target:
>
> - FullTextQuery
> - Search
> - FullTextSession
>
> and two more lesser ones, but I think the 3 above are probably "THE
> API”.
That was my thinking as well.
>
1 - 100 of 1142 matches
Mail list logo
