I can't get trunk to run with the current mc/aop snapshots due to this error on startup. Where is {urn:jboss:aop-beans:1.0}lifecycle element handler supposed to be coming from? 01:50:35,765 ERROR [BeanDeployer] Error during deployment: vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/default/deployers/jboss-aop-jboss5.deployer/ org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/default/deployers/jboss-aop-jboss5.deployer/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:121) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:88) at org.jboss.deployers.plugins.deployers.kernel.BeanDeployer.deploy(BeanDeployer.java:59) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:170) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:557) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:495) 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 org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:121) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:110) at org.jboss.profileservice.aop.MainDeployerAspect.process(MainDeployerAspect.java:42) at org.jboss.aop.advice.org.jboss.profileservice.aop.MainDeployerAspect_z_process_127276743.invoke(MainDeployerAspect_z_process_127276743.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at AOPContainerProxy$0.process(AOPContainerProxy$0.java) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:248) at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403) at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342) at org.jboss.Main.boot(Main.java:210) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: {urn:jboss:aop-beans:1.0}lifecycle not found as a child of {urn:jboss:bean-deployer:2.0}deployment at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:187) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:147) at org.jboss.deployers.plugins.deployers.helpers.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:80) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.parse(AbstractParsingDeployer.java:176) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:114) ... 24 more Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {urn:jboss:aop-beans:1.0}lifecycle not found as a child of {urn:jboss:bean-deployer:2.0}deployment at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:283) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:381) 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:183) ... 28 more 01:50:35,818 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/default/deployers/jboss-aop-jboss5.deployer/ -> org.jboss.xb.binding.JBossXBRuntimeException: {urn:jboss:aop-beans:1.0}lifecycle not found as a child of {urn:jboss:bean-deployer:2.0}deployment

-----Original Message----- From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Scott M Stark Sent: 18 January 2007 10:29 To: JBoss.org development list Subject: Re: [jboss-dev] {urn:jboss:aop-beans:1.0}lifecycle problems I was able to get this working by changing the jmx declaration to: <!-- Add the JMX --> <aop:lifecycle-configure xmlns:aop="urn:jboss:aop-beans:1.0" name="JMXAdvice" class="org.jboss.aop.microcontainer.aspects.jmx.JMXIntroduction" classes=&quot;(a)org.jboss.aop.microcontainer.aspects.jmx.JMX&quot; manager-bean="AspectManager" manager-property="aspectManager" pointcut="execution(* @org.jboss.aop.microcontainer.aspects.jmx.JMX->$implements{org .jboss.kernel.spi.dependency.KernelControllerContextAware}(..))"> <property name="mbeanServer"><inject bean="JMXKernel" property="mbeanServer"/></property> </aop:lifecycle-configure> I'm working on gettting trunk in synch with the latest mc snapshot to get the profile service changes I have checked in. Scott M Stark wrote: > I guess its because the aop descriptors are not in synch with this change: > http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002348#... > 48 > > Scott M Stark wrote: >> I can't get trunk to run with the current mc/aop snapshots due to >> this error on startup. Where is {urn:jboss:aop-beans:1.0}lifecycle >> element handler supposed to be coming from? >> _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development