ApplicationModuleTag - How to use custom ApplicationPool

Question

Hi,
The document written by Mr.Juan sometime back on "USER LEVEL SECURITY" focuses more on Data Web Beans. Now we are trying to create an application using datatags. We want to use database usernames for authentication. I added my custom pool (MyApplicationPool) to the bc4j.xcfg. How should I make my ApplicationModuleTag talk to the custom pool class. I am really stuck on this issue. If Mr.Juan can post an HOW TO on this topic, it will be really helpful. I really need help from Oracle Development Team on this topic. All your help is greatly appreciated.
Thanks
Virinchi

Answer 1

We found a solution to the problem. Let me explain my project structure:
1. Total 5 project folders created in Jdeveloper, under one workspace
2. One project, we have our businesscomponents (ViewObjects, AppModule, etc)
3. All other projects have JSPs
4. For View Form and Master-Detail forms we are using datawebbeans.
5. For Edit and Submit edit, we are using datatags.
6. Create two classes called MyApplicationPool and CustomDWB as per the document written by Mr. Juan from JDEV team.
7. Create one property file with the same name as your ApplicationModuleTag ID. For Example (IISmt_BC.IISmt_BCModule.properties). Have a reference to the custom application pool (MyApplicationPool) in this property file using "PoolClassName" as per the document written by Mr. Juan.
8. As soon as the user logs in call the CustomDWB initialize method by passing any viewobject, in the background. This step will create the pool with the name (IISmt_BC.IISmt_BCModule). Modify all your JSP view forms to access the new property file (IISmt_BC.IISmt_BCModule). Now you should be able to access any JSP with this pool.
9. One more important step is to customize the ApplicationModuleTag. I will paste the customized code at the end of this document. In your edit/insert JSPs, use "ApplicationModuleEx" instead of "ApplicationModule". You can put this customized class in any package, but you need to update the "DataTags.tld" to add a new tag called "ApplicationModuleEx".
Customized code for ApplicationModuleTag
========================================
package businesscomponent;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
import javax.servlet.jsp.tagext.TagSupport;
import javax.servlet.jsp.JspException;
import java.io.*;
import oracle.jbo.html.jsp.ConnectionInfo;
import oracle.jbo.common.ampool.PoolMgr;
import oracle.jbo.common.ampool.ApplicationPool;
import oracle.jbo.ApplicationModule;
import oracle.jbo.common.*;
import oracle.jbo.*;
import java.util.*;
public class ApplicationModuleTagEx extends TagSupport
String sApplicationName;
String sConfigName;
String sUserName;
String sPassword;
String siiopUserName;
String siiopPassword;
public ApplicationModuleTagEx()
public void setId(String sAppName)
this.sApplicationName = sAppName;
public void setConfigname(String sValue)
this.sConfigName = sValue;
public void setUsername(String sValue)
this.sUserName = sValue;
public void setPassword(String sValue)
this.sPassword = sValue;
public void setIiop_username(String sValue)
this.siiopUserName = sValue;
public void setIiop_password(String sValue)
this.siiopPassword = sValue;
* doEndTag
* @return int
* @exception javax.servlet.jsp.JspException
public int doEndTag() throws JspException
try
PoolMgr poolManager = PoolMgr.getInstance();
MyApplicationPool pool = null;
if(!poolManager.isPoolCreated(sApplicationName))
// we don't need any code here as pool is already existing in our case.
// Get an application module resource.
oracle.jbo.html.jsp.JSPApplicationRegistry appRegistry =
oracle.jbo.html.jsp.JSPApplicationRegistry.getInstance();
// this step will access the custom pool from the property file
// sApplicationName in my case is IISmt_BC.IISmt_BCModule
appRegistry.registerApplicationFromPropertyFile(sApplicationName);
// get an instance of the pool, which is already existing
pool = (MyApplicationPool)PoolMgr.getInstance().getPool(sApplicationName);
// get an instance of the application module
ApplicationModule am = appRegistry.getAppModuleInstance(sApplicationName, pageContext);
// place default renderers into session, these will not be
// exposed via config file
pageContext.getSession().putValue("oracle_ord_im_OrdImageDomain_Renderer", "oracle.ord.html.OrdBuildURL");
pageContext.getSession().putValue("oracle_ord_im_OrdAudioDomain_Renderer","oracle.ord.html.OrdBuildURL");
pageContext.getSession().putValue("oracle_ord_im_OrdVideoDomain_Renderer","oracle.ord.html.OrdBuildURL");
pageContext.getSession().putValue("oracle_ord_im_OrdVirDomain_Renderer", "oracle.ord.html.OrdBuildURL");
pageContext.getSession().putValue("oracle_ord_im_OrdImageDomain_EditRenderer", "oracle.ord.html.FileUploadField");
pageContext.getSession().putValue("oracle_ord_im_OrdAudioDomain_EditRenderer", "oracle.ord.html.FileUploadField");
pageContext.getSession().putValue("oracle_ord_im_OrdVideoDomain_EditRenderer", "oracle.ord.html.FileUploadField");
pageContext.getSession().putValue("oracle_ord_im_OrdVirDomain_EditRenderer", "oracle.ord.html.FileUploadField");
catch(Exception ex)
StringWriter writer = new StringWriter();
PrintWriter prn = new PrintWriter(writer);
ex.printStackTrace(prn);
prn.flush();
throw new JspException(writer.toString());
return SKIP_BODY;
10. Please note that, the above code is not thoroughly tested, but it works for us. I will let you know if there are any changes to it.
Hope this helps.
Virinchi