Destroying singletons resutling in bean not found

[Stephane Eybert]

http://cxf.547215.n5.nabble.com/file/n5518443/ajater.txt ajater.txt 

I have a puzzling one here, a bean that seems to be defined and cache and
retrieved all right, is then not found.

The web application is deployed just fine on the Tomcat container, with the
cxf.xml file being loaded all right.

And the exception occurs when the client sends in its web service request.

I can see in the log some beans being destroyed. I wonder why is that.

Here is my configuration:

<beans xmlns="http://www.springframework.org/schema/beans";
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
        xsi:schemaLocation="http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans.xsd";>

        <bean id="userAccreditation"
class="no.nki.sesam.ws.common.security.UserAccreditation">
                <property name="userAccountService" ref="userAccountService" />
        </bean>

        <bean id="helloService"
class="no.nki.sesam.ws.common.service.impl.HelloServiceImpl">
        </bean>

</beans>

  <bean id="wss4jInInterceptor"
class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor">
    <property name="properties">
      <map>
        <entry key="action" value="UsernameToken"/>
        <entry key="passwordType" value="PasswordDigest" />
        <entry>
          <key>
            <value>passwordCallbackRef</value>
          </key>
          <ref bean="userAccreditation"/>
        </entry>
      </map>
    </property>
  </bean>

I wonder why is the cxf.xml file being loaded again when the client sends a
request.

It was already loaded fine at server startup time when the web application
was deployed in the Tomcat container.

Stephane

--
View this message in context: 
http://cxf.547215.n5.nabble.com/Destroying-singletons-resutling-in-bean-not-found-tp5518443p5518443.html
Sent from the cxf-user mailing list archive at Nabble.com.