Accessors exposed in entity object

Hi, I came from JPA world and I am suited to use relathionship field (old CMR ) in entity class.
Now I am working with ADF EntityObject (EO) and I found equivalent concept as Accessors in Association component.
Then ,starting from my EntityOne I create 2 associations :+
the first one to many to EntityTwo, and the second one to one to EntityThre.
After I have created a ViewObject based on EntityOne and I expected to have in DataControl iterator related to ViewObjet :
one field pointing to EntytyThre(one to one) and a sub iterator of collection of EntityTwo elements (one to many), but I don't understand why I don't see any of two in DataControl .
My intention was to have a link navigation on ADF page to navigate separately to Table of EntityTwo element and a Link to navigate to related EntityThree object.
Can someone help me ?
Edited by: Kronos72it on Sep 27, 2012 3:21 PM

Kronos72it wrote:
Yes, I make a ViewObject based on EntitOne wich is the root entity .
Are you maning to create VieweObject also for EntityTwo and EntityThree and after make ViewLink between all ViewObject ?- Yes.
If it is true, then associations between entity object doesn't influence iterator exposed on DC ? - Quite so.
then what are utility of associations on EO ?https://blogs.oracle.com/smuenchadf/entry/what_are_entity_associations_g

Similar Messages

HOWTO: Expose Entity Object Methods to Clients

