Raising exceptions at Application Module

Question

Hi there;
    For this simple example;
        public void autenticateUser(String pUser, String pPassw) {
        StringBuffer wStatement = new StringBuffer("Begin");
                                 wStatement.append("  PackUser.autenticate(:1, :2);");
                                 wStatement.append("End;");
        try
          CallableStatement cllS = getDBTransaction().createCallableStatement(wStatement.toString(),DBTransaction.DEFAULT);
          cllS.setString(1,pUser);
          cllS.setString(2,pPassw);
          cllS.execute();
        catch (Exception e)
          throw new JboException(e);
       PackUser.autenticate will run into an No_data_found exception when user is not found , and the " catch " will throw an jboException;
   In authenticate bounded  adf task flow, i posted the login page fragment (whose will run into an region)   , the doAutenticate flow control , the am' binding authenticate user setting the parameters for enviromentBean (userName, passWord and so one ... ) and finally the errorPage configured as exception handler.
   Finally
            My jboException was raised, but my errorPage never was called ? as a meter of fact i received the " no_data_found error " inside one popup window.
            Does adf-task-flow not recognize Am's jboExceptions's interface (class errors)  to re-route errors page ?
            _Or Maybe it's not an best practice to raise exceptions into an Application's data modules to "annunciate"  BI constraints !_
    Many thanks ...
Marcos Ortega
  Brazil

Answer 1

Hi,
I'ts almost always best practice to return a result to the UI when calling an AM or VO method.
If you want to get a bit more fancy, you can return a String array containg a result and a message. Eg.
    // AM Method
    public String[] addLocation(Number locationId, String locationCode) {
                 try  {
                    // Do some stuff
                } catch (Exception ex)  {
                    ex.printStackTrace();
                    return new String[] {"Error", ex.getMessage()};
        return new String[] {"Success", "This location has been added."};     
    }Drag the method onto the page to create a parameter form and page bindings.
You can then access the method results on the page declaratively like this:
       <af:panelHorizontal rendered="#{bindings.addLocation.result[0] == \'Error\'}"  partialTriggers="add">
                <af:objectIcon name="error" rendered="#{bindings.addLocation.result[0] == \'Error\'}"/>
                <af:objectSpacer width="5" height="10"/>
                <af:outputText value="#{bindings.addLocation.result[0]} : #{bindings.addLocation.result[1]}"
                               styleClass="x3s"
                               inlineStyle="font-size:smaller;"/>
            </af:panelHorizontal>Brenden