1 Reply Latest reply on Jan 31, 2005 6:31 AM by Thomas Diesler

    Unable to deploy with a custom container configuration

    Steven Wisener Newbie

      Using JBoss 4.0.1, I get an error when attempting to deploy with a custom container configuration:

      org.jboss.deployment.DeploymentException: Failed to find InvokerProxyBindingMetaData for: 'session-webservice-invoker'. Check the invoker-proxy-binding-name to invoker-proxy-binding/name mappings in jboss.xml
      


      standardjboss.xml doesn't even define a session-webservice-invoker invoker proxy binding... The only thing I'm trying to do in my custom container configuration is add an interceptor. Here's the relevant portion from jboss.xml:

      <container-configurations>
       <container-configuration extends="Standard Stateless SessionBean">
       <container-name>My Custom Stateless SessionBean</container-name>
       <container-interceptors>
       <interceptor>my.custom.Interceptor</interceptor>
       <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
       <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
       <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
       <!-- CMT -->
       <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
       <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
       <interceptor transaction="Container" metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
       <interceptor transaction="Container">org.jboss.webservice.server.ServiceEndpointInterceptor</interceptor>
       <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
       <!-- BMT -->
       <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
       <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor>
       <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
       <interceptor transaction="Bean" metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
       <interceptor transaction="Bean">org.jboss.webservice.server.ServiceEndpointInterceptor</interceptor>
       <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
       </container-interceptors>
       </container-configuration>
      </container-configurations>
      


      This is just a cut and paste of the container interceptors from standardjboss.xml with my own interceptor added. All session beans will deploy properly with this configuration exception the service endpoints. The service endpoints will deploy properly with the standard container configuration. I have not changed standardjboss.xml in any way. Any ideas on why JBoss is looking for session-webservice-invoker?