By design, clients cannot directly access entity objects. The view object layer provides an extra layer of security--you can choose exactly what data and methods you want clients to see.
This HOWTO describes the process of exposing an entity object method to client programs.
First, if you don't already have one, you must base a view object on your entity object and add the view object to your data model. For full details of how to do this, see the help topics under
+Developing Business Components
--Working with View Objects, View Links, Application Modules, and Clients
+----Creating and Modifying View Objects, View Links, Application Modules, and Clients
For the purposes of this HOWTO, we'll assume that you already have an entity object, Employees, with a method on it, calculateBonus(),
and a view object EmployeesView based on Employees.
First, you must generate a view row class. A view row represents one row of the view object's cache; it corresponds to a view of a particular entity object.
To generate a view row class:
1. Right-click EmployeesView and choose Edit.
2. In the View Object Editor, select the Java page.
3. Select Generate Java File and Generate Accessors for the view row class.
4. Click Done. This creates a class called EmployeesViewRowImpl.
Next, you should add a "delegator" method to the view row class--a public method with the exact same signature as the entity method, that simply calls the entity method. For example:
public int calculateBonus(int rating) {
return getEmployees().calculateBonus(rating);
Next, you should export this method.
1. Right-click EmployeesView and choose Edit.
2. In the View Object Editor, select the Client Row Methods page.
3. Shuttle the method you just created into the Selected list and click Done.
This creates an interface called EmployeesViewRow that contains your method.
Now you can call the method from your client. You should cast the row returned by EmployeesView.current(), the <jbo:Row> tag, or a similar method or data tag to EmployeesViewRow.
For example,
<jbo:Row id="myRow" datasource="ds" action=Current>
<% out.println(((EmployeesViewRow) myRow).calculateBonus(3)); %>
</jbo:Row>
null

Hi Lisa,
There's a difference between exporting methods (on an application module, view object, and view row--this is done on the "Client Methods" tab of the view object and application module wizards and the "Client Row Methods" tab of the view object wizard) and making an application module remotable (which is done on the "remote" tab of the application module wizard).
You should always export methods you want clients to use--and you only need to do this on the application module if you've written methods on your application module (which I didn't in this HOWTO). You can still use these methods in local mode--the interfaces will be present locally. The advantage of exporting methods is that it doesn't lock you into local mode--you'll be able to change to remote mode later (if you decide that's the way to go) with minimal changes--because the interfaces will be present locally even when the implementation classes aren't.
By contrast, you should only make an application module remotable if you're planning on deploying in a non-local configuration. You can do this step right before deployment.
Hope this helps,
Avrom
null

ADF: use of view link Accessor in Entity Object = always null?

Hi,
JClient 9.0.5.2, adf model.
I would like to use the view link accessor method in the master EO to retrieve detail EO values and the view link accessor method in the detail EO to retrieve master EO values.
Detail Rule:
In the detail EO an attribute is derived from an attribute of the master EO: detail attribute = master attribute.
Master Rule:
In the master EO an attribute is derived from the detail EO: master atribute set to 0 if detail EO exist else set to 0.
Tables:
Table Master => MasterEO => MasterVO
- masterPK (not updateable)
- masterField (not updateable)
- hasDetailsFlag
Table Detail => DetailEO => DetailVO
- detailPK (not updateable)
- masterPK => foreign key (not updateable)
- masterField (query only)
MasterDetailLink based on foreign key.
In link wizard I asked for the generation of following accessors in the source & destination Entity Objects:
In DetailEO accessor name: RetrieveFromMaster
In MasterEO accessor name: RetrieveFromDetail
In the DetailEO, I asked for the generation of the DetailEOImpl file, accessors and create method.
As wriiten in the file, before the create method:
** Add attribute defaulting logic in this method. **
I tought this is the place to retrieve the master attribute:
The code:
MasterVORowImpl masterVO = getRetrieveFromMaster();
if (masterVO == null)
System.out.println("MasterVORowImpl masterVO create NNNNNNNNNNNUUUUUUUULLLLLLLLLL");
The masterVO is always null?
I suppose I didn't understand something, my guest is that ViewObjects may not be used for default logic?
I know how to implement those rules in the database with triggers.
I think that the data I need for implementing those rules exist somewhere at the ADF level so retrieving the data from the db is not necessary?
Could somebody give some clues?
I didn't find a similar example in the Business Rules in BC4J document.
Your help will be appreciated
Frederic

Hi,
Detail Rule, copy attribute value form master.
In DetailEOImpl:
protected void create(AttributeList attributeList)
setAttribute(MASTERFIELD,this.getMaster().getMasterField());
super.create(attributeList);
Master rule, set flag to 0 if no details else set to 1.
In the MasterEOImpl added method to check if detail row exists based on Row Iterator => no db retrieval?
This method also sets the flag accordingly:
protected void checkHasOtherDetails()
oracle.jbo.RowIterator ri = this.getRetrieveFromdetail();
ri.last();
// last() must be called else hasNext() returns true even on last delete ???
Number hasDetails = Constants.NUMBER_NO; // = 1
if (ri.hasNext() || ri.hasPrevious())
hasDetails = Constants.NUMBER_YES; // = 0
if (!getHasDetailsFlag().equals(hasDetails)) {
this.setHasDetailsFlag(hasDetails);
I call this method in the remove method of the detailEOImpl:
public void remove()
this.getRetrieeFromMaster().checkHasOtherDetails();
super.remove();
To set the flag I added follwoing code in the create method of the DetailEOImpl:
protected void create(AttributeList attributeList)
setAttribute(MASTERFIELD,this.getMaster().getMasterField());
**** ADDED ***
Number masterHasDetailsFlag = getRetrieveFromMaster().getHasDetailsFlag();
if (!masterHasDetailsFlag.equals(Constants.NUMBER_YES)) {
getRetrieveFromMaster().setHasDetailsFlag(Constants.NUMBER_YES));
super.create(attributeList);
One more question:
Is there a danger of calling last() on row iterators in create/update/remove methods of *Impl files?
=> current row changed => any effect on display in JPanel
Thanks
Frederic
PS All variable/method/class names have been manually renamed in this code so some small syntax problems may exist.

Problem exposing Accessor Methods on View object (ViewRowImpl.java)

JDeveloper 9.03
I have a view link, ViewLinkSourceDest, that links two view objects Source and Destination. Each view object has its respective ViewRowImpl.java file created.
I have selected "Generate Accessor in View Object" in View link Properties of the View Link Wizard for both source and destination view objects.
The correct Accessor methods are available in both the source and destination ViewRowImpl files.
When I access the Source accessor method from the DestinationViewRowImpl object I receive the following error:
          ORA-00904: invalid column name
          It is also is displaying the Source view object's SQL statement with the (:1 = Destination.ID) where clause.
The error is occurring when trying to retrieve the view object using this type of method call:
          Row r = this.getSourceView();
After further investigation I have found an example set of view objects in which the error does not occur. The difference was in the ViewLink.xml file.
The ViewLink.xml file that accesses the Accessor with the error begins like this:
          <ViewLink
               Name="ViewLink"
               Where=":1 = Destination._ID" >
The ViewLink.xml file that accesses the Accessor with no error begins like this:
          <ViewLink
               Name="ViewLink"
               EntityAssociation ="SourceDestAssociation" >
suggesting that the use of an association would resolve this problem.
I was not able to create a View link based on an association that would generate a ViewLink.xml file that ressemble the successful file above. I could however manually add the correct entry to the xml file that caused the error and sucessfully access the Accessor method in the source object. This is not the final answer because the IDE will regenerate the ViewLink.xml file to its original state even if created with the appropriate Association.
Is this a bug?
Is the way the ViewLink.xml file created different in JDev 9.03 than in 9.02
Is there something I am missing that is causing the ViewLink.xml file to generate incorrectly?
Any suggestions would be helpful.
Rob

Steps to recreate:
1 Create SomeSuperEntityImpl.java extended by SourceEntityImpl.java and DestinationEntityImpl.java entity objects.
2 Create SourceView and DestinationView objects
3 Create SourceDestinationAssociation linking the entity object Source PK to Destination FK
4 Create SourceDestinationView linking Source and Destination view using the SourceDestinationAssociation
View the SourceDestinationView.xml file and you will see that the viewlink has Where=":1 = source.src_id"
This is the scenario that causes the initial problem with the Accessor Methods.
If the SomeSuperEntityImpl.java is removed as the super class and the same procedure is followed you will get the desired 'EntityAssociation = "package.SourceDestinationAssociation"' in the SourceDestinationView.xml file .
Hope this is a little clearer.
Rob

Entity Object ACCESSOR

I use a view object VO1 which relies on 2 entity objects EO1 and EO2. Neither has been set to readonly in VO1.
I set in EO2, a set metod (for one attributes) which use an accessor to EO1 (by its Association).
When I insert an EO2 object on an existing EO1 object, everything is OK.
When I insert by a single command both EO1 and EO2, the accessor can't reach the corresponding EO1.
Any Idea?
Thanks

Hi,
Detail Rule, copy attribute value form master.
In DetailEOImpl:
protected void create(AttributeList attributeList)
setAttribute(MASTERFIELD,this.getMaster().getMasterField());
super.create(attributeList);
Master rule, set flag to 0 if no details else set to 1.
In the MasterEOImpl added method to check if detail row exists based on Row Iterator => no db retrieval?
This method also sets the flag accordingly:
protected void checkHasOtherDetails()
oracle.jbo.RowIterator ri = this.getRetrieveFromdetail();
ri.last();
// last() must be called else hasNext() returns true even on last delete ???
Number hasDetails = Constants.NUMBER_NO; // = 1
if (ri.hasNext() || ri.hasPrevious())
hasDetails = Constants.NUMBER_YES; // = 0
if (!getHasDetailsFlag().equals(hasDetails)) {
this.setHasDetailsFlag(hasDetails);
I call this method in the remove method of the detailEOImpl:
public void remove()
this.getRetrieeFromMaster().checkHasOtherDetails();
super.remove();
To set the flag I added follwoing code in the create method of the DetailEOImpl:
protected void create(AttributeList attributeList)
setAttribute(MASTERFIELD,this.getMaster().getMasterField());
**** ADDED ***
Number masterHasDetailsFlag = getRetrieveFromMaster().getHasDetailsFlag();
if (!masterHasDetailsFlag.equals(Constants.NUMBER_YES)) {
getRetrieveFromMaster().setHasDetailsFlag(Constants.NUMBER_YES));
super.create(attributeList);
One more question:
Is there a danger of calling last() on row iterators in create/update/remove methods of *Impl files?
=> current row changed => any effect on display in JPanel
Thanks
Frederic
PS All variable/method/class names have been manually renamed in this code so some small syntax problems may exist.

Which is better creating view accessor based on view object or view instanc

When creating view accessors whether in the entity object or in the view object, we have two options:
1- create the view accessor based on a view object.
2- create the view accessor based on a view instance.
what are the differences between these two options?
what are the cases where I should only use option 1 or option 2?
which one is better?

Hello Timo,
I will try to explain my question better.
when we create view accessor, after click on create new view accessor icon, the create view accessor window is opened, at the header of this window there is a statement says:
Select a view object or shared view instance and shuttle it to the selected list to create a view accessor.
and here is my concern, which one to use
1- select a view object from one of the available view object and shuttle it to the selected list.
2- select a view instance from the application module and shuttle it to selected area.
If you have FOD sample (and I am sure you have it :) ), I see that oracle team has used both of them in different places, for examples
1- in oracle.fodemo.storefront.entities.PersonEO all view accessors are created from view instance in SharedLookupService application module.
<ViewAccessor
    Name="PersonTypesVA"
    ViewObjectName="oracle.fodemo.storefront.lookups.LookupsBaseVO"
    AMUsageName="SharedLookupService"
    ViewInstanceName="PersonTypes"/>is it because they are used to create LOV?
2- in oracle.fodemo.storefront.entities.OrderEO the view accessor is created from a view object, not from instance inside application module.
    <ViewAccessor
    Name="OrdersVO"
    ViewObjectName="oracle.fodemo.storefront.store.queries.OrdersVO"/>I couldn't find the usage of this accessor?
Hope it is clear now.

Accessing all rows in Entity Object

Hi All,
I have a master-child relationship with ChildVO based on entity object. When user hits on save after making some changes, I would like to pass all rows in master view object and all fetched rows in entity object to a pl/sql api which takes pl/sql table datatypes. I would call this API in AM. So is there any way to access all entity rows of child view object?I tried to use view link accessors but it returns null. I can think of the following way:
for each row in master view object
loop
set current row for master view object. This would execute child vo for that master row.
then fetch all rows from child vo. populate pl/sql table
move on to next master vo row.
end loop;
Drawback with above approach is that we would excute child object query for every master row. Is there any direct way to access rows in entity object in AM? Any pointers on this would be of great help.
Thanks in advance,
Murari

"and all fetched rows in entity object"
is not a correct statement to make, EO will always represent a single row of the database record.you will get all the fetched rows in the VO, not the EO.
Tapash

Problem to give default value in entity object using query

hi,
i have one entity object and i want to set default value of attribute like division which is based on employee code.
entity object based on table leavedetail and using refrence table employee_hdr(empcode ,division).
so how can i set default value of division attribute which is based on empcode attribute using SQL

well,
yes user, fetish nailed correctly.
make some viewlink.
something like says as example.
department vo
employee vo
make viewlinks between those vo's
important thing: exposed then source and destination accesor.
use groovy :
go to employee vo - create Department name field ( as transiest)
use this statement default value expersion type.
DepartmentView1.DepartmentName
it will get the value. check over.
so this example well suits to your scenario.
i hope this will helps you.
well create is an video. to get the value using groovy.
http://www.youtube.com/watch?v=mpHV4x89a_A
Edited by: ADF7 on Apr 14, 2012 5:46 AM

How to create entity object (Business Component) using service interface

Hi,
I have tried to create one entity object (ADF Business Component) in JDeveloper 11g using service interface option instead of database schema but getting Failed to read service WSDL URL: http://....?wsdl message.
I have tried with axis default service Admin & Version wsdl and got same error message.
Regards,
Devang

Hi,
+"Oracle ADF Business Components application modules offer built-in support for web services and for publishing rows of view object data as service data objects (SDOs). This means that you can use an application module both as a local component and as a remotely accessible service, thereby using the same component to support interactive web user interfaces and web service clients. Entity objects that you create in your local Business Components project can utilize SDOs that the service-enabled application module exposes on its service interface."+
This means that you don't use Axis services but ADF Business Components Services. I am not sure this functionality made it in Boxer, but surely will in the next
Frank

Entity object not found

JDeveloper 10g EJB testing on standalone OC4J exception java.ejb.ObjectNotFoundException followed by:
myEJBHome_EntityHomeWrapper13.finderMethod(). The Servlet has performed the initial.lookup for the bean successfully and is accessing a finder method thru the remote home interface. The thing is, I had this working and have somehow managed to break it. Either while playing around with deployment and/or client-application descriptors or something I'm not even aware of. Also, what is the "Wrapper13" which gets appended to my home class which number changes with each debug session?
Any suggestions are appreciated.

Let me go thru the steps that I performed and maybe you can tell me where I went wrong. Like I said I had it working before.
1) Created a project for an Entity Bean based on a Table View.
2) Created a Servlet to test the EJB and it was able to lookup the EJB
3) Looped thru the findAll() Home method and displayed all of the view rows
4) Created a finder method using the findAll as an example by:
6) Adding a finder method using the Bean properties dialog and to return an EJBObject with a String param used in the EJB QL and selecting to expose it thru the Home interface.
7) The matching prototype was added to the RemoteHome class.
8) Added the call in the Servlet and I get the Entity object exception.
I just recreated this by creating a new finder method as I wrote these steps and got the same exception. Is there some step(s) I'm missing? Thx for any help.

