[jira] Reopened: (ARIES-296) Add org.osgi.framework.system.packages to config.ini of samples so that we can specify javax.transaction mandatory properties

["Joe Bohn (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARIES-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bohn reopened ARIES-296:
----------------------------


reopening to revert one small unintended change in the previous commit.  For the Blog sample I removed the geronimo-jta spec from the list of started configurations.   AFAIK it doesn't create any problems ... but just to be sure I'll add it back in.

> Add org.osgi.framework.system.packages to config.ini of samples so that we can specify javax.transaction mandatory properties
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-296
>                 URL: https://issues.apache.org/jira/browse/ARIES-296
>             Project: Aries
>          Issue Type: Bug
>          Components: Samples
>    Affects Versions: 0.1
>            Reporter: Joe Bohn
>            Assignee: Joe Bohn
>             Fix For: 0.1
>
>
> With recent updates we are now loading some transaction classes from the system bundle and others from the transaction spec bundle.  This is causing a linkage error as follows:
> java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.transaction.Transaction.enlistResource(Ljavax/transaction/xa/XAResource;)Z" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/apache/aries/transaction/jdbc/ConnectionWrapper, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, javax/transaction/Transaction, have different Class objects for the type javax/transaction/xa/XAResource used in the signature
>         at org.apache.aries.transaction.jdbc.ConnectionWrapper.<init>(ConnectionWrapper.java:67) 
> To avoid the error we need to add org.osgi.framework.system.packages  entries that include a mandatory attribute on the transaction packages so that our bundles do not wire to the system bundle which only includes a subset of the necessary classes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.