Concept of "service availability"
by Steve Ebersole
This ties together a few different discussions that have been going on
simultaneously on the mailing list that I think are all related.
Right now to configure certain services (select one impl over another)
users generally give the FQN for that impl Class. For example to use
C3P0 connection pooling users would say:
hibernate.connection.provider_class =
org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider
We have discussed why this is bad even before any of the OSGi
discussions and the solution we wanted to shoot for was that of naming
"selectors" such that the user would instead say:
hibernate.connection.provider_class = c3p0
And "c3p0" here would be interpreted to mean "instantiate and configure
the
org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider
Class". But that still means a limited set of short name values *and*
still gives us a problem (iiuc) under OSGi due to visibility.
So what I propose instead is a way for service implementors to be
registered under a short name via discovery. The main piece to this is
the "registry" (which is also a service under the BootstrapServiceRegistry):
interface AvailableServiceRegistry extends Service {
public <T> Class<? extends T>
findAvailableServiceImplementor(Class<T> serviceRole, String selector);
}
class AvailableServiceRegistryImpl
implements AvailableServiceRegistry,
ServiceRegistryAwareService {
private Map<Class,Map<String,Class>> availableImplementors = ...;
@Override
public <T> Class<? extends T>
findAvailableServiceImplementor(Class<T> serviceRole, String selector) {
// purposely simplistic :)
return availableImplementors.get( serviceRole ).get( selector );
}
@Override
public void injectServices(ServiceRegistryImplementor
serviceRegistry) {
final LinkedHashSet<ServiceAvailabililtyNotifier> notifiers =
serviceRegistry.getService( ClassLoaderService.class ).loadJavaServices(
ServiceAvailabililtyNotifier.class );
for ( ServiceAvailabililtyNotifier notifier : notifiers ) {
for ( ServiceAvailabililty availability :
notifier.getAvailabilities() ) {
// again, purposely simplistic
Map<String,Class> serviceImplementors =
availableImplementors.get( availability.getRole() );
serviceImplementors.put(
availability.getSelector(),
availability.getImplementor()
);
}
}
}
}
Outstanding question... Especially in OSGi, where service bundles can be
added/removed, how do we best account for cleaning up no-longer valid
references (even more importantly perhaps, what the hell does it mean to
Hibernate when a ConnectionProvider implementation, for example, that is
in use gets taken away?!?). Perhaps this is just where an OSGi-specific
Hibernate ServiceRegistry implementation would come into play.
--
steve(a)hibernate.org
http://hibernate.org
13 years, 9 months
Jira instance
by Steve Ebersole
The Hibernate Jira is not feeling well today :)
I have notified Atlassian/Contegix. We should hear shortly
--
steve(a)hibernate.org
http://hibernate.org
13 years, 9 months
Eclipse-specific execution filters in POMs
by Brett Meyer
I know a lot of you don't use Eclipse, but...
Its Maven plugin (M2E) does not have connectors for several of Hibernate 3.3's lifecycle mappings. The only way to get the IDE to ignore them is to add the following (as an example). What are your opinions of having IDE-specific areas, like this, in the parent POM?
<!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>
org.jboss.maven.plugins
</groupId>
<artifactId>
maven-injection-plugin
</artifactId>
<versionRange>
[1.0.2,)
</versionRange>
<goals>
<goal>bytecode</goal>
</goals>
</pluginExecutionFilter>
<action>
<ignore></ignore>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
13 years, 10 months
org.hibernate.jpa.test.packaging.PackagingTestCase
by Steve Ebersole
org.hibernate.jpa.test.packaging.PackagingTestCase uses ShrinkWrap to
facilitate "packaged" JPA tests. It uses metadata from
src/test/bundles, BUT it gets the copies moved over to target/bundles.
I am curious why it uses the target/bundles copy rather than the
src/test/bundles original?
--
steve(a)hibernate.org
http://hibernate.org
13 years, 10 months
Hibernate Search documentation build problem
by Nicolas Helleringer
Hi all,
I have problem with the documentation build of Hibernate Search :
[INFO] --- maven-jdocbook-plugin:2.3.5:generate (default-generate) @
hibernate-search-documentation ---
15 [main] INFO org.jboss.jdocbook.profile.ProfilerImpl - applying DocBook
profiling [C:\Dev\hibernate-search\hibernate-s
earch-documentation\target\docbook\work\profile\en-US\master.xml]
Error on line 27 column 19 of
file:/C:/Dev/hibernate-search/hibernate-search-documentation/src/main/docbook/en-US/master
.xml:
Error reported by XML parser: Invalid byte 1 of 1-byte UTF-8 sequence.
On got it either on master or 4.1.0.Fiinal tag
Does this ring a bell to someone ?
Thanks
Niko
13 years, 10 months
Re: [hibernate-dev] JPA callback listeners and CDI
by Gunnar Morling
Emmanuel,
What do you think about the idea outlined before of having an
EntityListenerFactory in the JPA spec similar to BV's
ConstraintValidatorFactory?
I think the situation in JPA is very similar to BV and feel it would make
sense to solve the problem similarly in both cases. This would also avoid a
direct dependency from JPA to CDI altogether (implementation-wise). The JPA
spec would just require the EE container to plug in a CDI-aware factory,
similar to what we've been discussing for BV constraint validators.
WDYT?
--Gunnar
Am 23.08.2012 17:11 schrieb "Emmanuel Bernard" <emmanuel(a)hibernate.org>:
13 years, 10 months
JPA callback listeners and CDI
by Steve Ebersole
Recently I just finished up adding JPA 2.1 support for CDI injection of
callback listeners. Couple of things about this:
1) Took this opportunity to refactor and clean up a lot of this code.
On benefit of this was I added a feature now where after transaction
hooks are not added as part of ActionQueue processing unless registered
listeners say it is needed for that particular entity type! This is
something users have been asking for for quite some time. So thats a
good win. This is both for Envers and HEM.
2) The way this is currently implemented, using JPA now has a dependency
on the CDI API being available on the classpath. We need to decide if
that is unreasonable. The other option is to handle it like we do for
BeanValidation and use messy reflection to isolate the dependency.
--
steve(a)hibernate.org
http://hibernate.org
13 years, 10 months
Re: [hibernate-dev] Running Gradle build against an Infinispan version passed as command line parameter?
by Galder Zamarreño
That doesn't seem to work. It's still using the version defined in the configuration file.
On Aug 23, 2012, at 3:08 PM, Steve Ebersole wrote:
> Try -P instead of -D. Not sure it will work, but -P is the means to set project variables.
>
> On Thu 23 Aug 2012 08:02:28 AM CDT, Galder Zamarreño wrote:
>> Hi,
>>
>> I'd like to have a CI job that tests Hibernate Infinispan integration against the latest Infinispan 5.1.
>>
>> So, I'm wondering if there's a way in which you can define the Infinispan version to use via command line. Something like:
>>
>> ./gradlew clean build -DinfinispanVersion=5.1.7-SNAPSHOT
>>
>> The above command does not currently work, but wondered if there's a way to achieve something like that?
>>
>> Cheers,
>> --
>> Galder Zamarreño
>> Sr. Software Engineer
>> Infinispan, JBoss Cache
>>
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
13 years, 10 months
Running Gradle build against an Infinispan version passed as command line parameter?
by Galder Zamarreño
Hi,
I'd like to have a CI job that tests Hibernate Infinispan integration against the latest Infinispan 5.1.
So, I'm wondering if there's a way in which you can define the Infinispan version to use via command line. Something like:
./gradlew clean build -DinfinispanVersion=5.1.7-SNAPSHOT
The above command does not currently work, but wondered if there's a way to achieve something like that?
Cheers,
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
13 years, 10 months
