• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Axis2 Generation - Multiple WSDL Ports

 
Scott Selikoff
author
Saloon Keeper
Posts: 4020
18
Eclipse IDE Flex Google Web Toolkit
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Consider the following WSDL outline:


When I run Axis2 code generation on it (org.apache.axis2.wsdl.WSDL2Java), the Stub it generates "WidgetServiceStub" only contains methods for one of the ports above. For example, in one generation I only have methods defined in Sale port. But if I remove this definition, the generation then contains methods only for Trade or Sell ports. The one it chooses seems order irrelevant.

Is there some obvious reason it only wants to generate one port per service? Do I need to change the command-line parameters to WSDL or does the WSDL to need to be restructured?
[ May 16, 2008: Message edited by: Scott Selikoff ]
 
Scott Selikoff
author
Saloon Keeper
Posts: 4020
18
Eclipse IDE Flex Google Web Toolkit
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Actually reviewing through some documentation, it seems like I can specify the port using the "-pn portname" on generation. But what if I have a client application in which I want to use all 3 Sale/Buy/Trade services? Is there a way to generate it with everything? What's the common solution in this type of environment?
 
Michael Ernest
High Plains Drifter
Sheriff
Posts: 7292
Netbeans IDE VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Scott Selikoff:
Actually reviewing through some documentation, it seems like I can specify the port using the "-pn portname" on generation. But what if I have a client application in which I want to use all 3 Sale/Buy/Trade services? Is there a way to generate it with everything? What's the common solution in this type of environment?

The likely solution here is to get the bug in your tool fixed. There are multiple WSDL code generators out there that did/do not support multiple port types for a single service, even though the WSDL spec calls it out plainly enough.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic