[svn:fx-trunk] 10050: Per-Module Style Management: Create a style manager for each application/module.

Revision: 10050
Author:   [email protected]
Date:     2009-09-08 07:43:16 -0700 (Tue, 08 Sep 2009)
Log Message:
Per-Module Style Management: Create a style manager for each application/module.
The singleton StyleManager is still the only style manager that is currently used.
QE notes: None.
Doc notes: None.
Bugs:
Reviewer: Alex
Tests run: checkintests, Managers/StyleManager
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/SWFLoader.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/FlexModuleFactory.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/IFlexModuleFactory.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/events/Request.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/ISystemManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/modules/IModuleInfo.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/modules/ModuleLoader.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/modules/ModuleManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/IStyleManager2.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/StyleManagerImpl.as
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/StandardDefs.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

Similar Messages

Transaction Management for Nested Application Module

Hi
I'm using Jdev 11.1.2.0
I am having nested Application Module. In that I want to separate view object data need to commit without commit the root application module view object.
Is it possible. Kindly reply me.

No, the root application module controls the transaction of all need application modules. A commit will commit all changes together. You have to use different root application modules for this.
Timo

Invalid arguments in call for an Application Module

We are writing a web-app which has two packages in our BC4J project, each with an Application Module. One of these app modules contains business components for objects owned by the user ILOGNET and the other for objects owned by the user EAGLE. We are allowing users to logon and connect to the database as themselves by specifying username and password dynamically as attributes of each instance of both application modules.
The problem we are having is that for a particular JSP sometimes when we deploy, we get an "invalid arguments in call" error. Other times, it doesn't seem to be a problem. The user I am testing with has Oracle roles that have privileges to view all the necessary objects. I'm just not sure why it seems to be temperamental like this. Does anyone have any ideas ? The code for the problem JSP is shown below.
Thanks for any help :
<%@ taglib uri="/webapp/DataTags.tld" prefix="jbo" %>
<%@ page contentType="text/html;charset=windows-1252"%>
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<link rel="stylesheet" type="text/css" href="../style/style.css">
<TITLE>
Commenting Subject Administration Portlet
</TITLE>
<script language="JavaScript">
var g_valid = false;
function get_validate()
var el_subject = document.getElementById("id_subject");
el_subject.value = pro_trim(el_subject.value);
if (el_subject.value == "")
alert("Subject is a required field");
g_valid = false;
else
g_valid = true;
function pro_trim(p_in)
var s_remaining = p_in;
while (s_remaining.charAt(s_remaining.length - 1) == ' ')
s_remaining = s_remaining.substring(0, s_remaining.length - 1);
while (s_remaining.charAt(0) == ' ')
s_remaining = s_remaining.substring(1, s_remaining.length);
return s_remaining;
</script>
</HEAD>
<body class="portlet">
<jbo:ApplicationModule id="am_subjectAdmin" configname="eagle.EagleModule.EagleModuleLocal" releasemode="Stateful" username="<%=request.getRemoteUser()%>" password='<%=(String)session.getValue("PASSWORD")%>' />
<jbo:DataSource id="ds_enditems" orderbyclause="eiacodxa" rangesize="4" appid="am_subjectAdmin" viewobject="EIACSELECTView" />
<table class="portlet" width="100%" cellpadding=10 cellspacing=0>
          <tr class="portlet-title">
          <td>
Commenting Subject Administration Portlet
          </td>
          </tr>
          <tr class="portlet-body" height="100%">
          <td>
