-
1. Re: @WebMethod @WebParam: no effect on generated wsdl.
I've read on (http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg115272.html)
that the operationName attribute of @WebMethod and @WebParam is being ignored.
Is this still the case? or is there some update I can use where this is fixed?
Kristof. -
2. Re: @WebMethod @WebParam: no effect on generated wsdl.
I'm having good luck with the following style in JBoss-5:
@Stateless @WebService (name = "TestInterface", serviceName = "TestService", targetNamespace = "urn:TestService/wsdl") @PortComponent (contextRoot = Constants.WEBSERVICE_DOCLITERAL_URLROOTCONTEXT, urlPattern = "/TestService") @SOAPBinding (style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED) public class TestBean implements TestInterface { /** * Returns the provided String * @param sessionID A valid session ID * @param input String value to return * @return The input value */ @WebMethod(operationName = "echoString", action = "urn:EchoString") @WebResult(name = "echoStringResult") @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) public String echoString( @WebParam(name = "sessionID") String sessionID, @WebParam(name = "input") String input) { return input; } }
The variable "Constants.WEBSERVICE_DOCLITERAL_URLROOTCONTEXT" in my case can be set to something like:
"/test"
... which means the WSDL URL would be:
"http://serveraddress:8080/test/TestService?wsdl"
Hope this helps! -
3. Re: @WebMethod @WebParam: no effect on generated wsdl.
http://jira.jboss.org/jira/browse/JBWS-1157
Note, @RequestWrapper is not yet supported in jbossws-1.0.3