[jboss-user] [Microcontainer] - lifecycle-configure not found as a child of {urn:jboss:bean-
i'm using JBossMC 2.0.0.Beta4 with JBossaop 2.0.0.beta1.
With the following configuration:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <deployment xmlns="urn:jboss:bean-deployer:2.0">
|
| <bean name="MBeanServer" class="java.lang.Object">
| <constructor
factoryClass="org.jboss.jms.server.microcontainer.factory.mBeanServerCreator"
| factoryMethod="createMBeanServer"/>
| </bean>
|
| <aop:lifecycle-configure xmlns:aop="urn:jboss:aop-beans:1.0"
| name="DependencyAdvice"
|
class="org.jboss.aop.microcontainer.aspects.jmx.JMXLifecycleCallback"
|
classes="(a)org.jboss.aop.microcontainer.aspects.jmx.JMX">
| <property name="mbeanServer">
| <inject bean="MBeanServer"/>
| </property>
| </aop:lifecycle-configure>
|
| <bean class="com.arjuna.ats.jbossatx.jta.TransactionManagerService"
| name="TransactionManager">
| <property name="transactionTimeout">300</property>
| <property
name="objectStoreDir">tx-object-store</property>
|
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=TransactionManager",
|
exposedInterface=com.arjuna.ats.jbossatx.jta.TransactionManagerServiceMBean.class
| </annotation>
| </bean>
|
| </deployment>
|
i get the following error:
| Exception in thread "main" java.lang.RuntimeException: Exception during
Bootstrap
| at
org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:99)
| at
org.jboss.jms.server.microcontainer.JBMBootstrapServer.main(JBMBootstrapServer.java:67)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
| Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source:
file:/home/andy/projects/Branch_Andy_MC_Integration/src/etc/META-INF/mbeansupport.xml@13,86
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:164)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:133)
| at
org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXMLDeployer.java:86)
| at
org.jboss.jms.server.microcontainer.JBMBootstrapServer.deploy(JBMBootstrapServer.java:130)
| at
org.jboss.jms.server.microcontainer.JBMBootstrapServer.bootstrap(JBMBootstrapServer.java:105)
| at
org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
| ... 6 more
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException:
{urn:jboss:aop-beans:1.0}lifecycle-configure not found as a child of
{urn:jboss:bean-deployer:2.0}deployment
| at
org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:280)
| at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:323)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
| at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
| at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:160)
| ... 11 more
|
Anyone have any ideas?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094441#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...