ViewObject programmatically

Similar Questions

• Bug: ViewObject programmatic and form Validation

  Hello
  
  I've set up a display object as described here: http://stackoverflow.com/a/14611815/59087
  
  Assigned to the view object is a shown here validation rule: http://i.imgur.com/HXiwPUL.png
  
  The StartDate attribute value must be a date equal to or earlier than the EndDate attribute.
  
  The view object is not supported by an entity. With the help of an entity here is not logically necessary as these input parameters are intended to be transmitted directly to a report. The parameters are independent of an entity and rather arbitrary.
  
  When a February 1, 2013 start date and an end date of February 28, 2013 are given, a validation rule error: http://i.imgur.com/8v4007w.png
  
  You can see how the view object has been created here: http://imgur.com/HQLNh5U, uqtt5Fq, X8fldVt, HXiwPUL, 8v4007w #0
  
  This was recorded as a SR with Oracle and received the following response, "I guess the question here is this place where you added the validation. If this is added to the attribute level, then he will be fired by updating the attributes and there is no guarantee of the order of the attributes updates. If this is not the right place for you to add validation dealing with several attributes of value. Ideally it should have been added as entity level validation in your OE. And if your VO is updatab; e, that he must have been supported by EO-it is British Colombia was designed.
  If EO the introduction is not possible now, maybe, you can try to replicate the validation at the attribute level and trigger the validation of the attribute last updated"
  
  I'm fairly certain that by selecting programmatic (http://i.imgur.com/HQLNh5U.png), this means that no entity is necessary for the view.
  
  In addition, given that the Rules of Validation tab appears (http://i.imgur.com/HXiwPUL.png), and a comparison rule can be defined, it leads me to believe that it is a bug.
  
  As a workaround, I can define an 'empty' entity that is not accompanied by a database object and performs an entity-level validation. I don't like this because it is a little more work and requires the implementation of a transitional 'ID' fake to uniquely identify the row.
  
  Other ideas (how can I enforce the order of updates of attributes so that StartDate is filled in the view before EndDate object, thereby ensuring that the validation is successful)?
  
  Published by: Dave.Jarvis on February 7, 2013 11:31

  Dave, support has a point here. Level of the attribute validation cannot cover the rules that have other attributes in the rule. In this case, you are detailed on the order of the attributes. The reason is that the validation of the attribute levels fires when the attribute changes its value. This is why the framework allows entity level validation (naturally only on an EO) where you can assume that all values are up to date and can be compared with each other.
  However, on a view levels validation object only transient attributes attribute is permitted. As is the validation of the attribute levels the same ruling applies as for EO. You should not compare two attributes of a levels of attribute validation rule as you cannot predict the order attributes and so you cannot predict the outcome of the rule.
  I do not see a bug here, such as validation to only at the level of the attribute.

  OK, what can you do?
  You can add an EO (as you said already) and add a level entity rule it. It will work, but needs some work more.
  You can remove the date field validation rules. MinValue and validate them in for example a bean or you can even use a method that is exposed in the client interface of your VO for this. Then, you call the method when the user clicks the button before you start the report. When the rule is triggered, you do not start the report, but the message.

  Timo

• Viewobject programmatically insert.

  Hello
  It's my use case.
  
  I need to insert data into a table at the click of the button. To do this, I did the following steps:
  
  (1) I created a method in the module of the application. (I've hard-coded the data to insert)
  (2) I exposed in the client interface.
  (3) the data control, I slipped and fell into the page as a button.
  It works very well.
  
  Now, I want to pass parameters to the method, and these values must be inserted into the table. How to call this method of backup bean.
  
  My code in the application module:
  
  public void test5 () {}
  NewRow rank is getUser_detail1 () .createRow ();.
  newRow.setAttribute ("SlNo", "1");
  newRow.setAttribute ("DomainUsername", "the Infanta");
  newRow.setAttribute("SecretQuestionNo","2");
  newRow.setAttribute ("SecretAnswer", "girl");
  System.out.println ("Done");
  getUser_detail1 () .insertRow (newRow);
  getDBTransaction () .commit ();
  getUser_detail1 () .executeQuery ();
  
  }
  
  The code in the bean to support:
  public void save_bn() {}
  
  String namevar = (String) username.getValue ();
  FacesContext context = FacesContext.getCurrentInstance ();
  BindingContext bindingContext = BindingContext.getCurrent ();
  DC DCDataControl = bindingContext.findDataControl ("AppModule");
  AppM AppModuleImpl = (AppModuleImpl) dc.getDataProvider ();
  appM.test5 ();
  }
  
  Slno, domain username, question secret, meets values that I need to attend support bean. How to do this?

  Redefine your customer interface with settings method and add it as a link to the specific page, that you will call the bean support.

  The bean support

  DCBindingContainer bindings = ((DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry());
  OperationBinding method = bindings.getOperationBinding("clientMethodId");
  Map params = method.getParamsMap();
  params.put("param1name", param1Value);
  params.put("param2name", param2Value);
  ...and so on...
  method.execute();
  

  CM.

• ViewObject do not retrieve all rows programmatically

  Hi all
  I use Jdeveloper version 11.1.2.1.0
  I consulted a VO inside a bean managed by the following code

       
  private void getEmployeeRowCount(){  
   BindingContext bctx = BindingContext.getCurrent();
   DataControl myAMDataControl = bctx.findDataControl("MyAMDataControl");
   ApplicationModule service = (ApplicationModule)myAMDataControl.getDataProvider();
   ApplicationModule myAM = service.findApplicationModule("MyAM");
   ViewObject employeeVO = myAM.findViewObject("EmployeeVO");
   System.out.println(employeeVO.getRowCount());
   }

  At first it prints the actual number of lines in the t
  But if I call this function after the I accessed EmployeeVO during execution (specifically when I change any value in EmployeeVO), the employeeVO.getRowCount () function returns the value 1
  
  what I am doing wrong?
  
  Thank you
  Puneet

  After you clear the view criteria to get the actual number of lines.
  Try

  vo.applyviewCriteria(null);
  vo.executeQuery();
  sop(" " +vo.getRowCount());
  

• Binding form to ViewObject fields programmatically

  I created a view 'UdfVO' object which not is not related with any sql infact I created it by selecting the third option i.e. lines adding programmatically. It contains only the unique field "Udf1. Now, I have a form and I'll add control on this form at runtime, then liaison "Udf1. It is runnning perfect, but it does not show the value in the line added by program in 'UdfVO '. In addition, it is also show field as readonly. I pasted my code below:
  
  ViewObjectImpl udfVO = (ViewObjectImpl) getApplicatoinModule () .findViewObject ("UdfVO1");
  Line udfRow = udfVO.getCurrentRow ();
  If (udfRow == null) {}
  udfRow = udfVO.createRow ();
  
  }
  udfRow.setAttribute ("Udf1", "Udf Value");
  udfVO.setCurrentRow (udfRow);
  
  DCBindingContainer bc = getBindingContainer();
  DCIteratorBinding ib = bc.getIteratorBinding ("UdfVO1", null, "UdfVO1Iterator", 25); creation of iterator
  
  ValueExpression ve = FacesContext.getCurrentInstance () .getApplication () .getExpressionFactory () .createValueExpression (FacesContext.getCurrentInstance () .getELContext (), "#{bindings.") Udf1.inputValue} "(,Java.lang.String.Class);"
  JUCtrlAttrsBinding vb = new JUCtrlAttrsBinding (testComp, ib, new String [] {"Udf1"});
  vb.setName ("Udf1");
  Name RichInputText = new RichInputText();
  name.setLabel ("Udf 1");
  
  name.setReadOnly (false);
  name.setRendered (true);
  name.setValueExpression ("value", ve);
  employeeFormLayout.getChildren () .add (name);
  AdfFacesContext.getCurrentInstance () .addPartialTarget (employeeFormLayout);
  AdfFacesContext.getCurrentInstance () .addPartialTarget (name);

  Documentation of VO:

  public line createRow()

  Creates a new line object, but does not insert any there in the line set.
  >
  If you insert the line in your VO after it is created.

  For the second problem:
  The intput field is read-only because your VO is not based on an OA. In this case, the framework assumes that the attribute is read-only. You should be able to allocate the available attribute writable (setReadOnly (false)) in your code of bean before putting it on the page.

  Timo

