How do I remove a row from the database?

Question

Guys and Gals,
I'm using Studio Edition Version 11.1.1.3.0.
The code below will delete a row from my table, but how do I actually delete the row from the database as well?
    DCBindingContainer dcbc = (DCBindingContainer)getBindings();
    DCIteratorBinding dcib = dcbc.findIteratorBinding("TipsSelectorIterator");
    dcib.removeCurrentRow();
    BindingContainer bindings = getBindings();
    OperationBinding operationBinding = bindings.getOperationBinding("Commit");
    Object result = operationBinding.execute();
    AdfFacesContext adffacesctx = AdfFacesContext.getCurrentInstance();
    adffacesctx.addPartialTarget(this.getQueryTable()); In this post, I believe Frank sums up what I should do: Remove row from af:table
>
The problem in your case is that this removes the row from the iterator but not your business service. EJB exposes explicit methods to remove an entity. A method lime removeEmployees(employee) >expsed on the EJB model must be called.
You can drag and drop the "removeEmployees" method then as a button to your page. Rename the text label to "Remove" or "Delete". In the opened dialog box, point the method argument to the >following EL #{bindings.iteratorName.currentRow.dataProvider}. Next time you press the button, the row is deleted from the iterator and the business service
Huh? So to delete the row, I need to expose a method. But where? Do I do this in the AppModuleImpl so I can expose it to the Client Interface? But then how do I access entities? And what data type is the #{bindings.iteratorName.currentRow.dataProvider}?
If anyone could point me in a general direction, it'd be great.

Answer 1

Frank and Shay,
Thank you both for your posts. I'm amazed there's such a great place to get help. Between the forums, ADF code corner, Not Yet Documented ADF Samples, various blogs and tutorials, it's obvious you guys really care about what you do.
On my example, that approach doesn't seem to work. I tried following it like so in one of the video tutorials by Shay: http://blogs.oracle.com/shay/2010/04/doing_two_declarative_operatio.html. Following Shay's approach, in my particular case, deletes only from the table. Perhaps it is due to my iterator / collection setup?
TipsSelector (1 to 1) -> TipsView (1 to *)-> DependentBom -(1 to * Recursive)> RecursiveBom
TipsSelector references the same View Object as TipsView, but it is set as a 1 to 1 relationship so that I can show TipsView on the page one record at a time. This is the same setup as Tuhra2's hierarchy veiwer example. TipsView / DependentBom is a classic parent / child setup. RecursiveBom is DependentBom referencing itself. Think of it as departments within departments within departments etc...
I have dragged TipsSelector's Named Criteria (All Queriable Attributes) onto my page and created an ADF Query with Table. A remove button on the table's toolbar calls the two actions, Delete (from TipsSelector's iterator) and then Commit. I have modified the code slightly from my previous post but the end result seems to be the same.
    BindingContainer bindings = getBindings();
    OperationBinding operationBinding = bindings.getOperationBinding("Delete");
    operationBinding.execute();
    bindings = getBindings();
    operationBinding = bindings.getOperationBinding("Commit");
    operationBinding.execute();
    AdfFacesContext adffacesctx = AdfFacesContext.getCurrentInstance();
    adffacesctx.addPartialTarget(this.getQueryTable());Page Def file
    <action id="Commit" InstanceName="AppModuleDataControl"
            DataControl="AppModuleDataControl" RequiresUpdateModel="true"
            Action="commitTransaction"/>
    <action IterBinding="TipsSelectorIterator" id="Delete"
            InstanceName="AppModuleDataControl.TipsSelector"
            DataControl="AppModuleDataControl" RequiresUpdateModel="false"
            Action="removeCurrentRow"/>On ppr of the query table, the row is gone. However, when I press the Search button on the query again, the record reappears.
This is beyond me. Am I somehow deleting from the query results but not the database?