aspose file tools*
The moose likes Web Services and the fly likes Authentication in Webservices Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Authentication in Webservices" Watch "Authentication in Webservices" New topic
Author

Authentication in Webservices

Mortin kim
Ranch Hand

Joined: Nov 15, 2007
Posts: 44
HI.,
I have some basic doubts in Web-Services,Please clarify.

1.what type of authetication used for Webservices..?
2.what are the standards that the interface,implementation class must fallow to expose to Wbservices..?
3.What is XMl-rpc..?what is the purpose of it..?
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 42635
    
  65
1.what type of authetication used for Webservices.?

The WS-Security standard defines how authentication should work.

2.what are the standards that the interface,implementation class must fallow to expose to Wbservices.?

I'm not quite sure what you're asking, but the prevalent standards for Java WS are SAAJ and JAX-WS.

3.What is XMl-rpc.?what is the purpose of it?

XML-RPC is a protocol for performing RPC calls using HTTP. It has been more or less obsoleted by Java WS line JAX-WS.


Ping & DNS - my free Android networking tools app
Mortin kim
Ranch Hand

Joined: Nov 15, 2007
Posts: 44
HI.,
Thanks for the reply.
What I mean the standards for our Interface,Class that need to expose to webservices is
like interface should be publically avilable..like this
and also I want to know all the stadards for the implementation class and as well as interface.

Thanks
Kim.
Peer Reynders
Bartender

Joined: Aug 19, 2005
Posts: 2922
    
    5
Originally posted by Mortin kim:
What I mean the standards for our Interface,Class that need to expose to webservices is like interface should be publically avilable..like this and also I want to know all the stadards for the implementation class and as well as interface.


Web Services are not EJBs that work over the net ... web services ultimately provide web content designed to be consumed by other applications (rather than human users) - applications that may not even be written in Java.

So many standards don't even mention Java, interfaces, or classes (especially web service standards). If you are dealing with SOAP web services, the SOAP standard describes the elements of the SOAP messages that are exchanged between the initial sender and ultimate receiver. The WSDL standard describes a language that can be used to define the exact structure/format of the SOAP messages that are accepted and emitted by a SOAP web service endpoint. So a SOAP web service is defined by SOAP messages that it can receive and send.

Java interfaces and classes only become a concern when you decide to build a web service consumer or provider in Java. The exact classes and interfaces depend on the Java API used to process the SOAP messages.

The SAAJ (JSR-67) specification outlines an API the can be used to build a SOAP web service consumer.

J2EE 1.4 introduced the JAX-RPC (JSR-101) specification to outline an API for building web service providers. In Java EE 5 JAX-WS (JSR-224) was introduced to replace JAX-RPC at some later point in time.

Then there are web services that are not based on SOAP (or even XML) at all. REST-style web services don't even have a specification that defines them however there is already a Java framework for building them (Restlet) and an official API specification is in the works (JSR-311:JAX-RS: The Java API for RESTful Web Services as implemented in Jersey).
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Authentication in Webservices