[jbossws-issues] [JBoss JIRA] Updated: (JBWS-299) Tools: "NoDataBinding" option for doc/literal Web Services

[Darran Lofthouse (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBWS-299?page=all ]

Darran Lofthouse updated JBWS-299:
----------------------------------

    Fix Version/s: jbossws-2.0.1
                       (was: jbossws-2.0.0)

> Tools: "NoDataBinding" option for doc/literal Web Services
> ----------------------------------------------------------
>
>                 Key: JBWS-299
>                 URL: http://jira.jboss.com/jira/browse/JBWS-299
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>          Components: wstools
>            Reporter: Anil Saldhana
>         Assigned To: Darran Lofthouse
>            Priority: Optional
>             Fix For: jbossws-2.0.1
>
>
> wscompile has an option "-f:nodatabinding"  that turns off data binding in the input parameters and return types for doc/lit web services. More information is available in the feature matrix. That info is copy/pasted here:
>  
>  wscompile uses this option to turn off data binding for literal encoding. This is a very important option when dealing with doc/literal wsdl files.  Let us take an example of a web service that returns employee data.  
>  
> The SEI generated by wscompile will look as follows: 
> public interface EmployeeQuery extends Remote {             
>   public double getSalary() throws RemoteException;
>   public String getManagerName(int level) throws RemoteException;
> }
> Now if the -f:nodatabinding option is used, the generated SEI will not have any typed arguments or return types, but they will all be mapped to javax.xml.soap.SOAPElement  (xsd:any  equivalent).
> public interface EmployeeQuery extends Remote {             
>   public javax.xml.soap.SOAPElement getSalary() throws RemoteException;
>   public javax.xml.soap.SOAPElement getManagerName(javax.xml.soap.SOAPElement level) throws RemoteException;
> }
> Supported by jbossws with the "nodatabinding" attribute in the <wsdltojava> element.
> A point to be noted is the user will have to use SAAJ to construc  messages to invoke the webservice and has to decode the return message (if any) using SAAJ.

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