[matmosis]

hi, i’m searching for a tool that automatically create a schema (like a tree) of all the JSP in a folder…

something that automatically reconize <%@ include file=”” %> tag and similar tags and create a visual strucure of all jsp dependency (like a parent – childs node’s)

thanx!

[Scott Anderson]

Sort of like the Java Hierarchy View functionality?

[rogue_dev]

I would add my vote to this.

Having such a schema would also allow you (MyEclipse) to eliminate false-positive error messages. Since you now know that a JSP fragment is included by the main JSP, you would also know that the object which the fragment uses has been instantiated by the main JSP.

[arjan.tijms]

Of course, it’s not -that- simple: a JSP fragment can be included by multiple other JSP’s, and each context can potentially give different warnings. Nevertheless, it would be a huge advantage to have a feature like this.

Something that was proposed long ago (but never implemented) was to set a “default” context for a fragment. That is, a user would select any JSP that included the fragment as a default JSP for that particular fragment. After that, all validation would be performed in the context of that choice.

[rogue_dev]

Well it could be that simple.

The error messages would not appear in the fragment, but rather in the JSP which includes the fragment. Something along the lines of “The JSP fragment requires that the object java.util.Calendar be imported”, or “The JSP fragment requires that the object com.company.Data” be instantiatied”, and so on.

So while the error would actually occur in the fragment (during compile), the actual fault lies with the JSP which includes the fragment.

[Author]

Posts