[OPENJPA-2669] Add karaf feature and adapt imports#5
[OPENJPA-2669] Add karaf feature and adapt imports#5cschneider wants to merge 2 commits intoapache:trunkfrom cschneider:OPENJPA-2669
Conversation
| <feature name="openjpa" description="Apache OpenJPA 3 persistence engine support" version="${project.version}"> | ||
| <details>Apache OpenJPA persistence engine</details> | ||
| <bundle dependency="true">mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1</bundle> | ||
| <bundle dependency="true">mvn:org.eclipse.persistence/javax.persistence/2.1.0</bundle> |
There was a problem hiding this comment.
There was a problem hiding this comment.
Well alpha-1 does not sound so trustworthy :-) I just checked that you created the bundle. Is it stable ? If yes it would be great if you could release a 1.0.0 version so people know it is safe to use.
There was a problem hiding this comment.
alpha-1 for EE 7 spec was cause of this TCK thing only, I didn't check the OSGi part but that would be easy to enhance and stay consistent with karaf ecosystem I think.
| <bundle dependency="true">mvn:org.eclipse.persistence/javax.persistence/2.1.0</bundle> | ||
| <bundle dependency="true">mvn:org.apache.geronimo.specs/geronimo-annotation_1.0_spec/1.1.1</bundle> | ||
| <bundle dependency="true">mvn:org.apache.geronimo.specs/geronimo-el_1.0_spec/1.0.1</bundle> | ||
| <bundle dependency="true">mvn:commons-pool/commons-pool/1.6</bundle> |
There was a problem hiding this comment.
we should likely move to dbcp2 today no?
There was a problem hiding this comment.
Makes sense .. or not use require any pooling at all. I let pax-jdbc-config create a pooled DataSource
There was a problem hiding this comment.
+1 to not handle it there
|
@cschneider how hard would it be to have a unit test with pax to ensure it is not broken in the main build? |
|
A pax exam test is on my todo list. I think it is crucial to make sure the feature still works in the future. |
|
Fwiw, validating the features with the Karaf 4 maven plugin ensure that the feature can be deployed correctly. An integration test can certainly be done to actually test the bundles, but it's not necessary to verify that the bundles can be installed and resolved correctly. |
|
Well I was more concerned about the runtime behavior than the installation (= ensure it deploys and then we can load properly classes, listeners etc... and that tccl is the right one). Some work will get started soon with some lazy instantiation logic and I would like to avoid a half working state. |
3 participants
No description provided.