New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JS/CSS files not loaded on JBoss #9

Closed
glucazeau opened this Issue Dec 3, 2015 · 8 comments

Comments

Projects
None yet
3 participants
@glucazeau

glucazeau commented Dec 3, 2015

Hello,

I have installed Sling 7 webapp on JBoss EAP 6.4.0
I've deployed Composum 1.3.0 but when I go to this page: http://192.168.75.201:8080/sling/bin/browser.html

I see only HTML elements (forms), but JS and CSS files are not loaded. In the Sling logs I see this error:

03.12.2015 15:12:39.127 *INFO* [http-/0.0.0.0:8080-2] logs/request.log 03/Dec/2015:15:12:39 +0100 [1652] -> GET /sling/bin/browser.html HTTP/1.1 03.12.2015 15:12:39.146 *ERROR* [10.129.201.66 [1449151959129] GET /sling/bin/browser.html HTTP/1.1] org.apache.sling.scripting.jsp.jasper.runtime.JspFactoryImpl Exception initializing page context java.lang.IllegalStateException: JBWEB000043: Cannot create a session after the response has been committed at org.apache.catalina.connector.Request.doGetSession(Request.java:2649) at org.apache.catalina.connector.Request.getSession(Request.java:2382) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:791) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:801)

How can I fix this issue? I've tried version 1.3.1 but it doesn't start because of a wrong bundle version:
missing requirement [121.1] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.8.0)(!(version>=2.0.0)))

Thank you

@ist-rw

This comment has been minimized.

Show comment
Hide comment
@ist-rw

ist-rw Dec 7, 2015

Member

The new Bugfix Release 1.3.2 should solve the bundle version problem. The other problem is mostly a result of insufficient permissions of the current user (of the anonymous user); to handle this a check is added and delivered with release 1.3.2 which displays a simple login form if the initialization is not done properly. To use the console app read access to the paths '/libs/composum' and '/libs/jslibs' is needed.

Member

ist-rw commented Dec 7, 2015

The new Bugfix Release 1.3.2 should solve the bundle version problem. The other problem is mostly a result of insufficient permissions of the current user (of the anonymous user); to handle this a check is added and delivered with release 1.3.2 which displays a simple login form if the initialization is not done properly. To use the console app read access to the paths '/libs/composum' and '/libs/jslibs' is needed.

@ist-rw ist-rw added the bug label Dec 9, 2015

@ist-rw

This comment has been minimized.

Show comment
Hide comment
@ist-rw

ist-rw Dec 15, 2015

Member

@glucazeau Are the changes with release 1.3.2 solving your problem or is there anything open?

Member

ist-rw commented Dec 15, 2015

@glucazeau Are the changes with release 1.3.2 solving your problem or is there anything open?

@glucazeau

This comment has been minimized.

Show comment
Hide comment
@glucazeau

glucazeau Dec 15, 2015

Hello,

Sorry I've tested quickly and didn't respond immediately.

No it doesn't seem to solve my problem. First, the login form action is "/j_security_check" so it's missing the context name.

I've edited the source to add "/sling" and when submitting the form with admin credentials (default from Sling install) I'm redirected to "http://localhost:8080/sling/index.html/" with a 403 error. If I go to browser.html again I briefly see the page without assets and then I'm redirected to the login form, displaying:

Console assets not accessible...
Current User: admin

Do I have to manually edit ACLs or should the admin user work already?

glucazeau commented Dec 15, 2015

Hello,

Sorry I've tested quickly and didn't respond immediately.

No it doesn't seem to solve my problem. First, the login form action is "/j_security_check" so it's missing the context name.

I've edited the source to add "/sling" and when submitting the form with admin credentials (default from Sling install) I'm redirected to "http://localhost:8080/sling/index.html/" with a 403 error. If I go to browser.html again I briefly see the page without assets and then I'm redirected to the login form, displaying:

Console assets not accessible...
Current User: admin

