CODEWITHSUNDEEP
websphere-liberty
AmitM
AmitM

Reputation: 101

WAS Liberty not serving images, css, js

I have an application which is working fine on Websphere server (as war and Eclipse Project). Direct deploy on Liberty through WAR is also working fine.

I was trying to deploy it on WAS Liberty through Eclipse project. There are no console errors but once the application loads, none of the following files are getting loaded in the web page: js, gif, css

Because of this the page is looking distorted and most of the functionality is lost. Surprisingly there are some JSPs in the js folder and these are getting loaded, so looks like the folders are published properly. But for all the mentioned files (js etc), I get following error in the browser console: 500 (Internal Server Error) . There are no errors and the server log is also clean.

My setup: WAS Liberty 8.5, RHEL 6.5. Eclipse Luna, WDT 8.5.5.2. Project having Eclipse structure, not maven. I have tried both loose config and 'from workspace' settings

Edit1: I noticed that Spring beans are not getting initialized properly. Getting null pointer on applicationContext.getBean.

Upvotes: 0

Views: 2148

Answers (2)

JGarnica
JGarnica

Reputation: 228

I am facing the same issue using open liberty and Eclipse Krazo when the base path is 

application path (“/”)

so i have changed the path as shown below

package io.openliberty.sample;

import javax.ws.rs.ApplicationPath;
import javax.ws.rs.core.Application;

@ApplicationPath("")
public class ConfigApplication extends Application {
}

Now the CSS and imgs are loading with no issues.

Upvotes: 0

AmitM
AmitM

Reputation: 101

OK, found the problem.

As I guessed this was related to spring initialization, though the problem was more code related.

Due to wrong implementation of REST implementation, where the base path was set as root application path (“/”), rest API classes were getting instantiated on application load and were then making calls to code which was instantiating few Spring beans. But at this point the Spring listeners had not fired, hence the appcontext was empty. Some of the base application object were getting initialized with empty beans and hence spring security context and related classes were failing to serve the application content properly. (Problem is spring related code is created by another team and we just get the jar, hence I am not even able to debug it properly, so I don't know where it was failing exactly)

The thing that makes it Liberty specific is: The same problematic code is working fine on Websphere full profile and Weblogic and even on Liberty if we deploy as WAR. Not sure what classloading difference is causing difference in behaviour.

Thanks to all who took time and efforts for replying.

Upvotes: 1

Related Questions