Tag: architecture
Questions Related to architecture
-
Annotations
-
Deployment descriptor
-
This is not possible as you cannot use both.
-
It is specific to application server product
-
When fetching frequently used read-only data.
-
If you need to manage the workflow or several EJBs.
-
At any time, multiple clients can have access to the bean instance.
-
When the bean should represent a business entity.
-
The bean needs to hold data about the client across multiple invocations.
-
To asynchronously receive JMS messages.
-
At any time, only one client has access to the bean instance
-
At any time, multiple clients can have access to the bean instance
-
When the bean should represent a business entity
-
The bean is not required to be persistent
-
To synchronously receive JMS messages
-
To asynchronously receive JMS messages
-
In EJB 3.0, persistent fields must be identified through deployment descriptor.
-
The persistent state of an entity is represented either by its persistent fields or persistent properties.
-
For an EJB 3.0 entity, you no longer need to code interfaces such as LocalAddressHome and LocalAddress.
-
In the Java Persistence API, you do not not need to provide an XML descriptor to specify an entity's primary key.
-
Java Persistence API is simplified by removing support for complex relationships between Entities.
-
Application can be isolated from the database and the only connection to it is using the ORM framework and a JDBC driver.
-
Developer productivity increases.
-
Performance will be slower than direct JDBC connections.
-
Application maintainance may be a problem.
-
Supports the processing of XML content, data binding, and the development SOAP based and RESTful Web Services.
-
Web Services exposed by JAX-WS can only be of type document/literal.
-
Stateless session beans cannot be exposed as web services using Java EE technology.
-
JAX-WS greatly simplifies the web service implementation model.
-
When EJB is called by client, parameters will be passed by reference
-
Methods must have RMI-IIOP compatible parameters and return types
-
Methods must have JAXB compatible parameters and return types
-
Use annotation @WebService and @WebMethod for deployment.
-
Dependency Injection
-
Interceptors
-
Intercepting Filter Pattern
-
None of the above. You need to write code for measuring response times.
-
You must write ejbPassivate() method. Shift the logic to this method.
-
Mention the method name in the deployment descriptor
-
Use annotations
-
There is no such facility in EJB3.0
-
They are components.
-
A container manages them.
-
More than one of them can be combined in a single program (not application).
-
They live on the server side of an application.
-
They can be part of a transaction.