• ViewObject range Paging performance problem

  Hi all

  I am facing a performance problem with the implementation of an obligation to programmatically add a number of extra where the parameters of the clause (using bind) variable in combination with range paging.

  My code looks like this

  ...
  
  ApplicationModule am = Configuration.createRootApplicationModule("services.DossierAM", "DossierAMLocal");
  ViewObject vo = am.findViewObject("DossierListView");
  
  // apply programmatic view criteria
  ViewCriteria vc = vo.createViewCriteria();
  ViewCriteriaRow vcr = vc.createViewCriteriaRow();
  vcr.setAttribute("Reference", "15/%");
  vc.addElement(vcr);
  vo.applyViewCriteria(vc, true);
  
  
  // enable range paging
  vo.setAccessMode(RowSet.RANGE_PAGING);
  vo.setIterMode(RowIterator.ITER_MODE_LAST_PAGE_PARTIAL);
  vo.setRangeSize(50);
  vo.scrollToRangePage(5); // Cause a java.sql.SQLException: Parameter IN or OUT missing for index.....debugging learned that the :vc_temp_1 bind variable is not filled
  // vo.scrollToRange(250); // Cause a java.sql.SQLException: Parameter IN or OUT missing for index.....debugging learned that the :vc_temp_1 bind variable is not filled
  
  ... 
    ...
  

  I found 2 solutions, but they both require an application of additional database that is, performance wise, is not acceptable.

  The first solution is to slip into an additional call to exectueQuery() before the call to function scrollToRangePage (int) or scrollToRange (int).

  The second solution is to use the method (int) setRangeStart instead of variants scrollToRange (Page). This method performs also 2 database calls.

  My question to you:

  Is there another way to satisfy the requirement of programming add a certain number of parameters of the additional where clause (using the variable binding) in combination with the pagination of the range without the need to perform queries of database 2?

  The code is tested with JDeveloper, 11.1.2.4.0, and 12.1.3.0.0 and behaves the same on both versions.

  Kind regards

  Steven.

  Have you tried to create truly VC with bind variable (rather than use binding implied var created by frame)?

  Something like: http://www.jobinesh.com/2010/10/creating-view-criteria-having-bind.html

  Dario

