|
Replies:
4
-
Last Post:
Sep 6, 2005 7:10 AM
by: kirillcool
|
|
|
|
|
|
|
|
Re: Mustang is too big (again)
Posted:
Sep 6, 2005 2:00 AM
in response to: netsql
|
|
|
I have had a few exceptions in corba packages when working with WebLogic with no authorization. If you don't work with CORBA directly, it doesn't mean core java classes don't.
|
|
|
|
|
|
|
|
|
Re: Mustang is too big (again)
Posted:
Sep 6, 2005 6:48 AM
in response to: kirillcool
|
|
|
WebLogic, excelent.
That means the corba can be moved to J2EE.jar. And for backwards compatibility into it's own jar.
What else to slim down Java?
.V
|
|
|
|
|
|
|
|
|
Re: Mustang is too big (again)
Posted:
Sep 6, 2005 7:04 AM
in response to: netsql
|
|
|
Very constructive...
I am talking about a client (running on J2SE) that connects to running WebLogic server and executes an EJB function. If you do not specify the security authentication provider, you will get an exception. It so happens that working with EJBs involves eventually using CORBA.
What is the JRE size that will satisfy your needs? What would you be willing to cut down on? Swing because it's ugly? SAX / DOM because everybody is said to use JDOM? How about AWT? Or JDBC? Or even the java.lang.Math class? Seems like no one uses hyperbolic trigonometry anymore. java.io package?
There's a third-party for everything. How many of those do you use? Do you count them with your application?
What's backward compatibility? Instead of installing full JRE, the user should install "core" JRE and additional JRE components (otherwise it's not really backward compatible). Anything to gain from breaking the JRE (except that you will not be able to count on anything to be present on the client machine)?
This discussion is so old... Just make peace with the fact that this will not happen. Not today, not tomorrow. Not while Sun develops it. Much like IE7 will not breaking existing corporate sites by supporting CSS standards. Too much money at stake.
I have a thing to slim down Java - don't use it. If your users are not satisfied with the download size, you have a choice - don't use Java. Use Flash, C++, C##, web applications. I don't think users mind that much.
|
|
|
|
|
|
|
|
|
Re: Mustang is too big (again)
Posted:
Sep 6, 2005 7:10 AM
in response to: netsql
|
|
|
About the link to "Java Puzzlers" review. Did you read the book? Does it say anything about the supposed "language bloat"? It says a lot about language semantics, and what could be done to improve it. May be I missed the item that ends with "That's why the language designers should have kept CORBA out"...
|
|
|
|
|
java.net RSS
