Entity Object Example

Hi dear developers.
I'm searching a good tutorial about entity objects to implement a Java-Database connection. Could you help me about this subject? Could you suggest a link or something useful?
Thanks in advance
Best Regards
Erdo

You can find plenty of examples here:
http://download.oracle.com/docs/cd/E18941_01/tutorials/jdtut_11r2_55/jdtut_11r2_55_1.html
http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/adfinsiderBC/adfinsiderBC.html
https://wikis.oracle.com/display/jdeveloperandadf/Home#

Similar Messages

View all rows in Entity object

please I have a problem can I one help me
I want to get all rows from specific Entity object
example
I am now in validate method in XXX Entity Object and i want to get all the rows in XXX table from validate method(all rows)
can any one help me to do that
thanks in advance

ya sire
I want from validate method in EO XXX to validate all the rows in the table XXX
so I want to get all the rows from validate methods in the EO XXX
thanks in advance

Entity Object Classes Example

Hi,
Does anyone have an example on how to use Entity Object Class for a given Entity Object (i.e. a table). I was looking for an example that shows usage of a DML operation (say for e.g. insert) using this Entity Object Class.
I did google, and searched this forum, but could not find an example.
Please help, Thanks you,
J
Edited by: 843190 on Apr 5, 2011 2:13 PM

