Page History

Supports WSDL 1.1

Supports SOAP 1.1 over HTTP

Default

Default

Supports SOAP 1.2 over HTTP

Supports XML over HTTP

Supports HTTPS SOAP binding

Supports SOAP 1.1 over HTTP with MTOM enabled

Supports SOAP 1.2 over HTTP with MTOM enabled

POJO support - JAX-WS 2.0

supports Supports web service deployment (new deployment)

supports Supports web service deployment (expose existing deployed Java EE components as a web service)

supports Supports web.xml is optional

supports Supports wsdl is optional

supports Supports javax.jws.WebService annotation

supports Supports javax.xml.ws.WebServiceProvider annotation

supports Supports web service annotation without web service descriptor file

supports Supports web service descriptor file without annotation

supports Supports web service annotation with web service descriptor file - web service deployment descriptor file overide or enhance web service annotations

SEI is not required

for For servlet based endpoints using web service annotation, enforce full qualified name of the service implmentation bean class must be used as <servlet-link> element in web.xml

serviceName ServiceName attribute of the webservice annotation prefixed with "/" maps to <url-pattern> element in web.xml

no No more than 1 servlet mapping should be specified and the url-pattern must be an exact match pattern.

only Only methods annotated with @WebMethod in the service implmentation bean are exposed to the client

supports Supports optional @PostConstruct or @PreDestroy annotation for lifecycle event callbacks. (p44)

supports Supports @Resource annotation to access message context and security info (p44)

allows Allows a developer able to specify protocol binding on a web service endpoint by using javax.xml.ws.BindingType annotation

Able to ignore JAX-RPC mapping file for JAX-WS projects (p47)

Annotated JAX-WS components may be mixed with deployment descriptor based JAX-RPC components in a module (p47)

supports Supports OASIS XML Cataglos 1.1 specification to be used to resolve web service description document (wsdl/xsd) (p47)

Supports HandlerChian (both logical and protocol types)

  -handlers must be able to transform the SOAP header

  -handlers must be able to transform just parts of the body

  -handlers must be able to just read a message where no additions/modifications to the message is made

  -Supports jacax.jws.HandlerChain annotation

  -Supports handler run after the container has performed the security constraint checks or method level authorization

  -a handler may access the env-entry-names and env-entrys by JNDI lookup.

  -the handler-chain in DD can be processed and the ordering of the handler must be maintained.

publish Publish the service-ref WSDL

publish Publish the deployed WSDL

make Make the required service interface implmentation avail at the JNDI namespace location java:comp/env/service-ref-name. (p135)

deployment Deployment time binding info (for example, bind port-component with port-component-link)

Security - basic auth

Security - symmetric HTTPS

POJO support - JAX-RPC 1.1

JAX-RPC 1.1 based web service apps should continue work and routed to Axis1

EJB support {}Support

supports Supports javax.ejb.stateless annotation

supports Supports optional deployment descriptor file (ejb-jar.xml)

supports Supports wsdl is optional

supports Supports javax.jws.WebService annotation

supports Supports javax.xml.ws.WebServiceProvider annotation

supports Supports web service annotation without web service descriptor file

supports Supports web service descriptor file without annotation

supports Supports web service annotation with web service descriptor file - web service deployment descriptor file overide or enhance web service annotations

supports Supports optional @PostConstruct or @PreDestroy annotation for lifecycle event callbacks. (p44)

supports Supports @Resource annotation to access message context and security info (p44)

allows Allows a developer able to specify protocol binding on a web service endpoint by using javax.xml.ws.BindingType annotation

Supports HandlerChian (both logical and protocol types)

  -handlers must be able to transform the SOAP header

  -handlers must be able to transform just parts of the body

  -handlers must be able to just read a message where no additions/modifications to the message is made

  -Supports jacax.jws.HandlerChain annotation

  -Supports handler run after the container has performed the security constraint checks or method level authorization

  -a handler may access the env-entry-names and env-entrys by JNDI lookup.

  -the handler-chain in DD can be processed and the ordering of the handler must be maintained.

publish Publish the service-ref WSDL

publish Publish the deployed WSDL

make Make the required service interface implmentation avail at the JNDI namespace location java:comp/env/service-ref-name. (p135)

deployment Seployment time binding info (for example, bind port-component with port-component-link)

Security - basic auth

Security - symmetric HTTPS

Client support {}

may May reside in a Java EE container (e.g. an EJB that uses a web service)

may May reside in a Java EE client container

could Could use J2SE or J2ME

allows Allows the client to locate a service interface by using JNDI APIs

allows Allows the client to call any SOAP 1.1, 1.2 based web services via HTTP 1.1 or HTTPS SOAP binding

Packaging - CXF or Axis2

Provide CXF and Axis2 as geronimo plugins?