Jetspeed 2
  1. Jetspeed 2
  2. JS2-464

Redeployment of portlets that have services defined jetspeed-portlet.xml ARE NOT updating the JETSPEED_SERVICES table with new/altered values.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0-FINAL
    • Fix Version/s: 2.1-dev, 2.1
    • Component/s: Deployment
    • Labels:
      None

      Description

      I noticed this on one of my devlopment servers when re-deploying the full portal without wiping/recreating the database. The MultiColumnPortlet was failing to retrieve the "DecorationsFactory" service even though it was defined in the updated wersion of the jetspeed-portlet.xml deployment was not updating the JETPSEED_SERVICES table. This forced me to manually added the entry to the table.

        Activity

        Hide
        Jacek Wi?licki added a comment -

        Please, try to solve this problem. One of the most powerful functionalities of Jetspeed (i.e. services) become rather difficult to obtain with regular redeployments. I think that at least some note about this bug should be mentioned at http://portals.apache.org/jetspeed-2/multiproject/jetspeed-security/high-level-services.html.

        Show
        Jacek Wi?licki added a comment - Please, try to solve this problem. One of the most powerful functionalities of Jetspeed (i.e. services) become rather difficult to obtain with regular redeployments. I think that at least some note about this bug should be mentioned at http://portals.apache.org/jetspeed-2/multiproject/jetspeed-security/high-level-services.html .
        Hide
        Ate Douma added a comment -

        Bug confirmed.
        Currently, only portlet.xml is taken into account for changes.
        The solution isn't very difficult, but it requires an api change for FileSystemHelper and ChecksumHelper to fix.
        I don't have time for this the next few days, but will try to solve it soon after.

        Show
        Ate Douma added a comment - Bug confirmed. Currently, only portlet.xml is taken into account for changes. The solution isn't very difficult, but it requires an api change for FileSystemHelper and ChecksumHelper to fix. I don't have time for this the next few days, but will try to solve it soon after.
        Hide
        Ate Douma added a comment -

        Turned out I could solve this without api change.
        Well, I "cheated" of course by writing a new MultiFileChecksumHelper instead of modifying the (single file) ChecksumHelper class.

        Anyway, this issue is now fixed.

        And: not only is jetspeed-portlet.xml now properly checked, but I also throwed web.xml into the mix.
        As some registry info is retrieved from web.xml re-registration should also be done if those change.

        Please note: as the current checksum is stored in the database and this fix will lead to a completely different checksum,
        all existing deployed portlet applications will be re-registered once.

        Show
        Ate Douma added a comment - Turned out I could solve this without api change. Well, I "cheated" of course by writing a new MultiFileChecksumHelper instead of modifying the (single file) ChecksumHelper class. Anyway, this issue is now fixed. And: not only is jetspeed-portlet.xml now properly checked, but I also throwed web.xml into the mix. As some registry info is retrieved from web.xml re-registration should also be done if those change. Please note: as the current checksum is stored in the database and this fix will lead to a completely different checksum, all existing deployed portlet applications will be re-registered once.

          People

          • Assignee:
            Ate Douma
            Reporter:
            Scott T Weaver
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development