Provide a full path to your classes in the CLASSPATH variable when starting the
server. If you are running the batch file provided with the implementation,
modify it and include paths to your packages. We've been using our locally
developed classes and it works for us just fine.
Primoz
> C Kruppa wrote:
>
> Hey guys,
>
> The import statements that are in the code of my Bean (not the JSP) are
> failing because JSWDK can't find the classes. I'm wondering where I am
> supposed to put the classes that the Bean is looking for? Or how to
> configure the server to know where to look for them? Specifically, the
> classes I need to import are XML parsers and not part of the Java API, so it
> is not an issue of having my "JAVAHOME" directory specified in the
> CLASSPATH. That is done correctly. I even resorted to copying the whole
> packages into the same directory as the Bean, and that didn't work either.
> Thanks for any help somebody can offer.
>
> Carrie Beth
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