Do I have to manually edit ACLs or should the admin user work already?

@glucazeau

This comment has been minimized.

Show comment
Hide comment
@glucazeau

glucazeau Dec 17, 2015

I also realize that using the Sling standalone launchpad I can log in and use Composum as an anonymous user. The problem only occurs with JBoss.

glucazeau commented Dec 17, 2015

I also realize that using the Sling standalone launchpad I can log in and use Composum as an anonymous user. The problem only occurs with JBoss.

@ist-rw

This comment has been minimized.

Show comment
Hide comment
@ist-rw

ist-rw Dec 17, 2015

Member

I think we have a general gap in our implementation - we don't support a context path; if such a path is configured for the Http-Service of the standalone application all the symptoms are reproducible. In the JBoss context such a context path is essential and we must solve this problem. But it's a bigger change with some test effort and we take a little bit of time to do that, sorry.

Member

ist-rw commented Dec 17, 2015

I think we have a general gap in our implementation - we don't support a context path; if such a path is configured for the Http-Service of the standalone application all the symptoms are reproducible. In the JBoss context such a context path is essential and we must solve this problem. But it's a bigger change with some test effort and we take a little bit of time to do that, sorry.

ist-rw added a commit that referenced this issue Dec 28, 2015

ist-rw added a commit that referenced this issue Dec 29, 2015

Merge branch 'issue/#9-JS-CSS-files-not-loaded' into change/detail-view
# Conflicts:
#	sling/core/console/src/main/resources/root/libs/composum/sling/console/browser/js/browser.js
#	sling/core/console/src/main/resources/root/libs/composum/sling/console/browser/js/nodeview.js
#	sling/core/console/src/main/resources/root/libs/composum/sling/console/browser/js/properties.js
#	sling/core/console/src/main/resources/root/libs/composum/sling/console/browser/js/version.js

ist-rw added a commit that referenced this issue Dec 29, 2015

drere added a commit that referenced this issue Jan 4, 2016

drere added a commit that referenced this issue Jan 5, 2016

drere added a commit that referenced this issue Jan 5, 2016

drere added a commit that referenced this issue Jan 5, 2016

drere added a commit that referenced this issue Jan 5, 2016

drere added a commit that referenced this issue Jan 5, 2016

@glucazeau

This comment has been minimized.

Show comment
Hide comment
@glucazeau

glucazeau Jan 6, 2016

Thank you for working on this issue, Composum is a very nice tool that I'd like to be able to use in JBoss. No need to be sorry about the time required to implement the changes. Unfortunately I'm too new to Sling to be able to really help I think.

glucazeau commented Jan 6, 2016

Thank you for working on this issue, Composum is a very nice tool that I'd like to be able to use in JBoss. No need to be sorry about the time required to implement the changes. Unfortunately I'm too new to Sling to be able to really help I think.

@mzeibig mzeibig added this to the release-1.3.3 milestone Feb 5, 2016

@ist-rw

This comment has been minimized.

Show comment
Hide comment
@ist-rw

ist-rw Feb 8, 2016

Member

@glucazeau This issue should be solved with release 1.3.3 (the current master also), can you recheck this?

Member

ist-rw commented Feb 8, 2016

@glucazeau This issue should be solved with release 1.3.3 (the current master also), can you recheck this?

@ist-rw ist-rw closed this Feb 8, 2016

@glucazeau

This comment has been minimized.

Show comment
Hide comment
@glucazeau

glucazeau Feb 8, 2016

Hello,

I was actually testing, it works well, I can access everything, anonymous or not, I don't see any issue.

Thank you very much for the quick fix, I'm very glad to have Composum on our JBoss environment 👍

glucazeau commented Feb 8, 2016

Hello,

I was actually testing, it works well, I can access everything, anonymous or not, I don't see any issue.

Thank you very much for the quick fix, I'm very glad to have Composum on our JBoss environment 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment