I guess I've automatically always used private because only the JSP page
will use the method; there might be pros and cons relating to
weird-and-wonderful things such as visibility for inner classes etc. but
I've never thought too hard about it nor do I try and do to much in the JSP
code but instead try and break it out into other Java classes, however
sometimes I'll put little formatting routines in like this.

The import statement should still use the JSP page directive:

<%@ page import="..." %>

this will directly translate to import statements in the generated servlet
code,

HTH,
Joe

> -----Original Message-----
> From: Peter Barraud [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 24 April 2001 2:52 PM
> To: [EMAIL PROTECTED]
> Subject: Re: writing a function in JSP
>
>
> Thanx a lot, works perfectly, what I had missed was "!"
> but any idea what is the difference between declaring a
> function in jsp
> "private or public"
> Also I tried this import statement but the browser (IE) gives
> a huge error
> statement
> with the first line saying
> "org.apache.jasper.compiler.ParseException:
> C:\jsp\yourfile.jsp(0,4) Invalid
> directive"
> any idea will be most welcome
> thanx
> peter
[snip]

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to