hibernate 3.6.0.FINAL and OSGi

Hibernate does not come OSGi enabled from jboss. That’s okay. We can use bundlor to fix that. Grab bundlor from springsource and execute the following commands to make them available in maven. You can also add these to a maven pom.xml to have them automatically run. Note that the commands below assume the jar is in a specific subdirectory and the output goes to another subdirectory. Just replace yourprefix with the prefix you want to use. Springsource likes to use com.springsource but pick your own. Then just use your maven dependency declaration as you normally would.

bundlor.bat -i nonosgilibs/hibernate3.jar -o ./libs/hibernateuser.org.hibernate-3.6.0.Final.jar -m template-hibernate3.mf
mvn install:install-file -Dfile=libs/hibernateuser.org.hibernate-3.6.0.Final.jar -DgroupId=org.hibernate -DartifactId=hibernateuser.org.hibernate -Dversion=3.6.0.Final -Dpackaging=jar

bundlor.bat -i nonosgilibs/hibernate-jpa-2.0-api-1.0.0.Final.jar -o libs/hibernateuser.javax.persistence2-1.0.0.Final.jar -m template-hibernate-jpa.mf
mvn install:install-file -Dfile=libs/hibernateuser.javax.persistence2-1.0.0.Final.jar -DgroupId=javax.persistence -DartifactId=hibernateuser.javax.persistence2 -Dversion=1.0.0.Final -Dpackaging=jar

bundlor.bat -i nonosgilibs/hibernate-validator-4.1.0.Final.jar -o libs/hibernateuser.org.hibernate.validator-4.1.0.Final.jar -m template-hibernate-validator.mf
mvn install:install-file -Dfile=libs/hibernateuser.org.hibernate.validator-4.1.0.Final.jar -DgroupId=org.hibernate -DartifactId=hibernateuser.org.hibernate.validator -Dversion=4.1.0.Final -Dpackaging=jar

bundlor.bat -i nonosgilibs/validation-api-1.0.0.GA.jar -o libs/hibernateuser.javax.validation-1.0.0.GA.jar -m template-hibernate-validator-api.mf
mvn install:install-file -Dfile=libs/hibernateuser.javax.validation-1.0.0.GA.jar -DgroupId=javax.validation -DartifactId=hibernateuser.javax.validation -Dversion=1.0.0.GA -Dpackaging=jar
The template.mf files are below:

template-hibernate3.mf 

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: JBoss Hibernate Objec-Relational Mapper
Built-By: hibernateuser
Bundle-Vendor: hibernateuser
Implementation-Vendor-Id: org.hibernate
Bundle-SymbolicName: hibernateuser.org.hibernate
Bundle-Version: 3.6.0.Final
Eclipse-BuddyPolicy: registered
Excluded-Exports: *.internal*
Import-Template: antlr*;version="[2.7.6,3)",
 com.ibm.*;resolution:=optional,
 javasssist.*;version="[3.12.0,4.0.0)",
 javax.naming*,
 javax.persistence*;version="[2,2.1)",
 javax.security.auth*,
 javax.security.jacc*,
 java.sql*,
 javax.transaction*;resolution:=optional;version="[1.1,2)",
 javax.xml*,
 javax.validation*;version="[1.0,1.1)",
 net.sf.cglib*;version="[2.2,3]",
 org.slf4j*;version="[1.6.1,2.0)",
 org.dom4j*;version="[1.6.1,2)",
 org.apache.commons.collections*;version="[3.1,4)",
 org.w3c.dom*,
 org.xml.sax*,
 *
Export-Template: org.hibernate.*;version=3.6.0
Unversioned-Imports: *