How to intercept update on entity object using bc4j

Hi all,
I need to intercept a user from updating a particular entity object and create a new entity instead. I have a particular row in a database table that has a primary key with special meaning. If a user attempts to update this row, I want to automatically create a new row in the table with the information they entered and leave the original row unmodified. Any suggestions on how to do this at the entity layer?
Thanks
Mike

Hi Sung,
I've created 2 Entity Objects, named TestEo and OtherEo. The logic I've included is as follows: Before posting data for TestEo to the database (thus as part of the prepareForDML), I create a new instance of OtherEo, using the createBlankInstance method exposed on OtherEoDefImpl.
However, the instance thus created ends up in a STATUS_UNMODIFIED, regardless of locking mode (I've managed to eliminate the locking mode as an issue).
Could you give me an idea of where I'm going wrong? I've attached the prepareForDML() (with diagnostic msgs) and createBlankInstance() methods below.
TestEoImpl.prepareForDML()
protected void prepareForDML(int p0, TransactionEvent p1)
switch (this.getDBTransaction().getLockingMode())
case DBTransaction.LOCK_OPTIMISTIC:
System.out.println("Locking mode: LOCK_OPTIMISTIC");
break;
case DBTransaction.LOCK_PESSIMISTIC:
System.out.println("Locking mode: LOCK_PESSIMISTIC");
break;
// TODO: Override this oracle.jbo.server.EntityImpl method
super.prepareForDML(p0, p1);
OtherEoDefImpl otherEoDef = (OtherEoDefImpl) EntityDefImpl.findDefObject(
"testapp.OtherEo");
System.out.println("Entity Class: " + this.getClass().getName());
switch (this.getEntityState())
case EntityImpl.STATUS_DEAD:
System.out.println("Entity State: STATUS_DEAD");
break;
case EntityImpl.STATUS_DELETED:
System.out.println("Entity State: STATUS_DELETED");
break;
case EntityImpl.STATUS_INITIALIZED:
System.out.println("Entity State: STATUS_INITIALIZED");
break;
case EntityImpl.STATUS_MODIFIED:
System.out.println("Entity State: STATUS_MODIFIED");
break;
case EntityImpl.STATUS_NEW:
System.out.println("Entity State: STATUS_NEW");
break;
case EntityImpl.STATUS_UNMODIFIED:
System.out.println("Entity State: STATUS_UNMODIFIED");
break;
EntityImpl otherEo = otherEoDef.createBlankInstance(getDBTransaction());
System.out.println("Entity Class: " + otherEo.getClass().getName());
int state = otherEo.getEntityState();
switch (state)
case EntityImpl.STATUS_DEAD:
System.out.println("Entity State: STATUS_DEAD - " + state);
break;
case EntityImpl.STATUS_DELETED:
System.out.println("Entity State: STATUS_DELETED - " + state);
break;
case EntityImpl.STATUS_INITIALIZED:
System.out.println("Entity State: STATUS_INITIALIZED - " + state);
break;
case EntityImpl.STATUS_MODIFIED:
System.out.println("Entity State: STATUS_MODIFIED - " + state);
break;
case EntityImpl.STATUS_NEW:
System.out.println("Entity State: STATUS_NEW - " + state);
break;
case EntityImpl.STATUS_UNMODIFIED:
System.out.println("Entity State: STATUS_UNMODIFIED - " + state);
break;
OtherEoDefImpl.createBlankInstance()
public EntityImpl createBlankInstance(DBTransaction p0)
// TODO: Override this oracle.jbo.server.EntityDefImpl method
return super.createBlankInstance(p0);
Output - Test 1
Locking mode: LOCK_OPTIMISTIC
Entity Class: testapp.TestEoImpl
Entity State: STATUS_NEW
Entity Class: testapp.OtherEoImpl
Entity State: STATUS_UNMODIFIED - 1
Output - Test 2
Locking mode: LOCK_PESSIMISTIC
Entity Class: testapp.TestEoImpl
Entity State: STATUS_NEW
Entity Class: testapp.OtherEoImpl
Entity State: STATUS_UNMODIFIED - 1

Have the capability that let Entity Objects from Web Services Datasources?

Have the capability that let Entity Objects from Web Services Datasources? or
where can we found the example about implement Entity Objects from Web Services Datasources ?

I'm not sure what are you asking for. If you are looking to create a data-control based on a web service then this online demo might help:
http://www.oracle.com/technology/products/jdev/viewlets/1013/WebServicesAndADF_viewlet_swf.html
Or are you asking how to expose an ADF Business Component as a Web service?

Error while deleting a row from the Entity Object

Hi OAF Guys,
i am unable to delete the newly created row from the entity object.
let me explain my scenario.
1. i have a table of which some of the columns are mandatory.
2. I am writing the code in the validateEntity to check wether the user really enter anything into the fields.
3. My problem is, when the user creates row and wanted to delete the row without entering any details, the validate entity of the EO gets fired which will not allows to delete the row.
Is there any workaround for this problem.
Regards,
Nagesh Manda.

Hi Tapash,
I am very sorry for not providing you the complete details of my scenario. Here i am explaining
1. what code you have placed while creating the row and in validation method on EOImpl.
while creating a new row i am initializing the primary key of the EO with the sequence value.
2.When you say, you are unable to delete the row, are you getting a error message ? if yes, custom message or fwk error ?
its not the fwk error, its the custom message which wrote in my validateEntity method of EO to check whether the user had entered all the necesary columns or not.
3.How are you trying to delete the row ?
while the user clicks on the delete switcher i am getting the primary key of the row and searching for the row in the vo and finally deleting it.
The problem arises when the user creates a row, and later doesnt want to enter the details and delete it. Here while deleting the row the validateEntity method of the EO gets fired and doesnt allow me to do so :(.
Any way appreciate your help tapash.
Regards,
Nagesh Manda.

Refreshing Entity Objects after Altering the table

Hi,
My Entity Object is based on a table... and View Objects on the Entity Objects. Now if I alter the table (just changing the width of the column), that change is not visible on the Entity Object. Is there any way I can automatically refresh the Entity Objects after altering the table(only column width is changed).
(Changes made to Entity Objects manually are reflected in the View Object correctly.)
Regards
Faiyaz

'changing the width of the column' means changing the size of the column in the table description in the database. For e.g.. In the original table I had a column OIL_KEY NUMBER(6). Now I change the column to be of size 12 i.e. OIL_KEY NUMBER(12). This does not get refreshed in the Entity Object.

Two View Objects & One Entity Object

Has anyone ever had it where they create a row from a view object, set some attributes, insert it into that view object, and it shows up in another view object (as well as the one the row was actually inserted on)? Both of these view objects are using the same single entity object, it's just that their where clauses are slightly different. When I do a commit and then executeQuery, all is good and the new row only shows up in the intended view object.
Here is the code in my app module to do a row insertion on one of the view objects.
public void addQCNote(int userID, Number theStudyID, String theNote)
          try
               //StudyFtsViewObjImpl freeTextVO = getStudyFtsViewObj();
               StudyFtsQCOnlyViewObjImpl freeTextVO = getStudyFtsReadOnlyViewObj();
               freeTextVO.setWhereClauseParam(0, theStudyID);
               DBSequence freeTextTypeCode = null;
               StudyFTSQCCodeValueViewObjImpl freeTextCodeValue = getStudyFTSCodeValueViewObj();
               freeTextCodeValue.executeQuery();
               Row[] freeTextCodeValueCurrentRowArray = freeTextCodeValue.getAllRowsInRange();
               // There SHOULD only be one ... but if there is more, pick one - geeez.
               for (int i = 0; i < freeTextCodeValueCurrentRowArray.length; i++)
                    Row currentFTRow = freeTextCodeValueCurrentRowArray[0];
                    freeTextTypeCode = ((DBSequence) (currentFTRow.getAttribute(StudyFTSQCCodeValueViewObjRowImpl.CODEVALUE1)));
               Row freeTextRow = freeTextVO.createRow();
               // Sets up default values for insertion into db at commit time
               freeTextRow.setAttribute(StudyFtsQCOnlyViewObjRowImpl.PARENTENTITYID, theStudyID);
               freeTextRow.setAttribute(StudyFtsQCOnlyViewObjRowImpl.PARENTENTITYNAME, "STUDY");
               freeTextRow.setAttribute(StudyFtsQCOnlyViewObjRowImpl.FREETEXT, theNote);
               freeTextRow.setAttribute(StudyFtsQCOnlyViewObjRowImpl.FREETEXTTYPECD, freeTextTypeCode);
               freeTextRow.setAttribute(StudyFtsQCOnlyViewObjRowImpl.CREATEDID, new Number(userID));
               freeTextVO.insertRow(freeTextRow);
               freeTextVO.setCurrentRow(freeTextRow);
          catch (Exception ex)
               System.out.println("Exception in AR3MainAppModule.addQCNote: " + ex.toString());
-brian

Did you read this?
Re: Row created in one ViewObject added to all VOs based on the same Entity
Why don't you search this forum before posting?
Sascha

Accessors exposed in entity object

Similar Messages

Maybe you are looking for