REMINDER: Participation Requested: Survey about Open-Source Software Development
by Jeffrey Carver
Hi,
Apologies for any inconvenience and thank you to those who have already
completed the survey. We will keep the survey open for another couple of
weeks. But, we do hope you will consider responding to the email request
below (sent 2 weeks ago).
Thanks,
Dr. Jeffrey Carver
Assistant Professor
University of Alabama
(v) 205-348-9829 (f) 205-348-0219
http://www.cs.ua.edu/~carver
-----Original Message-----
From: Jeffrey Carver [mailto:opensourcesurvey@cs.ua.edu]
Sent: Monday, June 13, 2011 11:53 AM
To: 'hibernate-dev(a)lists.jboss.org'
Subject: Participation Requested: Survey about Open-Source Software
Development
Hi,
Drs. Jeffrey Carver, Rosanna Guadagno, Debra McCallum, and Mr. Amiangshu
Bosu, University of Alabama, and Dr. Lorin Hochstein, University of
Southern California, are conducting a survey of open-source software
developers. This survey seeks to understand how developers on distributed,
virtual teams, like open-source projects, interact with each other to
accomplish their tasks. You must be at least 19 years of age to complete the
survey. The survey should take approximately 15 minutes to complete.
If you are actively participating as a developer, please consider completing
our survey.
Here is the link to the survey: http://goo.gl/HQnux
We apologize for inconvenience and if you receive multiple copies of this
email. This survey has been approved by The University of Alabama IRB board.
Thanks,
Dr. Jeffrey Carver
Assistant Professor
University of Alabama
(v) 205-348-9829 (f) 205-348-0219
http://www.cs.ua.edu/~carver
15 years
[HSEARCH] Hibernate search core module proposal
by Davide D'Alto
Hi,
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:
hibernate-search
|-- hibernate-search
|-- ...
I was a bit surprised because others Hibernate and JBoss projects I
saw so far seem to use the "-core" suffix for the main module.
Shouldn't hibernate-search follow the same convention?
This looks like a good time to review module names for Hibernate Search 4.0
Best regards,
Davide D'Alto
15 years
JIRA maintenance
by Steve Ebersole
The Hibernate JIRA instance graciously provided by Atlassian and hosted
by Contegix will be upgraded sometime this weekend from version 4.1 to
4.3 and will be unavailable for a short period of time during that
process. I'll reply here when I know the exact times.
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
15 years
Hibernate OGM: birth announcement
by Emmanuel Bernard
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
15 years
Processing mapping information followup
by Steve Ebersole
Wanted to start a follow up discussion to the conversation we had at the
IRC meeting on 6/13 with regards to changing the way we process mapping
information to follow dependencies in the various types of information.
What we do currently (in the metamodel code) is essentially the same as
the legacy code. That is to say we process through a mapping source in
full and then move on to the next one, saving off "second passes"
whenever we encounter information on which we have to wait. The second
passes in the new metamodel code are isolated I guess (so far) to
org.hibernate.metamodel.source.internal.EntityReferenceResolver
What I proposed instead is quite different, more like what I did for the
rest of the MetadataImpl constructor code in terms of defining
dependencies and processing stuff in an order that makes sure to avoid
the need for second passes.
Here is the initial swab at the levels of information:
1) entity - basic entity information such as name, hierarchy
2) identifiers - normal identifiers could almost be handled in the first
level. key-many-to-one still needs some form of delayed queuing.
3) secondary tables
4) attributes
5) associations
The dependencies flow downward; (2) depends on (1); (3) depends on (2); etc.
I liked handling (3) secondary tables separately because they basically
expand the possible set of columns available for (4) and (5).
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
15 years
Improving AuditProcessManager
by Adam Warski
Trying to find one user's problem today, I've stumbled on the AuditProcessManager class.
It currently uses a ConcurrentHashMap to bind an AuditProcess to a transaction (where transaction is the current key).
This is suboptimal for several reasons, firstly it's not too nice ;), secondly it relies on the transaction always being the same object.
So I thought that maybe v4 is a good moment to try to fix that?
What would be needed there is a transaction-scoped "service".
Or just a way to obtain a registered BeforeTransactionCompletionProcess with some specified class from the ActionQueue?
What do you think?
Adam
--
Adam Warski
http://twitter.com/#!/adamwarski
http://www.warski.org
http://www.softwaremill.eu
15 years
Country-Specific Constraints
by George Gastaldi
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 these country-specific
constraints on a separate package (like "br" for Brazil, "fr" for
France, etc) so that a standard is placed when new country specific
constraints are needed.
WDYT ?
Regards,
George Gastaldi
15 years
