Forum Stats

  • 3,768,281 Users
  • 2,252,770 Discussions
  • 7,874,513 Comments

Discussions

Session Issue from same browser in Oracle ADF 12.2.1.4.0

Meetendra
Meetendra Member Posts: 66 Red Ribbon

we have migrated one application from oracle jdev 11.1.2 to 12.2.1.4.0 and from weblogic 12 to 19

when the user login first-time tree details on the home page appears fine but when the user login with another login details, tree column not getting displayed correctly. what settings we could introduce in web.xml or welogic.xml to resolve this as this doesn't seem code issue.

Image 1 Name tags appear Image 2 doesn't appear


Answers

  • Timo Hahn
    Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 37,655 Red Diamond

    Do you use MDS or allow the users to hide reorder columns?

    It looks like the user logged in on the second image has hidden the name column. This can be stored in MDS per user and remains this way until the user resets this setting.

    Ask him to look at the 'View' menu above the table and select to show the name column again.


    Timo

  • Meetendra
    Meetendra Member Posts: 66 Red Ribbon

    Hi, @Timo Hahn no there is no such hidden column functionality. I only found this issue and when I logged in with the same login credentials in another tab.

    we faced the same issue when we were using the below old code after migration for redirecting to home page. so we used adfc-config.xml control flow with <af:button id="saveExit" text="#{msg['go.saveExit']}" action="returnToSourceHome" immediate="false" partialSubmit="true" >instead of this code.

      public String goHomeRedirect()

      {

        try

        {

          FacesContext context = FacesContext.getCurrentInstance();

          String defaultHomePage = MenuUtil.getDefaultHomePage();

          System.out.println("defaultHomePage : " + defaultHomePage);

          String homePageURI = context.getExternalContext().getRequestContextPath() + defaultHomePage;

          System.out.println("homePageURI : " + homePageURI);

          context.getExternalContext().redirect(homePageURI);

        }

        catch (IOException e)

        {

          getLogger().severe("IOException caught. Unable to redirect to page. e=\n" +

              e.getMessage(), e);

        }


        return null;

      }

  • Timo Hahn
    Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 37,655 Red Diamond

    So, do you see the missing column in the view menu?

    Timo

  • Meetendra
    Meetendra Member Posts: 66 Red Ribbon

    Hi @Timo Hahn thanks for reply .

    No, the Missing column(Name) won't appear in view menu even if it works fine.

    as it might be because of Name column is in facet "nodestamp" and all other columns are in "pathstamp"



          <f:facet name="nodeStamp">

            <af:column id="c1" width="375px" rowHeader="true" align="left"

                  inlineStyle="#{row.dueDateWarning ? 'background-color: yellow' : ''}">

              <f:facet name="header">

                <af:panelGroupLayout id="srcnmpgl1" layout="horizontal" valign="top">

                  <af:outputText value="#{msg['src.home.name']}" id="ot1"/>

                  <af:spacer width="30px" id="s1"/>

                  <af:link icon="/images/sort_up.png" shortDesc="#{msg['go.sort.up']}"

                       action="#{source_home.sort_click}" id="l1">

                    <af:setPropertyListener from="false"

                                to="#{source_home.searchCriteriaBean.sortDescending}"

                                type="action"/>

                    <af:setPropertyListener from="name" to="#{source_home.searchCriteriaBean.sortProperty}"

                                type="action"/>

                  </af:link>

                  <af:spacer width="5px" id="s2"/>

                  <af:link icon="/images/sort_down.png" shortDesc="#{msg['go.sort.down']}"

                       action="#{source_home.sort_click}" id="l2">

                    <af:setPropertyListener from="true"

                                to="#{source_home.searchCriteriaBean.sortDescending}"

                                type="action"/>

                    <af:setPropertyListener from="name" to="#{source_home.searchCriteriaBean.sortProperty}"

                                type="action"/>

                  </af:link>

                </af:panelGroupLayout>

              </f:facet>

              <af:link id="cl1" text="#{row.name}" action="#{source_home.displayWorkItem}"

                   disabled="#{row.nameLinkDisabled}"/>

            </af:column>

          </f:facet>

          <f:facet name="pathStamp">

            <af:outputText value="#{row.name}" id="ot2"/>

          </f:facet>

          <af:column id="col1" headerText="#{msg['src.home.blocked']}" width="130px" sortProperty="blockedReason"

                align="left" sortable="false"

                inlineStyle="#{row.dueDateWarning ? 'background-color: yellow' : ''}">

            <af:outputText value="#{row.blockedReason}" id="ot3"/>

          </af:column>

  • Timo Hahn
    Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 37,655 Red Diamond

    I don't see anything special that would trigger this behavior.

    Do you have a reproducible test case built on the HR DB schema?


    Timo