I think this has to do something with url forwarding.
I have an apache mod_jk installed with a workers.properties that redirects all
traffic to jboss. The setting for this is:
I guess that themes are loaded by faces/struts (?) and that some internal url is not properly resolved. I say this as I noticed as well with this configuration that a login goes to //portal instead of going to /portal.
Somewhere in the link direction/templates things go wrong maybe?
Hmm, looking in my code though I do see:
, but no stylesheet gets loaded.
Actually also no images get loaded.
Have a look at http://www.jankester.com/portal
I have an apache mod_jk installed with a workers.properties that redirects all traffic to jboss. The setting for this is:
I think this is really just related to the jk connector. To see all the design stuff try adding
Furthermore your portal is titled "...2.0 Release Candidate",
whereas your cms fragment is labelled "...v2.0 Alpha Release". With my installation both titles refer to the same portal version - maybe this is another reason for some problems.
the URI thing solved the problem, so for my theme portal-core was not forwarded.
About the inconsistency of naming:
a few days ago I downloaded jboss-portal-2.0-RC2-jboss-4.0.2
Both my windows and my linux version have a file index_1.0.html here that contains the word "Alpha Release".
The index.jsp of portal-core/nodesk/ on the other hand has the word Release in it. Could it be there have been released more 2.0RC2 versions?