Home/ Questions/Q 3616332
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T22:29:10+00:00

I have my application running properly in Jboss. To to write spring webservice client,

  • 0

I have my application running properly in Jboss. To to write spring webservice client, i have generated classes using wsimport. I have written following in configuration

 <bean id="messageFactory" class="org.springframework.ws.soap.saaj.SaajSoapMessageFactory">
<property name="messageFactory">
    <bean class="com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl"/>
</property>

in jboss?lib i have jboss-jaxws.jar,spring.jar…Now i copied 

spring-ws-1.5.0.jar and  saaj-impl-1.3.jar

but i am getting follwoing errors:

The Spring ContextLoaderListener we wrap threw on contextInitialized.
But for our having caught this error, the web application context would not have initialized.
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/applicationContext.xml]; nested exception is java.lang.IllegalArgumentException: Class [org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not implement the NamespaceHandler interface
Caused by: 
java.lang.IllegalArgumentException: Class [org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not implement the NamespaceHandler interface
    at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.initHandlerMappings(DefaultNamespaceHandlerResolver.java:119)

Please help me to resolve this error. These errors i am getting only after keeping these jars. But these required to run my new code. Please suggest me how to avoid them?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You could create WEB-INF/jboss-web.xml file for your application with next content

    <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss-web PUBLIC
    "-//JBoss//DTD Web Application 4.2//EN"
    "http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd">
<jboss-web>
    <class-loading java2ClassLoadingCompliance="false">
        <loader-repository>
                   myapp:loader=anyUniqueName
            <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
        </loader-repository>
    </class-loading>
</jboss-web>

    This should prevent classloader from looking for JBoss libs. As a downside you’ll have to provide all your 3rd-party jars in a WAR/lib folder.

    This works for 4.2 you could lookup something similar for version you currently use.

    • 0