[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2892) Conflicting operations in 2 WS within the same archive and package

[Martin Vecera (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBWS-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Vecera updated JBWS-2892:
--------------------------------

    Attachment: Quickstart_helloworld_ejb3.jar


> Conflicting operations in 2 WS within the same archive and package
> ------------------------------------------------------------------
>
>                 Key: JBWS-2892
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2892
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions:  jbossws-native-3.1.2
>            Reporter: Martin Vecera
>            Priority: Critical
>         Attachments: Quickstart_helloworld_ejb3.jar
>
>
> I have two web services with the sayHello() operation. The first WS requires a string parameter, the second does not have any. Both WS are in the same package (see the attached jar). The following exception is thrown when you try to deploy it. If the services are deployed as two separate archives, the problem disappears.
> org.jboss.ws.WSException: arg0 is not a valid property on class org.jboss.soa.esb.samples.quickstart.helloworld_ejb3.jaxws.SayHello
>         at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccessor(JAXBContextImpl.java:936)
>         at org.jboss.ws.metadata.accessor.JAXBAccessorFactory.create(JAXBAccessorFactory.java:49)
>         at org.jboss.ws.metadata.umdm.EndpointMetaData.createAccessor(EndpointMetaData.java:715)
>         at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeAccessors(EndpointMetaData.java:671)
>         at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:543)
>         at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:531)
>         at org.jboss.ws.metadata.umdm.ServiceMetaData.eagerInitialize(ServiceMetaData.java:433)
>         at org.jboss.ws.metadata.umdm.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:194)
>         at org.jboss.wsf.stack.jbws.EagerInitializeDeploymentAspect.start(EagerInitializeDeploymentAspect.java:48)
>         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)
>         ... 24 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira