Hi Stephen,
My jboss.xml used to have message driven beans as well as session beans defined. I had gone through the link (https://docs.jboss.org/author/display/AS71/jboss-ejb3.xml+Reference)
for migrating from jboss.xml to jboss-ejb3.xml. It only discusses about message driven beans,not the sesions beans. I tried to create this file. Please find the attachment and let me know if it's the right way to do.I am also attaching the ejb-jar.xml and jboss-webservices.xml ( removed the webservice.xml with jboss-webservices.xml file since it is not supported in AS 7). May be I am doing something wrong since I get the very same error of missing dependencies.The server log is given below---
15:29:18,586 INFO [com.performix.module.configuration.MesEnvironment] (MSC service thread 1-2) Executing static part.. Adding chars
15:29:18,624 INFO [com.performix.module.configuration.MesEnvironment] (MSC service thread 1-2) Configuration Already Present. Not Adding.
15:29:18,626 INFO [com.performix.module.configuration.MesEnvironment] (MSC service thread 1-2) :: Testing All Methods ::
15:29:18,663 INFO [com.performix.module.configuration.MesEnvironment] (MSC service thread 1-2) Default Chartericstic already created.
15:29:18,665 INFO [com.performix.module.configuration.MesEnvironment] (MSC service thread 1-2) Session Closed in MesEnvironment
15:29:18,729 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-2) Add Service
id=B2MMLInterfaceBean
address=http://localhost:3390/servicelayer/B2MMLInterfaceBean
implementor=com.performix.servicelayer.interfacemanager.B2MMLInterfaceBean
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://interfacemanager.servicelayer.performix.com/}B2MMLInterfaceBeanService
portName={http://interfacemanager.servicelayer.performix.com/}B2MMLInterfaceBeanPort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.subunit."xmes.ear"."servicelayer.jar".component.B2MMLInterfaceBean.VIEW."com.performix.servicelayer.interfacemanager.B2MMLInterfaceBean".SERVICE_ENDPOINT]
15:29:19,560 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://interfacemanager.servicelayer.performix.com/}B2MMLInterfaceBeanService from class com.performix.servicelayer.interfacemanager.B
15:29:23,224 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:3390/servicelayer/B2MMLInterfaceBean
15:29:23,684 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-2) WSDL published to: file:/D:/trunkV79JBoss7/external/tools/jboss-as-7.1.0.Final/standalone/data/wsdl/xmes.ear/servicelayer.jar/B2MMLInterfaceBeanService.wsdl
15:29:23,704 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.port-component-link
15:29:23,749 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."xmes.ear"."servicelayer.jar".B2MMLInterfaceBean
15:29:23,776 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /servicelayer
15:29:23,784 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=servicelayer,endpoint=B2MMLInterfaceBean
15:29:23,788 ERROR [org.jboss.as] (MSC service thread 1-2) JBAS015875: JBoss AS 7.1.0.Final "Thunder" started (with errors) in 122414ms - Started 1312 of 1440 services (38 services failed or missing dependencies, 87 services are passive or on-demand)
15:29:23,995 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "xmes.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.xmes.m
15:29:24,033 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015540: Stopping service jboss.ws.endpoint."xmes.ear"."servicelayer.jar".B2MMLInterfaceBean
15:29:24,092 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-3) remove: jboss.ws:context=servicelayer,endpoint=B2MMLInterfaceBean
15:29:24,038 INFO [com.performix.module.integration.systemevent.SystemEventManager] (MSC service thread 1-1) WindowsEventMessage content as - [xMES Server Shutdown at time 31-May-2013 15:29]
15:29:24,122 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015540: Stopping service jboss.ws.port-component-link
15:29:24,127 INFO [stdout] (MSC service thread 1-1) xMES WARN MSG - Call received for Windows Event = [XMES_SERVER_DOWN]
15:29:24,151 WARN [Evt] (MSC service thread 1-1) XMES_SERVER_DOWN : xMES Server Shutdown at time 31-May-2013 15:29
15:29:24,152 INFO [stdout] (MSC service thread 1-1) Updated event log time
15:29:24,372 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment mes-engine.jar in 374ms
15:29:24,374 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment OperatorUI_EJB.jar in 376ms
15:29:24,390 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment servicelayer.jar in 392ms
15:29:24,875 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment OperatorUI_Services.war in 877ms
15:29:27,744 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment adminui.war in 3746ms
15:29:28,660 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment xmes.ear in 4664ms
15:29:28,663 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.naming.context.java.jboss.resources.ConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.xmes.mes-engine."com.performix.mes.integration.PlanMgrMessageRouter".env.ConnectionFactory, service jboss.naming.context.j
service jboss.naming.context.java.jboss.resources.jms.topic.xMESTopicPlanMgrMessage (missing) dependents: [service jboss.naming.context.java.comp.xmes.mes-engine."com.performix.mes.integration.PlanMgrMessageRouter".env.jms.topic.xMESTopicPlanMgrMessage
service jboss.naming.context.java.jboss.resources.jms.topic.xMESTopicSystemEventMsg (missing) dependents: [service jboss.naming.context.java.comp.xmes.mes-engine."com.performix.mes.integration.SystemEventMessageRouter".env.jms.topic.xMESTopicSystemEven
service jboss.naming.context.java.jboss.resources.jms.topic.xMesTopicEvent (missing) dependents: [service jboss.naming.context.java.comp.xmes.mes-engine."com.performix.mes.integration.EventRouter".env.jms.topic.xMesTopicEvent, service jboss.naming.cont
service jboss.naming.context.java.jboss.resources.jms.topic.xMesTopicEventForMsgToOpUi (missing) dependents: [service jboss.naming.context.java.comp.xmes.OperatorUI_EJB."com.performix.integration.MiniPodMessageRouter".env.jms.topic.xMesTopicEventForMsg
service jboss.naming.context.java.jboss.resources.jms.topic.xMesTopicHistory (missing) dependents: [service jboss.naming.context.java.comp.xmes.mes-engine."com.performix.mes.integration.HistoryMessageRouter".env.jms.topic.xMesTopicHistory]
service jboss.naming.context.java.jboss.resources.jms.topic.xMesTopicOpcServer1Read (missing) dependents: [service jboss.naming.context.java.comp.xmes.mes-engine."com.performix.mes.integration.OpcMessageRouter".env.jms.topic.xMesTopicOpcServer1Read]
service jboss.naming.context.java.jboss.resources.jms.topic.xMesTopicPhaseSignal (missing) dependents: [service jboss.naming.context.java.comp.xmes.mes-engine."com.performix.mes.integration.PhaseMessageRouter".env.jms.topic.xMesTopicPhaseSignal]
service jboss.naming.context.java.jboss.resources.jms.topic.xMesTopicUi (missing) dependents: [service jboss.naming.context.java.comp.xmes.mes-engine."com.performix.mes.integration.UiMessageRouter".env.jms.topic.xMesTopicUi]
15:29:28,703 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies
=> ["jboss.naming.context.java.comp.xmes.mes-engine.\"com.performix.mes.integration.UiMessageRouter\".env.jms.topic.xMesTopicUijboss.naming.context.java.jboss.resources.jms.topic.xMesTopicUiMissing[jboss.naming.context.java.comp.xmes.mes-engine.\"com.
As you can see from the above logs there are some routers defined which are basically message driven beans which get started before webservices get started .Please find the logs below--
15:27:44,121 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'com.performix.mes.integration.EventRouter' with 'hornetq-ra' resource adapter
15:27:44,125 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'com.performix.mes.integration.PhaseMessageRouter' with 'hornetq-ra' resource adapter
15:27:44,129 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'com.performix.mes.integration.PlanMgrMessageRouter' with 'hornetq-ra' resource adapter
15:27:44,135 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'com.performix.mes.integration.UiMessageRouter' with 'hornetq-ra' resource adapter
15:27:44,139 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'com.performix.mes.integration.OpcMessageRouter' with 'hornetq-ra' resource adapter
15:27:44,142 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'com.performix.mes.integration.HistoryMessageRouter' with 'hornetq-ra' resource adapter
15:27:44,146 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'com.performix.mes.integration.SystemEventMessageRouter' with 'hornetq-ra' resource adapter
15:27:44,204 WARNING [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unable to process deployment descriptor for context '/MESServices'
Regards
Sachin