<table width="100%" align="center">
<tr>
<td height="50"></td>
</tr>
<tr>
<td>
<form name="frm_subject" action="cls_comment_subject" method="post" onSubmit="get_validate();return g_valid;">
<table>
<tr>
<td width="150">End Item :</td>
<td align="left">
<jbo:InputSelect datasource="ds_enditems" dataitem="Eiacodxa" displaydatasource="ds_enditems" displaydataitem="Eiacodxa" displayvaluedataitem="Eiacodxa" ></jbo:InputSelect>
</td>
<td align="right">Subject Type :</td>
<td align="left">
<select name="type">
<option value="C">Comment
<option value="R">Response
</select>
</td>
<td width="250"></td>
</tr>
<tr>
<td width="150">Subject Title :</td>
<td colspan="3">
<input id="id_subject" type="text" name="subject" size="100" maxlength="255">
</td>
</tr>
<tr>
<td colspan="4" align="right">
<input type="Submit" value="Submit Subject">
<input type="Reset" value=" Clear ">
</td>
</tr>
<tr>
<td height="250">
</td>
</tr>
</table>
</form>
</td>
</tr>
</table>
</td>
</tr>
</table>
</body>
</HTML><jbo:ReleasePageResources />
Regards,
Joe Mellors

I'd forgotten all about this until now when it just happened again. Seems strange that it works fine a lot of the time. It only seems to happen with one of the two Application Module's in the project.
Here is the call stack. I'd appreciate any help.
Thanks,
Joe
JBO-30003: The application pool (eagle.EagleModule.EagleModuleLocal) failed to checkout an application module due to the following exception:
oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
     at oracle.jbo.server.ConnectionPool.createConnection(ConnectionPool.java:193)
     at oracle.jbo.server.ConnectionPool.instantiateResource(ConnectionPool.java:116)
     at oracle.jbo.pool.ResourcePool.createResource(ResourcePool.java:290)
     at oracle.jbo.pool.ResourcePool.useResource(ResourcePool.java:208)
     at oracle.jbo.server.ConnectionPool.getConnection(ConnectionPool.java:63)
     at oracle.jbo.server.ConnectionPoolManagerImpl.getConnection(ConnectionPoolManagerImpl.java:53)
     at oracle.jbo.server.DBTransactionImpl.establishNewConnection(DBTransactionImpl.java:615)
     at oracle.jbo.server.DBTransactionImpl.initTransaction(DBTransactionImpl.java:815)
     at oracle.jbo.server.NullDBTransactionImpl.initTxn(NullDBTransactionImpl.java:489)
     at oracle.jbo.server.NullDBTransactionImpl.connect(NullDBTransactionImpl.java:367)
     at oracle.jbo.common.ampool.DefaultConnectionStrategy.connect(DefaultConnectionStrategy.java:201)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.connect(ApplicationPoolImpl.java:2304)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:1096)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:1669)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:289)
     at oracle.jbo.html.jsp.datatags.ApplicationModuleTag.doStartTag(ApplicationModuleTag.java:181)
     at org.apache.jsp.mp_0005fdt$jsp._jspService(mp_0005fdt$jsp.java:83)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:531)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
     at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
     at java.lang.Thread.run(Thread.java:536)
## Detail 0 ##
java.sql.SQLException: invalid arguments in call
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:185)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:227)
     at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:973)
     at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:197)
     at oracle.jdbc.driver.OracleConnection.(OracleConnection.java:353)
     at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:457)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:332)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:140)
     at oracle.jbo.server.ConnectionPool.createConnection(ConnectionPool.java:162)
     at oracle.jbo.server.ConnectionPool.instantiateResource(ConnectionPool.java:116)
     at oracle.jbo.pool.ResourcePool.createResource(ResourcePool.java:290)
     at oracle.jbo.pool.ResourcePool.useResource(ResourcePool.java:208)
     at oracle.jbo.server.ConnectionPool.getConnection(ConnectionPool.java:63)
     at oracle.jbo.server.ConnectionPoolManagerImpl.getConnection(ConnectionPoolManagerImpl.java:53)
     at oracle.jbo.server.DBTransactionImpl.establishNewConnection(DBTransactionImpl.java:615)
     at oracle.jbo.server.DBTransactionImpl.initTransaction(DBTransactionImpl.java:815)
     at oracle.jbo.server.NullDBTransactionImpl.initTxn(NullDBTransactionImpl.java:489)
     at oracle.jbo.server.NullDBTransactionImpl.connect(NullDBTransactionImpl.java:367)
     at oracle.jbo.common.ampool.DefaultConnectionStrategy.connect(DefaultConnectionStrategy.java:201)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.connect(ApplicationPoolImpl.java:2304)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:1096)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:1669)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:289)
     at oracle.jbo.html.jsp.datatags.ApplicationModuleTag.doStartTag(ApplicationModuleTag.java:181)
     at org.apache.jsp.mp_0005fdt$jsp._jspService(mp_0005fdt$jsp.java:83)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:531)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
     at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
     at java.lang.Thread.run(Thread.java:536)

