jQuery in Action, 2nd edition*
The moose likes Web Services and the fly likes Defining optional parameters (elements) for a web services, using a bottow-up approach Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Defining optional parameters (elements) for a web services, using a bottow-up approach" Watch "Defining optional parameters (elements) for a web services, using a bottow-up approach" New topic
Author

Defining optional parameters (elements) for a web services, using a bottow-up approach

Forum Web User
Greenhorn

Joined: Jan 22, 2012
Posts: 2
hello,

Im using IBM RAd/eclipse to create a bottow-up web service. My method have some input and ouput paramteres defnied as classes. Now I need to add a new input parameter but dont want to break compatibility with current clients. So, I need this new input parameter to be an optional parameter.

Is this possible to accomplish using the webservices wizard tool (from eclipe/IBM RAD). MAybe with a anotation or something like that?

thank you,

fwu
Amit Ghorpade
Bartender

Joined: Jun 06, 2007
Posts: 2716
    
    6

You mean to create optional components in your WSDL?


SCJP, SCWCD.
|Asking Good Questions|
Forum Web User
Greenhorn

Joined: Jan 22, 2012
Posts: 2
hello,

I mean that when the webservices wizard reads the input and the output paramters of my method to create a wsdl file, I want some of those parameters as optional in the wsdl file. How can I control this (using the wizard)?

thank you,
fwu
 
 
subject: Defining optional parameters (elements) for a web services, using a bottow-up approach
 
Similar Threads
Learning RAD
how to consume a webservice using axis2
IBM-399 Exam.
Java standalone Client for WebService Creation Problem
Some questions about the Scoped Model Driven interface of Struts 2