• Criteria of programmatic view adding the date condition

  Hi all

  I use Jdev 12.1.3. I wrote a method in AMImpl to filter my viewobject based on custom search screen of the user interface.

  I create the criteria for the view programmatically. I have check SMSDate field in my VO date between the criteria in the field settings start date and end date.

  How to define this condition by programming

  ' Public Sub searchInfo (String attribut1, String fullname, startDate, endDate oracle.jbo.domain.Date oracle.jbo.domain.Date) {}

  ViewObjectImpl vo = getSmsInfoVO1();

  ViewCriteria vc = vo.createViewCriteria ();

  ViewCriteriaRow vcRow = vc.createViewCriteriaRow ();

  If (attribut1! = null & &! attribute1.isEmpty ()) {}

  vcRow.setAttribute ("attribut1", attribute1);

  vc.addRow (vcRow);

  }

  If (fullname! = null & &! fullname.isEmpty ()) {}

  vcRow.setAttribute ("full name", fullname);

  vc.addRow (vcRow);

  }

  Need a logic here set VO attribute SMSDate and check the date between the startDate and endDate parameters method

  vo.applyViewCriteria (vc);

  vo.executeQuery ();

  }

  Check this box:

  setOperator ("between")

• [ADF, JDev12.1.3] How to get programmatically the value of a field of VO of detail while accessing the master istance VO?

  Hallo,

  I have a master VO based on entities and a retail entity based VO to which JDev automatically created a link display (1 to 1 relationship).

  In the request Module I programmatically access MasterVO and I would like to get the value of a field of DetailVO...

  ViewObject vo = getMaster1();
  RowSetIterator iterator = vo.createRowSetIterator(null);
  iterator.reset();
  if (iterator.hasNext()) {
    MasterVORowImpl row = (MasterVORowImpl) iterator.next();
    System.out.println(row.getField1);
    System.out.println(row.getField2);
    // ...
    System.out.println( <DetailVO.Field1> ); // How to...?
    // ...
    }
  iterator.closeRowSetIterator();
  

  How can I achieve this?

  Thank you

  Federico

  In MasterVORowImpl should be getter for the detail rows (if you selected "Include the accessors" option when you generated class MasterVORowImpl).

  Dario

