Show TOC Start of Content Area

Background documentation Restrictions to Web Service Implementation Beans  Locate the document in its SAP Library structure

In the endpoint of a Web service, you must not use any of the following types anywhere

      A class extending another class and at the same time implementing an interface.

Note

There is an exception to this rule when a class implements any of the marker interfaces listed below (the exception is explained in the entry for the marker interfaces in the table below).

      Hashed table-like types.

      Classes/objects that cannot be serialized.

Supported Types in Web Service Implementation Beans

The following types from java*.packages are supported in endpoints of Web services:

Simple Types Wrappers

java.lang.Void

java.lang.Boolean

java.lang.Byte

java.lang.Short

java.lang.Integer

java.lang.Long

java.lang.Float

java.lang.Double

java.lang.String

Marker Interfaces

java.io.Serializable

java.lang.Cloneable

java.lang.Comparable

Note

A class can implement any of these interfaces and extend another class. Also, a class can implement two interfaces, one of them being any of the interfaces listed here,

Array classes

java.util.ArrayList

java.util.HashSet

java.util.LinkedList

java.util.List

java.util.Stack

java.util.Vector

Date/Time

java.util.Calendar                 

java.util.Date                       

java.util.GregorianCalendar   

java.sql.Time                            

java.sql.Timestamp             

javax.xml.datatype.XMLGregorianCalendar

Long numbers

java.math.BigInteger

java.math.BigDecimal

Exception

java.lang.Exception

java.rmi.RemoteException

Object

java.lang.Object

Other

javax.xml.namespace.QName          

java.util.UUID                      

java.net.URI                        

java.awt.Image                    

javax.xml.datatype.Duration 

javax.xml.transform.Source  

javax.activation.DataHandler

java.util.HashMap                      

java.util.Collection

 

 

End of Content Area