JSV-Validation discards some backing bean properties

Hi guys,
I'm facing a curious problem occuring in my jsf-application. I have a userlist on my page. Every user can be edited (change password, etc) or a new user can be created. When I click the "edit-user"-button, a new page is opened where I can change different properties of this user. When I submit the form, the jsf-validation is beeing called (because I set some properties to attribute "required"). When an error occurs, the action-command returns null and goes back to the page. But not all properties of my backing bean arent set! It seems, that only the properties beeing set to attribute "required" are saved... How can I fix this?
My jspx-page that creates/updates a user looks like that:
<h:form>
     <h:inputHidden value="#{userFormBean.userID}" />
     <h:panelGrid border="0" columns="2" style="margin-bottom:15px;">
          <h:outputLabel value="#{msg['ui.user.create.lastname.label']}:" />
          <h:inputText value="#{userFormBean.name}"
                          required="true"
                          label="#{msg['ui.user.create.lastname.label']}" />
          <h:outputLabel value="#{msg['ui.user.create.firstname.label']}:" />
          <h:inputText value="#{userFormBean.firstname}"
                          required="true"
                          label="#{msg['ui.user.create.firstname.label']}" />
          <!-- more properties... -->
     </h:panelGrid>
     <c:if test="#{userFormBean.state == applicationScope.constants.STATE_NEW}">     
          <h:commandButton action="#{userFormBean.createUser}" value="#{msg['ui.user.create.button']}">
               <f:setPropertyActionListener value="#{applicationScope.constants.STATE_NEW}" target="#{userFormBean.state}"/>
          </h:commandButton>
     </c:if>
     <c:if test="#{userFormBean.state == applicationScope.constants.STATE_UPDATE}">
          <h:commandButton action="#{userFormBean.updateUser}" value="#{msg['ui.user.update.button']}">
               <f:setPropertyActionListener value="#{applicationScope.constants.STATE_UPDATE}" target="#{userFormBean.state}"/>
          </h:commandButton>
     </c:if>          
