You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Ryan Bohn (JIRA)" <ji...@apache.org> on 2007/12/14 22:53:26 UTC
[jira] Created: (SM-1175) spring-jmx is dependent on spring-aop and
needs included in the servicemix/lib directory
spring-jmx is dependent on spring-aop and needs included in the servicemix/lib directory
----------------------------------------------------------------------------------------
Key: SM-1175
URL: https://issues.apache.org/activemq/browse/SM-1175
Project: ServiceMix
Issue Type: Bug
Affects Versions: 3.2.1
Reporter: Ryan Bohn
The spring-aop jar needs included in the servicemix/lib directory because spring-jmx is dependent on it. I get the following error when trying to use the InterfaceBasedMBeanInfoAssembler:
java.lang.NoClassDefFoundError: org/springframework/aop/support/AopUtils
at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getTargetClass(AbstractMBeanInfoAssembler.java:94)
at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getClassName(AbstractMBeanInfoAssembler.java:131)
at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getMBeanInfo(AbstractMBeanInfoAssembler.java:64)
I tried including the jar in just my service unit, but still received the error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1175) spring-jmx is dependent on spring-aop
and needs included in the servicemix/lib directory
Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Custine resolved SM-1175.
-------------------------------
Resolution: Fixed
Fix Version/s: 3.3
3.2.2
> spring-jmx is dependent on spring-aop and needs included in the servicemix/lib directory
> ----------------------------------------------------------------------------------------
>
> Key: SM-1175
> URL: https://issues.apache.org/activemq/browse/SM-1175
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 3.2.1
> Reporter: Ryan Bohn
> Assignee: Chris Custine
> Fix For: 3.2.2, 3.3
>
>
> The spring-aop jar needs included in the servicemix/lib directory because spring-jmx is dependent on it. I get the following error when trying to use the InterfaceBasedMBeanInfoAssembler:
> java.lang.NoClassDefFoundError: org/springframework/aop/support/AopUtils
> at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getTargetClass(AbstractMBeanInfoAssembler.java:94)
> at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getClassName(AbstractMBeanInfoAssembler.java:131)
> at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getMBeanInfo(AbstractMBeanInfoAssembler.java:64)
> I tried including the jar in just my service unit, but still received the error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1175) spring-jmx is dependent on spring-aop
and needs included in the servicemix/lib directory
Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41308#action_41308 ]
Chris Custine commented on SM-1175:
-----------------------------------
See SM-1145
> spring-jmx is dependent on spring-aop and needs included in the servicemix/lib directory
> ----------------------------------------------------------------------------------------
>
> Key: SM-1175
> URL: https://issues.apache.org/activemq/browse/SM-1175
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 3.2.1
> Reporter: Ryan Bohn
> Assignee: Chris Custine
> Fix For: 3.2.2, 3.3
>
>
> The spring-aop jar needs included in the servicemix/lib directory because spring-jmx is dependent on it. I get the following error when trying to use the InterfaceBasedMBeanInfoAssembler:
> java.lang.NoClassDefFoundError: org/springframework/aop/support/AopUtils
> at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getTargetClass(AbstractMBeanInfoAssembler.java:94)
> at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getClassName(AbstractMBeanInfoAssembler.java:131)
> at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getMBeanInfo(AbstractMBeanInfoAssembler.java:64)
> I tried including the jar in just my service unit, but still received the error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1175) spring-jmx is dependent on spring-aop and
needs included in the servicemix/lib directory
Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Custine updated SM-1175:
------------------------------
Assignee: Chris Custine
> spring-jmx is dependent on spring-aop and needs included in the servicemix/lib directory
> ----------------------------------------------------------------------------------------
>
> Key: SM-1175
> URL: https://issues.apache.org/activemq/browse/SM-1175
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 3.2.1
> Reporter: Ryan Bohn
> Assignee: Chris Custine
>
> The spring-aop jar needs included in the servicemix/lib directory because spring-jmx is dependent on it. I get the following error when trying to use the InterfaceBasedMBeanInfoAssembler:
> java.lang.NoClassDefFoundError: org/springframework/aop/support/AopUtils
> at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getTargetClass(AbstractMBeanInfoAssembler.java:94)
> at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getClassName(AbstractMBeanInfoAssembler.java:131)
> at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getMBeanInfo(AbstractMBeanInfoAssembler.java:64)
> I tried including the jar in just my service unit, but still received the error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.