Custom themes and skins throwing error after migrating from portal5.1 - Websphere

This is a discussion on Custom themes and skins throwing error after migrating from portal5.1 - Websphere ; Hi All, I have migrated themes and skins from Portal 5.1 to portal 6.1. I have separated each theme and skin as a WAR file and deployed as per IBM info center. After applying theme to my page and skin ...

+ Reply to Thread
Results 1 to 12 of 12

Thread: Custom themes and skins throwing error after migrating from portal5.1

  1. Custom themes and skins throwing error after migrating from portal5.1

    Hi All,
    I have migrated themes and skins from Portal 5.1 to portal 6.1.

    I have separated each theme and skin as a WAR file and deployed as per IBM info center.

    After applying theme to my page and skin to portlet it is throwing the following error.


    Component E com.ibm.wps.composition.elements.Component render() EJPEF0007E: An unexpected error occurred during the component-rendering process. Reason: null.
    java.lang.NullPointerException
    at com.ibm.wps.util.SafeHashMap.get(SafeHashMap.java: 158)
    at com.ibm.wps.services.finder.FinderServiceImpl.cach eLookup(FinderServiceImpl.java:430)
    at com.ibm.wps.services.finder.FinderServiceImpl.find Template(FinderServiceImpl.java:386)
    at com.ibm.wps.services.finder.FinderServiceImpl.find SkinTemplate(FinderServiceImpl.java:306)
    at com.ibm.wps.services.finder.Finder.findSkinTemplat e(Finder.java:276)
    at com.ibm.wps.engine.templates.skins.Default.render( Default.java:139)
    at com.ibm.wps.engine.templates.SkinTemplate.render(S kinTemplate.java:68)
    at com.ibm.wps.composition.elements.Component.render( Component.java:632)
    at com.ibm.wps.composition.Composition.render(Composi tion.java:2883)
    at com.ibm.websphere.personalization.transformation.P znTransformationLayoutModel.render(PznTransformati onLayoutModel.java:90)
    at com.ibm.wps.model.wrappers.LayoutModelWrapperFacto ryImpl$LayoutModelWrapperImpl.render(LayoutModelWr apperFactoryImpl.java:275)
    at com.ibm.wps.engine.tags2.PageRenderTag.doStartTag( PageRenderTag.java:534)
    at com.ibm._jsp._Home._jspService(_Home.java:91)
    at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJsp Base.java:87)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:856)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1097)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1038)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:118)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain._ doFilter(WebAppFilterChain.java:87)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager .doFilter(WebAppFilterManager.java:834)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager .doFilter(WebAppFilterManager.java:682)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:566)
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.h andleRequest(ServletWrapper.java:486)
    at com.ibm.wsspi.webcontainer.servlet.GenericServletW rapper.handleRequest(GenericServletWrapper.java:12 2)
    at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensio nServletWrapper.handleRequest(AbstractJSPExtension ServletWrapper.java:226)
    at com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cher.include(WebAppRequestDispatcher.java:639)
    at com.ibm.wps.services.dispatcher.DispatcherServiceI mpl.handleRequest(DispatcherServiceImpl.java:93)
    at com.ibm.wps.services.dispatcher.DispatcherServiceI mpl.include(DispatcherServiceImpl.java:53)
    at com.ibm.wps.services.dispatcher.Dispatcher.include (Dispatcher.java:58)
    at com.ibm.wps.engine.templates.screens.Default.rende r(Default.java:96)
    at com.ibm.wps.engine.templates.ScreenTemplate.render (ScreenTemplate.java:59)
    at com.ibm.wps.engine.tags2.ScreenRenderTag.doStartTa g(ScreenRenderTag.java:189)
    at com.ibm._jsp._Default._jspx_meth_wps_screenRender_ 0(_Default.java:2008)
    at com.ibm._jsp._Default._jspService(_Default.java:11 67)
    at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJsp Base.java:87)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:856)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1097)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:570)
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.h andleRequest(ServletWrapper.java:486)
    at com.ibm.wsspi.webcontainer.servlet.GenericServletW rapper.handleRequest(GenericServletWrapper.java:12 2)
    at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensio nServletWrapper.handleRequest(AbstractJSPExtension ServletWrapper.java:226)
    at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensio nProcessor.handleRequest(AbstractJSPExtensionProce ssor.java:285)
    at com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cher.include(WebAppRequestDispatcher.java:639)
    at com.ibm.wps.services.dispatcher.DispatcherServiceI mpl.handleRequest(DispatcherServiceImpl.java:93)
    at com.ibm.wps.services.dispatcher.DispatcherServiceI mpl.include(DispatcherServiceImpl.java:53)
    at com.ibm.wps.services.dispatcher.Dispatcher.include (Dispatcher.java:50)
    at com.ibm.wps.engine.templates.themes.Default.doDisp atch(Default.java:283)
    at com.ibm.wps.engine.templates.themes.Default.render (Default.java:236)
    at com.ibm.wps.engine.templates.ThemeTemplate.render( ThemeTemplate.java:65)
    at com.ibm.wps.engine.phases.WPRenderPhase.processRen dering(WPRenderPhase.java:394)
    at com.ibm.wps.engine.phases.WPBaseRenderPhase.execut e(WPBaseRenderPhase.java:173)
    at com.ibm.wps.state.phases.AbstractRenderPhase.next( AbstractRenderPhase.java:106)
    at com.ibm.wps.engine.phases.WPAbstractRenderPhase.ne xt(WPAbstractRenderPhase.java:97)
    at com.ibm.wps.engine.Servlet.callPortal(Servlet.java :805)
    at com.ibm.wps.engine.Servlet.doGet(Servlet.java:607)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:743)
    at com.ibm.wps.engine.Servlet.doFilter(Servlet.java:1 184)
    at com.ibm.wps.resolver.servlet.ContentHandlerCleanup .doFilter(ContentHandlerCleanup.java:648)
    at com.ibm.wps.resolver.servlet.AbstractFilter.doFilt er(AbstractFilter.java:82)
    at com.ibm.wps.engine.Servlet.service(Servlet.java:11 75)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1097)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1038)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:145)
    at com.ibm.wps.engine.ExtendedLocaleFilter.doFilter(E xtendedLocaleFilter.java:93)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.wps.state.filter.StateCleanup.doFilter(Sta teCleanup.java:89)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.wps.resolver.friendly.servlet.FriendlySele ctionFilter.doFilter(FriendlySelectionFilter.java: 189)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.wps.engine.VirtualPortalFilter.doFilter(Vi rtualPortalFilter.java:88)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.wps.mappingurl.impl.URLAnalyzer.doFilter(U RLAnalyzer.java:282)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapp er.doFilter(FilterInstanceWrapper.java:190)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.d oFilter(WebAppFilterChain.java:130)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain._ doFilter(WebAppFilterChain.java:87)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager .doFilter(WebAppFilterManager.java:834)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager .doFilter(WebAppFilterManager.java:682)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:566)
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.h andleRequest(ServletWrapper.java:486)
    at com.ibm.ws.webcontainer.servlet.CacheServletWrappe r.handleRequest(CacheServletWrapper.java:90)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:748)
    at com.ibm.ws.wswebcontainer.WebContainer.handleReque st(WebContainer.java:1461)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:118)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpInboundLink.java:458)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpInboundLink.java:387)
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCa llback.complete(HttpICLReadCallback.java:102)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListe ner.futureCompleted(AioReadCompletionListener.java :165)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallbac k(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletion Actions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture .java:136)
    at com.ibm.io.async.ResultHandler.complete(ResultHand ler.java:195)
    at com.ibm.io.async.ResultHandler.runEventProcessingL oop(ResultHandler.java:784)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler .java:873)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1473)


    Can you please tell me when I am doing wrong?

    Thanks,
    Raj.

  2. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Are you able to apply the theme and skin separate? This looks like an issue with the skin, and the theme may be working ok.

    - Matt Munse

    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.

  3. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Hi,
    Thanks for the reply. I could see the theme is applying to my page and the portlet is not rendering in the page.

    What could be the problem with skin..any idea?

    Thanks,
    Raj.

  4. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Sure, please check this URL for some help:

    http://www-01.ibm.com/support/docvie...id=swg21268612

    - Matt Munse

    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.

  5. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Can you please upload your Control.jsp to the thread please?

    - Matt Munse

    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.

  6. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Hi,
    I have attached the Control.jsp to this thread.

    Also for your information I have added "ThinSkin" as of the skins allowed for my Theme as below in XML.




    MyTheme





    Now when I apply MyTheme to the page and selected skin as "ThinSkin"..still the problem exists. As per my understanding ThinSkin will come with Portal installation and still I am getting this error.Does that mean problem with my custome theme or skin?

    Thanks,
    Raj.

  7. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Sorry Control.jsp did not attach last time

  8. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Hi Matt,
    Did you find anything in control.jsp which is causing the issue? Could you please suggest something as this is very urgent for me..

    Thanks,
    Raj.

  9. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Hi Matt,
    Here is the content from Control.jsp as I am not able to attach to this thread.



















    div id="

    table width="100%" height="100%"


    td dir="ltr"





    span id="title.



     

    a href="#skipportlet
    img border="0" src=' /images/dot.gif' alt=' '
    title='







    wps:urlGeneration portletWindowState="solo" newWindow="true"
    contentNode=" " compositionNode="

    a href="#" class="actions" onclick="javascript: printPage('






    a href="





    a href='
    img border="0" align="absmiddle" src=' ' alt=' ' title='





    a href='
    img border="0" align="absmiddle" src=' ' alt=' ' title='



    a href='
    img border="0" align="absmiddle" src=' ' alt=' ' title='








    div id="












    %-- img src="
    a name="skipportlet

    var printID;

    var dynamicTitle =
    " ";
    var titleElement =
    document.getElementById("title. ");
    if (titleElement != null) {
    if (dynamicTitle != "" && dynamicTitle != "null")
    titleElement.innerHTML = dynamicTitle;
    }





    function printPage(id){
    if (document.getElementById != null){
    var html = ' \n 0)
    html += headTags[0].innerHTML;
    }
    html += '\n
      
    ';
    var printReadyElem = document.getElementById(id);
    var sample1 = printReadyElem.getElementsByTagName('*');
    for(i=0;i -1){
    sample1.Style="visibility:hidden;";
    }
    }
    }
    var printReadyElem = document.getElementById(id);
    if (printReadyElem != null){
    html += printReadyElem.innerHTML;
    }
    else{
    return;
    }
    html += ' ';
    var printWin = window.open("","printPage","resizable=yes,scrollbars=yes,menubar=no,toolbar=no ,status=no,width=700,height=500,screenX=100,screen Y=100,top=100,left=100");
    printWin.document.open();
    printWin.document.write(html);
    printWin.document.close();
    }
    else {
    alert("The print ready feature is only available if you are using an browser. Please update your browser.");
    }
    }


  10. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Control.jsp:
    =============
















    div id="

    table width="100%" height="100%"


    td dir="ltr"





    span id="title.



     

    a href="#skipportlet
    img border="0" src=' /images/dot.gif' alt=' '
    title='







    wps:urlGeneration portletWindowState="solo" newWindow="true"
    contentNode=" " compositionNode="

    a href="#" class="actions" onclick="javascript: printPage('






    a href="





    a href='
    img border="0" align="absmiddle" src=' ' alt=' ' title='





    a href='
    img border="0" align="absmiddle" src=' ' alt=' ' title='



    a href='
    img border="0" align="absmiddle" src=' ' alt=' ' title='








    div id="












    %-- img src="
    a name="skipportlet

  11. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Did you move your unlayered container files in the new theme?

    - Matt Munse

    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.

  12. Re: Custom themes and skins throwing error after migrating fromportal 5.1

    Hi Matt,
    No , I feel it is not required to move unlayered container files as they were not part of portal 5.1 themes and skins.

    Right now portal is not throwing exception but at the same time skin is not applying to the portlet. Earlier when this exception was throwing portlet was not coming up , but right now it is coming up without skin.

    There is a java script error in place of Portlet Menu as theme is not able to identify the skin I guess.

    I have removed everything from control.jsp to check that portlet should not comeup without "portal-skinortletRender" tag..but it is not throwing javascript error.

    Where can I check whether theme is identifying particular skin in portal? I have applied the skin to the portlet and theme to the page..but in this case theme is not identifying.

    Meantime I have another skin working which was migrated the same way I did for this skin , but not sure why this one is throwing javascript error.Can you tell me what are the possible ways I can try to resolve this issue?

    Thanks again,
    Raj.

+ Reply to Thread