Single session for all Application Modules

Hello,
I've got an application that has several Application Modules. All these modules need some data that are set from time to time. I've written some code that calls getSession().getUserData().put("myData",myData). After this method was called in another Application Module i want to retrieve myData with getSession().getUserData().get("myData"). But the result depends if I use 2-tier or 3-tier. In 2-tie I get myData while in 3-tier I get null. My question is:
Is there a Session object or any other data instance that could be accessed from all Application Modules for on application instance.
E.g. I've got two user (A,B) who start my application. Through using my app several instance of Application Modules are created. All Application Modules that are created for the instance of User A should be able to share his user name and some other dynamic data while the Application Modules created for B should have no access to that data.
Doe anybody know if static data of an Application Module are a possible solution?
regards
Joerg

Hi Joerg,
I am not 100% sure what you are trying to achieve, and with which version of JDeveloper/ ADF, technologies (JSP, Swing), etc, but I can tell you that I have been experimenting with single session accounts myself within a rich-client Swing environment, as I have experienced Oracle DBA guys who want to control user authentication via Oracle accounts (I have achieved this via the JCLoginDialog mechanism, and a bit of a hack)... Frank Nemphius (sp?) posted something about a white paper coming out on a related subject but I don't know where he is with that.
Anyway, I managed to do it in a prototype by nesting several application modules within a Root Application Module that was essentially simply a Container for the other application modules. Using this mechanism I was able to bind my root application module to any panel I wanted and it would inherit the roots Session.
ie. I used many application modules and it only used one Oracle Session.
However, my reservations -
1) This solution was not tested robustly!
2) I doubt this would be ideal for a distributed app with thousands of users - My solution is for a very complex app, with a limited number of users.
Finally, I cannot confirm this is a great solution - I can only tell you it worked in my prototype, and I am currently awaiting the ADF source - when my company and Oracle can decide what level of support we currently have and need!?!? - what exactly does being an "Oracle partner" mean??? Its all very boring and un-interesting to a Java person like me... ;-)
Once I have the source I will look at how it actually works and perhaps be able to answer questions like this more definitively. Hmm - I wonder if I could get the Oracle JDBC driver source too?? .... Is it written in C or C++?? I know them too... ;-)
Cheers........Dean

Default Code Generation for a Custom Class for an Application Module

