[MGNLSD-91] Pre-compile/validate JSPs (but not including them in the bundle) Created: 05/Dec/06  Updated: 16/Sep/15  Resolved: 12/Dec/06

Status: Closed
Project: Sitedesigner (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.1

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1229 Pre-compile JSPs (but not including t... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Following MAGNOLIA-1229, the sitedesigner JSPs should be pre-compiled/validated. Unfortunately, the jspc plugin seems to be unable to see a tld defined in the current project at the moment (actually, it works if the tld is moved to WEB-INF/tld instead of META-INF but that's not an option)

Depending on http://jira.codehaus.org/browse/MJSPC-4 and http://jira.codehaus.org/browse/MJSPC-7 , we could either ... wait for a fix, or split sitedesigner so that the tags reside in their own specific artifact.



 Comments   
Comment by Magnolia International [ 11/Dec/06 ]

Tom, is there any reason you use the urn:jsptld:path notation in your JSPs ?
As per http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPX3.html , this notation is only valid when the tld file is in WEB-INF/tld. When its bundled in a jar, we should use the <uri> declared in said tld. I'm correcting this locally, and seems to help with precompilation/validation of the jsps. What do you think ?

Comment by Magnolia International [ 12/Dec/06 ]

done

Comment by Michael Mühlebach [ 16/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

Generated at Mon Feb 12 10:55:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.