• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

JAXWS Stubs

 
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have used Axis/Mule and now have to work on JAXWS.
When i read about it i found the steps to be
1.Write a service class.
2.Compile the Service.
3.Generate WSDL/XSD/Beans
4.Package everything.
5.Deploy(Glassfish in my case)
6.Build/Compile the client.
7.Generate the stubs.
8.Run the client.

First of all have i got the flow right?
Because in Axis we developed the stubs before writing the client and that should ideally be the case.So the question is how and when are stubs used in JAXWS.
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Mustafa Garhi:
Because in Axis we developed the stubs before writing the client and that should ideally be the case.



That is still the case under JAX-WS - however the client application probably has a larger purpose than just accessing the service, so "client application development" could be started before the stubs are available.

I would like to point out that the development that you describe is called "contract last" development. Contract last development is usually chosen for "developer convenience".

For a variety of reasons, optimizing client interoperability being one of them, contract first web service development should be the preferred method.

Bottom-up or Top-down
Starting Out
Webservice - WSDL or Java Class
JAX-RPC to JAX-WS (Client impact)

A simple example of JAX-WS contract last development which uses wsgen. For contract first development the service skeleton is generated with wsimport (Creating a service from WSDL).
[ December 04, 2008: Message edited by: Peer Reynders ]
 
Mustafa Garhi
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks peer
Also, i have used ant to compile/WSDL generation/pack/deploy.
You need to make the build file for ant.
For Axis wsdl2java etc was much easy approach.
If you could please tell me alternate approaches for compile/WSDL generation/pack/deploy.One i could think of is Eclipse plug-ins.
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
wsimport Ant Task
wsgen Ant Task
JAX-WS Commons Maven Plugin
[ December 05, 2008: Message edited by: Peer Reynders ]
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic