• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/8

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

8 Cards in this Set

  • Front
  • Back

DESCRIBA UNA SOLUCION BASADA EN EJB 3 CON UNA ARQUITECTURA TRADICIONAL DE 4 CAPAS USANDO UN MODELO DE DOMINIO. (P28)

1. PRESENTATION LAYER: JSF + FACELETS
2. BUSINESS LOGIC LAYER: EJB3 SESSION BEANS
3. DOMAIN MODEL: ENTITIES
4. PERSISTENCE LAYER: CDI-MANAGED BEANS (POJOs)+ENTITY MANAGER
5. DATABASE LAYER

EN LA IMPLEMENTACION DE UN SESSION BEAN, ¿Qué VALOR SE ASIGNA POR DEFECTO SI NO SE ESPECIFICA SI ES LOCAL O REMOTA?

LOCAL (@Local)

¿QUE ALTERNATIVAS EXISTEN A LA ANOTACION @Local?

@Remote y @WebService

¿PARA QUE SON LAS ANOTACIONES @Remote y @WebService? ¿QUE DIFERENCIA EXISTE ENTRE ELLAS Y EN QUE CASOS SE RECOMIENDA CADA UNA?

1. Remote access through the @Remote annotation is provided under the hood by Java Remote Method Invocation (RMI), so this is the ideal means of remote access from Java clients.
2. If the EJB needs to be accessed by non-Java clients like Microsoft .NET or PHP applications, SOAP–based remote access can be enabled using the @WebService annotation applied either on the interface or on the bean class.

¿A TRAVÉS DE QUE MECANISMO/API FUNCIONA @Remote y @WebService, RESPECTIVAMENTE? ¿PARA QUE CLASES DE CLIENTES SE RECOMIENDA CADA UNA?

@Remote - Por medio de Java Remote Method Invocation (RMI). Para acceso remoto de clientes de Java
@WebService - Por medio de SOAP o RESTful para clientes no-Java, como .NET y PHP.

¿QUE EFECTO GENERA LA ANOTACION @Asynchronous EN UN METODO?

The @Asynchronous annotation placed on a business method makes the method asynchronously invokable. This means that th bean will return control back to the client as soon as the innovation happens. The method is then executed as a lightweight background process. This is an important piece of functionality if the process can potentially take a long time. Instead of making the user wait for the long process to finish, the @Asynchronous annotation means that the user gets an immediate response for the rest of the process.

¿PARA QUE ES LA ANOTACION @Remove? ¿QUE IMPLICACION TIENE SOBRE EL SERVIDOR? ¿EN QUE TIPO DE SESSION BEAN SE UTILIZA Y PARA QUE? P. 35

This annotation is used on Stateful Beans. Although this annotation is optional, it’s critical from a server performance standpoint. The @Remove annotation marks the end of the workflow modeled by a stateful bean. In this case, you’re telling the container that there’s no longer a need to maintain the bean’s session with the client after the annotated method is invoked. If you didn’t tell the container what method invocation marked the end of the workflow, the container could wait for a long time until it could safely time out the session. Because stateful beans are guaranteed to be dedicated to a client for the duration of a session, this could mean a lot of orphaned state data consuming precious server resources for long time periods.

¿EN QUE VERSION DE JAVA EE JPA ERA PARTE DE EJB 3? ¿EN QUE VERSION CAMBIÓ Y COMO?

In Java EE 5, JPA was part of EJB 3. It was moved to its own specification in Java EE 6.