java - Is JAX-WS using serverside Stubs (Skeletons) for communication? -
as far know, predecessor of jax-ws (jax-rpc) using a
client-stub (proxy) <--> server-skeleton (also called serverside stub, or tie) system communication between client , service.
but if reading on topic of communication in jax-ws, can't find relating skeletons, serverside stubs, or ties. neither can find writing, jax-ws no longer needs skeletons. researches lead me jax-rpc topics, java rmi, or wsdl java approaches (sei-skeletons, don't think skeletons looking for). in jax-ws has handle , steer work of taking soap-request, marshalling/unmarshalling jaxb , giving parameters methods of service implementation.
does know, if jax-ws still using skeletons/ties on server side , how created (with link source cool)? , if not used anymore, how work done?
i hope, english isn't bad.
the skeleton still there can't see it.
the "server stub" in picture below skeleton. created based on annotated classe (@webservice), when application deployed.
it still responsible in parsing content, using jaxb.
take @ link:
http://qallme.sourceforge.net/docs/sec_creatingawsimplementationskeleton.html
Comments
Post a Comment