JAX-RS 2.0 behavior changes

@Override
public Set<Object> getSingletons() {
    Set<Object> objs = new HashSet<Object>();
    objs.add(new CDIInjectResource());
    objs.add(new EJBInjectResource());
    return objs;
}

@Override
public Set<Object> getSingletons() {
    Set<Object> singletons = new HashSet<Object>();
    singletons.add(new JacksonJaxbJsonProvider());
    return singletons;
}

	
       <servlet>
		<servlet-name>javax.ws.rs.core.Application</servlet-name>
	</servlet>
	<servlet-mapping>
		<servlet-name>javax.ws.rs.core.Application</servlet-name>
		<url-pattern>/*</url-pattern>
	</servlet-mapping>

@Stateless
@Local(OneLocalInterfaceMyOtherStuffMessageBodyWriter.class)
public class OneLocalInterfaceMyOtherStuffProvide

@Provider
@Consumes("<custom/type>")
@Produces("<custom/type>")
@Singleton
public class MyMessageBodyReaderAndWriter implements MessageBodyReader,MessageBodyWriter {
                
    public boolean isReadable(Class<?> type,
                              Type genericType,
                              Annotation[] annotations,
                              MediaType mediaType) {
        if (mediaType.toString().equals("<custom/type>"))
            return true;
        return false;
    }

     public boolean isWriteable(Class<?> type,
                              Type genericType,
                              Annotation[] annotations,
                              MediaType mediaType) {
        if (mediaType.toString().equals("<custom/type>"))
            return true;
        return false;
    }
...
}

• org.apache.wink.common.model.atom.AtomEntry. For more information about integrating JAX-RS 2.0 with Atom, see Integrating JAX-RS 2.0 with Atom.
• org.apache.wink.client.handlers.BasicAuthSecurityHandler. If you want to use basic authentication in JAX-RS 2.0, see the following code snippets:
  1. Use ClientRequestFilter through the JAX-RS 2.0 standard Client API as shown in the code example:

     import java.io.IOException;
     import java.io.UnsupportedEncodingException;
     import javax.ws.rs.client.ClientRequestContext;
     import javax.ws.rs.client.ClientRequestFilter;
     import javax.ws.rs.core.MultivaluedMap;
     import javax.xml.bind.DatatypeConverter;
     
     public class BasicAuthFilter implements ClientRequestFilter {
     
         private final String usr;
         private final String pwd;
     
         public BasicAuthFilter(String usr, String pwd) {
             this.usr = user;
             this.pwd = pwd;
         }
     
         public void filter(ClientRequestContext requestContext) throws IOException {
             MultivaluedMap<String, Object> headers = requestContext.getHeaders();
            
          String token = this.usr + ":" + this.pwd;
          final String basicAuthentication ="Basic " + DatatypeConverter.printBase64Binary(token.getBytes("UTF-8"));
          headers.add("Authorization", basicAuthentication);
         }
     }

  2. Register to the ClientBuilder:

     ClientBuilder cb = ClientBuilder.newBuilder();
     cb.register(new BasicAuthFilter("user","password"));

• org.apache.wink.client.handlers.LtpaAuthSecurityHandler.
• org.apache.wink.server.internal.providers.exception.EJBAccessExceptionMapper. This API is no longer supported because it is the Wink-specified ExceptionMapper. You can define your own ExceptionMapper to map the EJBAccessException.
• com.ibm.websphere.jaxrs.server.IBMRestFilter. This API is no longer supported because it is based on Wink Filter.

1. Configure the SSL properties in the WebSphere® Application Server traditional administrative console.
2. Enable security for your JAX-RS application and configure your application to use an SSL channel for transport when it calls the REST resources.

   At application development or deployment time, edit the web.xml file to add a security constraint that requires use of SSL for your resources. See the securing JAX-RS applications within the web container information for more details on enabling SSL for your application.

   The following element within the security-constraint element specifies to enforce SSL for your application:

   <user-data-constraint id="UserDataConstraint_1">
       <transport-guarantee>CONFIDENTIAL</transport-guarantee>
    </user-data-constraint>

3. To enable client SSL when you develop your client application, add a client property in your client application code.

   Set the client property key to com.ibm.ws.jaxrs.client.ssl.config and its value to true. See the following code snippet as reference:

   ClientBuilder cb = ClientBuilder.newBuilder();
   cb.property("com.ibm.ws.jaxrs.client.ssl.config", "NodeDefaultSSLSettings");

   Tip: The property value equals to the server SSL alias that you set. For more information, go to Application servers->server n, where n is the number that you assigned to the application server.->Web container transport chains->WCInboundDefaultSecure->SSL inbound channel (SSL_2) to check it under the SSL configuration field.
4. Deploy your client application to WebSphere Application Server traditional by using the administrative console.
5. Start the client application in the WebSphere Application Server traditional administrative console.

   To start your application, go to Applications->Application types->WebSphere enterprise applications->Start.