Community
Participate
Working Groups
Let me know if this is functionality provided by IBM only for Rational Application Developer but it would be nice to have this functionality built into Eclipse. We have JSPs that include other JSPs or JSPs that include JSP fragment. If you change the included JSP or JSP fragment, you need to manually find the JSP that includes it and update it so the page will be refreshed. Also it would be nice to be in the included JSP or JSPf and launch the enclosing JSP in the editor. Another issue is that if a taglib is included in the 1 JSP, the tags from that taglib are not recognized in the include JSP or JSPf.
This looks like it might for you folks...
We will be looking to improve this in future releases (some of what you describe should work in WTP 1.5) ... but often I've found some of this issues can be divided up into many many special cases. So, if you have/come up with special cases, do not hesitate to document more detailed uses cases (and some indication of priority for you and yours :)
In my case, the architecture is as follows - content is stored in one JSP and code is in an included JSP or JSPF. Content changes more frequently and these changes are picked up by the server automatically as long as they are not in the included JSP or JSPF. Functionality that would be helpful: 1. If included JSP or JSPF is updated, refresh the page on the server. Right now, we have to find the including JSP in the Navigator view or in Windows Explorer and add a space to it or touch it to get the page to update. 2. If in the editor for the included JSP or JSPF, add the ability to launch the including JSP in the editor. 3. Content Assist in the included JSP or JSPF with tags in custom taglibs. Right now, content assist for these tags works in the including JSP but not the included JSP/JSPF. Custom tags in the included JSP/JSPF come up with warnings of IWAK0054E - unknown tag.
Related bugs: bug 147098 bug 155664 bug 157465 bug 155664
reassigning to inbox
This is indeed a tricky issue, parent pages know which child pages they include but not the other way around. Providing content assist based on tag-libs in "parent" JSPs in a "child" JSP is an iffy thing because depending on which "parent" JSP it is included in it may have access to different libraries. Though it is possible some of these situations could be improved, like the server case.
*** Bug 224117 has been marked as a duplicate of this bug. ***
