Another data point:
A lot of users who tried our preview bits (based on GFV3) were no
developers. So they are not OS and J2EE savvy. They just had the JRE
on their box and the errors displayed in the server.log were not clear
enough to describe how to fix it.
So by requiring a JDK, you are making it a bit difficult to create a
positive impression on non-developer kind of user who is using GFV3.
_raju
On 5/15/08, glassfish_at_javadesktop.org <glassfish_at_javadesktop.org> wrote:
> Thanks everyone for the insight into the JDK dependency.
>
> Usecase:
> I am attempting to create a standalone zip file that includes all the
> dependencies for my application. Thus I bundle the Appserver and its
> dependencies. The JRE is ~ 15MB and the JDK is ~67MB
>
> Solution:
> If GFV3 is designed such that features that require the JDK fail gracefully
> with messages when only a JRE is available, it will solve the above usecase.
>
> Tomcat 5.5 onwards will work with a JRE or a JDK.
> I feel getting the most commonly used features (JSP Compilation etc) to work
> with just the JRE will give feature parity with Tomcat. Having this feature
> will contribute towards greater adption to GFV3 IMHO.
>
> thanks,
> _raju
> [Message sent by forum member 'uppalapati' (uppalapati)]
>
> http://forums.java.net/jive/thread.jspa?messageID=274610
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>