Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

SASS is not working on Weblogic

Description

The following change in portal.properties:

set A

to set B

causes Weblogic 10.3.2 to fail on SASS jruby execution, giving the following exception:

Visually, this issue is represented as lack of CSS styles.

Environment

Weblogic 10.3.2.

Activity

Show:

Michael Saechang July 23, 2012 at 4:30 PM

Committed on:
Portal 6.1.x CE GIT ID: dd7461fa6a0138b914aa410a9974b53dd7ecf035.
Portal 6.2.x GIT ID: 3b7459650b7b26fc62d07a97c429c7ea2de65485.

Brian Chan July 20, 2012 at 11:25 AM

I changed the logic a bit in:

b4c9c345164a95e002494ddeaba6a84e57ab03cd

It'll now extract it to the temp dir.

Igor Spasic July 19, 2012 at 7:20 AM
Edited

The solution will be the set C:

we will extract the contenct of jruby-gems.jar to ${liferay.home}/ruby; this way it will be available to all application servers and there will be no issues in accessing liferay.home.

Igor Spasic July 18, 2012 at 2:05 AM

When I test weblogic with the set A everything works.

Igor Spasic July 18, 2012 at 2:01 AM
Edited

This is a regression issue as we had similar problem before.

The above change happened in the . I believe that the cause is what has been described in : Weblogic classloader (ChangeAwareClassLoader) returns differently formatted URL. Because of that the class path in exception is wrong:

Note the '/C/' part in the path - it is non existent and probably should be '/ruby-gems.jar/'.

Fixed

Details

Assignee

Reporter

Branch Version/s

6.1.x

Backported to Branch

Committed

Fix Priority

5

Git Pull Request

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created July 18, 2012 at 1:51 AM
Updated June 24, 2023 at 3:50 PM
Resolved July 20, 2012 at 10:06 AM
Loading...