Deprecated Methods |
com.sun.xml.ws.model.AbstractSEIModelImpl.applyParameterBinding(WSDLBoundPortTypeImpl)
To be removed once client side new architecture is implemented |
com.sun.xml.ws.api.server.WSEndpoint.create(Class, boolean, Invoker, QName, QName, Container, WSBinding, SDDocumentSource, Collection extends SDDocumentSource>, EntityResolver)
|
com.sun.xml.ws.api.pipe.TubelineAssemblerFactory.create(ClassLoader, BindingID)
Use TubelineAssemblerFactory.create(ClassLoader, BindingID, Container) |
com.sun.xml.ws.api.pipe.TransportPipeFactory.create(ClassLoader, ClientPipeAssemblerContext)
Use TransportTubeFactory.create(ClassLoader, ClientTubeAssemblerContext) |
com.sun.xml.ws.api.message.Messages.create(Marshaller, Object, SOAPVersion)
Use Messages.create(JAXBRIContext, Object, SOAPVersion) |
com.sun.xml.ws.api.message.Headers.create(SOAPVersion, Element)
Use Headers.create(Element) |
com.sun.xml.ws.api.message.Headers.create(SOAPVersion, Marshaller, Object)
Use Headers.create(JAXBRIContext, Object) instead. |
com.sun.xml.ws.api.server.InstanceResolver.createDefault(Class, boolean)
This is added here because a Glassfish integration happened
with this signature. Please do not use this. Will be removed
after the next GF integration. |
com.sun.xml.ws.api.message.Packet.createResponse(Message)
Use createClientResponse(Message) for client side and
createServerResponse(Message, String) for server side response
creation. |
com.sun.xml.ws.api.streaming.XMLStreamWriterFactory.createXMLStreamWriter(OutputStream)
Use XMLStreamWriterFactory.create(OutputStream) |
com.sun.xml.ws.api.streaming.XMLStreamWriterFactory.createXMLStreamWriter(OutputStream, String)
Use XMLStreamWriterFactory.create(OutputStream, String) |
com.sun.xml.ws.api.streaming.XMLStreamWriterFactory.createXMLStreamWriter(OutputStream, String, boolean)
Use XMLStreamWriterFactory.create(OutputStream, String) . The boolean flag was unused anyway. |
com.sun.xml.ws.developer.StatefulWebServiceManager.export(Class, String, T)
This method is provided as a temporary workaround, and we'll eventually try to remove it. |
com.sun.xml.ws.api.message.HeaderList.get(QName)
Use HeaderList.get(QName) |
com.sun.xml.ws.api.message.HeaderList.get(String, String)
Use HeaderList.get(String, String, boolean) |
com.sun.xml.ws.api.addressing.AddressingVersion.getAnonymousUri()
Use AddressingVersion.anonymousUri |
com.sun.xml.ws.api.message.Packet.getApplicationScopePropertyNames(boolean)
Use Packet.getHandlerScopePropertyNames(boolean) .
To be removed once Tango components are updated. |
com.sun.xml.ws.client.PortInfo.getBindingID()
Only meant to be used via PortInfo .
Use PortInfo.bindingId . |
com.sun.xml.ws.api.message.Packet.getEndPointAddressString()
The programatic acccess should be done via
Packet.endpointAddress . This is for JAX-WS client applications
that access this property via BindingProvider.ENDPOINT_ADDRESS_PROPERTY . |
com.sun.xml.ws.client.RequestContext.getEndPointAddressString()
always access RequestContext.endpointAddress . |
com.sun.xml.ws.api.message.Packet.getHeaderList()
This method is for exposing header list through PropertySet.get(Object) ,
for user applications, and should never be invoked directly from within the JAX-WS RI. |
com.sun.xml.ws.api.message.HeaderList.getHeaders(String)
use HeaderList.getHeaders(String, boolean) . |
com.sun.xml.ws.api.message.HeaderList.getHeaders(String, String)
Use HeaderList.getHeaders(String, String, boolean) |
com.sun.xml.ws.model.JavaMethodImpl.getInputParametersCount()
no longer use in the new architecture |
com.sun.xml.ws.api.addressing.AddressingVersion.getNoneUri()
Use AddressingVersion.noneUri . |
com.sun.xml.ws.api.addressing.AddressingVersion.getNsUri()
Use AddressingVersion.nsUri . |
com.sun.xml.ws.client.PortInfo.getPortName()
Only meant to be used via PortInfo .
Use PortInfo.portName . |
com.sun.xml.ws.model.AbstractSEIModelImpl.getQNameForJM(JavaMethodImpl)
Use JavaMethod.getOperationName() . |
com.sun.xml.ws.transport.http.WSHTTPConnection.getRequestHeaders()
This is a potentially expensive operation.
Programs that want to access HTTP headers should consider using
other methods such as WSHTTPConnection.getRequestHeader(String) . |
com.sun.xml.ws.client.PortInfo.getServiceName()
Only meant to be used via PortInfo .
Use WSServiceDelegate.getServiceName() . |
com.sun.xml.ws.model.WrapperParameter.isWrapperStyle()
Why are you calling a method that always return true? |
com.sun.xml.ws.transport.http.servlet.ServletAdapter.publishWSDL(ServletContext, HttpServletRequest, HttpServletResponse)
Use ServletAdapter.handle(ServletContext, HttpServletRequest, HttpServletResponse) |
com.sun.xml.ws.message.AbstractHeaderImpl.readAsJAXB(Bridge, BridgeContext)
|
com.sun.xml.ws.api.message.HeaderList.remove(int)
HeaderList is monotonic and you can't remove anything. |
com.sun.xml.ws.api.message.HeaderList.remove(Object)
HeaderList is monotonic and you can't remove anything. |
com.sun.xml.ws.api.message.HeaderList.removeAll(Collection>)
HeaderList is monotonic and you can't remove anything. |
com.sun.xml.ws.api.message.HeaderList.retainAll(Collection>)
HeaderList is monotonic and you can't remove anything. |
com.sun.xml.ws.api.pipe.Fiber.run()
|
com.sun.xml.ws.api.wsdl.writer.WSDLGeneratorExtension.start(TypedXmlWriter, SEIModel, WSBinding, Container)
|
com.sun.xml.ws.api.server.InstanceResolver.start(WebServiceContext)
Use InstanceResolver.start(WSWebServiceContext,WSEndpoint) . |
com.sun.xml.ws.api.server.Invoker.start(WebServiceContext)
Use Invoker.start(WSWebServiceContext,WSEndpoint) |
com.sun.xml.ws.util.ByteArrayBuffer.toByteArray()
this method causes a buffer reallocation. Use it only when
you have to. |
com.sun.xml.ws.api.message.HeaderList.understood(Header)
By the deifnition of ArrayList , this operation requires
O(n) search of the array, and thus inherently inefficient.
Because of this, if you are developing a Pipe for
a performance sensitive environment, do not use this method. |