You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Chris Custine (JIRA)" <ji...@apache.org> on 2009/10/12 07:35:53 UTC

[jira] Created: (SMX4NMR-162) ClassNotFoundException on Spring PlatformTransactionManager after restart

ClassNotFoundException on Spring PlatformTransactionManager after restart
-------------------------------------------------------------------------

                 Key: SMX4NMR-162
                 URL: https://issues.apache.org/activemq/browse/SMX4NMR-162
             Project: ServiceMix NMR
          Issue Type: Bug
    Affects Versions: 1.1.0
            Reporter: Chris Custine
            Assignee: Chris Custine
            Priority: Critical


JBI Deployer and JBI OSGi are getting this exception on restarts when deployed in features:
java.lang.ClassNotFoundException: org.springframework.transaction.PlatformTransactionManager

It looks like the greedy proxy in the blueprint recipe for those bundles will require an import on org.springframework.transaction.PlatformTransactionManager.

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


[jira] Commented: (SMX4NMR-162) ClassNotFoundException on Spring PlatformTransactionManager after restart

Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/SMX4NMR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54707#action_54707 ] 

Chris Custine commented on SMX4NMR-162:
---------------------------------------

Oddly, this exception only happens in Felix.  Equinox seems to work just fine, even though there it seems clear that these bundles need the additional import.  Fixed so that it works in Felix as well.

> ClassNotFoundException on Spring PlatformTransactionManager after restart
> -------------------------------------------------------------------------
>
>                 Key: SMX4NMR-162
>                 URL: https://issues.apache.org/activemq/browse/SMX4NMR-162
>             Project: ServiceMix NMR
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Chris Custine
>            Assignee: Chris Custine
>            Priority: Critical
>             Fix For: 1.1.0
>
>
> JBI Deployer and JBI OSGi are getting this exception on restarts when deployed in features:
> java.lang.ClassNotFoundException: org.springframework.transaction.PlatformTransactionManager
> It looks like the greedy proxy in the blueprint recipe for those bundles will require an import on org.springframework.transaction.PlatformTransactionManager.

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


[jira] Resolved: (SMX4NMR-162) ClassNotFoundException on Spring PlatformTransactionManager after restart

Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SMX4NMR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Custine resolved SMX4NMR-162.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.0

> ClassNotFoundException on Spring PlatformTransactionManager after restart
> -------------------------------------------------------------------------
>
>                 Key: SMX4NMR-162
>                 URL: https://issues.apache.org/activemq/browse/SMX4NMR-162
>             Project: ServiceMix NMR
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Chris Custine
>            Assignee: Chris Custine
>            Priority: Critical
>             Fix For: 1.1.0
>
>
> JBI Deployer and JBI OSGi are getting this exception on restarts when deployed in features:
> java.lang.ClassNotFoundException: org.springframework.transaction.PlatformTransactionManager
> It looks like the greedy proxy in the blueprint recipe for those bundles will require an import on org.springframework.transaction.PlatformTransactionManager.

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