• Create a list of values (Lov) programmatically

  I need to dynamically create the ListOfValues during execution.

  For this, I found a few links, in which it is explained how to create the ViewAccesor and the ListBindingDef which defined the Lov in the model project.

  Andrejus Baranovskis Blog: The ADF for BC and dynamic ADF ADF UI generator

  Binary: Activation for dynamic attributes ViewObject LOVs

  This kind of list of values can be rendered with the component, af:dynamicComponent, but I want to use them with the original component.

  The main problem is that: a dynamic list of values attributes do not have listOfValuesModel in the exposed binding.

  <af:inputListOfValues id="comunidadAutonomaId"
                                popupTitle="Search and Select: #{bindings.ComunidadAutonoma.hints.label}"
                                value="#{bindings.ComunidadAutonoma.inputValue}"
                                label="#{bindings.ComunidadAutonoma.hints.label}"
                                model="#{bindings.ComunidadAutonoma.listOfValuesModel}"
                                required="#{bindings.ComunidadAutonoma.hints.mandatory}"
                                columns="#{bindings.ComunidadAutonoma.hints.displayWidth}"
                                shortDesc="#{bindings.ComunidadAutonoma.hints.tooltip}">
              <f:validator binding="#{bindings.ComunidadAutonoma.validator}"/>
          </af:inputListOfValues>
  

  Model = "#{Bindings.ComunidadAutonoma.listOfValuesModel}"-> This property is empty in an attribute with a dynamic lov, at the same time, it exists in a standard attribute with lovs. "

  I could check bindings exposed during this attributes are different too.

   <attributeValues IterBinding="ProvinciasIterator" id="ComunidadAutonoma">
        <AttrNames>
          <Item Value="ComunidadAutonoma"/>
        </AttrNames>
      </attributeValues>
      <listOfValues IterBinding="ProvinciasIterator" StaticList="false" Uses="LOV_Nombre" id="Nombre"/>
  

  To solve it, I thought that I could create the ListOfValuesModel of the ListBindingDef and the ViewAccesor dynamically exposed in a managed Bean, but I don't know how he.

  public class MyBean {
  
  
    public MyBean() {
      initListOfValuesModel();
    }
  
  
    private ListOfValuesModel listOfValuesModel;
  
  
    public ListOfValuesModel getListOfValuesModel() {
      return listOfValuesModel;
    }
  
  
    private void initListOfValuesModel() {    
      DCBindingContainer bindings = getBindings();
      JUCtrlValueBinding attrBinding = (JUCtrlValueBinding)bindings.get("myAttrib");
      ViewAttributeDefImpl attr = (ViewAttributeDefImpl) attrBinding.getAttributeDef();
      ViewDefImpl viewDef = attr.getViewDef();
      ArrayList<ListBindingDef> listBindings = viewDef.getListBindingDefs();
      ListBindingDef lbLov = null;
      for (ListBindingDef listBinding : listBindings) {
        if (listBinding.getListVOName().equals(attr.getLOVName())) {
          lbLov = listBinding;
          break;
        }
      } 
      ...
      //listOfValuesModel = ;
    }
  
  
  
  
  
  
  
  
  

  Another solution would be resolved in the code of the ad: dynamicComponent, because it could render the ListOfValues I programmatically add.

  ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Code for adding programmatically to a lov

      private void buildLovVO(String voName, String voPath, String sql, Set<DataBindVar> bindVars, List<String> labels) {
          ViewDefImpl lovDef = new ViewDefImpl(voPath);
          lovDef.setBindingStyle(SQLBuilder.BINDING_STYLE_ORACLE_NAME);
          
          lovDef.setQuery(sql);
            
          lovDef.resolveDefObject();
          lovDef.registerDefObject();
          
          if (bindVars != null && bindVars.size() > 0) {
              VariableValueManager vvm = lovDef.ensureVariableManager();            
              for (DataBindVar bindVar : bindVars) {
                  VariableImpl lovBindVar = (VariableImpl)vvm.addVariable(bindVar.getBindVarName());
                  lovBindVar.setJavaType(bindVar.getBindVarType());
                  lovBindVar.setVariableKind(VariableImpl.VAR_KIND_WHERE_CLAUSE_PARAM);
                  lovBindVar.setProperty(AttributeHints.ATTRIBUTE_DISPLAY_HINT, AttributeHints.ATTRIBUTE_DISPLAY_HINT_HIDE);   
              }
          }
          
          if (labels != null && labels.size() > 0) {
              ViewObjectImpl lovVO = (ViewObjectImpl)app.createViewObject(voName, lovDef);
              for (int i = 0; i < labels.size(); i++) {
                  ((AttributeDefImpl)lovVO.getAttributeDefs()[i]).setProperty(AttributeHints.ATTRIBUTE_LABEL, labels.get(i));   
              }
          }
      }    
      
      
      private void buildListDef(ViewDefImpl dViewDefImpl, String viewAccessorName, String lovName, 
                              String listDataSourceViewDefName, Set<DataBindVar> bindVars, List<String> attribNames,
                              List<String> listAttribNames, List<String> listDisplayAttribNames) {
          ViewAccessorDef vdef = new ViewAccessorDef();
          vdef.setName(viewAccessorName); 
          vdef.setViewDefFullName(listDataSourceViewDefName);
          vdef.setRowLevelBinds(true);
          
          if (bindVars != null && bindVars.size() > 0) {
              for (DataBindVar bindVar : bindVars) {
                  vdef.getBoundParameters().addBoundParameter(bindVar.getBindVarName(), bindVar.getBindVarValue());
              }
          }
          dViewDefImpl.addViewAccessorDef(vdef);
          
          //---------PREPARAR STRING ARRAYS PARA LA FUNCION buildListBindingDef ------------//
          String[] strAttribNames = attribNames.toArray(new String[attribNames.size()]);
          String[] strListAttribNames = listAttribNames.toArray(new String[listAttribNames.size()]);
          String[] strListDisplayAttribNames = listDisplayAttribNames.toArray(new String[listDisplayAttribNames.size()]);
          
          ListBindingDef listBindingDef = buildListBindingDef(dViewDefImpl.getDefManager(), viewAccessorName, lovName,
              strAttribNames,
              strListAttribNames,
              strListDisplayAttribNames);
          dViewDefImpl.addListBindingDef(listBindingDef);  
      }
      
      private static ListBindingDef buildListBindingDef(DefinitionManager defMgr,
                                                       String listVOName,
                                                       String listBindingName,
                                                       String[] attribNames,
                                                       String[] listAttribNames,
                                                       String[] listDisplayAttribNames) {
          ListBindingDef lstbindingDef = new ListBindingDef(defMgr, DefinitionObject.DEF_SCOPE_PERS);
          lstbindingDef.setListVOName(listVOName);
          lstbindingDef.setName(listBindingName);
          lstbindingDef.setListRangeSize(-1);
          lstbindingDef.setNullValueFlag(AbstractListBinding.LIST_ADD_NULL_NOWHERE);
          lstbindingDef.setNullValueId("");
          lstbindingDef.setAttrNames(attribNames);
          lstbindingDef.setListDisplayAttrNames(listDisplayAttribNames);
          lstbindingDef.setListAttrNames(listAttribNames);
          
          return lstbindingDef;
      }
  

  ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  JDeveloper 12 c (12.1.2.0.0)

  You can download code for ADF Rich Client Demo application (ADF Faces Rich Client Demos ) and see what the code is behind the af:inputListOfValues example (LOV in this example is populated by managed bean).

  If you need create liaison for lov programmatically, and then read this blog post: ADF practice: dynamic linking LOV

  Dario

• How to create VOS programmatically using SelectOneRadioButton

  Hello world

  I use Jdeveloper 11.1.1.4 and I need to create a programmatic option using VO box.

  I created on VO... i.e. the EmployeeVO which is 'Lines Popolated programmatically, not based on query' and I created a transitional attribute 'name '.

  "So I have to assign static to this attribute values so that when I will drag to jspx it will shows me the radio buttons."

  Can anyone suggest me how acchieve this by aasigning the static value in the temporary variable may how displayed us as radio buttons?

  Thanks in advance

  A sample of 1. Can be found at http://tompeez.wordpress.com/2012/09/02/jdeveloper-using-static-viewobjects-for-lookup-data/

  Timo

• Fill the programmatic view object during execution

  Hi all

  I have a requirement to switch between the three different data source during execution in a single page. The user interface and the field names are the same for these three cases, but data from various sources (queries).

  So, imagine that we have 3 objects in view which has implemented read-only (object request depending on the view) and we want to fill a display object at the main performance as a data source for my page.

  My idea is to use "Prgorammatic view object" for this data source and then fill dynamically the contents of one of the three objects view read-only based on a setting in the user's selection.

  First of all, I want to know if it is thin approach and if yes, then get some points on the implementation or any other sample.

  I found this example:

  http://techiecook.WordPress.com/2011/05/17/programmatically-populate-view-objects-in-Oracle-ADF/

  Thanks in advance,

  Nasser

  Hello

  It is more a case of use for Adaptive connections. See:https://blogs.oracle.com/groundside/entry/towards_ultra_reusability_for_adf

  You can use EL to change the name of the ViewObject that an iterator in ADF queries its data. If the switch is on the link layer and there is no need for programmatic view objects. Unlike in the article of the blog above, VO 3 exist in your case then you don't need to create on the fly. Just change the name of VO in the managed bean referenced

  Frank

• [SOLVED] Create ViewObject as placeholder for the parameters of the form

  Hello
  
  I posted the following question (JDeveloper 11.1.2.3):
  
  http://StackOverflow.com/questions/14592202/create-ViewObject-as-placeholder-for-form-parameters
  
  Basically, how do you create a ViewObject that can perform validation and harness LOVs, but don't don't don't need to be supported by any source of data?
  
  Is it still the right approach?
  
  Thank you!

  Hey, Timo.

  This can be accomplished without an OA. As far as I can tell, it's the right answer, but this forum does not allow me to choose my own answer as correct, but somehow allows me to report my own post as an abuse. Strange.

  Find the property formatted (and selected as correct) answer on StackOverflow: http://stackoverflow.com/a/14611815/59087

  # Solution

  You have:

  -Create a view object to be programmatic, with the desired attributes.
  -Configure the view with validation rules object.
  -Configure the Module of the Application.
  -Create the form on the web page.
  -Update the page link to create a new line.

  # Create object View

  Create the view as follows:

  1. type Control+n to open the * New Gallery *.
  1. search and select * view object *.
  1. click on * OK *.
  1 set * Package *, * name *, and * display name * properly.
  1 set * data * to * programme *.
  1. click on * following *.
  1. click on * new * and provide a significant attribute name.
  1. click on * OK *.
  1. Add the remaining attributes.
  1. click on * following *.
  1 set * Updatable * to * always * all attributes.
  1 set * Type * for the appropriate data type.
  1. click on * finish *.

  # Configure Validation rules

  Configure the following validation rules:

  1. click on the * attributes * tab.
  1. Select the desired attribute.
  1. click on the * tab Validation rules *.
  1. click on the * + * icon in the * section Validation rules *.
  1 set it * rule definition * as required.
  1. set * error * as required.
  1 Repeat to add validation as necessary rules.

  At this point a view object has been configured and the * list tab of values * can be used to reference LOVs based on a query.

  # Configuration Application Module

  Configure the module of the application as follows:

  1 double-click on the module of the app.
  1. Select * model data * tab.
  1 Shuttle the object view of * available see items * to * model data *.
  1. remove the * 1 * suffix.
  1. save the application.

  Note: If the view object is not visible, restart JDeveloper.

  # Create Web Form Page

  Create a web page to the form as follows:

  1. create a new JSF of the object view page.
  1 update the * data controls * see the instance of the view object.
  1. drag and drop the view on the page object.
  "1. Select * form" ADF form *.
  1 check * include submit button *.
  1. click on * OK *.

  The web page is created.

  # Update the Page link

  Cannot change the attributes of the view object unless there is a 'line' created for the instance of the view object. Creation of this line in memory must occur before the display of the content on the page. Accomplish this as follows:

  1 extend the data controls to reveal the view object * operations *.
  1 drag * Create * in the facet of footer.
  1. Select * ADF button *.
  1. right-click on the page.
  1. Select * go to Page definition *.
  1. click on * + * next * executable *.
  1. Select * invokeAction *.
  1. click on * OK *.
  1. set * id * to: create
  1. set * lie * for: create
  1. click on OK.
  1. the refresh value: * prepareModel *.
  1. save all.

  You can now remove the create"" button.

  The validation is applied, and data-driven LOVs can be used.

  Published by: Dave.Jarvis on January 30, 2013 11:15

• Where the programmatic point of view is stored in the database.

  Hi all
  What will be the scope of the views that are created by programming in the database.
  they will store in any temporary tabels in the database, anyone would give an idea.
  
  Thanks in advance.
  
  Renuka

  Renuka,

  Although we do not require that any object database like (views / synonyms) to create the programmatic view object we need a database connection to initially create the ProgViewObject.

  Whence your data? Other sources of data in DB?

  And as you said ViewObjects will be only held at the Application level in DB used for objects of the BC.
  In this case even if we ProgViewObjects the BC project in a large number is should not affect performance on the side of demand on the underlying DB used to correct App?

  Not really. ViewObjects themselves has not only any space in DB (these are simple XML files - with or without related java classes). However, the VO must contact the DB to retrieve data. If you do not use the database (that you used to create a connection), to fetch data (and using a different data Source), then the answer to your question is Yes. It would not impact on the underlying DB performance. However, there would be on the Data Source, you use for programming of your.

  Arun-

• Several tables af, same viewobject, whereclause different

  Hello.
  
  JDeveloper 11.1.1.2, bc4j, jsff
  
  
  Is it possible to have pages (jsff) based on the same viewobject IE. people where page 1 shows men (where sex = male) and page 2 shows women (where sex = female)?
  
  How?
  
  Best regards
  Erik

  Hi Erik,

  Yes, you can have two pages based on the object of the view and what you can do is to have a bean managed for each page and alter the query from the VO programmatically add the male/female criteria on the managed bean class constructor method (or call a method that alter the manufacturer VO criteria) or by using PagePhaseListener.

  I hope this helps.

  Thank you
  Cree

• Best practices for ViewObjects when inserting data through pl/sql procedure

  My applications is form of oracle database level enterprise application and developing now the new module of ADF 11 g but there is restriction that all insert, update, and delete data will be through procedures oracle pl/sql. Now my question is that adf pages should be linked with ViewObjects based on the entity object or Viewobjects not based on entity / sql query. Currently, I have pages with programmatic ViewObjects that don't rely on entity objects, or on the sql query. In these display objects, I create transient attributes and then used to create pages in the adf. Click Save, I extracted the data of the current line of ViewObject and pass it to the procedure. It's works well but I was wondering if this approach is ok or it is better for it. Ideally, I would like to create from EntityObject ViewObjects but don't have not find a way to sync entityObjects with the data inserted through procedures.

  Hello

  I have create an EO for database view and replace the doDML () - method. For insert/update, and delete, I call the pl/sql functions.

  See "38.5 basis an entity on a Package PL/SQL API object" in the merger Oracle® Fusion Middleware developer for Oracle application development Guide
  Framework.