Update "rendered" attribute via ajax

Is there a workaround to update the "rendered" attribute of a commandLink via AJAX? I'm getting an error 'malformedXML: During update: j_idt12:prevCmd not found'.
code snippet:
<h:commandLink action="#{controller.previous}"
                                   value="Previous"
                                   rendered="#{controller.hasPreviousPage}"
                                   id="prevCmd">
     <f:ajax render="table prevCmd nextCmd" immediate="true"/>
</h:commandLink>
<h:commandLink action="#{controller.next}"
                                   value="Next"
                                   rendered="#{controller.hasNextPage}"
                                   id="nextCmd">
     <f:ajax render="table prevCmd nextCmd" immediate="true"/>
</h:commandLink>

Try adding the form name to the components names:
<f:ajax render="form1:table form1:prevCmd form1:nextCmd" immediate="true"/>

Similar Messages

  • How do I update "Rendered" attribute property from VO in runtime?

    I can override isAttributeUpdateable() in RowImpl for "updateable" attribute property of a VO in runtime.
    Is there API to update "Rendered" attribute property? I need to set it based on some condition or business rule in runtime.
    thanks,

    If you have a work flow there are several ways to do this. If the attribute is global, and can change on all resources, you can set user.global.<attribute> to what ever you want and it will usually propagate out fine. You can also update the attribute specifically on the resource with user.accounts[LDAP].<attribute>.

  • Updating the model via AJAX

    Victor,
    I find Tor's and Greg M's bpcatalog documents describing AJAX and JSF useful. However they do not address 'updates'.
    Updating the model via an AJAX request that is handled by the JSF framework as suggested by bccatalog examples is a challenge.
    I am not sure if it is best to use the "Update Model" phase of the life cycle or just cheat and put he update code in the tags render response phase. Also, it appears that the "update model Phase" may not be included in the lifecycle as the ajax request is not really a JSF "postback".
    Does anyone know what tradeoff result in doing an update in the Render Response Phase?
    Cheers,
    Godfrey

    I've tried updating the model using AJAX and a RenderPhaseListener, but never succeeded. I have a simple CRUD form with two selectOneMenu components, some text boxes, and a submit button. When a selection is made in the first select list, an AJAX call is made that populates the second select list. Once that happens, the second select list contains a different list of <f:selectItems> in the DOM than it does in the underlying component model. If the array of SelectItems that are used to populate the second select list is in a managed bean, when the form is submitted, the second select list fails validation (Validation Failed: Not a Valid Value) because the selected item exists in the DOM, but not in the SelectItem array in the managed bean. To work around this, I placed the SelectItem array in the session, instead of in the managed bean. When the AJAX call is made, the backend Java code updates the SelectItem array in the session. This prevents the model and the DOM from getting out of synch. I hate putting anything in the session, because sessions tend to die, but this is the best workaround I could come up with. I'm open for any better solutions. Oh, by the way, if I use AJAX enabled select lists on a JSF page in a JSF 1.0 web app, the Invoke Application phase is mysteriously skipped when the form is submitted, which prevents the form contents from being saved. If I use JSF 1.1_01, the form saves like a charm. You gotta love being on the bleeding edge.

  • Updating Document Attributes via XML

    I found an article in Metalink which gives the following example:
    <?xml version = '1.0' standalone = 'yes'?>
    <CustomDoc>
    <UPDATE reftype="path">/public/MyiFS/MyDoc.myextension</UPDATE>
    <MyCustomAttribute>NewValue</MyCustomAttribute>
    </CustomDoc>
    This updates the custom attribute "MyCustomAttribute" for document
    "MyDoc.myextension" stored in the "/public/MyiFS" folder, which is an
    instance of the subclassed document type with the registered
    extension of "myextension".
    Source Article: http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=125517.1
    Has anyone gotten this to work? If so could you give a real example? I don't believe we created a custom document type, but we have added some custom attributes which show up for every document we put in iFS.
    null

    I found an article in Metalink which gives the following example:
    <?xml version = '1.0' standalone = 'yes'?>
    <CustomDoc>
    <UPDATE reftype="path">/public/MyiFS/MyDoc.myextension</UPDATE>
    <MyCustomAttribute>NewValue</MyCustomAttribute>
    </CustomDoc>
    This updates the custom attribute "MyCustomAttribute" for document
    "MyDoc.myextension" stored in the "/public/MyiFS" folder, which is an
    instance of the subclassed document type with the registered
    extension of "myextension".
    Source Article: http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=125517.1
    Has anyone gotten this to work? If so could you give a real example? I don't believe we created a custom document type, but we have added some custom attributes which show up for every document we put in iFS.
    null

  • Updating AD Attributes via OIM user forms

    Hi,
    I have configured an AD connector. Firstly, I did a trusted recon to create the OIM. Next, I did a user recon to link the AD user to the OIM user. After that I have configured to pre-populate to show the AD attributes onto the OIM user form.
    Now, what I want to do is to update the AD attributes (eg. Mobile) in the OIM web interface, and has it reflect back to AD.
    Appreciate a detail description as I am very new to OIM.
    Cheers, SK

    You may want to try this:
    a. Add an entry in Lookup.USR_PROCESS_TRIGGERS
    b. Add a Process Form field and a Process task in each Process where you want to push the value.
    The task should have a name "<UDF label> Updated"
    c. Create another one called "Change <UDF label>"
    d. Make the tasks conditional, "allow multiple instances"
    e. Wire the "Change <UDF label>" to copy values from the user profile to the process form
    f. Wire the "<UDF Label> Updated" to the connector adapter.
    --Deepak                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Validation Error after updating a SelectOneMenu via Ajax (DWR)

    I have a <t:selectOneMenu> that is bound to a backing bean together with a <f:selectItems> that is bound to a SelectItems[] attribute in the same backing bean. See below:
    <t:selectOneMenu forceId="true"
    id="department"
    value="#{DeptBean.departmentId}">
    <f:selectItems value="#{DeptBean.departmentList}" />
    </t:selectOneMenu>
    When the user changes another field on my page, I use DWR to retrieve a new list of departments and update the <t:selectOneMenu> accordingly. That works just fine.
    The problem is that if I select a value from the updated department list and then submit the page I get a "Validation Error".
    I suspect that the JSF Component Tree still has the old list of values and does some validation which obviously fails.
    Has anyone dealt with this before? Any ideas would be appreciated!

    <t:selectOneMenu forceId="true"
    id="department"
    value="#{DeptBean.departmentId}">
    <f:selectItems value="#{DeptBean.departmentList}"
    />
    </t:selectOneMenu>What is the type of departmentId ? If it is not a String, then try making it a String and see if the issue is resolved. I am not sure if this will help you. But its worth a try.

  • Issue Setting Resource Attributes via Workflow Process

    I'm currently trying to set resource attributes via a workflow process, but for whatever reason the attribute is not detected as "changed" and the update object has nothing about the attribute. I'm wondering if I'm just doing something wrong with the way I'm setting it, or if I'm missing a piece to apply the upate.
    What I'm doing is...
    1. Checking out the user view
    2. updating the attribute via code something like this...
    <set name='user.accounts[ldap].attributeIWantToChange'>
    Logic in here
    </set>
    3. then I'm checking the view back in.
    Anyone know why this isn't working(I can set other attributes like waveset.roles fine this way)?
    Edited by: UNO-AD-HM on Jul 6, 2009 12:54 PM

    Figured it out, have to load a different form in when I check the view out, the tabbed user's form will not update resource attributes.

  • Updating value of for taxonomy attributes via ABAP API

    Hi ,
    We have table Product hierarchy repository in that we have Products table and ProductHierarchy table which is of type taxonomy .
    The product hierarchy is assigned to each product as lookup taxonomy field.
    Can anyone please let me know how we can update the values assgined to the attribute throght ABAP API.
    Example we have the attribute called color which assigned to Product Hierarchy 'A' and this product hierarchy 'A' is attached to Material '111' and the attribute color will have value 'Blue' for material '111' now I want to update the value of color to 'Red' . How we can achieve this via the MDM ABAP API.
    Regards,
    Amar Kamat

    If your question is how to change the value of an attribute for a specific product this is the solution:
    Use IF_MDM_CORE_SERVICES->RETRIEVE( ) to retrieve the product record so that you have a populated structure of type MDM_PARAMETER. In this structure you will find the entry relating to the taxonomy field. The VALUE attribute of this line entry will be a reference to type MDM_TAXONOMY_ENTRY.
    At this point you will want to take the TAXONOMY_ENTRY_ID and TAXONOMY_TABLE_CODE of this structure to retrieve the attributes. Using IF_MDM_CORE_SERVICE->RETRIEVE_ATTRIBUTES( ) and the attributes mentioned before you will get the results into a table of line type MDM_ATTRIBUTE_INFORMATION_SL.
    Select the appropriate line from the result table based on the attribute name (ATTR_NAME). In the record of type MDM_ATTRIBUTE_INFORMATION_SL you will now want to select the appropriate line from the table found in field ATTR_FEATURE_DOMAIN. Find the appropriate attribute (in this case color) by VALUE_NAME and copy the VALUE_ID (type MDM_UNIQUE_ID).
    Now back to where we left off in the original record (MDM_PARAMETER), loop through the table found at field TAXONOMY_ATTRIBUTES of the MDM_TAXONOMY_ENTRY looking in ATTR_INFO for the correct ATTR_NAME. When the correct entry is found, update the ATTR_FEATURE_DOMAIN with the new VALUE_ID and viola, you've got a mdm record ready to be updated.
    Simply call IF_MDM_CORE_SERVICE-UPDATE( ) with the modified record and you've updated your attribute assignment.
    In short:
    Navigate to the MDM_TAXONOMY_ENTRY of the product record
    Retrieve the attributes from the corresponding taxonomy table and navigate to the unique ID of the desired attribute
    Navigate to the attribute within the record's MDM_TAXONOMY_ENTRY and update the VALUE_ID with the new unique ID
    Update the product record
    Regards,
    Brian Dennett

  • Update marketing attribute and customer master data via Survey Response

    Hi,
    I am creating a marketing survey. I have come to a point where I am able to get the reponses posted by the business partners.
    Now I would like to update the BP's directly when they respond. The challenge here is I want to update both Marketing attribute and Customer master.
    Is this possible with standard function modules. I am using version 4.0. Please let me know.
    Regards,
    Hemanth

    Hello Hemanth,
    Check my last response in the below thread, it could be a reason.
    update marketing attributes in BP via survey
    Thanks
    Raja Pamireddy
    CRM Marketing Forum Moderator.

  • Rendered attribute of commandButton preventing action method from executing

    When I add a rendered tag to my commandButton it'll only execute the method intermittantly. After a lot of testing, I've narrowed down the problem so I now know when it does and does not work properly.
    If rendered="true" it always works fine
    If rendered="#{issue.update}" and isUpdate() is simply "return true;" it'll always work correctly
    If rendered="#{issue.update}" and isUpdate() is simply "return this.getId() != 0;" it will not execute the action specifiied, however the page does refresh.
    It's also interesting to note that on the rendered page, the button is always shown only when it should be. So when the action fails to execute, the button is shown on the screen.
    In the case that doesn't work, I debugged through and noticed that isUpdate() is called six times for a single page refresh. By printing a stacktrace for each call, I discovered that it's called once in the ApplyRequestValues stage of the lifecycle and the other five times are from RenderResponse (I have the stacktraces, let me know if they'd be worth posting). This method is only referenced once and only on the jsf page, never in the java code... but I'll go back and try to understand why it's calling it so many times later.
    The first time isUpdate() is called, it will retrun false because the value for id has not yet been assigned, which makes sense. This causes a "false" to be returned from isUpdate() and this is what is causing the action to not be executed. If I debug through and change the return value to be true here (only the first time) the action is updated. So my question is, what's going on here? I don't understand why is isUpdate() called so many times, why is it called so early in the lifecycle, and why the call in the apply request values stage determines whether or not it executes the action?
    Now, as a workaround, I put a binding on the id, and tried to use that value. That exposed another problem with my page which requires some explanation... Here are the relevent sections of the page and backing bean...
    issue.jsp
    <h:outputText value="#{issue.init}" />
    there's a datatable here which displays all issues and has a commandLink to edit the issues (immediate="true"). It posts back to this page and passes an ID on the URL.
    <h:inputHidden id="id" value="#{issue.id}" binding="#{issue.idBinding}" />
    <h:inputText id="name" value="#{issue.name}" required="true" />
    <h:commandButton id="updateIssue" value="Update" action="#{issue.updateIssue}" rendered="#{issue.update}" />
    Issue.java
    getInit() will get the id from the FacesContext (specifically, the URL) and load the data from the database.
    On the rendered page in my web browser:
    After clicking on an edit link, the page is loaded and the name is filled in, the update button is on the screen, and everything looks good.
    When I view source, I see that the hidden input for id is set to zero. I'm still trying to figure out why this is the case since all the other parameters are set properly. I stepped through getInit() and it is, indeed setting the id property properly.
    So when I added the binding to get the value from there instead of via the local values, I found that it always got zero (presumedly because that's what is rendered in the HTML code). This means that isUpdate() still returns false on the first call, and my attempt at a workaround fails! So, just as a test, I used some "javascript on the URL" trickory to set the id field to "10". That worked just fine. So the root of the problem is that issue.id is not loading. I put code in the getId() method to always look at the binding and then faces context and put the id into this.id if it found a non-null and non-zero value. It now returns the correct value all of the time but the HTML produced still says the value is zero.
    I've spent about 4 hours on this issue and I'm to the point where I need advice from someone who is more educated on how JSF works. I know the inputHidden get the vaule for the HTML tag it produces from getId() because when I hard code that to always return 10, it works. But when I leave it to return the proper value, the debug statements say it's returning the proper value, but the HTML always says it's zero. This isn't an acceptable solution anyway because I use getId() in the datatable to display the IDs of each of the issues; I just wanted to see if it'd work and it didn't.
    Here's my latest getInit() method (which returns the value from the URL when called from the datatable, but not when called from the inputHidden.
        public int getId() {
            if(getIdBinding() != null && !getIdBinding().isLocalValueSet()) {
                if(getIdBinding().getSubmittedValue() != null) {
                    int temp = Integer.parseInt((String)getIdBinding().getSubmittedValue());
                    if(temp != 0) {
                        this.id = temp;
                        log.info("Got binding value of "+this.id);
            FacesContext ctx = FacesContext.getCurrentInstance();
            if(ctx != null) {
                Map<String, String> map = ctx.getExternalContext().getRequestParameterMap();
                    if(map != null) {
                    String given_id = map.get("id");
                    if(given_id != null) {
                        // if given an ID and no action, we load the data
                        try {
                            log.info("Got value from FacesContext of "+given_id);
                            int temp = Integer.parseInt(given_id);
                            if(temp != 0)
                                this.id = temp;
                        } catch(NumberFormatException e) {
                            // if what's passed in isn't an integer, we leave everything at default values
            return this.id;
        }Thanks in advance,
    Adam

    I'm clicking a link which will load data into a form. In the form there is a field called "id" which has a value of something other than zero. I press the update button (which is only rendered when the id is non-zero), it submits the form. When the restore view happens, the id is the default value of 0 because it has not yet applied the values from the form to the backing bean. Therefore the rendered attribute of update button (isUpdate()) will return false, and the update() method does not get queued.
    When I switch my backing bean to session level, the restore view already has the id loaded, even before the values from the form are applied, so everything works as expected. The problem was that I needed to have the correct return values before any values have been loaded into the member variables.
    As a solution to this, I made some private boolean variables called isNew and isUpdate. Both of them are true by default. This makes sure that the isNew() and isUpdate() methods (attached to the render attribute of my command buttons) return true in the restore view phase. When I read in the id from the URL or hidden input, it'll update the boolean values accordingly, which makes sure the buttons are rendered properly. This allowed me to set the backing bean back to the request scope, which make me happy. <img class="emoticon" src="images/emoticons/grin.gif" border="0" alt="" />
    Thank you Mr. De Campo. You gave me exactly what I was looking for... a better understanding of how thigns work, and (indirectly) a clean solution to my problem.

  • Problem with rendered attribute in jhs 10.1.3.3

    We are currently trying to migrate our applications from jhs 10.1.3.2.52 to jhs 10.1.3.3.87 using jdeveloper 10.1.3.5. We are facing a problem with all the detail groups structured inside detail group regions - they have all disappear from the pages.
    In my example code i have two master-detail groups Products (Master) and ExpertiseAreas (Detail) on the same page:
    Products - Group
    -> ExpertiseAreasDtl - Detail Group Region
         -> ExpertiseAreas - Group (Samepage="true")
    The problem is that the detail group ExpertiseAreas is not rendered on the page.
    As i looked in through the pages generated by the 2 different releases of jhs using the same app definition, i can see the following:
    CODE GENERATED FOR THE ExpertiseAreasDtl Detail Group Region (all the vms used are the default):
    in jhs10.1.3.3.87:
    <af:panelGroup *rendered="#{(ProductsIterator.currentRow!=null and ProductsIterator.findMode!='true')}"* id="ProductsRegionsExpertiseAreasDtlPanelGroup">
    in *jhs 10.1.3.2. 52*:
    <af:panelGroup id="ProductsRegionsExpertiseAreasDtlPanelGroup">
    First of all a rendered attribute is being generated in the new version of jhs and not in the old.
    The real problem seems to be with the iterator binding generated from verticalRegionContainer.vm in the regular expression: "#{(ProductsIterator.currentRow!=null and ProductsIterator.findMode!='true')}". It should have been *bindings.*ProductsIterator and not plain ProductsIterator. Has anybody got any ideas on how to solve the problem?
    Thanks
    Giorgos
    Edited by: user647567 on 17 Δεκ 2009 2:16 πμ
    Edited by: user647567 on 17 Δεκ 2009 5:58 πμ

    Giorgos,
    We have uploaded a new service update, 10.1.3.3.88, on the cso.oracle.com site. This should fix your issue.
    Steven Davelaar,
    JHeadstart Team.

  • Is it possible to set webapp item releaseDate when submitting via ajax?

    I've been trying to set the releaseDate of a webapp item when entering the item via ajax.  So far I have been unable to do so....is it possible?
    For the field name and date format I referenced the API docs.
    I've tried both releaseDate and ReleaseDate
    Here's the console of the variable before submission
    theItemName: Test
    strDate: 12/14/2014
    Here's the relevant submit code
              var testOpts = {
                    url: profileAction,
                    data: {
                        ItemName: theItemName,
                        releaseDate: strDate
                    type: "POST",
                    success: function(data, txt, jqXHR) {
                        console.log("submit success");
                    error: function(jqXHR, txt, error) {
                        console.log("submit error");
                        return false;
                $.ajax(testOpts)
    Anyone done this successfully?
    Thanks
    Dave

    Hi Dave,
    The date format specified in the parameters section was incorrect, I have fixed that and will push the update shortly. The correct date format is YYYY-MM-DD - sorry for the inconsistency.
    I have just re-tested the sample code here - Reference guide - Create web app item (that one had the correct format and it was working properly.
    Thanks and have a nice weekend,
    Mihai

  • Powershell - Bulk Set-ADUser attributes via a CSV file

    I am attempting to do a Bulk replace of AD User account attributes via a CSV file.  Each line in this script works except the part of Set-ADUser where I enter -Replace $attribs. I'm not sure how to code this
    part.
    <#
    The .csv file should have the following headers (first line)
    GroupName,Status,Approver1,Approver2,Owner
    #>
    #Import CSV
    $csv = @()
    $csv = Import-Csv -Path "C:\TempAdd_Grp_Attrib.csv"
    #Loop through all items in the CSV
    ForEach ($item In $csv)
    $gname = $item.GroupName
    $attribs = @{'extensionAttribute2'=$item.Status; 'extensionAttribute3'=$item.Approver1; 'extensionAttribute4'=$item.Approver2; 'managedBy'=$item.Owner}
    Set-ADGroup -Identity $gname #-Replace $attribs
    mamadukes

    Yes. I am attempting to update the AD Group extension attributes.
    The code below works, but I know I can streamline this if I use the INSTANCE, which I am having an issue with (Set-ADGroup -Instance $Update)
    Import-Module ActiveDirectory
    <#
    The .csv file should have the following headers (first line)
    GroupName,Status,Approver1,Approver2,Owner
    #>
    #Import CSV
    $date = get-date -Format "MMddyyyymm"
    $csv = @()
    $csv = Import-Csv -Path "C:\Temp\Add_Grp_Attrib2.csv"
    #Loop through all items in the CSV
    ForEach ($item In $csv)
    $Update=(Get-ADGroup $item.GroupName -Properties extensionAttribute2,extensionAttribute3,extensionAttribute4,ManagedBy);
    $Update."extensionAttribute2"=$item.Status
    $Update."extensionAttribute3"=$item.Approver1
    $Update."extensionAttribute4"=$item.Approver2
    # Set-ADGroup -instance $Update
    Set-ADGroup -Identity $item.groupName -ManagedBy $item.Owner
    Get-ADGroup $item.GroupName -Properties extensionAttribute2,extensionAttribute3,extensionAttribute4,ManagedBy | select name,extensionAttribute2,extensionAttribute3,extensionAttribute4,ManagedBy | Export-Csv "C:\temp\Add_Grp_Attrib_Updates_$date.csv" -NoTypeInformation
    mamadukes

  • Update AD groups via resourceObjectUpdate?

    Hello idm experts,
    I need to update to update an object in AD - move in into a different container, update some attributes and add AD security groups.
    Is that possible to do all at once via updateResourceObject com.waveset.provision.WorkflowServices call?
    Trying to do it - rename (move to different OU) is correct, modifying attributes is correct. Group membership gets completely wiped out.
    Here is the user object I'm passing:
    <Object>
    <Attribute name='user'>
    <Object>
    <Attribute name='attributes'>
    <Object>
    <Attribute name='description' value='xxxx111'/>
    <Attribute name='groups'>
    <List>
    <String>CN=na_approver,OU=FWD Groups,OU=Ldap Data,OU=INT,DC=msqa,DC=qa,DC=ms,DC=com</String>
    <String>CN=NA_BranchAdmin1,OU=Common Groups,OU=ISG,OU=INT,DC=msqa,DC=qa,DC=ms,DC=com</String>
    </List>
    </Attribute>
    <Attribute name='objectGUID' value='106d443e62585a469d0ddf6dfdbaacfe'/>
    <Attribute name='sAMAccountName' value='xxxxxtest09'/>
    <Attribute name='ws_newAccountId' value='cn=paveltest0909,ou=gwm,ou=exchange,ou=isg,ou=int,dc=msqa,dc=qa,dc=ms,dc=com'/>
    </Object>
    </Attribute>
    <Attribute name='objectId' value='CN=xxxxxtest0909,OU=GWM,OU=Exchange,OU=ISG,OU=INT,DC=msqa,DC=qa,DC=ms,DC=com'/>
    <Attribute name='objectType' value='User'/>
    <Attribute name='resourceId' value='#ID#Resource:AD'/>
    </Object>
    </Attribute>
    </Object>
    And here is the call:
    <Action name='Update User' application='com.waveset.provision.WorkflowServices'>
    <Argument name='op' value='updateResourceObject'/>
    <Argument name='objectId' value='$(iden)'/>
    <Argument name='objectType' value='User'/>
    <Argument name='object' value='$(ldapObject.user)'/>
    <Argument name='resourceId' value='#ID#Resource:AD'/>
    <Argument name='action' value='update'/>
    <Return from='applicationError' to='applicationError'/>
    </Action>
    Update seems to be OK, the object is moved, attributes are updated, but group membership is wiped out.
    WavesetResult contains this:
    <WavesetResult>
    <ResultItem type='result' status='UI_MSG_SEVERITY_OK'>
    <WavesetResult>
    <ResultItem type='ACCOUNT_RENAMED'>
    <String>CN=xxxxxtest0909,OU=GWM,OU=Exchange,OU=ISG,OU=INT,DC=msqa,DC=qa,DC=ms,DC=com</String>
    </ResultItem>
    <ResultItem type='message' status='UI_MSG_SEVERITY_OK'>
    <Message id='WF_RESOURCE_OBJECT_UPDATED'>
    <String>WF_RESOURCE_OBJECT_TYPE_USER</String>
    <String></String>
    </Message>
    </ResultItem>
    </WavesetResult>
    </ResultItem>
    </WavesetResult>
    What happened with group membership? Is there something I'm missing in object parameters or WorkflowServices parameters?

    You can "nest" an AD group in a SharePoint group and that will work just fine. What does not work is if you add users to an AD group, then nest that group in another AD group, and apply that second AD group to SharePoint. SharePoint is unable to crack open
    the nested group to parse the users.
    What do you mean by Site Collection Web Policy? Policies are applied at the Web Application level (in Central Administration).
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Errors in rendered attribute of main jspx files generated code using JAG

    I have been using JHeadStart in JDeveloper 10.1.3 Release 3 using the JHeadStart from the update site: http://files.oraclecorp.com/content/AllPublic/SharedFolders/JHeadstart%2010.1.3%20Preview-Public/center.xml
    When using JAG on a HR project with 5 levels I get an error in Locations, Regions, Countries, Departments, Employees.jspx files
    It generates the following:
    rendered="#{!createModes.CreateEmployees ${JHS.addELExpression(${JHS.current.group.insertAllowedExpression},"and")}}"
    I fix the "and" problem
    rendered="#{!createModes.CreateEmployees ${JHS.addELExpression(${JHS.current.group.insertAllowedExpression},'and')}}"
    Disassembling the above for better readability:
    rendered=""
    !createModes.CreateEmployees ${}
    JHS.addELExpression()
    ${JHS.current.group.insertAllowedExpression},'and'
    This should be legal code!?
    It complains that it encountered a "(" where another character is expected
    Replacing ${JHS.addELExpression(...)} with ${1} I get an error saying Expression Language is not supported for rendered attribute!?
    Where do I go from here?
    Thanx in advance :-D
    PS: I am giving a Java community presentation tomorrow at noon with a JHeadStart demo, so it would be really cool with a fix ASAP ;)
    Perhaps using the JHeadStart from local file would fix the problem!? I will give it a try...

    This forum is intended for Oracle customers. Please use the Oracle internal mailing list [email protected]
    Steven Davelaar,
    JHeadstart Team.

Maybe you are looking for