hi all
Oracle® Fusion Middleware
Fusion Developer’s Guide for Oracle Application Development
Framework
11g Release 1 (11.1.1)
with Jdeveloper TP3 ,
By default, the application module Java class will look similar to what you see in
Example below when you've first enabled it. Of interest, it contains:
■ Getter methods for each view object instance in the data model
■ A main() method allowing you to debug the application module using the
Business Components Browser
[package devguide.model;
import devguide.model.common.StoreServiceAM;
import oracle.jbo.server.ApplicationModuleImpl;
import oracle.jbo.server.ViewLinkImpl;
import oracle.jbo.server.ViewObjectImpl;
// --- File generated by Oracle ADF Business Components Design Time.
// --- Custom code may be added to this class.
// --- Warning: Do not modify method signatures of generated methods.
public class StoreServiceAMImpl extends ApplicationModuleImpl {
/** This is the default constructor (do not remove) */
public SRServiceImpl() { }
/** Sample main for debugging Business Components code using the tester */
public static void main(String[] args) {
launchTester("devguide.model", /* package name */
"SRServiceLocal" /* Configuration Name */);
/** Container's getter for YourViewObjectInstance1 */
public ViewObjectImpl getYourViewObjectInstance1() {
return (ViewObjectImpl)findViewObject("YourViewObjectInstance1");
// ... Additional ViewObjectImpl getters for each view object instance
// ... ViewLink getters for view link instances here
when i try this i didn't find the default generation for main method
have i do something before enable custom java file for Application module
hope to hear from you soon

hi nonStop
Since you are using Jdeveloper TP3, this might be a better place to ask your question:
"JDeveloper and OC4J 11g Technology Preview"
JDeveloper and OC4J 11g Technology Preview
success
Jan Vervecken

Best practice for calling application module methods and plsql code

In my application I am experiencing problems with connection pooling, I seem to be using a lot of connections in my application when only a few users are using the system. As part of our application we need to call database procedures for business logic.
Our backing beans, call methods on the application module which in turn call a database procedure. For instance in the backing bean we have code like this to call the application module method.
// Calling Module to generate new examination/test.
CIGAppModuleImpl appMod = (CIGAppModuleImpl)Configuration.createRootApplicationModule("ky.gov.exam.model.CIGAppModule", "CIGAppModuleLocal");
String testId = appMod.createTest( userId, examId, centerId).toString();
AdfFacesContext.getCurrentInstance().getPageFlowScope().put("tid",testId);
// Close the call
System.out.println("Calling releaseRootApplicationModule remove");
Configuration.releaseRootApplicationModule(appMod, true);
System.out.println("Completed releaseRootApplicationModule remove");
return returnResult;
In the application module method we have the following code.
System.out.println("CIGAppModuleImpl: Call the database and use the value from the iterator");
CallableStatement cs = null;
try{
cs = getDBTransaction().createCallableStatement("begin ? := macilap.user_admin.new_test_init(?,?,?); end;", 0);
cs.registerOutParameter(1, Types.NUMERIC);
cs.setString(2, p_userId);
cs.setString(3, p_examId);
cs.setString(4, p_centerId);
cs.executeUpdate();
returnResult=cs.getInt(1);
System.out.println("CIGAppModuleImpl.createTest: Return Result is " + returnResult);
}catch (SQLException se){
throw new JboException(se);
finally {
if (cs != null) {
try {
cs.close();
catch (SQLException s) {
throw new JboException(s);
I have read in one of Steve Muench presentations (Oracle Fusion Applications Team' Best Practises) that calling the createRootApplicationModule method is a bad idea, and to call the method via the binding interface.
I am assuming calling the createRootApplicationModule uses much more resources and database connections that calling the method through the binding interface such as
BindingContainer bindings = getBindings();
OperationBinding ob = bindings.getOperationBinding("customMethod");
Object result = ob.execute()
Is this the case? Also is using getDBTransaction().createCallableStatement the best way of calling database procedures. Would it be better to expose plsql packages as webservices and then call them from the applicationModule. Is this more efficient?
Regards
Orlando

Thanks Shay, this is now working.
I successfully got the binding to the application method in the pagedef.
I used the following code in my backing bean.
package view.backing;
import oracle.binding.BindingContainer;
import oracle.binding.OperationBinding;
public class Testdatabase {
private DCBindingContainer bindingContainer;
public void setBindingContainer (DCBindingContainer bc) {this.bindingContainer = bc;}
public DCBindingContainer getBindingContainer() {return bindingContainer;}
public static String validateUser()
// Calling Module to validate user and return user role details.
System.out.println("Getting Binding Container from Home Backing Bean");
BindingContainer bindings = BindingContext.getCurrent().getCurrentBindingsEntry();
System.out.println("Obtain binding");
OperationBinding operationBinding = bindings.getOperationBinding("calldatabase");
System.out.println("Set username parameter");
operationBinding.getParamsMap().put("p_userId",userId);
System.out.println("Set password parameter");
operationBinding.getParamsMap().put("p_testId",examId);
Object result = operationBinding.execute();
System.out.println("Obtain result");
String userRole = result.toString();
System.out.println("Result is "+userRole);
}

Error when generating Web Services Proxy for SCA Application Module

Hello,
I'm trying to create Web Services for a simple Application Module with JDeveloper 11g (11.1.1.3.0).
I start a new ADF Project, I create an Application Module as simple as possible : it contains only a simple View Object on the DEPT Entity.
On my Application Module, I choose "Service Interface" and I add my View Object in the service interface.
I test my Web Service in the Embedded Weblogic Server, it works well. (I succeed in using the Get operation, for example).
But when I try to generate a Web Service proxy (right-click on the WSDL File -> Generate Web Service Proxy), It always fail with such errors :
oracle.jdeveloper.webservices.tools.WsdlValidationException: Error creating model from wsdl "file:/C:/JDeveloper/mywork/ApplicationAppelServiceSCA/Model/src/model/common/AppModuleService.wsdl": 'unset' is already defined'Bytes' is already defined'ref' is already defined'Duration' is already defined'Types' is already defined'Character' is already defined'type' is already defined'Day' is already defined'nestedInterfaces' is already defined'Date' is already defined'datagraph' is already defined'Type' is already defined'Integer' is already defined'ModelsType' is already defined'ChangeSummaryType' is already defined'instanceClass' is already defined'Month' is already defined'DataObject' is already defined'javaClass' is already defined'LongObject' is already defined'DateTime' is already defined'dataObject' is already defined'YearMonth' is already defined'ShortObject' is already defined'Long' is already defined'types' is already defined'JavaInfo' is already defined'IntObject' is already defined'Boolean' is already defined'DoubleObject' is already defi...
Can someone help me to understand this error ?
i never manually edited the WSDL File, so I don't understand why the generated WSDL or XSD files might contain errors.
Thanks for your Help,
Laurent

We have the same problem, and the problem was in the xsd import:
The wdsl import a schema that import other schema, the second import use a relative path, that was wrong.
So check the xsd import sequence....

Guidelines for setting Application Module Pool Size Parameters?

Are there guidelines for setting the application module pool size parameters, such as initial pool size, maximum pool size, etc., based on the expected number of users or other factors? I've read the developer guide sections (ch 28-29), but still don't have a good feel for how to correctly set the optimal values for the pool configuration parameters? Even more importanty, how do I monitor the pool's efficiency during runtime to determine if the pooling parameters are configured correctly?
This will be critical to performance and scalability, so I'm looking for a way to get some visibility into how the pooling is working during production operation to assess whether there are bottlenecks/constraints/ineffeciencies?
Note I am using Tomcat as the java runtime container; ADF BC / JSF jdev 10.1.3.1
Thanks in advance and Merry Christmas!

KUBA - were you able to resolve these issues and if so are there any lessons learned you can share?
I'm hoping someone from the ADF team can answer our original question including guidelines for setting pool parameters and how to monitor the pool's performance while running in production.
thanks

9.7.3 Default Code Generation for a Custom Class for an Application Module

hi all
Oracle® Fusion Middleware
Fusion Developer’s Guide for Oracle Application Development
Framework
11g Release 1 (11.1.1)
with Jdeveloper TP3 ,
By default, the application module Java class will look similar to what you see in
Example below when you've first enabled it. Of interest, it contains:
■ Getter methods for each view object instance in the data model
■ A main() method allowing you to debug the application module using the
Business Components Browser
[package devguide.model;
import devguide.model.common.StoreServiceAM;
import oracle.jbo.server.ApplicationModuleImpl;
import oracle.jbo.server.ViewLinkImpl;
import oracle.jbo.server.ViewObjectImpl;
// --- File generated by Oracle ADF Business Components Design Time.
// --- Custom code may be added to this class.
// --- Warning: Do not modify method signatures of generated methods.
public class StoreServiceAMImpl extends ApplicationModuleImpl {
/** This is the default constructor (do not remove) */
public SRServiceImpl() { }
/** Sample main for debugging Business Components code using the tester */
public static void main(String[] args) {
launchTester("devguide.model", /* package name */
"SRServiceLocal" /* Configuration Name */);
/** Container's getter for YourViewObjectInstance1 */
public ViewObjectImpl getYourViewObjectInstance1() {
return (ViewObjectImpl)findViewObject("YourViewObjectInstance1");
// ... Additional ViewObjectImpl getters for each view object instance
// ... ViewLink getters for view link instances here
when i try this i didn't find the default generation for main method
have i do something before enable custom java file for Application module
hope to hear from you soon

hi nonStop
Since you are using Jdeveloper TP3, this might be a better place to ask your question:
"JDeveloper and OC4J 11g Technology Preview"
JDeveloper and OC4J 11g Technology Preview
success
Jan Vervecken

Is it proper for an application module has 300 views in the data model?

Based on my understanding, all view object instances are initialized at the same time as the application module.
It follows that when an application module is associated with a user session, the queries of each view object in the data model are executed.
ie. if the data model has 325 view object instances, 325 queries will be executed.
This doesn't seem efficient:
1. As each user session only need to access a subset of the view objects (for examples 35 views), the rest of view objects need not be instantiated for that session.
2. Performance may be slow on executing all 325 queries at one time, even worse when some queries are complex queries.
Am I correct on this?
In this case, will it be better to instantiate the view objects using the view object definition at runtime instead of adding all of them to the application module at design time?

No, that's not the default behaviour.
Assuming you're talking JDev 11, the AM on it's General tab as a Tuning option where you can set the loading of the VOs to Lazy or Non-Lazy, Lazy is the default. In turn each VO on their General tab also has a Tuning option of similar nature.
Online documentation says:
Lazy LoadingSelect to choose lazy loading. In this case, the application module instance is created without any of its components. Your view object and nested application module instances will not load until the first time they are used. For example, when lazy loading is enabled, a view object is instantiated only when the application accesses it. This will make start-up time faster.
Non-lazy Loading
Select to choose non-lazy loading. Your view object and nested application module instances will load when the application starts up. For example, suppose the application module you are editing defines three view objects and two nested application modules (which appear in the Application Module Instance section of the Data Model page over the application module overview editor). When lazy loading is disabled, the application module instance is created together with all three view objects and both nested application modules.>
So in essence as you describe for each session, if we're using the Lazy setting, even though you have 325 VOs within an AM, if the user within the session only visits 35 queries, only 35 queries should fire.
Does this help?
CM.

[svn:bz-trunk] 20754: My latest EndpointPushNotifier change changed the style of the code quite a bit (sorry for that, it was my IDE settings getting in the loop here) I only changed one char line 389.

Revision: 20754
Revision: 20754
Author:   [email protected]
Date:     2011-03-10 03:36:05 -0800 (Thu, 10 Mar 2011)
Log Message:
My latest EndpointPushNotifier change changed the style of the code quite a bit (sorry for that, it was my IDE settings getting in the loop here) I only changed one char line 389.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/client/EndpointPushNotifier.java

I seem to have fixed it by putting <div class="clearfloat"></div> after the navigation bar?

[svn:fx-trunk] 12293: Fix ASC-3726: implement ECMA-262 style numeric conversions for constant numerics.

Revision: 12293
Revision: 12293
Author:   [email protected]
Date:     2009-11-30 13:23:52 -0800 (Mon, 30 Nov 2009)
Log Message:
Fix ASC-3726: implement ECMA-262 style numeric conversions for constant numerics.
Tests: asc,flex,tamarin checkin tests
Review: Jeff Dyer (src), Chris Peyer (tests)
Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3726
    http://bugs.adobe.com/jira/browse/ECMA-262
Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/ConstantEvaluator.java
Added Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/util/NumericConversions.java
Removed Paths:
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefClPrivInstMethArg ValIntErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefClPrivInstMethArg ValUintErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefClPubInstMethArgV alIntErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefClPubInstMethArgV alUintErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefInstMethArgValErr .err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefInstMethArgValuin tErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefMethArgValErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefMethArgValuintErr .err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefPackMethArgValErr .err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefPackMethArgValUin tErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefStatMethArgValErr .err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvDefStaticMethArgValU intErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvIntClDefInstMethArgU intErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvPubClPrivInstMethArg ValIntErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvPubClPrivInstMethArg ValUintErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvPubClPubInstMethArgV alUintErr.err
    flex/sdk/trunk/modules/asc/test/compiler/as3/Definitions/Function/InvPubClPubInstMethArgV alintErr.err

[svn:fx-trunk] 16037: Per request of TLF, rewrote CSSTextLayoutFormat to extend TextLayoutFormat rather than implement ITextLayoutFormat .

Revision: 16037
Revision: 16037
Author:   [email protected]
Date:     2010-05-11 11:55:08 -0700 (Tue, 11 May 2010)
Log Message:
Per request of TLF, rewrote CSSTextLayoutFormat to extend TextLayoutFormat rather than implement ITextLayoutFormat. This will allow TLF to add new formats and continue to use Flex without requiring any immediate work on our part.
QE notes:
Doc notes: None
Bugs:
Reviewed By: Gordon
Tests run: checkintests
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/core/CSSTextLayoutFormat.as

Manage bean methods not able to call application module methods

Hi,
I have an ADF application where in my managed bean method needs to call AppModuleImpl methods. I use the code as below:
public void getSummary() {
DCBindingContainer binding = (DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();
OperationBinding op = binding.getOperationBinding("getVOData");
op.execute();
The code works fine when I run the application in my IntegratedWeblogicServer and I am able to get the data on my .jsp pages.
I have installed weblogic server on another machine and I need to deploy and run my application on that server. But when I try doing that, the above code is not able to call the AppModule method and I see no data on my page (Also there is no error or exceptin thrown). Seems that the ViewController project is not able to interact with the Model project.
Is there any extra configuration to be done on the newly installed weblogic server to get this work? Or will some change in the application code help?
Please suggest.
Thanks and regards,
Ansh

Hi,
While creating the weblogic domain, we had the following checkboxes checked:
1. Basic weblogic server domain [wlserver_10.3]
2. Oracle JRF [oracle_common]
I hope this is what we need.
Yes, I also have the adf runtime installed.

[svn:fx-trunk] 12663: Adding the resource bundle and fat-swc targets for osmf and textlayout.

Revision: 12663
Revision: 12663
Author:   [email protected]
Date:     2009-12-08 12:22:31 -0800 (Tue, 08 Dec 2009)
Log Message:
Adding the resource bundle and fat-swc targets for osmf and textlayout. Also for osmf adding the doc target. This new format that I added to the two project build files will be what we will use going forward for all projects. I have all the other projects modified and plan on checking them in soon. The format change will make adding new locales easier as well as adding the fat-swc target when needed.
QE notes: no
Doc notes: no
Bugs: no
Reviewer: gaurav
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/build.xml
    flex/sdk/trunk/frameworks/projects/osmf/build.xml
    flex/sdk/trunk/frameworks/projects/textLayout/build.xml
Added Paths:
    flex/sdk/trunk/frameworks/projects/osmf/bundles/
    flex/sdk/trunk/frameworks/projects/osmf/bundles/en_US/
    flex/sdk/trunk/frameworks/projects/osmf/bundles/en_US/osmf.properties
    flex/sdk/trunk/frameworks/projects/textLayout/bundles/en_US/textLayout.properties
Removed Paths:
    flex/sdk/trunk/frameworks/projects/osmf/src/OSMFDocClasses.as
    flex/sdk/trunk/frameworks/projects/textLayout/bundles/en_US/empty.properties

Thats good news.

[svn:fx-trunk] 10050: Per-Module Style Management: Create a style manager for each application/module.

Similar Messages

Maybe you are looking for