Develop Reference

Amdatu Web using Jersey

Amdatu web uses apache wink to create restful web app in OSGi. Recently the Apache Wink project retired - I don't know exactly why.
My question is: Can I use apache web for my production OSGi application? is the RETIRED apache wink with in amdatu web stable for production usage? and If not how to use other rest providers like Jersey?
Thanks

In the next Amdatu Web release of Apache Wink will be replaced by RESTEasy, you can't just drop in any provider so it won't be possible to use Jersey.
Furthermore we are updating the whiteboard implementation in Amdatu Web to implement the JAX-RS Whiteboard specification mentioned by Neil Bartlett.

Using JAX-WS RI of java 6 under heavy load

I have recently started with web services. In my project, I have to create a client side using wsdl provided.
I have implemented the client part using JAX-WS RI which is available as part of Java 6.
Now when I was going through some blogs, they mentioned that we should not use JAX-WS of java, as it is just an reference implementation and
we have to go for libraries like Apache CXF or Axis2.
Could you please advice if we can use JAX-WS RI of java in production ?
At the moment with JAX-WS RI of Java, our client application testing is going on without any issues. Will it create any problem if we use it under high load ?
Thanks,
Vijay

what actually JAX-WS is?

I need to work on webservice project. So going through book to cover the basics of webservice project. But these are questions I am struggling with:-
1.Java API for XML Web Services(JAX-WS):- JAX-WS is nothing but just a java programming language API for creating web services which is now a part of core java starting from version 6 (though originally developed as part of Java Web Services Development Pack). Is it right?
2.All other webservices framework whether it is metro, jersey, glassfish uses the JAX-WS internally. Is it correct?

Q: 1.Java API for XML Web Services(JAX-WS):- JAX-WS is nothing but just a java programming language API for creating web services which is now a
part of core java starting from version 6 (though originally developed
as part of Java Web Services Development Pack). Is it right?
It is correct, JAX-WS is an application programming interfaces (API). That API, together with the JAX-WS reference implementation (JAX-WS RI, RI = reference implementation) is a part of JDK since version 6. To extend a little bit, JAX-WS 2.0 is included in JDK 6 from the beginning, JAX-WS 2.1 comes with JDK 6u4, and you will find JAX-WS 2.2 in JDK 7 (see this link).
Q: 2.All other webservices framework whether it is metro, jersey, glassfish uses the JAX-WS internally. Is it correct?
Strictly speaking, Metro doesn't "use" JAX-WS, but includes already mentioned JAX-WS reference implementation. Jersey included JAX-RS implementation, and Glassfish is not a Web-service framework, but an application server. Glassfish comes with the complete Metro distribution.

JAX-WS is a Web Services framework that provides tools and infrastructure to develop Web Services solutions for the end users and middleware developersJAX-WS stands for Java API for XML Web Services. JAX-WS is a technology for building web services and clients that communicate using XML. JAX-WS allows developers to write message-oriented as well as RPC-oriented web services.
In JAX-WS, a web service operation invocation is represented by an XML-based protocol such as SOAP. The SOAP specification defines the envelope structure, encoding rules, and conventions for representing web service invocations and responses. These calls and responses are transmitted as SOAP messages (XML files) over HTTP.
There is another type of web-service, which is called RESTful.RESTful web services are built to work best on the Web. Representational State Transfer (REST) is an architectural style that specifies constraints, such as the uniform interface, that if applied to a web service induce desirable properties, such as performance, scalability, and modifiability, that enable services to work best on the Web. In the REST architectural style, data and functionality are considered resources and are accessed using Uniform Resource Identifiers (URIs), typically links on the Web. The resources are acted upon by using a set of simple, well-defined operations. The REST architectural style constrains an architecture to a client/server architecture and is designed to use a stateless communication protocol, typically HTTP. In the REST architecture style, clients and servers exchange representations of resources by using a standardized interface and protocol.
Genrally JAX-RS is used for developing RESTful web services. JAX-RS is a Java programming language API designed to make it easy to develop applications that use the REST architecture. The JAX-RS API uses Java programming language annotations to simplify the development of RESTful web services. Developers decorate Java programming language class files with JAX-RS annotations to define resources and the actions that can be performed on those resources. JAX-RS annotations are runtime annotations; therefore, runtime reflection will generate the helper classes and artifacts for the resource. A Java EE application archive containing JAX-RS resource classes will have the resources configured, the helper classes and artifacts generated, and the resource exposed to clients by deploying the archive to a Java EE server.
Different frameworks uses either JAX-WS or JAX-RS. Jersey uses JAX-RS and Metro uses JAXWS.

