Amy:
Would not give up on JRun. It is a dramatic departure from JRun2.3 and thus the
increased difficulty. Would read the servlet spec 2.2 document (not that bad, really!)
which explains alot. Staying with JRun 2.3 may seem simpler at this point, but don't
think it is a viable long-term alternative as the servlet specification has moved
forward leaving JR 2.3 behind a bit.
JRun 3.0 is not intuitive but I think that is because the 2.2 spec is so different
from prior specifications. The enhancements you get (like application-specific session
settings, plug&play deployment of applications, etc...) has made our lives much easier
---- once we got used to the various JR3 and servlet 2.2 spec idiosyncracies.
There are some issues with the JMC and I would make manual changes when you can. Not
ideal, but I don't think the JMC is 100% bug-free at the moment --- although
administering (and restarting) remote servers through it is much easier than trying to
administer remote systems with the JRun 2.3 mechanism (telnet on UNIX versus ?applet
on Windows systems).
Again, I think 10minutes spent on reading the servlet 2.2 spec would go a long way in
making the transition smoother.
--Mike H
*********** REPLY SEPARATOR ***********
On 8/25/00 at 6:11 PM Amy Wan wrote:
>Problem again.
>
>I tried to edit (remove) the MIME-type of an JRUN Demo application.
>It doesn't take effect at all. THe Mime type I tried to remove stays there
>and stay in the local.properties file
>
>
>JRUN 3.0 is so hard to use (compare to JRun 2.3) and ...I am very
>disappointed.
>
>Amy
>
>
>
>
>------------------------------------------------------------------------------
>Archives: http://www.egroups.com/group/jrun-interest/
>Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
>or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
>body.
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebarRsts&bodyRsts/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.