2010-11-23 207 views
28

我正在JBoss 5和Java 1.6下开发Web服务。什么可能导致这种异常?以下是我简化的Web服务代码。IllegalAnnotationException:两个类具有相同的XML类型名称

@Stateless 
@WebService() 
public class AccountWS { 

@WebMethod() 
public CreateAccountResponse createAccount(@WebParam(name = "request") CreateAccountRequest request) { 
    return null; 
} 

下面是完整的堆栈跟踪。

16:19:03,421 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/Apps/jbdevstudio/jboss-eap/jboss-as/server/default/deploy/sif_esb.esb/ state=PreReal mode=Manual requiredState=Real 
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/C:/Apps/jbdevstudio/jboss-eap/jboss-as/server/default/deploy/sif_esb.esb/ 
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) 
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177) 
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1440) 
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1158) 
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1099) 
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) 
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633) 
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935) 
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083) 
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985) 
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823) 
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) 
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:782) 
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) 
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) 
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) 
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) 
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) 
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) 
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633) 
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935) 
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083) 
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985) 
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:775) 
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540) 
at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) 
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256) 
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) 
at org.jboss.Main.boot(Main.java:221) 
at org.jboss.Main$1.run(Main.java:556) 
at java.lang.Thread.run(Unknown Source) 
Caused by: java.lang.IllegalStateException: Cannot build JAXB context 
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:984) 
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:151) 
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50) 
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:76) 
at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:69) 
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129) 
at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:76) 
at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60) 
at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:113) 
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) 
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) 
... 29 more 
Caused by: org.jboss.ws.WSException: Failed to create JAXBContext 
at org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:114) 
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:980) 
... 39 more 
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions 
Two classes have the same XML type name "{http://kona.webservice.sif.unidata.com/}createAccountResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them. 
this problem is related to the following location: 
    at com.unidata.sif.kona.account.message.CreateAccountResponse 
    at private com.unidata.sif.kona.account.message.CreateAccountResponse com.unidata.sif.webservice.kona.jaxws.CreateAccountResponse._return 
    at com.unidata.sif.webservice.kona.jaxws.CreateAccountResponse 
this problem is related to the following location: 
    at com.unidata.sif.webservice.kona.jaxws.CreateAccountResponse 

at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102) 
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:448) 
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:297) 
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139) 
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105) 
at org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:108) 
... 40 more 

回答

73

我发现我的问题的原因。

发生此问题的原因是JAX-WS为每种方法生成一个类,并通过级联methodName + "Response"构造类名。在我的情况下,JAX-WS新生成的类将与我的响应对象具有相同的名称。

实施例:

@Stateless 
@WebService() 
public class AccountWS { 

    @WebMethod() 
    public CreateAccountResponse createAccount(@WebParam(name = "request") CreateAccountRequest request) { 
     return null; 
    } 
} 

JAX-WS将产生一个新的类CreateAccountResponse对于具有相同的名称作为响应对象Web方法createAccount

解决方案:

确保响应对象和方法的名称不匹配。同样的事情也适用于方法参数。

9

你必须使用相同的名称(createAccountResponse)和对应的Java类型com.unidata.sif.kona.account.message.CreateAccountResponsecom.unidata.sif.webservice.kona.jaxws.CreateAccountResponse同一个命名空间(http://kona.webservice.sif.unidata.com/)两个XML架构元素。第二个是由WebMethod注释生成的“automagicaly”,它将更容易更改消息元素的XMLType注释。

要解决这个问题,您应该为其中的一个更改name,或者定义两个分开的名称空间(一个用于消息元素,另一个用于WS请求和响应组件)。我建议最后一种方法(两个分开的命名空间)。

即:

1.更改消息元素com.unidata.sif.kona.account.message.CreateAccountResponse的名称。

@XMLType(name="CreateAccountResponseMsg", namespace="http://kona.webservice.sif.unidata.com") 

2.改变在消息元素的命名空间(包com.unidata.sif.kona.account.message

@XMLType(name="CreateAccountResponse", namespace="http://kona.webservice.sif.unidata.com/message") 
+0

类这就是堆栈痕迹试图告诉我我相信。但我不明白的是为什么我的其他Web服务不会抛出这个异常..我检查了其他Web服务,代码或多或少类似。 – 2010-11-23 09:36:38

+0

有了我的信息,我无法告诉你这种不同行为的原因。抱歉。 – 2010-11-23 14:33:42

2

另一种解决方案是使用@WebMethod(operationName="differentFromMethodName")。这甚至会更改客户端上的接口方法名称。 JAX-WS仍然使用SEI的方法名称为wsgen和wsimport生成类;但现在消息元素类与JAX_WS内部生成的不同。

我不想触摸wsgen生成的类(消息元素类)。

2

我得到了同样的错误,但我不能ajust使用@XmlType注释(从库中推出) 那么另一种解决方案是提供一个com.unidata.sif.kona.account.message/package-info.java与下面的代码内

@javax.xml.bind.annotation.XmlSchema(namespace = "http://kona.webservice.sif.unidata.com/") 
package com.sopra.banking.processengine.servicecontract.v1_1.dto; 
相关问题