</h:form>     This is my backing bean that does all the logic...
public String updateUser(){
     try{
          // do some business-logic
     }catch (Exception ex){
          // set error message and return to form
          FacesContext ctx = FacesContext.getCurrentInstance();
          // provide some error-msgs
          return null;
     return "success";
}I need to save all the properties on my backing bean, especially my "state"-property that decides whether I create a new user or update a given user identified by its id...

To start, do not mix JSF with JSTL this way. Remove all of those c:if tags and use the JSF 'rendered' attribute instead.
E.g.
     <c:if test="#{userFormBean.state == applicationScope.constants.STATE_NEW}">     
          <h:commandButton action="#{userFormBean.createUser}" value="#{msg['ui.user.create.button']}">
               <f:setPropertyActionListener value="#{applicationScope.constants.STATE_NEW}" target="#{userFormBean.state}"/>
          </h:commandButton>
     </c:if>should be
     <h:commandButton action="#{userFormBean.createUser}" value="#{msg['ui.user.create.button']}" rendered="#{userFormBean.state == applicationScope.constants.STATE_NEW}">
          <f:setPropertyActionListener value="#{applicationScope.constants.STATE_NEW}" target="#{userFormBean.state}"/>
     </h:commandButton>Back to your actual problem: I cannot correlate your problem description to the given code snippet. Which non-set values are you talking about?

Similar Messages

  • Create a report in a popup (validation needed in back bean before popup)

    Hi all,
    I am very new to JDev and ADF, I am struggling to generate a report in a popup through the back bean, some validation is needed in the back bean before the popup. When creating the popup window, the url of the popup will be the URL of a servlet I searched the forum and found 2 approaches:
    http://thepeninsulasedge.com/frank_nimphius/2007/09/11/adf-faces-showing-reports/
    can af:showPopupBehavior work together with action- or launchListener? (approach by Julian Stephen)
    But I have a few questions for these approaches:
    for first approach:
    is “documentURL” in the commandButton_action() the url for the my report servlet,
    another thing is that, in this commandButton_action(), it said: return "dialog:open"; But I couldn’t find anywhere in the content that shows dialog, open are component ids? Or I am misunderstood it?
    for the second approach:
    where is the url for my report servlet put? Is it in the "hints" in the function “popup.show(hints)”?
    I can try the second approach first, but for the first approach I really want to know what is the "return dialogLopen" about?
    If there are any other means, please let me know!
    Your help is highly appreciated!
    Shawn

    My bad, in the first approach, "dialog:open" is the action string not component ids.

  • Backing bean properties not getting updated

    I have an input text in my JSP page and it is component-bound to backing bean. The problem is that when I change value of the InputText in the JSP, the value is not getting updated in the backing bean.
    Here is the InputField definition in JSP page.
    <h:inputText binding="#{backing_employeeEdit.firstName}"
    id="firstName"/>
    and here is the setter in backing bean
    public void setFirstName(HtmlInputText inputText1) {
    this.firstName = inputText1;
    Pls note that there is no validation errors because the page navigates successfully. The only problem is that new value is not updated.

    I don't know, wht exactly u wants to do... Here is java code and is working fine for me...
    Emp.java
    public void action() {
         System.out.println(inputText.getValue());
         Emp tt = new Emp();
         inputText.setValue(inputText.getValue().toString()+"bilal");
         tt.setInputText(inputText);
         System.out.println(inputText.getValue());
    JSP...
    <f:view>
    <h:form>
    <h:inputText binding="#{emp.inputText}" />
    <h:commandButton value="submit" action="#{emp.action}" />
    </h:form>
    </f:view>
    faces-config file contents....
    <managed-bean>
              <managed-bean-name>emp</managed-bean-name>
              <managed-bean-class>
                   com.nous.application.Emp
              </managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    </managed-bean>
    Here scope has to be session, otherwise u will lose old value...

  • Page Template Backing Bean Availability

    I have a page template that is used in pages across in a bounded Task flow. The backing bean is defined in the adfc-config.xml file.
    There are properties in the template backing bean that I use to determine whether to set some UI Components Visible property to true or false. So far so good and the UI Visible property is set as expected when run. e.g.
    #{backingBeanScope.beanNameBacking.myGroupAccordionVisible}
    I created another bounded Task Flow that contains a page that also references the Page Template. The new Task Flow is called from the original Task Flow.
    When I run the application now, the backing bean properties (in the Page Template) are highlighted as unknown and I get a runtime null pointer exception.
    This is even more confusing as I reference the template backing bean as a managed bean in the new (and old) Task Flow, and from the new Task Flow I can call a method in the template backing bean successfully. Why would the properties be unknown?
    Cheers.

    Hi,
    >highlighted in yellow and the hint says the bean property contained in the EL is not known
    First remove your existing EL and create EL as i said before,After create new EL it will not highlighted in yellow because EL is based on your managed Bean.

  • Feedback requested: in backing bean, use AM svc method or operation binding

    Hello all,
    I'm posting this here to solicit feedback from both Oracle and from the community at large. The basic question is around what is the best/better practice for calling Application Module service methods from a backing bean. One choice is to call the service method directly on the application module; the other is to put an operation binding in the page definition and to execute that binding. The basic code for the two methods:
    ((MyAppModule) getBindings().getDataControl.getApplicationModule()).serviceMethod();or
    getBindings().getOperationBinding("serviceMethod").execute();My question comes up specifically because of differences in how the default error handling works. For testing, we created a simple AM with a single service method that throws a JboException (a kind of RuntimeException). Then, we created a simple ADF Faces page with an af:messages (to see how error handling works) and four af:commandButtons. The four command buttons are as follows (the code is in the backing bean for each of them):
    1). partialSubmit=false, calls application module service method directly
    2). partialSubmit=false, executes service method via operationBinding
    3). partialSubmit=true, calls application module service method directly
    4). partialSubmit=true, executes service method via operationBinding
    None of the backing bean methods catch any exceptions. Note that #2 and #4 could be bound directly to the methodBinding in the pagedef, but we did it via code in the backing bean to more accurately mimic some of the code in our application; in any case, the results were the same using either method for #2 and #4.
    The results when clicking each button:
    1). ugly stack trace in the browser window (yuck!)
    2). the af:messages component displays the JboException (nice)
    3). No stack trace, no error message (even worse than #1, user thinks "success," even though exception occurred)
    4). the af:messages component displays the JboException (nice)
    This leads me to think that perhaps calling via the binding container is the preferred method because the default error handling gives acceptable behaviour, whereas using the AM directly gives unacceptable behaviour.
    Another "benefit" of calling through the binding container is that the technology in the model layer could be changed without having to change the view layer. I say "benefit" in quotes because I personally believe that one should write applications to take full advantage of the technology they choose, not try to strive for technology/database independence (no flames on this one please - that's not the main point here ;).
    Having made the preliminary conclusion that the binding container is the preferred way to go for service methods - that could then ostensibly be extended to view objects as well. Should the view layer use iteratorBindings instead of dealing with view objects directly as well? This is a bit more shaky ground because there are some points in the view/controller layer (namely managed beans not associated with any page) where there is no binding container available. However, in backing beans, for re-executing queries we could make the "best practices" statement to always use iteratorBindings instead of accessing the AM/VO. I just completed a test comparing view object usage vs iterator binding usage (vo.executeQuery() vs myIter.executeQuery()) with similar results to the AM testing - the binding container route gives acceptable error handling, whereas the VO route forces me to implement my own error/exception trapping and message display.
    I am aware of one drawback to using the binding container instead of the AM directly - that is that each page that needs the service method must have something in it's pageDef for that method. Originally, we had some code in a superclass of some backing beans that called the AM directly, and we didn't need to touch the pageDefs of approximately 20 JSF pages - when changing to use the operation binding - we had to add it to a lot of page defs.
    I'm very interested in feedback from the community at large on my conclusions. If the discussion gets to be too big/complicated for here, we can change venues to perhaps the oracle wiki or another forum. I did do a quick review of SRDemo ADFBC and noted that all of the service method calls are done through operation bindings - I never noticed that before! Most of the discussion we see in the forums shows people calling them directly, which is why I thought it important to post here.
    Best regards,
    John

    What we did in our project was that we create a "Headless" pagedefinition, (that was how it was described in SRDemo documentation or in JDeveloper help, its on the latter part about Security).
    You have to create that pagedef manually. and it only has an
    <page id="yourPageDef_Id" path="..."> entry in your Databindings and no
    <page path=".../yourPageDef_id" usageId=".../???.jsp">And then in your faces_config and your managed bean name is backingSystemStateBean and is located at path.to.bean.SystemState add a Session scope bean entry like this:
      <managed-bean>
        <managed-bean-name>backingSystemStateBean</managed-bean-name>
        <managed-bean-class>path.to.bean.SystemState</managed-bean-class>
        <managed-bean-scope>session</managed-bean-scope>
        <managed-property>
          <property-name>bindings</property-name>
          <value>#{data.yourPageDef_Id}</value>
        </managed-property>

  • Aj4:support initialize backing bean

    Hi,
    I am a newbi in JSF and aj4.I have used ajs:support tag to do a server side validation (a business validation) ,invoking a backing bean method.
    What I have observed is ,when ever the ajax call happened for this validation method , the init() method of the backing bean is getting executed.I have annoted the init with @postConstruct.This is required for me.
    Please find the code below
    jsp
    <a4j:support event="onblur" action="#{accgpBean.validateId}" reRender="idValidMsg" immediate="true"/>
    <h:outputText  binding="#{accgpBean.idValidMsg}" id="idValidMsg"/>Backing bean
    @PostConstruct
         void init(){
              AccountGroup grp=new AccountGroup();
              grp.setAccntSuperGrp(new AccountGroup());
              this.setAccntGrp(grp);
              System.out.println("Retrieving the accnt grp>>>");
              accountGroupList=accountService.listSuperGroup();
    public String validateId(){
            System.out.println("Invoked validation method>>>");
            idValidMsg.setValue("Invalid Id");
            return null;
       }Can anybody suggest,how do I turn off the invokation of init() on the ajax requests ?
    Thanks in Advance
    Shaiju

    Hi,
    I am a newbi in JSF and aj4.I have used ajs:support tag to do a server side validation (a business validation) ,invoking a backing bean method.
    What I have observed is ,when ever the ajax call happened for this validation method , the init() method of the backing bean is getting executed.I have annoted the init with @postConstruct.This is required for me.
    Please find the code below
    jsp
    <a4j:support event="onblur" action="#{accgpBean.validateId}" reRender="idValidMsg" immediate="true"/>
    <h:outputText  binding="#{accgpBean.idValidMsg}" id="idValidMsg"/>Backing bean
    @PostConstruct
         void init(){
              AccountGroup grp=new AccountGroup();
              grp.setAccntSuperGrp(new AccountGroup());
              this.setAccntGrp(grp);
              System.out.println("Retrieving the accnt grp>>>");
              accountGroupList=accountService.listSuperGroup();
    public String validateId(){
            System.out.println("Invoked validation method>>>");
            idValidMsg.setValue("Invalid Id");
            return null;
       }Can anybody suggest,how do I turn off the invokation of init() on the ajax requests ?
    Thanks in Advance
    Shaiju

  • Multiple back bean calls for rendered panels

    Hello,
    We have experienced some strange behaviours, when rendering a panel based on some back bean paramater the backing bean method is called multiple times. It seems that the backing bean is called for each child element is the panel.
    For instance in the following example the backing bean will be called 6 times.
    <t:div id="test" rendered="#{! empty UCB.attribut}" >
         <t:outputText value="text1" />
         <t:outputText value="text2" />
         <t:outputText value="text3" />
         <t:outputText value="text4" />
         <t:outputText value="text5" />
    </t:div>Is this a configuration issue or just how jsf is implemented?
    //Chris

    Called sequentially (from my original post):
    wsCodeList["GetTupleList"].arguments.TupleName = "BUSTYPE";
    var call:Object = wsCodeList["GetTupleList"].send();
    call.destination = "busType";
    wsCodeList["GetTupleList"].arguments.TupleName = "ENTTYPE";
    call = wsCodeList["GetTupleList"].send();
    call.destination = "entityType";
    The docs seem to say this is allow and example found online
    do similar, except the arguments are passed as a parameter to send.
    This doesn't work for me though. The web service I'm using will
    only take the arguments using the arguments object.

  • ADF BC/Faces - Order of validation / backing bean action problem

    Hello,
    I want the user to enter the same "operation date" into all adf faces table rows created in one batch (one transaction).
    So I removed operation date field from the table and added "unbound" date field above the table. The date field value is then copied into all new rows in background. This process is invoked from backing bean from Commit button actionListener method.
    The problem is the validation of the operation date in entity is executed before a new date value is copied into the date attribute (validation of model is in JSF lifecycle executed prior invoking actions in backing beans).
    It means the user can enter dead lock when he enters invalid date (for example date higher then a valid value).
    Then after commit:
    1. First validation is ok (wrong date value haven't been copied into model yet)
    2. backing bean copy action is executed - model now contains wrong date value
    3. Validation before commit isn't successfult - error message is displayed
    4. User corrects the date value and presses commit again but:
    5. First validation is not successful - model still contains recent wrong date value - error message is displayed again
    6.There is no way out from this situation
    I'm going to override lifecycle to be able to invoke copy method before validation cycle. Is this solution acceptable? Do you have any other suggestion?
    Thank you.
    Rado

    hi Rado
    Would it make sense to design your ADF BC View Objects in some kind of master-detail shape that fits your data?
    View Object : OperationMaster (OperationDateAttr, ...)
    View Object : OperationDetail (OperationAttr1, OperationAttr2, ...)
    View Link : OperationDetailForMasterVL (based on some attribute that keeps the detail rows together)
    You would need some Application Module method that does the "row batch setup", but it look like your already have something like this.
    A change to OperationMaster.OperationDateAttr could update all its detail rows date attribute.
    I think that building a UI on this would be less "view layer dependant".
    Just a suggestion.
    regards
    Jan Vervecken

  • How to prepopulate properties of a backing bean

    Hi Everybody,
    I am new to JSF. In order to display a form with fields set to some value, I was trying to prepopulate properties of the form's backing bean based on properties of another bean. I tried the following and it doesnot work
    <managed-bean>
    <description>blah blah</description>
    <managed-bean-name>visitBean</managed-bean-name>
    <managed-bean-class>com.x.y.VisitBean</managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    </managed-bean>
    managed-bean>
    <description>blah blah</description>
    <managed-bean-name>infoBean</managed-bean-name>
    <managed-bean-class>com.x.z.InfoBean</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
    <managed-property>
    <property-name>name</property-name>
    <value>#{visitBean.user.name}</value>
    </managed-property>
    <managed-property>
    <property-name>phoneNumber</property-name>
    <value>#{visitBean.user.phoneNumber}</value>
    </managed-property>
    </managed-bean>
    I want to use the InfoBean class to capture data from info.jsp. I also want the info.jsp to be prepopulated with data from VisitBean.
    I first populate the visit bean from the database and then when the user clicks on the edit information link, the information form in info.jsp should be prepopulate with his information.
    Am I doing something wrong ? Is there a more elegant way of initializing the properties of a backing bean ?
    Any help will be appreciated.
    Thanks in advance.

    You can use the constructor to set the initial values of your bean.
    You may need to retrieve the visitBean from the session scope to do this.
    FacesContext.getCurrentInstance().getExternalContext().
                   getSessionMap().get("visitBean");Hope this helps.
    CowKing

  • JSF 1.0 Final - no backing bean validation of empty imputs

    Hi,
    I have simple inputText with validator in backing bean :
    <h:inputText id="layName" maxlength="30" value="#{shp.layerName}" validator="#{shp.validate}"/>
    and validator is executed properly when inputText isn't empty, but when is empty it isn't !.
    In my opinion validator should be executed in every reason, so I wonder if it is a bug ?
    I know that I can set required attribute to "true" and have additional validation of empty values :
    <h:inputText required="true" id="layName" maxlength="30" value="#{shp.layerName}" validator="#{shp.validate}"/>
    <h:message id="errors1" for="layName"/>
    but in this case I will receive standard error message. So my second question is how to overwrite this message with localized massage if backing bean validator isn't executed ?
    Thanks in advance.
    Olek

    If required is "false", then validators will not execute when the field is empty.
    The spec defines how to override the error message for when "required" validation fails, though I don't have the spec handy at the moment.
    -- Adam Winer (EG member)

  • Backing Bean Validation Method error

    Hi all,
    I've an ADF JSF User Registration Form and I want to set my server-side validation to confirm passwords entered by the user using the validator attribute bound to customized validation logic sitting in a method my backing bean. I've tried quite a few cracks at this but I still seem to get a java.lang.NullPointerException error when the method is invoked.
    The relevant method in my Backing Bean looks like this:
    public void comparePassword(FacesContext facesContext, UIComponent uiComponent, Object newValue) {
    //Get the new value that is passed passed from the Confirm Password field
    String confirmPassword = (String)newValue;
    //Get the password that has already been entered
    String password = (String)getLoginPasswordText().getValue();
    //Compare passwords and raise validation error message
    if (!password.equals(confirmPassword)){
    throw new ValidatorException(new FacesMessage
    (FacesMessage.SEVERITY_ERROR,
    "Passwords need to be the same",
    "Password values should be the same"));
    The getters and setters for the components are also in the bean and the gettLoginPasswordText() returns the original password input text field (the one that I want to compare it to).
    Is there something that I've missed here?
    Cheers

    Thanks Frank.
    I now understand a bit more about value binding. But unfortunately I need a little more help (from anyone) on this one. I've tried quite a few things and I think the problem stems from the fact that the validation code doesn't seem to pickup the value entered in the comparison field - at least in the way that I've coded it. Here's a more complete example of what I'm trying to overcome:
    I've got two input text components:
    <af:inputText required="true" simple="true"
    id="loginPasswordText"
    immediate="true"
    value="#{backing_UserRegistration.password1}">
    </af:inputText>
    <af:inputText required="true" simple="true"
    id="loginConfirmPasswordText"
    immediate="true"
    validator="#{backing_UserRegistration.comparePassword}"
    value="#{backing_UserRegistration.password2}">
    </af:inputText>
    I've setup the relevant accessors as in the following:
    String password1 = "";
    public String getPassword1(){
    return password1;
    String password2 = "";
    public String getPassword2(){
    return password2;
    And my validation now code looks like this:
    public void comparePassword(FacesContext context, UIComponent toValidate, Object value) {
    if (!Password2.equals(Password1)) {
    FacesMessage msg = new FacesMessage("summary message", " detailed message");
    msg.setSeverity(FacesMessage.SEVERITY_INFO);
    ValidatorException e = new ValidatorException(msg);
    throw e;
    I've tested the validation code on a standalone basis ie passing in a new variable as part of the method ie.
    String word = (String) value;
    if (word.equals("tom"))....
    The validator and message fires OK, so I know the problem lies with picking up the entered values for password1 and password2. I know the values are there because I can "see" them on screen and they are recognized by standalone validators and the bean has a session scope.
    Ideas anyone?
    Thanks

  • Backing bean usage question

    Hi guys,
    I'm quite new to JSF, and I was wondering wether this is the correct way to use a backing bean.
    I got a page, with two inputText boxes, 'name' and 'age'. When I submit that page, some simple validation is invoked and the page will call the submit() function in the backing bean.
    In the submit function, I want to get the values that are stored in the request scope, and that is where I'm not sure what to do...
    Should I just call 'this.getName()' and 'this.getAge()' ? It feels not right to me for some reason; I'm used to messing around in the request maps for those values and I was wondering if I should use the facesContext instead ? Either way seems to work, but I just want to use JSF the way it was ment to be used :-)
    Thanks lots!

    Hi, thanks for your reply
    So basically you mean that I have a regular bean (the VO) which I instantiate in the managed bean, after I press the submit button ?
    E.g.
    Submit() -> get values from facesContext -> create VO with those values ?
    Just asking because right now I have the properties that I want to have inside my managed bean. You suggest I should separate these properties in their own bean ?
    Thanks :-)
    Message was edited by:
    Ophyr

  • How to validate values from selectInputDate in backing bean

    I have two selectInputDate fields, arrivalDate and departureDate.
    I want to validate that arrivalDate cannot be greater than departureDate.
    java.lang.ClassCastException is raised at below line in the backing bean:
    Timestamp newArrivalDate = (Timestamp)newValue;
    I tried to use below in the backing bean for arrivalDate validation.
    import java.sql.Timestamp;
    public void arrivalDateValidator(FacesContext facesContext,
    UIComponent uiComponent, Object newValue) {
    //The new value is passed into us
    try {
    Timestamp newArrivalDate = (Timestamp)newValue; --> java.lang.ClassCastException raised at this line.
    //Get the Departure Date which is already bound on this screen
    Timestamp departureDate =
    (Timestamp)ADFUtils.getBoundAttributeValue("departureDate");
    // Now compare and raise an error if the rule is broken
    if (newArrivalDate.compareTo(departureDate) > 0)
    throw new ValidatorException(JSFUtils.getMessageFromBundle
    ("Arrival Date cannot be greater than Departure Date", FacesMessage.SEVERITY_ERROR));
    } catch(Exception e) {
    System.out.println("Some exception raised");
    e.printStackTrace();
    08/12/26 13:30:08 Some exception raised
    08/12/26 13:30:08 java.lang.ClassCastException
    08/12/26 13:30:08      at opera.activity.view.backing.app.TestApp.arrivalDateValidator(ActivityMain.java:1524)
    08/12/26 13:30:08      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    08/12/26 13:30:08      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    08/12/26 13:30:08      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    08/12/26 13:30:08      at java.lang.reflect.Method.invoke(Method.java:324)
    08/12/26 13:30:08      at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:146)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXEditableValue.validateValue(UIXEditableValue.java:400)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXEditableValue.validate(UIXEditableValue.java:206)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXEditableValue._executeValidate(UIXEditableValue.java:522)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXEditableValue.processValidators(UIXEditableValue.java:302)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXShowDetail.processValidators(UIXShowDetail.java:86)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at javax.faces.component.UIForm.processValidators(UIForm.java:190)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
    08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
    08/12/26 13:30:08      at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:932)
    08/12/26 13:30:08      at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:362)
    08/12/26 13:30:08      at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:98)
    08/12/26 13:30:08      at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
    08/12/26 13:30:08      at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110)
    08/12/26 13:30:08      at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213)
    08/12/26 13:30:08      at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
    08/12/26 13:30:08      at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:228)
    08/12/26 13:30:08      at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:197)
    08/12/26 13:30:08      at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:123)
    08/12/26 13:30:08      at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:103)
    08/12/26 13:30:08      at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
    08/12/26 13:30:08      at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:162)
    08/12/26 13:30:08      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    08/12/26 13:30:08      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
    08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
    08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
    08/12/26 13:30:08      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    08/12/26 13:30:08      at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
    08/12/26 13:30:08      at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
    08/12/26 13:30:08      at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
    08/12/26 13:30:08      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    08/12/26 13:30:08      at java.lang.Thread.run(Thread.java:534)
    Can someone suggest a solution?
    Thanks in advance.

    Hi user:
    Use the class oracle.jbo.domain.Date in the date component then is very easy using the compareTo Method (Returns -1 if DATE is less than date, 0 if DATE and date are equal (==), 1 if DATE is greater than date).
    Good Luck.

  • Value from backing bean in javascript confirm in 10.1.3

    Hallo,
    Please help
    I have 2 problems:
    Page with 1 record, where 8 items are updatable.
    In entity I 've a method where I set a value in bean. (BotId1 is one of these 8 updatebale items)
    What I expect: when I change a value in BotId1 the value of botId in ValiderenBotBean will be also changed
    public void setBotId1(Number value) {
    setAttributeInternal(BOTID1, value);
    EL.set("#{ValiderenBotBean.botId}",BotId.toString());
    My bean (session scope):
    package viewcontroller.pagedefs.produceren.backing;
    import org.apache.commons.logging.Log;
    import org.apache.commons.logging.LogFactory;
    public class ValiderenBotBean
    private static Log log = LogFactory.getLog(ValiderenBotBean.class);
    private String botId;
    public ValiderenBotBean() {
    // accessors
    public void setBotId(String botId) {
    log.debug("setBotId : " + botId);
    this.botId = botId;
    public String getBotId() {
    log.debug("getBotId : " + this.botId);
    return this.botId;
    Op my generaten page I have the button:
    <af:commandButton actionListener="#{bindings.Commit.execute}"
    action="Commit" onclick="if (validateForm('dataForm')){return(confirm(#{ValiderenBotBean.botId} + 'la')}"
    rendered="#{(((jhsUserRoles['JDMR_PRD03']) or (jhsUserRoles['JDMR_PRD03'])) or (jhsUserRoles['JDMR_PRD03'])) or (jhsUserRoles['JDMR_PRD03'])}" textAndAccessKey="#{nls['SAVE_BUTTON_LABEL_KOPPELENPRODUCTIEGEGEVENS']}"
    id="KoppelenProductiegegevensSaveButton">
    <af:resetActionListener/>
    </af:commandButton>
    I get the following error:
    Foutdetails webpagina
    Gebruikersagent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6.6; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.1; AskTB5.6)
    Tijdstempel: Thu, 17 Feb 2011 13:54:46 UTC
    Bericht: Syntaxisfout
    Regel: 3744
    Teken: 1
    Code: 0
    URI: http://172.16.6.108:8988/demeter/adf/jsLibs/Common10_1_3_2_0.js
    The code from Common:
    3732 function _callChained(
    3733 a0,
    3734 a1,
    3735 a2
    3736 )
    3737 {
    3738 if(a0&&(a0.length>0))
    3739 {
    3740 if(a2==(void 0))
    3741 {
    3742 a2=a1.window.event;
    3743 }
    3744 var a3=new Function("event",a0);
    3745 a1._tempFunc=a3;
    3746 var a4=a1._tempFunc(a2);
    3747 a1._tempFunc=(void 0);
    3748 return!(a4==false);
    3749 }
    3750 else
    3751 {
    3752 return true;
    3753 }
    3754 }
    Problem nr.1:
    When I call the button I do not see any logging that indicate that the value is set in backing bean
    Workaround: I made item on my page depending on item where I put my code.
    Result: I have to press 2 times on my button to execute the button code. First time to make the validation and the second time the button code itself.
    Not nice. The validation is also slow.
    But ok:
    Problem 2:
    I still get the same error, I see logging of execution of my validation.
    There is also the difference between loggings is 2 cases:
    If I use
    onclick="if (validateForm('dataForm')){return((#{ValiderenBotBean.botId} + 'la')}"
    what I really want instead of
    onclick="if (validateForm('dataForm')){return'la')}"
    I get:
    17-feb 14:28:40 DEBUG (ValiderenBotBean) -getBotId : -1
    17-feb 14:28:40 DEBUG (ValiderenBotBean) -getBotId : -1
    It means that value is obtained correctly.
    But still the same error.
    If I put for test purpose
    the following code into my bean:
    public String getBotId() {
    log.debug("getBotId : " + this.botId);
    botId = "23";
    return this.botId;
    I do not get any error.
    Any ideas?
    Please help

    Thanks, Amit,
    I will try it tomorrow.
    Some remarkes:
    1. I need javascript for confirmation
    2. I really do not PPR. It takes so long. The user use the scanner to put the value into input items in order speed up the process. And now PPR...
    3. My transient attribute will depend on 8 items. Even more waiting process.
    What I really want is to execute my db function only 1 time "onclick" or "oncommit" and according to outcome of db-function ask user for confirmation of commit.
    I tried already to implement dialog from ADF with launchDialog function.
    But ReturnListener did not function while I launch the Dialog manually.
    Anna

  • How to update bean properties when using an immediate link

    Hello,
    I have a page with a find link next to an input text field. The input text field requires a valid code to be entered. If the user doesn't know the code they need to press the find link to go to a search page and select the code. The input text code field needs to have a value entered so it has its required attribute set because the validator I have and attached to the input text field does not get called unless something is entered in the field. If I don't set the link to immediate the required constraint prevents the search page from being invoked but if I do set it to immediate the values typed on the page are not updated to the bean properties they are bound to.
    I have read many posts but I fail to see a way to resolve this. The update model phase is apparently skipped because of the immediate attribute and so the values typed in by the user are lost.
    Please help.
    Thanks,
    Randall

    A UIInput holds the submitted value.
    When updating models it is cleared to null but when some error occurs it keeps to hold the submitted value.
    The TextRenderer uses the submitted value if the value is null.
    Therefore, you can see the submitted value is redrawn when some error occurs.
    Unfortunately, this mechanizm does not work beyond requests
    because the default application action listener always create a new viewroot based on the navigation rules.
    An general solution of your problem is not so easy.
    I think it may be to customize the action listener or the lifecycle.
    A temporal solution may be that the link action copys the submitted value to the managed-beans.

Maybe you are looking for

  • Domain Guideance and Clarification using SVN and an Export suggestion

    Hello Oracle SQL Data Modeler Support, Apologies if this has been documented somehwere and I have missed reading it, but have gone through the User Guide and cannot find the clarification I want regarding domains. 1) WHAT IS BEST PRACTICE TO SAVE WHE

  • Two users on one iCloud account?

    We are atwo iPhone household (currently both are 3Gs), one for me and one for mywife.  We share an iTunes account and MobileMe account so both phones have access to the same music (iTunes) and the same Calendar (MobileMe).  When we convert to iCloud

  • How can i see my kernel level patch.

    Dear Friends, How can i see my kernel level patch. sach

  • Problem during database creation of 9.2.0 in RedHat 7.3

    hello I installed successful the 9.2.0 release on Linux7.3 RedHat, and I want to create a database. ERROR: ORA-01043: ORACLE not available ORA-27101: shared memory realm does not existI try to start the database: sqlpus /nolog connect / as sysdba sta

  • How do i transfer data from my old PC to my new imac?

    Basic dilemma.  I have the apple package of software to handle Microsoft Office documents, but don't know how to get my data from the old PC to the new Mac.  Seems like it ought to be easy, but i don't know where to start