Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-13880

Extlet deploy fail because "Global lib directory" is empty

    Details

    • Branch Version/s:
      6.0.x, 5.2.x, 5.1.x
    • Backported to Branch:
      Committed
    • Liferay Contributor's Agreement:
      Accept

      Description

      Extlet deploy fail because Liferay is unable to detect "Global lib directory".

      During the portal startup, into PortalImpl, Liferay try to detect the global lib directory asking to the application server where it have loaded portal-service.jar.

      As Katsuyuki Ohmuro state in LPS-11643, JBoss doesn't use the "!" to delimit the boundary between the jar and jar contents in vfszip URLs.

      To undestand what I mean, we can look how the application server inform which system.properties has loaded.

      In tomcat, for example, this is the line into the log about system.properties

      ....liferay-portal-6.0.5/tomcat-6.0.26/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/system.properties

      In JBoss the same info appear without !

      ..../jboss-5.10.GA/server/all/deploy/ROOT.war/WEB_INF/lib/portal-impl.jar/system.properties

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  8 years, 49 weeks, 5 days ago

                  Packages

                  Version Package
                  --Sprint - SP
                  6.1.0 CE RC1