Does anyone know how to apply this "fix" to WebSphere. Probably the two
most annoying things about JSP IMO are:
1) New beans (i.e. non servlet classes) added to WebSphere's
ncf.jvm.classpath (in jvm.properties) require a web server restart to be
detected, and
2) New JSP files that are invoked via CallPage from a servlet require a web
server restart to be re-page compiled (JSP files called directly do not).
Dan
> ----------
> From: Weiner, Sam[SMTP:[EMAIL PROTECTED]]
> Reply To: Weiner, Sam
> Sent: Wednesday, March 31, 1999 5:45 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Dynamic loading of beans
>
> I had the same problem using GNUJSP - I presume the solution will be
> applicable to your situation as well.
>
> The problem is, from what I can tell, that JSP uses different sources for
> it's CLASSPATH information between run-time and compile time.
>
> It's documented that the effect of including your beans path in the
> servlet
> engine level classpath (called wrapper.classpath in GNUJSP) is to allow
> your
> beans to run within any JSP page, but with the downside being that the
> beans
> aren't dynamically reloaded when they change. If you include the classpath
> in the servlet repository's properties file instead, the class loader for
> the servlet takes care of re-loading the bean.
>
> The problem you then run into, and I didn't see this well documented, is
> that the JSP pages no longer compile - as you point out.
>
> The fix I found is to not only add the beans path to the properties file
> (e.g. repositories=[BEANSPATH]), but to change the JSP compiler parameters
> to include the beans path (e.g.
> servlet.gnujsp.initArgs=compiler=builtin-javac -classpath
> %classpath%:%repository%:[BEANSPATH] -d %repository% -deprecation
> %source%.
>
> The documentation suggests that an alternative way to do this is to create
> an init parameter %beanspath% and insert this into the compiler arguments,
> but I couldn't get this to work.
>
> Hope this helps!
>
> Sam Weiner
>
> ----------
> From: S. N. Prasanna[SMTP:[EMAIL PROTECTED]]
> Reply To: S. N. Prasanna
> Sent: Wednesday, March 31, 1999 4:40 AM
> To: [EMAIL PROTECTED]
> Subject: Dynamic loading of beans
>
> Hi,
>
> I am developing an application using JSP. My environment is
> NT4.0
> Service pack 4, IIS-4.0, Jrun 2.3.
> I am putting all the classes created by me including JSP beans in
> a
> package
> named "myClasses" under
> C:\jrun\classes directory, which is in the class path. The
> problem
> is these
> classes are not loaded dynamically. What can I do to make these
> classes
> especially JSP beans to load dynamically. If I put them in
> servlets
> directory JSP page compiler gives me error : "class jsp.classname"
> is not
> found. If I put beans in class path and every time I make some
> changes to
> the bean( which is common at the time of development) I have to
> shut down
> and restart the server to make changes to take effect.
> recompilation
> of JSP
> also doesn't help.
>
> Is there any way by which I can force the JSP to load/compile
> changed beans
> dynamically.
>
> Thanks in advance
> Prasanna
>
>
> ==========================================================================
> =
> 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".
>
> ==========================================================================
> =
> 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".
>
===========================================================================
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".