Thank you Shay.
I was searching just a little bit off, and moreover I could not see any end to end example, then. Thanks as always for your guidance.
I ended up doing the following for inserting a new row to a table using the entity object class as follows:
EntityDefImpl wmDoc = DocumentImpl.getDefinitionObject();
DocumentImpl newDoc;
newDoc = (DocumentImpl)wmDoc.createInstance2(((ApplicationModuleImpl)am).getDBTransaction(), null);
newDoc.setBlah(blah);
newDoc.setBlooh(blooh);
try
{ ((ApplicationModuleImpl)am).getDBTransaction().commit();
} catch (JboException ex) {
((ApplicationModuleImpl)am).getDBTransaction().rollback();
throw ex;
Configuration.releaseRootApplicationModule(am, false);

Best practice for linking fields from multiple entity objects

I am currently transitioning from PHP to ADF. I'm looking for the best practice for linking data from multiple entity objects.
Example:
EO 'REQUESTS' has fields: req_id, name, dt, his_stat_id, her_stat_id
EO 'STATUSES' has fields: stat_id, short_txt_descr
'REQUESTS' is linked to EO 'STATUSES' on: STATUSES.stat_id = REQUESTS.his_status_id
'REQUESTS' is also linked to EO 'STATUSES' on: STATUSES.stat_id = REQUESTS.her_status_id
REQUESTS.his_status_id is independent of REQUESTS.her_status_id
When I create a VO for REQUESTS, I want to display: REQUESTS.name, REQUESTS.dt, STATUSES.short_txt_descr (for his_stat_id), STATUS.short_txt_descr (for her_stat_id)
What is the best practice for accomplishing this? It appears I could do it a few different ways:
1. Create the REQUESTS VO with a LOV for his_stat_id and her_stat_id
2. Create the REQUESTS VO with the join to STATUSES performed within the query for the VO. This would require joining on the STATUSES EO twice (his_stat_id, her_stat_id)
3. I just started reading about View Links - would that somehow do what I'm looking for?
I also need to be able to update his_status_id and her_status_id through the by selecting a STATUSES.short_txt_descr from a dropdown.
Any suggestions on how to approach such a stupidly simple task?
Using jDeveloper 11.1.2.2.0 if that makes a difference in the solution.
Thanks ahead of time,
CJ

CJ,
I vote for solution 1 as it's just your use case. As you said you what to update the his_status_id and her_status_id through the by selecting a STATUSES.short_txt_descr by a drop down. This is exactly the LOV solution.
ViewLinks are used fro master detail navigation (which you don't do here) and Joining the data make it difficult to update (and you still need a LOV for the drop down box.
Timo

Using JPA Entity-Objects defined in other EJB-Development Component

Hello Community,
I'm working on a Java-Application on NW CE 7.1, using JEE5 Beans in the Business-Logic-Layer and WebDynpro/Java in the UI-Layer.
I designed a Bean for working with data, stored in a database-table of the system-database.
For that addtionally i created a class, representing the Entity-Object, in the same Development-Component of Type EJB 3.0.
It looks like this:
@NamedQueries ({
     @NamedQuery (name="findAllSdCust", query="SELECT c from SdCust c ORDER BY c.kdnr"),
     @NamedQuery (name="findSdCustByKdnr", query="SELECT c from SdCust c WHERE c.kdnr = :kdnr"),
     @NamedQuery (name="findSdCustByIlnnr", query="SELECT c from SdCust c WHERE c.ilnnr = :ilnnr")
@Entity
@Table(name="ZKALL_SD_CUST")
public class SdCust implements Serializable {
     @Id
     @TableGenerator (name="idGenerator", table="ZKALL_ID_GEN", pkColumnName="GEN_KEY", valueColumnName="GEN_VALUE", initialValue=100)
     @GeneratedValue (strategy=GenerationType.TABLE, generator="idGenerator")
     private long id;
     private String name;
     private String lname;
     private String kdnr;
     private String ilnnr;
     private long connid;
     private long cnt;
     @Version
     private long version;
      Constructor, Getter and Setter methods follow here
The corresponding bean looks like this
@Stateless(name="SdCustBean")
public class SdCustBean implements SdCustLocal {
     @PersistenceContext (unitName="xyz")
     private EntityManager em;
     public SdCust getSdCustByKdnr (String kdnr)
          SdCust result = new SdCust();
          // List<Manufacturer> resultList = new ArrayList<Manufacturer>();
          Query myQuery = em.createNamedQuery("findSdCustByKdnr");
          myQuery.setParameter("kdnr", kdnr);
          result = (SdCust) myQuery.getSingleResult();
          return result;
     public void setEM (EntityManager iem)
          em = iem;
       // other methods .....
After that i created a new Development-Component of Enterprise Application-Type and added above DC to this EAR-DC. I also supplied the nessecary descriptor-files/Enries in EJB-DC and EAR-DC.
When now using this bean from WebDynpro with the Web-Dypro EJB-Model-Import everything works fine.
The bean returns the desired object(s).
But now i created a new DC of type EBJ 3.0
This DC contains a Message Driven Bean. That MDB is a Job-Bean which i want to schedule. That Bean uses JRA to connect to an SAP-Abap-System to read some Data and should use JPA to insert/upate/delete the read data in the Database. This should work as a simple replication for my application.
I assigned that EJB-DC containing the MDB to a new EAR-DC together with job-definition-xml and the neccessary entries in deployment-descriptors.
After deploying i see the corresponding job-defition in the NW scheduler using the administrator-views.
I'm also able to schedule the job and it executes fine. Connecting to SAP-Abap System also works fine using JRA.
But JPA does not work!!!!!
I created an dependency from my EAR-DC containing the Job EJB-DC and to the EJB-DC containing the Entity-Class.
I tried three diferent things to get i running, but all of them failed.
1.)
The part looks like:
public class MasterDataReplicateJobBean extends MDBJobImplementation implements MessageListener
@EJB SdCustBean mybean;
   public void onJob(JobContext ctx) throws Exception {
        SdCust sdCust = mybean.getSdCustByKdnr (mykdnr);
Compiles fine. But this fails because the Data is stored in the system-database. The exception says, that i have to use a datasource which supports 2-Phase commit. I know, that i could possibly solve this problem by annotation the Method getSdCustByKdnr with the Annotation for the Transaction-Manager to use REQUIRES_NEW Transaction. But i dont want to generally annotate my methods this way.
2.)
This part looks like this
public class MasterDataReplicateJobBean extends MDBJobImplementation implements MessageListener
@PersistenceContext (unitName="xyz")
private EntityManager em;
   public void onJob(JobContext ctx) throws Exception {
     SdCust cust = new SdCust();
     Query myQuery = em.createQuery("SELECT c from SdCust c WHERE c.kdnr = :kdnr");
     myQuery.setParameter("kdnr", dbkdnr);
     cust = (SdCust) myQuery.getSingleResult();
This also results in a runtime-exception because the entity-Manager cant resolve SdCust from the Query as an Object. The Exception is:
java.lang.IllegalArgumentException: line 1: Abstract Schema Type 'SdCust' doesn't exist
SELECT c from SdCust c WHERE c.kdnr = :kdnr
3.) and last try so far:
public class MasterDataReplicateJobBean extends MDBJobImplementation implements MessageListener
@PersistenceContext (unitName="xyz")
private EntityManager em;
   public void onJob(JobContext ctx) throws Exception {
     SdCustBean custBean = new SdCustBean();
     custBean.setEM(em);
     SdCust cust = custBean.getSdCustByKdnr(kdnr);
In this example i use the Bean from the beginning not as a bean itself but as a normal class. that class has an addtional Method setEM to set the Entity-Manager (which is injected when using the class as a bean)
In that way i got the exception, that the named Query "findSdCustByKdnr" cannot be found by the entity-manager.
It seems to me, that i can access the class, but that all annotations belonging to JPA for that class are not recognized.
Does anybody can give me a hint to solve this problem? Did i forgot something important?
best regards
matthias hayk
Edited by: Matthias Hayk on Feb 5, 2009 9:38 AM

I was already on wright trace.
My class "SdCust" was not recognized by the Entity-Manager as an Entity-Class.
This relies on the storage of the entity-class and where the Entity-Manager looks for entity-classes.
By default it seems to look for all classes in the same jar file. thats the reason why everything works fine when the using bean and the entity-class are in the same project.
In my last case, the using bean is in another development-component and so also in anohter jar file. in this case the entity-manager must be told where to find entity-classes.
this is done in the persistence.xml file.
i added the line
<jar-file>xxx.yyy.com~mdata_beans.jar</jar-file>
underneath the <persistence-unit>-tag.
This works.
regards
Matthias Hayk

Synchronize with Database on Entity Object re-creates Association

hi
Please consider this example application created using JDeveloper 11.1.1.4.0
at http://www.consideringred.com/files/oracle/2011/MovedAssociationApp-v0.01.zip
It has an EmpManagerFkAssoc Association which has been moved from the "movedassociationapp.model.entities" package to the "movedassociationapp.model.assoc" package (using the "Refactor - Move..." context-menu option).
When selecting "Synchronize with Database..." in the context-menu of the Employees Entity Object, and clicking the "Synchronize All" button, this results in JDeveloper re-creating the EmpManagerFkAssoc Association,
as shown in the screencast at http://screencast.com/t/l7jaoU2C
- (q1) Is this Association re-creation intended behaviour (if so, please explain, if not, which bug number)?
many thanks
Jan Vervecken

Ferez,
have you seen this thread in the ADF forum, Cannot 'Synchronize with database' my entity objects ?
It mentions the existence of a bug that may cause this (though no reference number), and one user posted a workaround they were using.

Specifying autoincrement on a field in an entity object declaratively

Hi,
I have a master-detail window where the detail entity has a composite key made up of m_id and d_id where m_id is a foreign key to the master table and d_id is the unique key to the detail table.
I have defined the detail entity object and checked the box for m_id and d_id as a primary key. When I create a new detail object using the create button that is available from the data control panel for the detail's view object it populates the m_id based on the currently selected master object. However since d_id needs to be populated as well.
Any ideas how I can do this declaratively in then entity object definition?
Cheers,
S

This can be done with programmatic VOs: http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/bcadvvo.htm#sm0341
Sample: http://blogs.oracle.com/smuenchadf/examples/#132
You can also opt to do this with a simple Java class and a data control based on it.
For example: http://blogs.oracle.com/shay/2009/07/java_class_data_control_and_ad.html

ADF BC Entity Object read security

hi
Please consider the example application in this blog post by Andrejus Baranovskis:
"ADF Security 11g and ADF Business Components"
http://andrejusb.blogspot.com/2008/10/adf-security-11g-and-adf-business.html
What is the "read" operation used for in the Security section of the "Jobs" Entity Object configuration?
I modified the example application and checked the enabled checkbox for the "read" operation on the "Jobs" Entity Object. After that, using the "Edit Authorization..." dialog (from the context menu on the "Jobs" Entity Object in the Structure Panel), I checked the "Read" checkbox for the "clerk" role.
This looks to me like a configuration from which one could expect that only a "clerk" can read.
After that I run the "HrModule" Application Module and authenticate as a "developer" (user "steve"), which has no privileges granted, and I can still read all the attributes for the rows in the "JobsView1" View Object instance (which is based on the "JobsView" View Object for which all the attributes come from the "Jobs" Entity Object).
How can this be explained?
many thanks
Jan Vervecken

Thanks for your reply Brenden.
Yes, my question seems to be the same as in the forum thread you refer to,
"11g ADF BC security - read operation?".
In that thread Frank Nimphius points out "this seems to be malfunctioning and will be bugged",
and also Chris Muir writes "... the documentation is a little misleading then ...".
regards
Jan

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.

26.4 Basing an entity Object on a PL/SQL Package API - Ref Cursor, no View

I am hoping that I could get some help in the details of a problem. I am trying to follow the directions in the Oracle Application Development Framework Developer's Guide for Forms/4GL Developers, Section 26.4 - Basing an Entity Object on a PL/SQL Package API.
There is example code in the downloadable AdvancedEntityExamples - EntityWrappingPL/SQLPackage
The question is, how will the implementation change if the entity is based entirely on PL/SQL - simply stated - no view is available, just ref cursors and insert,update,delete procedures.
In the example code, there are two procedures, lock_product and select_product. This is where things get more complicated. I can create a function to return a single record ref cursor, instead of the list of OUT variables defined in both functions (select_product and lock_product). It makes sense that I just return one cursor and get all of the columns from that instead of lots of OUT variables.
So what's stopping me you may ask... There is one difference between select_product and select_lock. Select_lock has a select that includes "FOR UPDATE NOWAIT". I don't have that as an option when creating my ref cursor. I am not sure what the impact of "FOR UPDATE NOWAIT" is? Can I ignore it?
In the problem I am working with, (getting data from Oracle Portal 10.1.4) I return the following:
function getRefCursor return ref_cursor is
v_tab wwsbr_all_items_object_type := wwsbr_all_items_object_type();
p_recordset wwsbr_types.cursor_type;
l_results wwsrc_api.items_result_array_type;
begin
wwctx_api.set_context(<username>,<password>);
l_results := wwsrc_api.item_search(.. parameters..);
<snip>
... Loop through the objects and populate v_tab
<snip>
open p_recordset for
select * from table(cast(v_tab as wwsbr_all_items_object_type));
return p_recordset;
end getRefCursor;
With this sample, it would be easy to return a single row by passing the masterid as a parameter.
So I am still left with, how should the implementation of callLockProcedureAndCheckForRowInconsistency() and callSelectProcedure() be changed in order to use a ref cursor instead of a view? The user guide was missing that extra section <bg>.
What would be REALLY helpful, is an example, say 26.4A that demonstrates creating an entity object from a ref cursor and procedures from PL/SQL only without a view.
Thank you, Ken

The lock procedure is expected to obtain a row-level lock on the row, given its key.
Depending on the setting of jbo.locking.mode, the entity object's lock() method will be invoked either as soon as the first persistent attribute is successfully modified by the user (in the case of jbo.locking.mode=pessimistic), or it will be called during commit processing just before the row is updated in the database (with jbo.locking.mode=optimistic).
Usually 2-tier Swing applications use pessimistic mode, while web applications use optimistic mode.
The FOR UPDATE NOWAIT is the Oracle clause that can be appened to a SELECT statement to acquire a row-level lock on the selected rows. The NOWAIT modifier means that rather than hanging, waiting for a row locked by another user to free up, it will raise an exception if any of the rows being selected-and-locked are not available to lock.
If you're not able to work the FOR UPDATE NOWAIT into the syntax of the ref cursor, perhaps you can initially perform the lock using a different cursor inside the stored procedure, then return your ref cursor.

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 I configure a default value in an entity object?

Hi,
1:how I configure a default value in an entity object?
attribute type: DATE
I want to set the current date
...thanks

Override the create() action in your entity object implementation:
protected void create(AttributeList attributeList)
* This method should be subclassed to supply programmatic default values to
* various attributes of a new Entity Object. For example, to create a sequence.
* Instances of subclasses should call super.create() before performing any operations.
System.out.println("create(AttributeList attributeList) - start");
Date datSysdate = ( oracle.jbo.domain.Date) Date.getCurrentDate();
super.create(attributeList);
// set the default to today...
setHiredate( datSysdate );
System.out.println("create(AttributeList attributeList) - end");
}

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

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.

Managing Entity Object and PL/SQL transactions

Hi,
I have requirement to use entity objects and PL/SQL API in the same transaction.
First the data is created in the entity object and then API is called to do some validations on the data created through entity object.
I am not able to fetch the rows created by the entity object in the PL/SQL API until I issue a commit before calling the API.
Can anyone suggest me how to get the data in PL/SQL API which was created by the entity object without commit. As I want to have a commit only after API returns true.
Thanks in advance

Override the beforeCommit method of the main entity object of your page.
The commit will only take place if the PLSQL does not throw any errors.
See example below:
public void beforeCommit(oracle.jbo.server.TransactionEvent e) {
methodToCheckUsingPLSQL();
super.beforeCommit(e);
private void methodToCheckUsingPLSQL() {
try {
String sql =
"BEGIN check_my_entity(p_id => :1" +
", x_return_status => :2" +
", x_return_msg => :3); END;";
OracleCallableStatement stmt =
(OracleCallableStatement)getDBTransaction().createCallableStatement(sql,
DBTransaction.DEFAULT);
// Rebind parameters
stmt.setNUMBER(1, getId());
stmt.registerOutParameter(2, Types.VARCHAR); //x_return_status
stmt.registerOutParameter(3, Types.VARCHAR); //x_return_msg
stmt.executeUpdate();
String returnStatus = stmt.getString(2);
String returnMsg = stmt.getString(3);
if (!"SUCCESS".equals(returnStatus)) {
throw new OAException(returnMsg);
} catch (Exception e) {
throw new OAException("Error during methodToCheckUsingPLSQL. " +
e.getMessage());
Regards,
Jeroen Kloosterman

Entity Object Example

Similar Messages

Maybe you are looking for