2 ejb3s exposed as web services. Can't have same methods wit

[sursha]

Hello,
I've 2 ejb3s exposed as 2 separate web services. They are packaged in the same ear file.
I use the WebContext annotation to keep the context root same for 2 services.

I've a method, authenticate(String userName) in one ejb and
authenticate(String userName, String password) in the other ejb.
When I deploy the ear file, I get the error as follows:

Looks like there is a name collision. It is complaining about the first ejb not having
password as a parameter. Any one seen this issue?


by: org.jboss.ws.WSException: password is not a valid property on class com.xxx.services.MyService1.v2.jaxws.Authenticate
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccessor(JAXBContextImpl.java:816)
at org.jboss.ws.metadata.acessor.JAXBAccessor$1$1.create(JAXBAccessor.java:84)
at org.jboss.ws.metadata.umdm.ParameterMetaData.eagerInitialize(ParameterMetaData.java:472)
at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:466)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:516)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:502)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:490)
at org.jboss.ws.metadata.umdm.ServiceMetaData.eagerInitialize(ServiceMetaData.java:429)
at org.jboss.ws.metadata.umdm.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:192)
at org.jboss.ws.core.server.ServiceEndpoint.start(ServiceEndpoint.java:112)
at org.jboss.ws.core.server.ServiceEndpointManager.startServiceEndpoint(ServiceEndpointManager.java:646)
at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:140)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndpoint(DeployerInterceptor.java:144)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:96)

[thomas.diesler]

Is this even related to 2 ejb3s?
i.e. can you deploy a single endpoint that uses authenticate(String userName, String password) ?

[sursha]

Thanks for looking into it.
If I have authenticate(String userName, String password) only in one endpoint/1 ejb3, it works.
If I have authenticate(String userName, String password) and authenticate(String userName) in one endpoint/1 ejb3, it did not work.
I thought authenticate(String userName, String password) in 1 endpoint/1 ejb3 and authenticate(String userName) in different endpoint/ejb3 should work. But it did not work. Both ejb3s were packaged into the same ear file.
Since both ejb3's have different name spaces, I thought it should work, but it did not !!
Am I missing something? Your help will be appreciated.

[dlofthouse]

You say your endpoints are in the same ear but are they also both in the same jar or in different jars?

[sursha]

Both ejbs are in the same jar.

[thomas.diesler]

Could you please create a jira issue and attach a test case that allows us to reproduce what you are seeing.

Maybe you can even find out why this is.

http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source

[sursha]

Created JIRA issue JBWS-1799.

[richard_opalka]

Issue was fixed. See:

http://jira.jboss.org/jira/browse/JBWS-1799

for possible workarounds untill next release will be available for download.

Richard

[ropalka]

This problem will no be fixed in next release, because it's not JAX-WS compliant.
To prevent your problem please use:

@RequestWrapper(className="package.UniqueClassName")
@ResponseWrapper(className="package.UniqueClassNameResponse")

method annotations on your second bean authenticate() method.

Richard

[ropalka]

Updated FAQ document, see:

http://jbws.dyndns.org/mediawiki/index.php?title=FAQ#Why_I.27m_getting_.22propertyname_is_not_valid_property_on_class_mypackage.jaxws.Propertyname.22.3F

Richard