[
https://issues.jboss.org/browse/ISPN-4249?page=com.atlassian.jira.plugin....
]
Martin Gencur updated ISPN-4249:
--------------------------------
Description:
The following package have to be defined by Import-Package in either ISPN core or the
client bundle which uses ISPN core (not sure about the client's bundle) so that JBoss
TS can be found on classpath:
{code}
com.arjuna.ats.arjuna,
com.arjuna.ats.arjuna.common,
com.arjuna.ats.arjuna.coordinator,
com.arjuna.ats.arjuna.exceptions,
com.arjuna.ats.arjuna.logging,
com.arjuna.ats.arjuna.objectstore,
com.arjuna.ats.arjuna.recovery,
com.arjuna.ats.arjuna.state,
com.arjuna.ats.arjuna.tools,
com.arjuna.ats.arjuna.utils,
com.arjuna.ats.internal.arjuna,
com.arjuna.ats.internal.arjuna.common,
com.arjuna.ats.internal.arjuna.coordinator,
com.arjuna.ats.internal.arjuna.recovery,
com.arjuna.ats.internal.arjuna.thread,
com.arjuna.ats.internal.arjuna.tools,
com.arjuna.ats.internal.arjuna.utils,
com.arjuna.ats.internal.arjuna.objectstore,
com.arjuna.common.internal.util.propertyservice,
{code}
We should make sure we either provide users with instructions which packages they have to
import to make transactions work, or we have to import them automatically. This issues
needs to be investigated more. The bad thing is that PAX EXAM did not reveal this issue.
Perhaps it uses DynamicImport-Package to import all packages.
was:
The following package have to be defined by Import-Package in either ISPN core or the
client bundle which uses ISPN core (not sure which one) so that JBoss TS can be found on
classpath:
{code}
com.arjuna.ats.arjuna,
com.arjuna.ats.arjuna.common,
com.arjuna.ats.arjuna.coordinator,
com.arjuna.ats.arjuna.exceptions,
com.arjuna.ats.arjuna.logging,
com.arjuna.ats.arjuna.objectstore,
com.arjuna.ats.arjuna.recovery,
com.arjuna.ats.arjuna.state,
com.arjuna.ats.arjuna.tools,
com.arjuna.ats.arjuna.utils,
com.arjuna.ats.internal.arjuna,
com.arjuna.ats.internal.arjuna.common,
com.arjuna.ats.internal.arjuna.coordinator,
com.arjuna.ats.internal.arjuna.recovery,
com.arjuna.ats.internal.arjuna.thread,
com.arjuna.ats.internal.arjuna.tools,
com.arjuna.ats.internal.arjuna.utils,
com.arjuna.ats.internal.arjuna.objectstore,
com.arjuna.common.internal.util.propertyservice,
{code}
We should make sure we either provide users with instructions which packages they have to
import to make transactions work, or we have to import them automatically. This issues
needs to be investigated more. The bad thing is that PAX EXAM did not reveal this issue.
Perhaps it uses DynamicImport-Package to import all packages.
Unable to find transaction manager due to missing imports in OSGi
-----------------------------------------------------------------
Key: ISPN-4249
URL:
https://issues.jboss.org/browse/ISPN-4249
Project: Infinispan
Issue Type: Bug
Reporter: Martin Gencur
Assignee: Mircea Markus
The following package have to be defined by Import-Package in either ISPN core or the
client bundle which uses ISPN core (not sure about the client's bundle) so that JBoss
TS can be found on classpath:
{code}
com.arjuna.ats.arjuna,
com.arjuna.ats.arjuna.common,
com.arjuna.ats.arjuna.coordinator,
com.arjuna.ats.arjuna.exceptions,
com.arjuna.ats.arjuna.logging,
com.arjuna.ats.arjuna.objectstore,
com.arjuna.ats.arjuna.recovery,
com.arjuna.ats.arjuna.state,
com.arjuna.ats.arjuna.tools,
com.arjuna.ats.arjuna.utils,
com.arjuna.ats.internal.arjuna,
com.arjuna.ats.internal.arjuna.common,
com.arjuna.ats.internal.arjuna.coordinator,
com.arjuna.ats.internal.arjuna.recovery,
com.arjuna.ats.internal.arjuna.thread,
com.arjuna.ats.internal.arjuna.tools,
com.arjuna.ats.internal.arjuna.utils,
com.arjuna.ats.internal.arjuna.objectstore,
com.arjuna.common.internal.util.propertyservice,
{code}
We should make sure we either provide users with instructions which packages they have to
import to make transactions work, or we have to import them automatically. This issues
needs to be investigated more. The bad thing is that PAX EXAM did not reveal this issue.
Perhaps it uses DynamicImport-Package to import all packages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira