We have an application that was originally started using Glassfish 4.0 using JSF2.2 and Primefaces 6.1 and everything worked exactly as we intended it to until it was decided that we would be moving to Weblogic 12.2.1.2. Since the application has been moved all of the navigation, EJBs, etc all work just as before but the primefaces UI is completely out of whack. None of the styling is there anymore even after making sure the resources directory was defined properly in the web.xml. I know this is a pretty vague question but I was hoping that someone had experienced a similar problem and found a solution.
Asked
Active
Viewed 83 times
0
-
What did you **debug**. If the PF components look bad it is a css related thing. 404's? security filters? considering an edit by BalusC in a related topic https://stackoverflow.com/questions/8480100/how-implement-a-login-filter-in-jsf I suspect something in this direction. But that should be easy to debug by you... – Kukeltje Sep 21 '17 at 21:02
-
That's the main problem there are no errors anywhere to debug but like you said it does look like the CSS is not being loaded as it should, just haven't figured out why yet. – ChadNC Sep 25 '17 at 13:14
-
Checking if the css files are not loaded is easy... Network tab should contain 404's then (or other 'errors') – Kukeltje Sep 25 '17 at 13:15
-
After a little more digging I have found a log message that could be the culprit. "
" If this is the problem I'm unsure as to why it happens on Weblogic 12.2.1 and not on glassfish 4.x. -
I doubt it is the reason. It is a jsf issue, then plain jsf would not work either. – Kukeltje Sep 25 '17 at 14:13
-
So it seems that then using the Weblogic 12.2.1.3 developer installation if you use an IP instead of localhost when configuring the domain this problem arises, weird. Tried a domain both ways several times and each time I use an IP instead of localhost when configuring this problem comes up so localhost it is. Thanks for the input. – ChadNC Sep 27 '17 at 17:25