This thread is probably best suited to [EMAIL PROTECTED] so excuse
the cross-posting.
The dependency of J2EE on J2SE is not an abstract one, there is a very real
engineering level linkage. It is true that the J2EE APM is taking a very
server centric view of the world. This was a deliberate decision since we
feel that J2EE has a great deal to offer in the specific area of the
impedance mismatch between the Web World and more traditional Enterprise
Computing Environments. As most developers know, there is no single answer
and there is no magic bullet that can possibly deal with all possible
application requirements. The J2EE APM is attempting to deal with clients
ranging from Cell Phones to Workstations. In actual fact, in the case of
the sample application, one could quite easily replace the Web Container
with a Swing client and have no impact on the business logic hosted in the
EJB container. I think that's really the point. J2EE makes it a lot easier
to transform a loosely coupled Web client into an Intranet client with a
much richer end-user interaction model. It's all a question of application
requirements. Hopefully, in an upcoming draft of the APM, we will do a
better job of clarifying the choices.
Regards,
Nicholas Kassem
At 06:05 PM 11/16/99 -0600, you wrote:
>I don't see the paradox. If you have an in-house app that doesn't need to do
>much on the client (say, an internal phone directory), then you use JSPs (or
>servlets). If you need to do more on the client (maybe like a simple admin
>program for the phone directory), then you include applets. If you *really*
>need to do more on the client (video editing, maybe), then you use a full
>blown application. It seems to me that the text you included just describes
>some of the options. As far as I can tell, the message is consistent: the
>best approach to enterprise development is to make your client application
>as thin as possible. J2EE helps facilitate this, while improvements in J2SE
>are designed to help you out when a fat client is your only option.
>
>KurtC
>
>-----Original Message-----
>From: Ron Yust [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, November 16, 1999 5:31 PM
>To: [EMAIL PROTECTED]
>Subject: J2SE and J2EE spin from Sun
>
>
>I'm confused. After reading Sun's J2EE Application Programming Model and
>listening to EJB experts on these newsgroups, I was under the impression
>that Java on the client was NOT the preferred method to deliver client GUI.
>But now on Sun's Java web page I find the following:
>
> _____
>
>Java technology running on the client, or desktop, has made dramatic
>improvements since the birth of the Java platform and is playing a key role
>in enterprises today, particularly in intranet and business-to-business
>applications.
>
>The biggest growth areas for Java technology on the client today are in
>business communications over intranets and the Internet. Major corporations
>are having great success developing and using client-based applets, which
>provide new services and functionality more quickly by avoiding the long
>development cycle of traditional programming languages.
>
>At the most basic level, the J2SE platform gives client-side users a wide
>range of features and capabilities that set it above alternative development
>languages:
>
>* Graphically rich user interface (vs. HTML)
>
>* Local data manipulation (vs. HTML)
>
>* Cross-platform compatibility (vs. ActiveX and C++)
>
>* Extreme security (vs. ActiveX)
>
>* Maintainable code (vs. JavaScriptTM)
>
>* Web deployed applications (vs. C++)
>
>From a broader perspective, the success and adoption of J2SE and continued
>innovation and improvements illustrate a more realistic picture of the state
>of the Java platform on the client: technologies such as the Java Plug-In,
>the Java HotSpotTM Client Virtual Machine, Java Foundation Classes, the Java
>Media Framework, and XML data integration are converging to enable
>enterprise customers to deliver mission-critical, client-side Java
>technology-based applets and applications, both on the Internet and in
>business-to-business e-commerce solutions.
>
> _____
>
>
>
>If I read this correctly, Sun says Java on the client provides advanced
>capabilities over HTML/JavaScript for (and I quote) "enterprise customers to
>deliver mission-critical, client-side Java technology-based applets and
>applications, both on the Internet and in business-to-business e-commerce
>solutions". So, on one hand Sun says Java provides superior client
>capabilities for the enterprise, but on the other hand the preferred
>enterprise client technology is HTML/JavaScript/Servlets/JSP. Does anyone
>else want to laugh?
>
>-Ron
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
