[MAGNOLIA-642] The tree structures and links don't work well with websphere App server 6.0 Created: 16/Feb/06  Updated: 23/Jan/13  Resolved: 01/Mar/06

Status: Closed
Project: Magnolia
Component/s: build
Affects Version/s: 2.1.3
Fix Version/s: 3.0 Beta 1

Type: Bug Priority: Major
Reporter: J2EE Assignee: Boris Kraft
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Websphere 6.0
Magnolia 2.1.3 and above


Attachments: File admincentral.jsp    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Websphere 6 has the ${pageContext.request.context} value unprocessed in the URL.
And that makes the request fail and results in 404 error page being displayed when you click any of the buttons in the adminCentral.

Is it a must that you use that kind of way to resolve URL

Would n't it be okay to get rid of the whole thing ${} alltogether and have it referenced path relative to / which works.

Any fixes?



 Comments   
Comment by Jay Moskos [ 17/Feb/06 ]

Can we reassess the priority of this bug? I believe it to be a Blocker because you can not do any development from the Magnolia author instance. Am I incorrect in my logic?

Comment by Jay Moskos [ 18/Feb/06 ]

the problem line is in /admintemplates/js/admincentral.jsp:

<%@ page contentType="text/javascript; charset=utf-8" %>

var contextPath = '${pageContext.request.contextPath}'; <--------- problem line

<!-- debug -->
<%@ include file="../../admindocroot/js/debug.js" %>

...

For some reason "${pageContext.request.contextPath}" isn't getting replaced in WebSphere 6 before it gets used by admincentral.js later on.

Comment by Jay Moskos [ 18/Feb/06 ]

Here is a patch that should work.

or simply replace:

var contextPath = '${pageContext.request.contextPath}';

with:

var contextPath = '<%= request.getContextPath() %>';

Comment by Philipp Bracher [ 01/Mar/06 ]

I commited this line. Perhaps it makes problems in combination with the old (not jspx) syntax.

What I'm wondering is if it works for you in the sample templates. Can you see the header image? Because there we use the same syntax but combined with jspx.

Generated at Mon Feb 12 03:19:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.