I am trying to use the client deployer. Our JSP pages use a number of compile time 
includes such as "<%@ include
file="someCommonCode1.jsp" %>".

The client deployer is trying to compile each of these included files independently. I 
am getting compile errors all over the place.

The reason is that one include will imports a profiling package that some of the other 
includes depend upon.

The deployer is trying to compile each ".jsp" file as a complete page.

Is there another approach for handling compile time includes that will avoid this 
problem?

Is there a way to designate jsp files that should not be compiled independently?

Thanks in advance - Richard



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

Reply via email to