Jasper compilation of included files

[Dave Minter]

I'm trying to get Jasper to pre-compile my JSP pages. I've got an Ant
task (swiped from the manual) kicking this off, and it works pretty
well up to a point. However...

This application has a number of pages that are built out of JSP
fragments. Something like this:

!-- File A --
% String s = foo; %
%@ include file=B.jsp %

!-- File B --
% if( s.equalsIgnoreCase(FOO) ) { %
PFoo/P
% } %

Obviously file B isn't valid on its own - it has an undefined label
s. On the other hand, A is entirely valid.

I can't figure out a way to tell Jasper (via the Ant task) NOT to try
to compile B.jsp on its own, without making B unavailable as an
include to A.

Is there a way to do this? Alternatively is there a reason why I
shouldn't be doing this in the first place?

Thanks,

Dave.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jasper compilation of included files

[Tim Funk]

File A should *not* be called fileA.jsp. It should be called fileA.jspf
An  added advanatage is you know what what all your incoded fragment files 
are by looking at the file name.

-Tim
Dave Minter wrote:
I'm trying to get Jasper to pre-compile my JSP pages. I've got an Ant
task (swiped from the manual) kicking this off, and it works pretty
well up to a point. However...
This application has a number of pages that are built out of JSP
fragments. Something like this:
!-- File A --
% String s = foo; %
%@ include file=B.jsp %
!-- File B --
% if( s.equalsIgnoreCase(FOO) ) { %
PFoo/P
% } %
Obviously file B isn't valid on its own - it has an undefined label
s. On the other hand, A is entirely valid.
I can't figure out a way to tell Jasper (via the Ant task) NOT to try
to compile B.jsp on its own, without making B unavailable as an
include to A.
Is there a way to do this? Alternatively is there a reason why I
shouldn't be doing this in the first place?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jasper compilation of included files

[Michael Schuerig]

On Friday 15 October 2004 13:52, Dave Minter wrote:
 I'm trying to get Jasper to pre-compile my JSP pages. I've got an Ant
 task (swiped from the manual) kicking this off, and it works pretty
 well up to a point. However...

 This application has a number of pages that are built out of JSP
 fragments. Something like this:
[snipped]

 Obviously file B isn't valid on its own - it has an undefined label
 s. On the other hand, A is entirely valid.

 I can't figure out a way to tell Jasper (via the Ant task) NOT to try
 to compile B.jsp on its own, without making B unavailable as an
 include to A.

I've given JSP segments (fragments) a .jspf extension and that does the 
trick for me. See the spec JSP.1.1.8.

Michael

-- 
Michael Schuerig Nothing is as brilliantly adaptive
mailto:[EMAIL PROTECTED]   as selective stupidity.
http://www.schuerig.de/michael/--A.O. Rorty, The Deceptive Self

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jasper compilation of included files

[Dave Minter]

On Fri, 15 Oct 2004 14:11:54 +0200, Michael Schuerig
[EMAIL PROTECTED] wrote:
 On Friday 15 October 2004 13:52, Dave Minter wrote:
[snip]
 
 I've given JSP segments (fragments) a .jspf extension and that does the
 trick for me. See the spec JSP.1.1.8.
 
 Michael

And indeed that seems to work for me too. Thanks to Michael and Tim
for swift and effective responses.

Reference from the spec particularly appreciated as I like to know if
I'm doing things by the book or not.

Dave.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]