Difference between JAX-WS, Axis2 and CXF

What is the difference between:
JAX-WS
Axis2
CXF
All three can be used to create webservices in Java.
As of I know JAX-WS is a specification and Axis2 and CXF are implementations, but Java 1.6 has implementation of JAX-WS if I am not wrong.
So one can use Java 1.6 to develop JAX-WS web services without using Axis2 or CXF? Then what is the use of Axis2, CXF?

The JAX-WS implementation built into the JDK really is just the basic soap stuff. If you need any of the more complex WS-* things like WS-Security, WS-RM, WS-Policy, etc..., you need to use one of the alternatives like CXF or Metro or Axis2. It can also depend on what you are trying to integrate with. For example, CXF has top notch Spring support as well as very good OSGi support.
CXF also has other things besides just JAX-WS. It has a compliant JAX-RS implementation as well and supports exposing services as both REST and SOAP very well. Has a W3C compliant SOAP/JMS implementation if that type of things is required. Basically, lots of stuff not available from the in-jdk JAX-WS impl.
Also see:
Difference between Apache CXF and Axis

In short.
WSDL WS-* are language-agnostic.
JAX-WS are Java standard to build web service.
Apache CXF and Apache Axis 2 are two implementations of JAX-WS. They also offer JAX-RS implementations so that you can build Restful services.
CXF has better integration with Spring, and Camel(camel-cxf). And Axis 2 seems not have a active release.

I found with CXF - integration with Spring is very easy. Moreover, It provides various features like:
Customization of Logging features
Inbound and Outbound interceptor
Application Level security
Easy Exception handling using custom Fault.
For more detail, if you want, please checkout this link:
http://predic8.com/axis2-cxf-jax-ws-comparison.htm
http://www.ibm.com/developerworks/java/library/j-jws11/
And, I read above links, its preety helpful for me. I hope it works for u too.
Thanks !

Web Service organization reles some guidelines i.e BP(Basic Profile) 1.0 and BP(Basic Profile) 1.1.
Base on the Guidelines All Language(Java/.Net) people release Specification with Default implementation
In java Base on BP 1.0 Specification Is JAX-RPC And 1.0 Specification Is JAX-WS
JAX-WS Default implementation is RI(Reference Implementation)
Base on the requirement/Choice we can change the implementation(RI/AXIS-2/CXF)
When we are using java 1.6 that case in JDK already available so not required any other jar. If you want to use different implementation that case required particular implememtation jar.
Axis-2 and CXF come from Apache

Is Jersey just a framework for developing RESTful web services in Java?

The way I understand it is Java EE 6 includes the classes for java.ws.rs (JAX-RS) which are defined in the JSR 311 spec document. But I don't know why you would use Jersey or Apache CXF if the base classes are already built into Java EE 6. Can you not create a RESTful web service with those classes alone? Are Jersey, Apache CXF, etc just frameworks to make development of REST-based web services easier?

why you would use Jersey or Apache CXF if the base classes are already built into Java EE 6.
Can you not create a RESTful web service with those classes alone?
Java EE only defines standards, those classes are the standard API, but there is no implementation behind them. Jersey and CXF are competing implementations of the standard.
However, if you have a server that claims to support Java EE 6, it will have to contain an implementation for every API that's in the standard. For example, Glassfish includes Jersey, so you don't have to add it explicitly.

JAX-RS is just a specification. In order to use JAX-RS, you need an implementation of the spec.
Jersey is a JAX-RS implementation. Specifically, it is the reference implementation.