[maslovsky]

Hello,

I remember that an option was advertised some time ago in one of the pre-releases that it would be possible to configure JSP compilation on a per-file basis. I don’t see such option in 2.7 release.

I have a bunch of JSP files that are used as textual includes and they are not intended to be compiled standalone. They produce compilation errors if I turn on JSP compilation in myeclipse. So I have to keep this usefull feature disabled…

It will be realy nice to have JSP compilaiton user configurable – based on individual files, project folders and eclipse working sets.

Thanks!

[Riyad Kalla]

This is a common problem when dealing with includes, the solution per the JSP Spec is to name the includes “jspf” for JSP Fragment (or JSP Segment as they are called in the 2.0 spec). Files that are intended solely for the inclusion in other files should be named this way, this keeps them from being compiled stand-alone.

[maslovsky]

@support-rkalla wrote:

This is a common problem when dealing with includes, the solution per the JSP Spec is to name the includes “jspf” for JSP Fragment (or JSP Segment as they are called in the 2.0 spec). Files that are intended solely for the inclusion in other files should be named this way, this keeps them from being compiled stand-alone.

Thanks for the info, although I now have about 30 such files, which I have to rename, not mentioning fixinf all references in all other JSP files…

The feature I suggest would still be usefull, I think

[Riyad Kalla]

The feature I suggest would still be usefull, I think

We take all the user requests seriously and will consider it for a future release.

[Author]

Posts