Community
Participate
Working Groups
Build Identifier: 20110615-0604 Holding ctrl and clicking at a declared custom tag-file in a jsp (or another tag-file) should open another jsp editor tab showing the tag-file source code. Instead, it opens a blank editor. That situation happens when: - The project references a tag-file which is inside META-INF/tags of an external jar in the project build path. - The project references a tag-file which is inside META-INF/tags of another java project in the main web project build path. Reproducible: Always Steps to Reproduce: 1. Add to a Web project build path an external jar (or another project) which contains a custom tag-file within META-INF/tags. 2. Create a jsp and declare that custom tag-file. 3. Hold ctrl and click at the declared tag-file. Should open a blank editor instead of showing the source code.
Created attachment 200748 [details] Patch to fix CMElementDeclarationImpl.setLocationString(String) from tag-files inside jar It seems when custom tag-files inside jar are loaded the location string defined at org.eclipse.jst.jsp.core.internal.contentmodel.tld.CMDocumentFactoryTLD:303 is wrong. This patch addresses this issue.
Created attachment 200749 [details] Patch to fix CMElementDeclarationImpl.setLocationString(String) from tag-files inside jar This patch was generated with my code formatter disabled. It seems when custom tag-files inside jar are loaded the location string defined at org.eclipse.jst.jsp.core.internal.contentmodel.tld.CMDocumentFactoryTLD:303 is wrong. This patch addresses this issue.
Good find, Andre. Thanks for the patch. I've released the changes.
(In reply to comment #3) > Good find, Andre. Thanks for the patch. I've released the changes. You're welcome!
