Monday, April 16, 2007

BEA WebLogic 8.1 Certified Administrator (2)

Manage Deployed Applications

##CONTINUE##
  • The getRequestDispatcher() method returns a RequestDispatcher object that acts as a wrapper for the resource located at the given path. A RequestDispatcher object can be used to forward a request to the resource or to include the resource in a response. The resource can be dynamic or static

Public RequestDispatcher getRequestDispatcher(String path)

Return null if the servletContext cannot return a requestDispatcher.

  • Javax.transaction.UserTransaction provides an interface to the transaction manager that allows the application developer to manage the scope of a transaction explicitly. The client application uses JNDI to obtain an object reference to the UserTransaction object for the Weblogic Server domain.

Client:

UserTransaction ut = (UserTransaction) jndicontext.lookup(“javax.transaction.UserTransaction”)

Bean:

UserTransaction ut = ejbContext.getUserTransaction()

  • The default Transaction level for EJB’s in Weblogic is Supports
  • JSP tag libraries are copied into the WEB-INF directory
  • WLS allows TX to be terminated only by the client that created the TX. WLS implements the flat TX model; nested TX are not supported. WLS supports multithreaded TX clients; clients can make TX requests concurrently in multiple threads. In WLS a client or a server object cannot invoke methods on an object that is infected with another TX. In WLS, client cannot using third-party implementations of the JAVA TX API.

Read more!

No comments: