Ethan Henry wrote:
> Hi,
>
> Michael Rumpf wrote:
> >
> > Read the FAQ !
> >
> > It is an error in the JSWDK implementation, it must be spelled "imports"
> > instead of "import".
>
> FAQ or no FAQ, it's a bug. They should change the specification or the
> implementation then because they don't ma
Use
<%@ page imports="java.util.*" %>
instead of
<%@ page langage="java" import="java.util.*" %>
===
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general
Philippe wrote:
>
> <%@ page langage="java" import="java.util.*" %>
>
If you are using the JSWDK-1.0-EA version that was released in June, it had a bug and
recognized the word
"imports" instead of "import". I presume this has been fixed in the JSWDK 1.0 release
that was posted on
JavaSoft's w
Hi,
Michael Rumpf wrote:
>
> Read the FAQ !
>
> It is an error in the JSWDK implementation, it must be spelled "imports"
> instead of "import".
FAQ or no FAQ, it's a bug. They should change the specification or the
implementation then because they don't match. Thanks for the pointer though.
Eth
Philippe wrote:
>
> I have installed the last version of jsp 1.0 reference implementation
> from sun (jswdk-1.0-ea) and I'm experimenting some problems with the
> import attribute in the page directive (I'm using jdk1.2.2) . It seems
> the import attribute is not interpreted during the compilation
I have installed the last version of jsp 1.0 reference implementation
from sun (jswdk-1.0-ea) and I'm experimenting some problems with the
import attribute in the page directive (I'm using jdk1.2.2) . It seems
the import attribute is not interpreted during the compilation of the
jsp page.
for exa
