Am i on the right track for establishing my client connection with BC4J?

Question

I am developing web-application with BC4J JSP project now. However, I find the auto-generated page not that useful as they are not flexible enough. Then, I decided to write coding by myself. But the first problem is - how to write the coding for client connection? To make maintenance easy, I would like to place those connection code in a class file instead of hard-coding each connection details in my JSP or Servlet page.
Question 1: Through the examples I search in my JDeveloper (Candidate 2) directory, found a file TestClient.java in the \BC4J\samples\Caching\src\demo directory with the following codes:
// Create an instance of the application module by name, using local mode
String _am  = "demo.DemoModule"; // Fully-qualified application module name
String _cf  = "DemoModuleLocal"; // Configuration name for connection info
ApplicationModule am = Configuration.createRootApplicationModule(_am,_cf);
// Find the Managers view object by name in the application module
ViewObject mgrVO = am.findViewObject("Managers");
// We're done with the AM instance, so release it
Configuration.releaseRootApplicationModule(am,true);
Is it for testing only or really useful for the production environment? Am I doing the right thing if i use such method to establish my web client connection? What's the pros and cons for using this method? Any other better alternatives?
Question 2: As I know BC4J automatically takes care of connection pooling as a default manner since version 3.2. Can I still use the following statement
session.setAttribute("user_name", user_name); //Set session attribute
String user_name = (String) session.getAttribute(user_name); // Get session attribute
to capture and assign client session correctly for individual clients?
Question 3: What codes should I use to achieve 'Transaction' update, which assembles the coding as follows:
Connection.setAutoCommit(false); //disable auto commit
connection.commit();
connection.rollback();
connection.close();
Thanks for answering!!!

Answer 1

Question 1: Through the examples I search in my JDeveloper (Candidate 2) directory, found a file TestClient.java in the \BC4J\samples\Caching\src\demo directory with the following codes:
// Create an instance of the application module by name, using local mode
String _am  = "demo.DemoModule"; // Fully-qualified application module name
String _cf  = "DemoModuleLocal"; // Configuration name for connection info
ApplicationModule am = Configuration.createRootApplicationModule(_am,_cf);
// Find the Managers view object by name in the application module
ViewObject mgrVO = am.findViewObject("Managers");
// We're done with the AM instance, so release it
Configuration.releaseRootApplicationModule(am,true);
Is it for testing only or really useful for the production environment? Am I doing the right thing if i use such method to establish my web client connection? What's the pros and cons for using this method? Any other better alternatives?The Configuration API (createRootApplicationModule, releaseRootApplicationModule) will work. However, please note
that it is intended for java clients that will hold an ApplicationModule reference for a long duration. The BC4J web
frameworks (represented, for example, by the ApplicationModule and ReleasePageResources tags) all use the
SessionCookie interface to acquire/release ApplicationModule instances on a per request basis. This will allow
better scalability. Please see the pooling sample / documentation / javadoc for more information about using these
APIs. The pooling sample servlet is located in \BC4J\samples\Pooling\src\demo\TestPoolServlet.
Question 2: As I know BC4J automatically takes care of connection pooling as a default manner since version 3.2. Can I still use the following statement
session.setAttribute("user_name", user_name); //Set session attribute
String user_name = (String) session.getAttribute(user_name); // Get session attribute
to capture and assign client session correctly for individual clients?BC4J will not interfere with your use of the HttpSession context. How do you intend the "user_name" to be used? Do
you intend it to represent the DB user, JAAS user, etc. If you intend it to be used as the DB user you will need to declare
the "user_name" to BC4J. Please see:
http://technet.oracle.com/products/jdev/howtos/bc4j/howto_dynamic_jdbc.html
Question 3: What codes should I use to achieve 'Transaction' update, which assembles the coding as follows:
Connection.setAutoCommit(false); //disable auto commit
connection.commit();
connection.rollback();
connection.close();ApplicationModule.getTransaction().commit();
ApplicationModule.getTransaction().rollback();
If you are using the Configuration or SessionCookie APIs, as mentioned above, then the connection lifecycle will be
managed for you. So, you should not need to invoke connection.close().
Thanks for answering!!!
Hope this helps.
JR