9:06 a.m.
Daniel Cote [https://community.jboss.org/people/daniel.cote.qc.ca] created the discussion
"Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802369#802369
--------------------------------------------------------------
Hi forum,
I'm taking the chance to put here an entry refering to my previous post made on the
more general 'Jboss AS 7' community ( https://community.jboss.org/thread/222322
cxf.xml and spring and jbossws-cxf-4.1.1.Final)
Since the topic is really related to the Web service stack, I hope I'll can get back
some additional clues...
To summarize:
I my quest to make my webservice client working with a specific configuration, I did
upgrate my JBOSS 7.1.1 final with jbossws-cxf-4.1.1.Final.
I did the upgrate using instructions provider in
https://community.jboss.org/docs/DOC-13545
https://community.jboss.org/wiki/JBossWS-Installation.
* I'm working with JBOSS 7.1.1 final. I updated the jboss-cxf stack to
*jbossws-cxf-4.1.1.Final*, including the installation of spring, using *-Dspring=true
option*, which I found is required in order for my cxf.xml file to be recognized by the
runtime.
* the declaration of the springs schemas NOT recognized by my current installation. When
I shutdowm my network services, I can see the attempt to resolve the schemas failed
because the definition, included in the
..jboss-as-7.1.1.Final\modules\org\apache\cxf\impl\main jars file are NOT correctly
resolved (hence the fallback on the http).
Ex.:
23:45:47,303 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
23:45:48,270 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/http-conf.xsd
23:45:48,676 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/wsdl/http-conf.xsd
23:45:48,926 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd
...
Are all going through the network instead of using the provided schemas (example:
...jboss-as-7.1.1.Final\modules\org\apache\cxf\impl\main\cxf-rt-transports-http.jar\schemas\configuration\
contains the http-conf.xsd... and the spring.schemas defines the location).
* the namespace handlers, declared in the
.jboss-as-7.1.1.Final\modules\org\apache\cxf\impl\main jars file are NOT correctly
resolved as we can see in the following trace, where the runtime was unable to locate the
*NameSpace handler,* altough this specifc handler is exposed by the
jboss-as-7.1.1.Final\modules\org\apache\cxf\impl\main\cxf-rt-transports-http.jar\META-INF\spring.handlers
08:42:20,168 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.prepareRefresh Refreshing
org.apache.cxf.bus.spring.BusApplicationContext@31906846: startup date [Wed Mar 13
08:42:20 EDT 2013]; root of context hierarchy
08:42:20,184 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Loaded configuration
file cxf.xml.
08:42:20,184 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Creating application
context with resources: [class path resource [META-INF/cxf/cxf.xml], class path resource
[cxf.xml]]
08:42:20,184 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions
Loading XML bean definitions from class path resource [META-INF/cxf/cxf.xml]
08:42:20,184 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions
Loading XML bean definitions from class path resource [cxf.xml]
08:42:20,184 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
08:42:20,932 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/http-conf.xsd
08:42:21,307 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/wsdl/http-conf.xsd
08:42:21,556 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd
08:42:22,134 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/parameterized-types.xsd
08:42:22,258 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/security.xsd
08:42:22,383 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/cxf-beans.xsd
08:42:22,524 WARN (http-localhost-127.0.0.1-8080-1)
org.jboss.ws.cxf.createApplicationContext JBWS024027: Spring initial application context
creation failed using classloader org.jboss.ws.common.utils.DelegateClassLoader@719b072f,
will try again after having switched the current thread context classloader to
ModuleClassLoader for Module "org.apache.cxf.impl:main" from local module loader
@7b41aa25 (roots: C:\AppServer\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\modules):
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration
problem: U*nable to locate Spring NamespaceHandler for XML schema namespace
[http://cxf.apache.org/transports/http/configuration]*
*Offending resource: class path resource [cxf.xml]*
at
org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
[spring-beans.jar:3.0.7.RELEASE]
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
[spring-beans.jar:3.0.7.RELEASE]
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:80)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:284)
[spring-beans.jar:3.0.7.RELEASE]
...
* Those inabilities to resolve the NamespaceHandler and the provided schemas seems to
indicate a problem of classloading, which is very difficult (for me) to diagnose.
* I followed some suggestions regarding the use of
EAR\META-INF\jboss-deployment-structure.xml, but none resolved the classloading problems.
I tried the followings
jboss-deployment-structure.xml with no dependencies, except the ones required by my
application (oracle driver, configuration parameters)
jboss-deployment-structure.xml with:
<module name="org.apache.cxf" export="true">
<imports>
<include path="META-INF**"/>
<include path="org**"/>
</imports>
</module>
jboss-deployment-structure.xml with:
<module name="org.apache.cxf" export="true">
<imports>
<include path="META-INF**"/>
<include path="org**"/>
</imports>
</module>
jboss-deployment-structure.xml with:
<module name="org.springframework.spring"
export="true">
<imports>
<include path="META-INF**"/>
<include path="org**"/>
</imports>
</module>
<module name="org.apache.cxf" export="true">
<imports>
<include path="META-INF**"/>
<include path="org**"/>
</imports>
</module>
jboss-deployment-structure.xml with:
<module name="org.jboss.ws.cxf.jbossws-cxf-client"
export="true">
</module>
(this one did NOT retrieve my cxf.xml configuration file...)
* Until now, I worked a lot to make thinks working using only a configuration file and the
JAX-WS api, but if I cannot resolve this issue, I will have to fall back on using the CXF
api directly
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802369#802369]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
9:55 a.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Alessio Soldano [https://community.jboss.org/people/asoldano] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802384#802384
--------------------------------------------------------------
Please note that after having installed JBossWS 4.1.1.Final on top of JBoss AS
7.1.1.Final, the org/apache/cxf module is changed, in particular you'll see that you
have 2 modules: org.apache.cxf and org.apache.cxf.impl. The latter should include the
schema you're looking for, so try modifying the module name in your
jboss-deployment-structure.xml accordingly.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802384#802384]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:40 a.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Daniel Cote [https://community.jboss.org/people/daniel.cote.qc.ca] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802400#802400
--------------------------------------------------------------
Hi Alessio, (I'm so happy you replied!!! there is still some hope...)
I've already tried this option with no result.
Just to be certain, I reconducted the test. Here the differents elements:
* EAR\META-INF\jboss-deployment-structure.xml
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
<deployment>
<dependencies>
<module name="com.oracle" export="true" />
<module name="com.logibec.parameters" export="true"
/> <!-- parameters -->
<module name="org.apache.cxf.impl" export="true">
<imports>
<include path="META-INF**"/>
<include path="org**"/>
</imports>
</module>
</dependencies>
</deployment>
</jboss-deployment-structure>
* The trace file shows the same problem occuring (both access to the http version for the
*.xsd resources and the inability to resolve the NamespaceHandler
11:34:25,190 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Loaded configuration
file cxf.xml.
11:34:25,190 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Creating application
context with resources: [class path resource [META-INF/cxf/cxf.xml], class path resource
[cxf.xml]]
11:34:25,190 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions
Loading XML bean definitions from class path resource [META-INF/cxf/cxf.xml]
11:34:25,190 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions
Loading XML bean definitions from class path resource [cxf.xml]
11:34:25,190 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
11:34:25,845 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/http-conf.xsd
11:34:26,266 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/wsdl/http-conf.xsd
11:34:26,485 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd
11:34:26,750 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/parameterized-types.xsd
11:34:26,859 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/security.xsd
11:34:28,450 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/cxf-beans.xsd
11:34:28,669 WARN (http-localhost-127.0.0.1-8080-1)
org.jboss.ws.cxf.createApplicationContext JBWS024027: Spring initial application context
creation failed using classloader org.jboss.ws.common.utils.DelegateClassLoader@2fc4db5e,
will try again after having switched the current thread context classloader to
ModuleClassLoader for Module "org.apache.cxf.impl:main" from local module loader
@a377714 (roots: C:\AppServer\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\modules):
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration
problem: Unable to locate Spring NamespaceHandler for XML schema namespace
[http://cxf.apache.org/transports/http/configuration]
Offending resource: class path resource [cxf.xml]
at
org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
[spring-beans.jar:3.0.7.RELEASE]
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
[spring-beans.jar:3.0.7.RELEASE]
...
dc
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802400#802400]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
11:47 a.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Alessio Soldano [https://community.jboss.org/people/asoldano] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802420#802420
--------------------------------------------------------------
Hi Daniel,
I don't have an answer yet for your issue, but I'm collecting info to try figuring
out what's happening.
So, first of all the WARNING JBWS024027 basically means that an initial attempt of
creating the a spring application context failed, so another try is being done with a
different thread context classloader; so my first question is, do you get any other
exception/log about error besides the the JBWS024027 above? If not, that would mean the
following creation of the application context succeeds. In any case it will help in
nailing down the problem...
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802420#802420]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:09 p.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Daniel Cote [https://community.jboss.org/people/daniel.cote.qc.ca] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802425#802425
--------------------------------------------------------------
Hi Alessio,
Thanks again!
TO my knowledge, no other weid situation occured... After the error, the stack fallback to
another classloader and the process resumes, but a lost my hability to configure my
outgoing call.
Here more context:
1) a web service call is received. No jboss specific information associated with this
endpoint. (see trace at 12:39:50,115)
2) In it's logic, the webservice must issues an outgoing soap call. For this step, a
jax-ws client is setup and we issue an invoke. It it this outgoing call that requires the
cxf.xml configuration to adapt to the requirements (specific certificate, truststore,
keystore, etc.) (start at 12:39:50,520)
3) the stacks get the exception trying to configure the call, using the cxf.xml, and
fallback on another classloader (12:39:54,280) and the fallback at (
2:39:54,358 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.prepareRefresh )
4) this outgoing calls don't benefit from my cxf.xml configuration, and abort because
does not meet the specifics...
Here the trace:
12:39:50,115 INFO (http-localhost-127.0.0.1-8080-1)
com.ibm.ai.xds.webContext.XDSHandler.Msg from: [ 127.0.0.1] target -->
http://localhost:8080/XDSRepositoryWS/DocumentRepository_Service
action:[urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b]
12:39:50,115 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.jaxws.handler.logical.LogicalHandlerInInterceptor@61aaeb72
12:39:50,115 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor@3a68a674
12:39:50,115 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.jaxb.attachment.JAXBAttachmentSchemaValidationHack@7b9955a8
12:39:50,115 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.interceptor.URIMappingInterceptor@1ee1d1de
12:39:50,115 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.interceptor.URIMappingInterceptor.handleMessage Invoking HTTP method POST
12:39:50,115 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.interceptor.URIMappingInterceptor.handleMessage URIMappingInterceptor can
only handle HTTP GET, not HTTP POST
12:39:50,115 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.interceptor.DocLiteralInInterceptor@6c15a383
12:39:50,130 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.binding.soap.interceptor.SoapHeaderInterceptor@a224e5
12:39:50,130 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.jboss.wsf.stack.cxf.interceptor.NsCtxSelectorStoreInterceptor@3ba7c498
12:39:50,130 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl@2ad5ddb4
12:39:50,130 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.ws.addressing.ContextUtils.retrieveMAPs retrieving MAPs from context
property javax.xml.ws.addressing.context.inbound
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.ws.addressing.ContextUtils.retrieveMAPs current MAPs [MessageId:
urn:uuid:EA4DB7A6C734B9ECC21363192789822, Action:
urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b, To:
http://localhost:8080/XDSRepositoryWS/DocumentRepository_Service]
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.ws.addressing.MAPAggregator.getMAPs MAPs retrieved from message [MessageId:
urn:uuid:EA4DB7A6C734B9ECC21363192789822, Action:
urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b, To:
http://localhost:8080/XDSRepositoryWS/DocumentRepository_Service]
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.ws.addressing.ContextUtils.retrieveMAPs retrieving MAPs from context
property javax.xml.ws.addressing.context.inbound
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.ws.addressing.ContextUtils.retrieveMAPs current MAPs [MessageId:
urn:uuid:EA4DB7A6C734B9ECC21363192789822, Action:
urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b, To:
http://localhost:8080/XDSRepositoryWS/DocumentRepository_Service]
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.ws.addressing.ContextUtils.storeMAPs associating MAPs with context property
javax.xml.ws.addressing.context.inbound
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.ws.addressing.ContextUtils.storeMAPs associating MAPs with context property
javax.xml.ws.addressing.context.inbound
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.interceptor.OneWayProcessorInterceptor@7f0732b3
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.jaxws.interceptors.WrapperClassInInterceptor@3191c6ec
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.jaxws.interceptors.SwAInInterceptor@411aeb95
12:39:50,146 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.jaxws.interceptors.HolderInInterceptor@599ac960
12:39:50,162 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.ws.policy.PolicyVerificationInInterceptor@33d4351c
12:39:50,162 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.ws.policy.PolicyVerificationInInterceptor.handle Verified policies for
inbound message.
12:39:50,162 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept Invoking handleMessage on
interceptor org.apache.cxf.interceptor.ServiceInvokerInterceptor@35bf5c1
12:39:50,162 INFO (http-localhost-127.0.0.1-8080-1)
com.ibm.ai.xds.convertor.GenericEbxmlV3Convertor.constructor.. first invocation...
12:39:50,302 WARN (http-localhost-127.0.0.1-8080-1) com.ai.utils.BaseParms.getInstance
Instance [EbxmlMappingConfiguration.xml] has been updated... Launching refresh
12:39:50,318 INFO (http-localhost-127.0.0.1-8080-1)
com.ibm.ai.xds.convertor.EbxmlConfiguration.specific_reload
12:39:50,318 INFO (http-localhost-127.0.0.1-8080-1)
com.ibm.ai.xds.convertor.EbxmlConfiguration.initialize
12:39:50,333 WARN (http-localhost-127.0.0.1-8080-1) com.ai.utils.BaseParms.getInstance
Instance [OrchestrationConfig.xml] has been updated... Launching refresh
12:39:50,349 WARN (http-localhost-127.0.0.1-8080-1) com.ai.utils.BaseParms.getInstance
Instance [XUAConfig.xml] has been updated... Launching refresh
12:39:50,364 WARN (http-localhost-127.0.0.1-8080-1) com.ai.utils.BaseParms.getInstance
Instance [RepositoryConfig.xml] has been updated... Launching refresh
12:39:50,380 WARN (http-localhost-127.0.0.1-8080-1)
com.ibm.ai.xds.xua.XUAOperations.validateXUA could not find getSamlAssertion header in the
context
12:39:50,380 INFO (http-localhost-127.0.0.1-8080-1)
com.ibm.ihii.repository.sm.impl.DocumentDAO.create document of size 36
12:39:50,396 INFO (http-localhost-127.0.0.1-8080-1)
com.ibm.ihii.repository.sm.RepositoryDAO.create Repository entry UniqueId:
1.2.3.4.5513.30846
12:39:50,520 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.prepareRefresh Refreshing
org.apache.cxf.bus.spring.BusApplicationContext@7bdd6068: startup date [Wed Mar 13
12:39:50 EDT 2013]; root of context hierarchy
12:39:50,536 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.TunedDocumentLoader.<clinit> FastInfoset not found on
classpath. Disabling context load optimizations.
12:39:50,552 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Loaded configuration
file cxf.xml.
12:39:50,552 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Creating application
context with resources: [class path resource [META-INF/cxf/cxf.xml], class path resource
[cxf.xml]]
12:39:50,552 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions
Loading XML bean definitions from class path resource [META-INF/cxf/cxf.xml]
12:39:50,567 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions
Loading XML bean definitions from class path resource [cxf.xml]
12:39:50,614 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
12:39:51,300 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/http-conf.xsd
12:39:51,675 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/wsdl/http-conf.xsd
12:39:51,924 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd
12:39:52,408 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/parameterized-types.xsd
12:39:52,548 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/security.xsd
12:39:54,124 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://cxf.apache.org/schemas/configuration/cxf-beans.xsd
12:39:54,280 WARN (http-localhost-127.0.0.1-8080-1)
org.jboss.ws.cxf.createApplicationContext JBWS024027: Spring initial application context
creation failed using classloader org.jboss.ws.common.utils.DelegateClassLoader@70d6dbc8,
will try again after having switched the current thread context classloader to
ModuleClassLoader for Module "org.apache.cxf.impl:main" from local module loader
@a377714 (roots: C:\AppServer\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\modules):
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration
problem: Unable to locate Spring NamespaceHandler for XML schema namespace
[http://cxf.apache.org/transports/http/configuration]
Offending resource: class path resource [cxf.xml]
at
org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
[spring-beans.jar:3.0.7.RELEASE]
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
[spring-beans.jar:3.0.7.RELEASE]
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:80)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:284)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1335)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1328)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:135)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390)
[spring-beans.jar:3.0.7.RELEASE]
at
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.doLoadBeanDefinitions(ControlledValidationXmlBeanDefinitionReader.java:115)
[cxf-rt-core.jar:2.6.4]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
[spring-beans.jar:3.0.7.RELEASE]
at
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.internalLoadBeanDefinitions(ControlledValidationXmlBeanDefinitionReader.java:154)
[cxf-rt-core.jar:2.6.4]
at
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.access$000(ControlledValidationXmlBeanDefinitionReader.java:66)
[cxf-rt-core.jar:2.6.4]
at
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader$1.run(ControlledValidationXmlBeanDefinitionReader.java:141)
[cxf-rt-core.jar:2.6.4]
at
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader$1.run(ControlledValidationXmlBeanDefinitionReader.java:140)
[cxf-rt-core.jar:2.6.4]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_17]
at
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions(ControlledValidationXmlBeanDefinitionReader.java:139)
[cxf-rt-core.jar:2.6.4]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
[spring-beans.jar:3.0.7.RELEASE]
at
org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:122)
[spring-context.jar:3.0.7.RELEASE]
at
org.apache.cxf.bus.spring.BusApplicationContext.loadBeanDefinitions(BusApplicationContext.java:322)
[cxf-rt-core.jar:2.6.4]
at
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
[spring-context.jar:3.0.7.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:467)
[spring-context.jar:3.0.7.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:397)
[spring-context.jar:3.0.7.RELEASE]
at org.apache.cxf.bus.spring.BusApplicationContext$1.run(BusApplicationContext.java:107)
[cxf-rt-core.jar:2.6.4]
at org.apache.cxf.bus.spring.BusApplicationContext$1.run(BusApplicationContext.java:106)
[cxf-rt-core.jar:2.6.4]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_17]
at
org.apache.cxf.bus.spring.BusApplicationContext.<init>(BusApplicationContext.java:105)
[cxf-rt-core.jar:2.6.4]
at
org.apache.cxf.bus.spring.BusApplicationContext.<init>(BusApplicationContext.java:96)
[cxf-rt-core.jar:2.6.4]
at
org.jboss.wsf.stack.cxf.client.configuration.JBossWSSpringBusFactory.createApplicationContext(JBossWSSpringBusFactory.java:119)
[jbossws-cxf-client.jar:4.1.1.Final]
at
org.jboss.wsf.stack.cxf.client.configuration.JBossWSSpringBusFactory.createBus(JBossWSSpringBusFactory.java:78)
[jbossws-cxf-client.jar:4.1.1.Final]
at org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:122)
[cxf-rt-core.jar:2.6.4]
at org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:94)
[cxf-rt-core.jar:2.6.4]
at org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:83)
[cxf-rt-core.jar:2.6.4]
at
org.jboss.wsf.stack.cxf.client.configuration.JBossWSBusFactory.createBus(JBossWSBusFactory.java:54)
[jbossws-cxf-client.jar:4.1.1.Final]
at
org.jboss.wsf.stack.cxf.client.ProviderImpl.setValidThreadDefaultBus(ProviderImpl.java:242)
[jbossws-cxf-client.jar:4.1.1.Final]
at
org.jboss.wsf.stack.cxf.client.ProviderImpl.createServiceDelegate(ProviderImpl.java:164)
[jbossws-cxf-client.jar:4.1.1.Final]
at javax.xml.ws.Service.<init>(Service.java:57)
[jboss-jaxws-api_2.2_spec-2.0.0.Final.jar:2.0.0.Final]
at javax.xml.ws.Service.create(Service.java:721)
[jboss-jaxws-api_2.2_spec-2.0.0.Final.jar:2.0.0.Final]
at com.ibm.ai.xds.soap.SoapClient.callJAXBWS(SoapClient.java:144) [XDSCommun.jar:]
at
com.ibm.ai.xds.client.XDSClient.documentRegistryRegisterDocumentSet(XDSClient.java:424)
[XDSClient.jar:]
at
com.ibm.ihii.repository.server.xdsb.XDSbDocumentRepositoryService.provideAndRegister(XDSbDocumentRepositoryService.java:215)
[XDSRepositoryEJB.jar:]
at
com.ibm.ihii.repository.server.xdsb.XDSbDocumentRepositoryService.provideAndRegister(XDSbDocumentRepositoryService.java:105)
[XDSRepositoryEJB.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_17]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_17]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_17]
at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.7.0_17]
at
org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at
org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at
org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at
org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at
org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at
org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at
org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at
org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32)
[jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:173)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
[jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at
org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72)
[jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at
com.ibm.ihii.repository.server.xdsb.XDSbDocumentRepositoryService$$$view26.provideAndRegister(Unknown
Source) [XDSRepositoryEJB.jar:]
at
com.logibec.ai.xds.repository.DocumentRepository_Port_Soap12Impl.documentRepositoryProvideAndRegisterDocumentSetB(DocumentRepository_Port_Soap12Impl.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_17]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_17]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_17]
at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.7.0_17]
at
org.jboss.ws.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:108)
[jbossws-common.jar:2.1.1.Final]
at org.jboss.wsf.stack.cxf.JBossWSInvoker.performInvocation(JBossWSInvoker.java:149)
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
[cxf-api.jar:2.6.4]
at
org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(AbstractJAXWSMethodInvoker.java:178)
[cxf-rt-frontend-jaxws.jar:2.6.4]
at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:64)
[cxf-rt-frontend-jaxws.jar:2.6.4]
at org.jboss.wsf.stack.cxf.JBossWSInvoker.invoke(JBossWSInvoker.java:129)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
[cxf-api.jar:2.6.4]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.7.0_17]
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.7.0_17]
at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.7.0_17]
at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
[cxf-api.jar:2.6.4]
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:107)
[cxf-api.jar:2.6.4]
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
[cxf-api.jar:2.6.4]
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
[cxf-api.jar:2.6.4]
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:236)
[cxf-rt-transports-http.jar:2.6.4]
at
org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:95)
at
org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156)
at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225)
[cxf-rt-transports-http.jar:2.6.4]
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:145)
[cxf-rt-transports-http.jar:2.6.4]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
[jbossws-spi.jar:2.1.1.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
12:39:54,358 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.prepareRefresh Refreshing
org.apache.cxf.bus.spring.BusApplicationContext@606a1ec2: startup date [Wed Mar 13
12:39:54 EDT 2013]; root of context hierarchy
12:39:54,374 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Creating application
context with resources: [class path resource [META-INF/cxf/cxf.xml]]
12:39:54,374 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions
Loading XML bean definitions from class path resource [META-INF/cxf/cxf.xml]
12:39:54,374 DEBU (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.obtainFreshBeanFactory Bean factory for
org.apache.cxf.bus.spring.BusApplicationContext@606a1ec2:
org.springframework.beans.factory.support.DefaultListableBeanFactory@2a3c98fd: defining
beans
[cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.apache.cxf.bus.spring.BusExtensionPostProcessor];
root of factory hierarchy
12:39:54,389 DEBU (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.initMessageSource Unable to locate
MessageSource with name 'messageSource': using default
[org.springframework.context.support.DelegatingMessageSource@f9b27d9]
12:39:54,405 DEBU (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.initApplicationEventMulticaster Unable to
locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using
default [org.springframework.context.event.SimpleApplicationEventMulticaster@530f0bbf]
12:39:54,405 INFO (http-localhost-127.0.0.1-8080-1)
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons
Pre-instantiating singletons in
org.springframework.beans.factory.support.DefaultListableBeanFactory@2a3c98fd: defining
beans
[cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.apache.cxf.bus.spring.BusExtensionPostProcessor];
root of factory hierarchy
12:39:54,405 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.configuration.spring.ConfigurerImpl.getBeanName Could not determine bean
name for instance of class org.apache.cxf.ws.policy.PolicyAnnotationListener.
12:39:54,420 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.configuration.spring.ConfigurerImpl.getBeanName Could not determine bean
name for instance of class org.apache.cxf.service.factory.FactoryBeanListenerManager.
12:39:54,420 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.configuration.spring.ConfigurerImpl.getBeanName Could not determine bean
name for instance of class org.apache.cxf.ws.policy.PolicyEngineImpl.
12:39:54,420 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.configuration.spring.ConfigurerImpl.getBeanName Could not determine bean
name for instance of class org.apache.cxf.ws.policy.PolicyDataEngineImpl.
12:39:54,420 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.configuration.spring.ConfigurerImpl.getBeanName Could not determine bean
name for instance of class org.apache.cxf.bus.managers.CXFBusLifeCycleManager.
12:39:54,420 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.configuration.spring.ConfigurerImpl.getBeanName Could not determine bean
name for instance of class org.apache.cxf.bus.managers.ServerRegistryImpl.
12:39:54,420 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.configuration.spring.ConfigurerImpl.getBeanName Could not determine bean
name for instance of class org.apache.cxf.management.jmx.InstrumentationManagerImpl.
12:39:54,420 DEBU (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.initLifecycleProcessor Unable to locate
LifecycleProcessor with name 'lifecycleProcessor': using default
[org.springframework.context.support.DefaultLifecycleProcessor@1399aea8]
12:39:54,436 TRAC (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.publishEvent Publishing event in
org.apache.cxf.bus.spring.BusApplicationContext@606a1ec2:
org.springframework.context.event.ContextRefreshedEvent[source=org.apache.cxf.bus.spring.BusApplicationContext@606a1ec2:
startup date [Wed Mar 13 12:39:54 EDT 2013]; root of context hierarchy]
....
Thanks!
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802425#802425]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:36 p.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Alessio Soldano [https://community.jboss.org/people/asoldano] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802431#802431
--------------------------------------------------------------
mmh... I'll probably need to try reproducing this locally.
Btw, did you try something like:
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
<deployment>
<dependencies>
<module name="com.oracle" export="true" />
<module name="com.logibec.parameters" export="true"
/> <!-- parameters -->
<module name="org.apache.cxf.impl" export="true">
<imports>
<include path="META-INF"/>
<include path="META-INF/cxf"/>
</imports>
<exports>
<include path="META-INF"/>
<include path="META-INF/cxf"/>
</exports>
</module>
<module name="org.apache.cxf" export="true">
<imports>
<include path="META-INF"/>
<include path="META-INF/cxf"/>
</imports>
<exports>
<include path="META-INF"/>
<include path="META-INF/cxf"/>
</exports>
</module>
</dependencies>
</deployment>
</jboss-deployment-structure>
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802431#802431]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1:09 p.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Daniel Cote [https://community.jboss.org/people/daniel.cote.qc.ca] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802442#802442
--------------------------------------------------------------
I will...
in a few minutes...
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802442#802442]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1:44 p.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Daniel Cote [https://community.jboss.org/people/daniel.cote.qc.ca] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802450#802450
--------------------------------------------------------------
Ho, it sounds promising....
I have something else that pops out, but I will have to investigate...
The previous problems seems to be resolved!!!
I will get back to you, once I concluded on this episod
Thanks!!!
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802450#802450]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:12 p.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Daniel Cote [https://community.jboss.org/people/daniel.cote.qc.ca] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802470#802470
--------------------------------------------------------------
Here the results:
* the proposed Solution allowed for resolving the "U*nable to locate Spring
NamespaceHandler"* issue
* it did not, at first resolved "ALL" the problems related to the correct
resolution of local *xsd schemas: there were still an issue with the schema
+http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd. This issue was raised
when trying to execute the program without having an access to internet...
+
15:58:17,984 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusEntityResolver.resolveEntity Attempting to resolve systemId
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
15:58:17,984 WARN (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.warning Ignored XML
validation warning: org.xml.sax.SAXParseException; lineNumber: 12; columnNumber: 74;
schema_reference.4: Failed to read schema document
'http://www.springframework.org/schema/beans/spring-beans-2.0.xsd', because 1)
could not find the document; 2) the document could not be read; 3) the root element of the
document is not <xsd:schema>.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:196)
at org.apache.xerces.util.ErrorHandlerWrapper.warning(ErrorHandlerWrapper.java:97)
at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
* being now instructed on how to face with such issu, I simply adapt the jboss deployment
for including the META-INF elements of the module where thoses resources resides (namely
'org.springframework.spring"'). Here the revisited
jboss-deployment-structure
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
<deployment>
<dependencies>
<module name="com.oracle" export="true" />
<module name="com.logibec.parameters" export="true"
/> <!-- parameters -->
<module name="org.apache.cxf.impl" export="true">
<imports>
<include path="META-INF"/>
<include path="META-INF/cxf"/>
</imports>
<exports>
<include path="META-INF"/>
<include path="META-INF/cxf"/>
</exports>
</module>
<module name="org.apache.cxf" export="true">
<imports>
<include path="META-INF"/>
<include path="META-INF/cxf"/>
</imports>
<exports>
<include path="META-INF"/>
<include path="META-INF/cxf"/>
</exports>
</module>
<module name="org.springframework.spring"
export="true">
<imports>
<include path="META-INF"/>
</imports>
<exports>
<include path="META-INF"/>
</exports>
</module>
</dependencies>
</deployment>
</jboss-deployment-structure>
Now the program behaves as expected...
THANKS a LOT Alessio in supporting a newbee.
Best regards
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802470#802470]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
2:19 a.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Alessio Soldano [https://community.jboss.org/people/asoldano] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802557#802557
--------------------------------------------------------------
OK, thanks for the feedback, I'm glad you had it working finally.
This basically confirm that in order for building up such a spring based cxf bus for a
in-container client, the imports and exports for META-INF in cxf and spring modules are
required.
Now, I'm wondering if it's possible to achieve the same by setting a dependencies
on the org.jboss.ws.cxf.jbossws-cxf-client module. In order for making that possible,
I'll have to review the import and exports of the AS modules; will do as part of
https://issues.jboss.org/browse/JBWS-3607 https://issues.jboss.org/browse/JBWS-3607
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802557#802557]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
6 a.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Daniel Cote [https://community.jboss.org/people/daniel.cote.qc.ca] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802620#802620
--------------------------------------------------------------
Hi Alessio,
I did the test, using the following configuration:
+<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">+
+ <deployment>+
+ <dependencies>+
+ <module name="com.oracle" export="true" />+
+ <module name="com.logibec.parameters" export="true"
/> <!-- parameters -->+
+<!--+
+ <module name="org.apache.cxf.impl" export="true">+
+ <imports>+
+ <include path="META-INF"/>+
+ <include path="META-INF/cxf"/>+
+ </imports>+
+ <exports>+
+ <include path="META-INF"/>+
+ <include path="META-INF/cxf"/>+
+ </exports>+
+ </module> +
+ <module name="org.apache.cxf" export="true">+
+ <imports>+
+ <include path="META-INF"/>+
+ <include path="META-INF/cxf"/>+
+ </imports>+
+ <exports>+
+ <include path="META-INF"/>+
+ <include path="META-INF/cxf"/>+
+ </exports>+
+ </module> +
+ <module name="org.springframework.spring"
export="true">+
+ <imports>+
+ <include path="META-INF"/>+
+ </imports>+
+ <exports>+
+ <include path="META-INF"/>+
+ </exports>+
+ </module> +
+ --> +
+* <module name="org.jboss.ws.cxf.jbossws-cxf-client"
export="true">*+
+* <imports>*+
+* <include path="META-INF"/>*+
+* </imports>*+
+* <exports>*+
+* <include path="META-INF"/>*+
+* </exports>*+
+* </module> *+
+ </dependencies>+
+ </deployment>+
+</jboss-deployment-structure>+
The problem, with this configuration, is that it makes MANDATORY to have an
META-INF/cxf/cxf.xml (which I did not managed to setup).
Here the trace file:
+06:54:28,996 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.prepareRefresh Refreshing
org.apache.cxf.bus.spring.BusApplicationContext@5cf70001: startup date [Thu Mar 14
06:54:28 EDT 2013]; root of context hierarchy+
+06:54:29,043 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.TunedDocumentLoader.<clinit> FastInfoset not found on
classpath. Disabling context load optimizations.+
+06:54:29,043 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Loaded configuration
file cxf.xml.+
+06:54:29,058 FINE (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources Creating application
context with resources: [class path resource [META-INF/cxf/cxf.xml], class path resource
[cxf.xml]]+
+06:54:29,058 INFO (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions
Loading XML bean definitions from class path resource [META-INF/cxf/cxf.xml]+
+06:54:29,058 WARN (http-localhost-127.0.0.1-8080-1)
org.apache.cxf.bus.spring.SpringBusFactory.createApplicationContext Initial attempt to
create application context was unsuccessful.:
org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML
document from class path resource [META-INF/cxf/cxf.xml]; nested exception is
java.io.FileNotFoundException: class path resource [META-INF/cxf/cxf.xml] cannot be opened
because it does not exist+
+at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:341)+
+at
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.internalLoadBeanDefinitions(ControlledValidationXmlBeanDefinitionReader.java:154)+
+at
org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.access$000(ControlledValidationXmlBeanDefinitionReader.java:66)+
+...+
In my understanding, this resource should be made optionnal.
Anyway, thanks again.
Ciao
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802620#802620]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
6:07 a.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Alessio Soldano [https://community.jboss.org/people/asoldano] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/802624#802624
--------------------------------------------------------------
OK, no problem, I'll give this stuff a try as soon as I have some time :-)
Ciao e grazie !
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/802624#802624]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:16 a.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Alessio Soldano [https://community.jboss.org/people/asoldano] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/816939#816939
--------------------------------------------------------------
For the records, I've worked a bit on JBWS-3607. There's basically nothing to be
changed on the current modules shipped in the AS, see the brief explanation at
https://issues.jboss.org/browse/JBWS-3607?focusedCommentId=12773037&p...
https://issues.jboss.org/browse/JBWS-3607?focusedCommentId=12773037&p...
and the more in details documentation additions at
https://docs.jboss.org/author/display/JBWS/JBoss+Modules#JBossModules-Spr...
https://docs.jboss.org/author/display/JBWS/JBoss+Modules#JBossModules-Spr...
(now also linked at
https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheC...
https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheC...
)
The use of a jboss-deployment-structure.xml here is required because there's no way to
import META-INF and META-INF/cxf paths using the MANIFEST.MF Dependencies entry.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/816939#816939]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:56 a.m.
New subject: [JBoss Web Services] - Re: Using apache cxf.xml with a jax-ws client
Daniel Cote [https://community.jboss.org/people/daniel.cote.qc.ca] created the discussion
"Re: Using apache cxf.xml with a jax-ws client"
To view the discussion, visit: https://community.jboss.org/message/816967#816967
--------------------------------------------------------------
Oh interesting...
Those documentation items are so essential...
Thanks again for the very helpfull support that allowed me to succeed in the transition
process from another commercial J2EE container to JBoss!
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/816967#816967]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4005
days inactive
4062
days old
13 comments
2 participants
participants (2)
-
Alessio Soldano -
Daniel Cote