7 Replies Latest reply on Feb 4, 2009 9:16 PM by dsf sdf

    The curious case of the magical portlet ...

    dsf sdf Newbie

      Hello,

      i have mysterious deployments problem with a portlet.

      When i deploy just this portlet in the portal, everything works fine.

      As soon as i deploy another portlet with this one, i can say good bye to the first one.

      No error in the server logs, nothing, it seems my first portlet isn't event deployed anymore...

      i can't figure out what can happen, i really need some help, any idea is welcome... thanks

        • 1. Re: The curious case of the magical portlet ...
          Prabhat Jha Master

          This would be very difficult to figure out based on your input.. You may want to post your deployment descriptors. If you are using *-object.xml, may be one is overwriting the other.

          • 2. Re: The curious case of the magical portlet ...
            dsf sdf Newbie

            I have something like 8 or 10 portlets i think, including the magical one.

            Yes i thought it could be some overwriting in the -object.xml but my magical portlet is configured to be displayed in the default page of the portal.
            Each one of the other portlets is configured to be displayed in its own page.
            So i don't think this problem can happen.

            by the way i'll have a look and post the descriptors

            • 3. Re: The curious case of the magical portlet ...
              dsf sdf Newbie

              so my problem also happens with another portlet set.

              I have narrowed the problem down to two portlets which seem to mutually exclusive ...

              Actually my portlet A when deployed alone or with other portlets is ok, but when i also deploy the portlet B, A disapears.
              No error in the server logs, is see logs for portlet B deployment but nothing for A.

              These portlets are deployed on the same jboss AS but not on the same portal.
              portlet A is deployed in default portal, portlet B in admin portal ...

              portlet A -object.xml :

               <deployments>
               <deployment>
               <parent-ref>Partner</parent-ref>
               <if-exists>overwrite</if-exists>
               <page>
               <page-name>Event</page-name>
               <security-constraint>
               <policy-permission>
               <action-name>viewrecursive</action-name>
               <role-name>User</role-name>
               </policy-permission>
               </security-constraint>
               <properties>
               <property>
               <name>order</name>
               <value>4</value>
               </property>
               </properties>
               <window>
               <window-name>PrtnrEventPortletWindow
               </window-name>
               <instance-ref>PrtnrEventPortletInstance
               </instance-ref>
               <region>center</region>
               <height>0</height>
               <initial-window-state>maximized</initial-window-state>
               <properties>
               <property>
               <name>theme.renderSetId</name>
               <value>emptyRenderer</value>
               </property>
               </properties>
               </window>
               </page>
               </deployment>
              



              portlet B -object.xml :
               <deployment>
               <parent-ref>Admin</parent-ref>
               <if-exists>overwrite</if-exists>
               <page>
               <page-name>Gestion Utilisateurs</page-name>
               <security-constraint>
               <policy-permission>
               <action-name>viewrecursive</action-name>
               <role-name>Admin</role-name>
               </policy-permission>
               </security-constraint>
               <properties>
               <property>
               <name>order</name>
               <value>2</value>
               </property>
               </properties>
               <window>
               <window-name>PrtnrBoUserPortletWindow
               </window-name>
               <instance-ref>PrtnrBoUserPortletInstance
               </instance-ref>
               <region>center</region>
               <height>0</height>
               <initial-window-state>maximized</initial-window-state>
               <properties>
               <property>
               <name>theme.renderSetId</name>
               <value>emptyRenderer</value>
               </property>
               </properties>
               </window>
               </page>
               </deployment>
              


              • 4. Re: The curious case of the magical portlet ...
                dsf sdf Newbie

                i have set JBossAS log4j level to debug and there is nothing in the 8MB server.log about my portlet 1. Not even the name.
                Whereas i can see the portlet B deployment logs...

                Can this problem be a JBossAS problem and not a portal problem ?

                • 5. Re: The curious case of the magical portlet ...
                  Peter Johnson Master

                  Login as admin and go to the Admin portal, the Admin tab.

                  a) On the Portlet Definitions tab, do both portlets show up?
                  b) On the Portlet Instances tab, do both portlet instances show up?
                  c) On the Portal Objects tab, dig down to the portal page and see if both portal objects show up.

                  • 6. Re: The curious case of the magical portlet ...
                    Prabhat Jha Master

                    On top of What Peter said, one thing I just noticed that your portletB setup has view recursive right for admin role while portletA setup has view recrusive right for user role. So consider that as well.

                    • 7. Re: The curious case of the magical portlet ...
                      dsf sdf Newbie

                      yes the roles defined are correct.

                      Actually i have solved one my two issues: the portletB / portletA problem.
                      It seems that portletB was not really correctly deployed, even if the portlet was displayed and behaved correctly.
                      There was a bean naming error in the spring applicationContext.
                      The strange thing is that portletB was correctly deployed, displayed and was fully functionnal. But it seems that this spring configuration error prevented the portletA from being deployed as it was the next portlet in the deployment order.
                      There was nothing in the server logs related to this error.

                      Well i now have one problem left, the real magical portlet, as this one is displayed if and only if it is the only one portlet in the portal.
                      It must be some kind of configuration problem too but the real pain is the total lack of log.
                      I can't understand why there is nothing in the server logs, even in debug mode.