Re: Question regarding security of delivered jsp's.

[Raymond Ko <raymond@isquare.com.hk>]

Hoffman,

Though I didn't deliver a solutions on JSP yet, but I did that in ASP
(don't fame me). What I did is to leave all the HTML generated stuff in ASP
while keeping the business logic in 'components' written in Java. This
practice can be applied to JSP solutions. Keeping the layout in JSP for
flexbility, but encasuplate the business logic in Bean.

Raymond

At 09:18 AM 2/10/99 -0700, Joe Hoffman wrote:
>How can I deliver runnable JSP's to my customers without extending them
>the ability to edit/change the JSP content?
>
>One suggested idea is to have a switch (I"m not sure where) that
>indicates that only generated .class files should be used, and thus not
>look for .jsp files.   Therefore I would only have to deliver the
>contents of the generated directory (apache).     Maybe there is a way
>to extend this idea somehow and just deliver a jar file that contains
>all my generated class files.
>
>Has anyone thought of this issue and are there any good/proposed
>solutions?
>
>regards
>
>joe hoffman
>Harland Corp.
>Denver, CO
>
>