https://github.com/uttesh/jax-ws-provider-based-endpoints

Simple JAX-WS provider webservice implemetation, as we know this type implementation is required only when there is huge xml file data input, JAXB will be performance pain for huge xml data.
https://github.com/uttesh/jax-ws-provider-based-endpoints

Last synced: about 7 hours ago
JSON representation

Simple JAX-WS provider webservice implemetation, as we know this type implementation is required only when there is huge xml file data input, JAXB will be performance pain for huge xml data.

• Host: GitHub
• URL: https://github.com/uttesh/jax-ws-provider-based-endpoints
• Owner: uttesh
• License: apache-2.0
• Created: 2013-11-29T11:41:06.000Z (almost 11 years ago)
• Default Branch: master
• Last Pushed: 2013-11-29T11:56:17.000Z (almost 11 years ago)
• Last Synced: 2023-04-05T18:55:19.820Z (over 1 year ago)
• Size: 22.4 MB
• Stars: 1
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
JAX-WS-Provider-Based-Endpoints

===============================

Simple JAX-WS provider webservice implemetation, as we know this type implementation is required only when there is huge xml file data input, JAXB will be performance pain for huge xml data.

Why Webservice Provider?



As we know SEI webservices are easy to implement and maintain, but fails on xml data parsing for huge data in soap message.

checkout the reference on web service provider basic information in below link

http://docs.oracle.com/cd/E24329_01/web.1211/e24965/provider.htm#WSADV191

How To implemet the Provider Service



We have to use @webserviceprovider annotation instead of @webservice, and @serverMode as SOAP/PAYLOAD. provider wont be having wsdl by default we have to write manual wsdl and xsd file, wegen tool won't help generation as well for webservice 

provider end point service.

sample URL: http://localhost:8080/wsprovider/secure/soap/SimpleProviderService?wsdl