<bean name="WSInjectionMetaDataDeploymentAspect" class="org.jboss.wsf.container.jboss50.deployment.metadata.InjectionMetaDataDeploymentAspect"> | <property name="requires">WebMetaData</property> | <property name="provides">InjectionMetaData</property> | <property name="ejbReferenceResolver"><inject bean="org.jboss.ejb3.EjbReferenceResolver"/></property> | </bean> I did not find the definition for the org.jboss.ejb3.EjbReferenceResolver bean within that jbossws-deployer-jboss-beans.xml. Does this mean that JBossWS will rely on EJB3 deployer jboss-beans.xml to deploy an EjbReferenceResolver? :) I would recommend that you define your own EjbReferenceResolver (with a unique MC bean name) within JBossWS to ensure that any changes to the EJB3 deployer will not affect JBossWS. Something like: <bean name="WSInjectionMetaDataDeploymentAspect" class="org.jboss.wsf.container.jboss50.deployment.metadata.InjectionMetaDataDeploymentAspect"> | <property name="requires">WebMetaData</property> | <property name="provides">InjectionMetaData</property> | <property name="ejbReferenceResolver"><inject bean="EJBReferenceResolverForWS"/></property> | </bean> | | <bean name="EJBReferenceResolverForWS" class="org.jboss.ejb3.common.resolvers.spi.EjbReferenceResolver"> | <constructor factoryClass="org.jboss.ejb3.common.resolvers.spi.EjbReferenceResolverFactory" | factoryMethod="newInstance"> | <parameter>org.jboss.ejb3.common.resolvers.plugins.FirstMatchEjbReferenceResolver</parameter> | </constructor> | </bean> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228657#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...