11g, reusing a popup window

Question

Hello,
I have a "search customer" dialog (and some others) which will be used throughout the application, and I would like to encapsulate it so other screens can easily use it. I am not really sure how should I do this:
- Use a page fragment: since it uses the binding container of the "receiving" page, I need to define an appropriately-named binding in every page that uses the page fragment. Also, I still don't know how to modify the action listener of the dialog so it calls the appropriate backing bean on each "receiving" page.
- Use a declarative component: I'm not sure if I can define bindings on a declarative component. There is also the annoyance of creating a Library each time I need to change one of the modal dialogs.
- Use an ADF Task Flow and a region: I'm not really sure how it would work with a popup dialog. Should the region be the af:dialog, the af:popup, or the content inside the af:dialog? How can I link the bounded task flow with the original screen after the user has selected an option?
Thanks for your help!!!
Juan Manuel
ps: in case it's important, here is the code I execute when I close the dialog:
public void dialogButtonClicked(DialogEvent dialogEvent) {
if (dialogEvent.getOutcome() == DialogEvent.Outcome.ok) {
DCIteratorBinding searchContractsIt = ADFUtils.findIterator("SearchAccountContractIterator");
SearchAccountContractRow contract = (SearchAccountContractRow)searchContractsIt.getCurrentRow();
if (contract == null) return;
DCIteratorBinding designRequestIt = ADFUtils.findIterator("DesignRequestsIterator");
DesignRequestVORow request = (DesignRequestVORow)designRequestIt.getCurrentRow();
request.setDesignRequestContractFK(new Number(contract.getId().getValue()));
}

Answer 1

Hi,
the winning solution is
+"Use a declarative component"+
You don't need a binding defined for the dialog. Just define an attribute on the declarative component that takes the iterator as the value. from within the component, to access the iterator you use
private DCIteratorBinding getIteratorBinding(){  
  FacesContext fctx = FacesContext.getCurrentInstance();
  ELContext elctx  = fc.getELContext();
  Application app = fctx.getApplication();
  ExpressionFactory elFactory = app.getExpressionFactory();
  ValueExpression valueExpr =
    elFactory.createValueExpression(elctx,"#{component}",Object.class);
  RichDeclarativeComponent _this = (RichDeclarativeComponent)
    valueExpr.getValue(elctx);
  //Access the Iterator attribute
  return (DCIteratorBinding)_this.getAttributes().get("Iterator");
}Note that in this example, the attribute name is "iterator"
Frank