cxf

CXF JCA Connector in JBOSS 7.1 (or 6.1) not supported?

懵懂的女人 提交于 2021-01-29 04:08:24
问题 we are migrating our application from JBoss 5 to JBoss 6 and there is one thing I can't figure out. We are using Apache CXF-JCA resource adapter (CXF-JCA home page). They say it is implementig JCA 1.5 specs and that seems to be a problem. Because JBoss is implementing JCA specs version 1.6 CXF's deployment fails because of following: Caused by: org.jboss.jca.validator.ValidatorException: Severity: ERROR Section: 19.4.2 Description: A ResourceAdapter must implement a "public boolean equals

How to exclude transitive dependency

*爱你&永不变心* 提交于 2021-01-28 12:16:26
问题 I use JavaMail in the same project with cxf. cxf brings an older version of JavaMail which does not suit me. How to excluded? I did so: compile (group: 'org.apache.cxf', name: 'cxf-rt-bindings-soap', version: apacheCfxVersion) { exclude module: 'geronimo-javamail_1.4_spec' } But it did not help. I find in the war WEB-INF \ lib \ geronimo-javamail_1.4_spec-1.6.jar 回答1: Try this: configurations { all*.exclude module: 'geronimo-javamail_1.4_spec' } 来源: https://stackoverflow.com/questions

Apache CXF Plugin - Failure Generating Client

梦想与她 提交于 2021-01-28 03:54:43
问题 I am trying to generate a webservice client using the Apache CXF Maven plugin but I am running into errors. I just have a very simple maven project setup in eclipse The wsdl file is located here - http://api.zenfolio.com/api/1.8/zfapi.asmx?wsdl The pom file I am using is as follows <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

[javax.xml.bind.UnmarshalException: unexpected element

三世轮回 提交于 2021-01-27 07:42:28
问题 When invkoing a webservice, I get the following exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:"urn:partner.soap.sforce.com", local:"metadataServerUrl"). Expected elements are <{}sessionId>,<{}sandbox>,<{}userId>,<{}passwordExpired>,<{}metadataServerUrl>,<{}userInfo>,<{}serverUrl>] The response expected is actually an object called LoginResult. But however I see the element names in the exception strace. The loginResult class is the expected output object from the

[javax.xml.bind.UnmarshalException: unexpected element

ぐ巨炮叔叔 提交于 2021-01-27 07:42:01
问题 When invkoing a webservice, I get the following exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:"urn:partner.soap.sforce.com", local:"metadataServerUrl"). Expected elements are <{}sessionId>,<{}sandbox>,<{}userId>,<{}passwordExpired>,<{}metadataServerUrl>,<{}userInfo>,<{}serverUrl>] The response expected is actually an object called LoginResult. But however I see the element names in the exception strace. The loginResult class is the expected output object from the

[javax.xml.bind.UnmarshalException: unexpected element

岁酱吖の 提交于 2021-01-27 07:41:45
问题 When invkoing a webservice, I get the following exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:"urn:partner.soap.sforce.com", local:"metadataServerUrl"). Expected elements are <{}sessionId>,<{}sandbox>,<{}userId>,<{}passwordExpired>,<{}metadataServerUrl>,<{}userInfo>,<{}serverUrl>] The response expected is actually an object called LoginResult. But however I see the element names in the exception strace. The loginResult class is the expected output object from the

Purpose of cxf-rt-transports-http-jetty

空扰寡人 提交于 2021-01-27 04:52:31
问题 I want to understand the purpose of below dependency while developing cxf webservices. <dependency> <groupId>org.apache.cxf</groupId> <artifactId>cxf-rt-transports-http-jetty</artifactId> <version>3.1.7</version> </dependency> Without adding this dependency CXF simple frontend doesn't create the service. Thanks, 回答1: Jetty provides a Web server and javax.servlet container for your CXF services. Adding the dependency above is like embedding the container into your application. Alternatively,

JBoss EAP 7 exclude webservices subsystem gives NoClassDefFoundError: Failed to link EndpointDefinitionParser$SpringEndpointImpl

廉价感情. 提交于 2021-01-03 07:09:03
问题 In Jboss EAP7 I have added cxf maven dependencies in pom.xml and excluded webservices subsystem in jboss-deployment-structure.xml since want to use my own version of cxf defined in pom.xml. But get below exception during server start up- Caused by: org.springframework.beans.FatalBeanException: Invalid NamespaceHandler class [org.apache.cxf.jaxws.spring.NamespaceHandler] for namespace [http://cxf.apache.org/jaxws]: problem with handler class file or dependent class; nested exception is java

JBoss EAP 7 exclude webservices subsystem gives NoClassDefFoundError: Failed to link EndpointDefinitionParser$SpringEndpointImpl

末鹿安然 提交于 2021-01-03 07:08:25
问题 In Jboss EAP7 I have added cxf maven dependencies in pom.xml and excluded webservices subsystem in jboss-deployment-structure.xml since want to use my own version of cxf defined in pom.xml. But get below exception during server start up- Caused by: org.springframework.beans.FatalBeanException: Invalid NamespaceHandler class [org.apache.cxf.jaxws.spring.NamespaceHandler] for namespace [http://cxf.apache.org/jaxws]: problem with handler class file or dependent class; nested exception is java

JBoss EAP 7 exclude webservices subsystem gives NoClassDefFoundError: Failed to link EndpointDefinitionParser$SpringEndpointImpl

╄→гoц情女王★ 提交于 2021-01-03 07:08:22
问题 In Jboss EAP7 I have added cxf maven dependencies in pom.xml and excluded webservices subsystem in jboss-deployment-structure.xml since want to use my own version of cxf defined in pom.xml. But get below exception during server start up- Caused by: org.springframework.beans.FatalBeanException: Invalid NamespaceHandler class [org.apache.cxf.jaxws.spring.NamespaceHandler] for namespace [http://cxf.apache.org/jaxws]: problem with handler class file or dependent class; nested exception is java