and template-hibernate-jpa.mf: 

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: JBoss Hibernate Objec-Relational Mapper
Built-By: hibernateuser
Bundle-Vendor: hibernateuser
Implementation-Vendor-Id: org.hibernate
Bundle-SymbolicName: hibernateuser.org.hibernate
Bundle-Version: 3.6.0.Final
Eclipse-BuddyPolicy: registered
Excluded-Exports: *.internal*
Import-Template: antlr*;version="[2.7.6,3)",
 com.ibm.*;resolution:=optional,
 javasssist.*;version="[3.12.0,4.0.0)",
 javax.naming*,
 javax.persistence*;version="[2,2.1)",
 javax.security.auth*,
 javax.security.jacc*,
 java.sql*,
 javax.transaction*;resolution:=optional;version="[1.1,2)",
 javax.xml*,
 javax.validation*;version="[1.0,1.1)",
 net.sf.cglib*;version="[2.2,3]",
 org.slf4j*;version="[1.6.1,2.0)",
 org.dom4j*;version="[1.6.1,2)",
 org.apache.commons.collections*;version="[3.1,4)",
 org.w3c.dom*,
 org.xml.sax*,
 *
Export-Template: org.hibernate.*;version=3.6.0
Unversioned-Imports: *

You can do the same thing for the validator jars: 

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: JBoss Hibernate Validator
Built-By: hibernateuser
Bundle-Vendor: hibernateuser
Bundle-SymbolicName: hibernateuser.org.hibernate.validator
Bundle-Version: 4.1.0.Final
Implementation-Vendor-Id: org.hibernate
Eclipse-BuddyPolicy: registered
Excluded-Exports: *.internal*
Export-Template: org.hibernate.validator.*;version=4.1.0.Final
Unversioned-Imports: *

and for the validator API 

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Java Validaton API
Built-By: hibernateuser
Bundle-SymbolicName: hiberanteuser.javax.validation
Implementation-Vendor-Id: org.hibernate
Bundle-Version: 1.0.0.GA
Eclipse-BuddyPolicy: registered
Excluded-Exports: *.internal*
Export-Template: javax.validation.*;version=1.0.0.GA
Unversioned-Imports: *

I have not completely tested this but this is the basic idea.

Comments

Post a Comment

Popular posts from this blog

quick note on scala.js, react hooks, monix, auth

quick note on scala.js, react hooks, monix, auth Reactjs hooks finally came out of preview in a recent version of React. scalajs-reaction has had support for hooks since they were in preview. React hooks seem like the hot new thing but for me the question is, do hooks help improve your code by improving maintainability, time to market, TCO, etc.? Let’s take a look using authentication as an example and employ monix , a reactive observable framework that also builds on cats . We will assume we are building a SPA. Does it improve your code and make your application & development experience better? Auth Auth processing can be complex. Many react auth examples you find in blogs like to show how to use “react-routing” and “auth” as a switch that determines which routes are protected or unprotected. Protected routes show application specific data. Unprotected routes show login content . Based on storing a “User” object in the browser session/local storage, th...
Read more

attributes with react and typescript.md

If you use typescript with react you may wonder what the right signature is for your “properties” interface. Obviously, your component will have few to many specific properties that reflect your domain. However, you may wish to also provide for the ability to add other attributes, such as those valid for a div property. In other words, you want to extend your props interface with that of the properties from a div element. How do you do that? There are really two issues: How do you extend your props interfaces How do you filter the props once you receive them to just those that apply. Extend Your Prop Interface or Use Sum Types It’s not uncommon to see interface Props { className ? : string yourProp ? : number } with the idea of using it in class MyComponent extends React.Component<Props, any> somewhere. If your component will have an outer div, you may also pass in a react element so that its configurable. But let’s say your outer element is a div and you wan...
Read more

zio environment and modules pattern: zio, scala.js, react, query management

zio environment and modules pattern: zio, scala.js, react, query management This blog covers a zio-based fetch design for scala.js, react web applications. It heavily uses the zio “environment” feature to help motivate a point of view on the modules pattern in effect systems. At the end, I summarize some thoughts on ergonomics and complexity. This blog assumes a basic knowledge of zio and react. scala.js is just like scala so you mostly already know scala.js. This blog is a follow-on to previous blogs: https://appddeevvmeanderings.blogspot.com/2019/10/scalajs-react-fetcher-hook_48.html and https://appddeevvmeanderings.blogspot.com/2019/11/scalajs-and-react-suspense.html . I have been keeping an eye on and culling ideas from typscript/javascript fetching libraries that address query management concerns. The formulation below incorporates some of those concerns but does not try to comprehensively duplicate well established javascript libraries. I only care about ...
Read more