WS_Stack_API
WS Stack API provides the contract between J2EE Server and particular Web Service Stack technology.
WS Stack API describes WS Stack features supported by particular J2EE Server.
WS Stack API also provides the list of libraries - jar files - related to particular WS Stack
that represents the subset of J2EE Server libraries included in J2EE Server classpath.
WS Stack API consists of SPI part (intended to implement by J2EE Server plugin) and API part (used by particular WS Stack support)
See:
Description
WS_Stack_API
WS Stack API provides the contract between J2EE Server and particular Web Service Stack technology.
WS Stack API describes WS Stack features supported by particular J2EE Server.
WS Stack API also provides the list of libraries - jar files - related to particular WS Stack
that represents the subset of J2EE Server libraries included in J2EE Server classpath.
WS Stack API consists of SPI part (intended to implement by J2EE Server plugin) and API part (used by particular WS Stack support)
Use Cases
WS Stack API is a contract between J2EE Server and IDE support for particular Web Service technology. The API is used to
separate web services capabilities, of J2EE Server, from other J2EE Server features.
On other side, a specific web service support in IDE doesn't have to comunicate with entire J2EE Server but only with the part describing
the particular web service technology available in particular J2EE Server.
Use cases:
JAX-WS Stack in GlassFish
GlassFish supports JSR109 deployment style for JAX-WS technology.
GlassFish plugin creates a WS Stack object for JAX-WS technology and sets JSR_109 feature to true.
The IDE support for JAX-WS obtains the WS Stack object from target J2EE Server lookup and knows that JSR109 deployment is supported.
(WSDL file is generated automatically by the server from WS Metadata annotations)
JAX-RPC Stack in GlassFish
GlassFish supports JAX-RPC 1.6 technology. GlassFish plugin creates a WS Stack object for JAX-RPC technology
and provides information about jar files containing JAX-RPC runtime for wscompile tool.
IDE support for JAX-RPC obtains this WS Stack object from J2EE Server lookup and uses those (server) jar files in wscompile ant tasks
generated by this support.
JAX-WS Stack in Tomcat
Tomcat supports JAX-WS technology. However it doesn't support JSR109 deployment style.
Tomcat plugin creates s WS Stack containing information that JSR109 is not suported.
Exported Interfaces
This table lists all of the module exported APIs
with
defined stability classifications. It is generated
based on answers to questions about the architecture
of the module. Read them all...
Group of java interfaces
Interface Name | In/Out | Stability | Specified in What Document? |
WS_Stack_API | Exported | Friend |
...//wiki.netbeans.org/WebServicesServerApi
WS Stack API provides the contract between J2EE Server and particular Web Service Stack technology.
WS Stack API describes WS Stack features supported by particular J2EE Server.
WS Stack API also provides the list of libraries - jar files - related to particular WS Stack
that represents the subset of J2EE Server libraries included in J2EE Server classpath.
WS Stack API consists of SPI part (intended to implement by J2EE Server plugin) and API part (used by particular WS Stack support)
|
|
Implementation Details
Where are the sources for the module?
The sources for the module are in the
NetBeans Mercurial repositories.
What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?
nothing
Read more about the implementation in the answers to
architecture questions.