[jira] [Commented] (ARIES-691) Add tests for EclipseLink - possibly include fragment for EclipseLink support

["Balazs Zsoldos (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARIES-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060408#comment-13060408 ] 

Balazs Zsoldos commented on ARIES-691:
--------------------------------------

Hi,

I have tried this solution in Glassfish 3.1. I ran into some problems:
- The import-package contains version lower than 2.0 for package javax.persistence and javax.persistence.spi. However Glassfish contains version 2.0.2. (I changed it to move forward)
- If there is no other application in Glassfish that uses JPA, Eclipselink bundle remains in RESOLVED state. Therefore the function "handlePotentialEclipseLink" is never called. I modified the source a bit that it starts the eclipselink bundle if it is in RESOLVED state. It might not be the best solution, I would be happy if you could direct me how to solve this in a better way.
- To make transactions work Eclipselink must know in what environment it runs. By default it thinks that it is in a standalone program and JTA does not work. To make JTA work we must have an entry in the persistence.xml that says we are in Glassfish. However it needs a package (as all platform does) to be imported into the adapter: org.eclipse.persistence.platform.server.sunas. I think all of the packages inside platform should be imported into adapter to let the classloader find the platform dependent classes.
- It seems to me that in Felix the getBundleContext() function gives back null when the Bundle is in RESOLVED state. The bundlecontext is set only when the function start() is called on the bundle. This is a problem of blueprint. It gives back a nullpointer exception when the blueprint file of a bundle is loaded. (Currently I always debug there and call the start() function by hand :))

Regards,
Balazs


> Add tests for EclipseLink - possibly include fragment for EclipseLink support
> -----------------------------------------------------------------------------
>
>                 Key: ARIES-691
>                 URL: https://issues.apache.org/jira/browse/ARIES-691
>             Project: Aries
>          Issue Type: Improvement
>          Components: JPA
>    Affects Versions: 0.4
>            Reporter: Timothy Ward
>            Assignee: Valentin Mahrwald
>             Fix For: 0.4
>
>
> We should test the Aries JPA container with EclipseLink as well as OpenJPA to give us better coverage. This may involve writing code to expose the EclipseLink PersistenceProvider implementation

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira