[TAP5-2034] When the application operates with a context path, asset URLs are incorrectly formed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-core
• Labels: assets js rewrite
• Assignee: Howard Lewis Ship
• Reporter: Matías Blasi
• Created: 11/Dec/12 21:36
• Updated: 22/Dec/12 00:42
• Resolved: 21/Dec/12 23:57

Description

When trying 5.4-alpha-1 from 5.4-js-rewrite branch, I'm getting the following error when trying to browse a recently created webapp (with mvn archetype:generate)

bootstrap.css: comexassets/1.0-SNAPSHOT-DEV/meta/tapestry5/bootstrap_2_1_1/css

"comex" is my context root, and the assets folder is added with no slash separator.

Note: I started with a working tapestry-5.3.6 application, created with maven archetype plugin, and later I built tapestry-5.4-alpha-1 from sources, and updated the pom' dependencies.

I know that 5.4-alpha-1 is not stable, but I didn't find this issue in jira, I think that it is something to fix.

Regards,
Matías.

Issue Links

• is broken by: TAP5-1965 Replace use of Request.getContextPath() with a symbol defined at application startup