Yesterday, Sun made an early access version of Studio Creator (i.e., "Project
Rave") available. I downloaded it for both of my normal development platforms
(the SPARCle, running Solaris, and Windows) and gave it a go.
On first impressions, Creator is meant to be a Web application development
tool, from the looks of it. There's no mention of distributed APIs outside of
the servlet environment and web services, although Web services do seem to be
pretty deeply integrated. Further, the kind of Web applications it's designed
to create are, specifically, JSF applications.
This is good and bad. I'm not a proponent of JSF, yet, because I can see
horrible, horrible things from it. Sun apparently sees it as a competitor to
MS' WebForms, which to me sounds like they're trying to compete against
something that just isn't that good, in someone else's arena. However, it's
technol... (more)
I've been actively involved with Java development in one way or another since
1996, including working with some of the original issues of the servlet
specification, the early adaptation of the EJB spec, and migration to JSP not
long after it became an official part of the J2EE spec. I remember when Rick
Ross first sent his e-mails for Javalobby on Usenet; I remember playing with
the specs to discover if the grail was to be found in them as promised.
It hasn't come through for me. That's okay, because technology is and will
always be a moving target; I've refined what the grail is ... (more)
In my last editorial (Vol. 8, issue 6), I argued that we, as an industry,
have too much innovation. We have solutions pouring out our ears, stuff we
often don't need, yet we use it anyway. This month, I'd like to clarify that
somewhat: we need more innovation.
The seeds for innovation are already present: new projects are fertile
ground. The problems are often unique, so the solutions that present
themselves are individual as well. What's more, sometimes there's a better
solution that's simply waiting for the right viewpoint in order to become
obvious.
New solutions often imply... (more)
Two conversations over the past few days started a train of thought about
where Java is right now, as did the settlement between Microsoft and Sun, the
new JCP revision, and the new 1.5 JDK.
One conversation was with the author of a messaging system, talking about the
use of his SDK to create a simple grid or service-based system. In short,
what we talked about was a lightweight replacement for UDDI, with the
conversation points being that it's far easier to manage on many levels,
among other things.
Another conversation was with someone who was looking into some Java APIs
that... (more)
I am really coming around to Java Studio Creator. I spoke with Jim Inscore
from Sun today about it, after detailing my initial impressions on it, and we
spent some time discussing the product, its positioning, and its future role.
For one thing, he never called it "Rave," that I remember. I like the name
"Rave;" it's distinctive, it has a certain panache. That said, it's only a
code name for Sun, and lacks Sun's typical vanilla naming, so we have
"Creator," instead.
We talked about where Studio Creator fits in the developer landscape. Sun
places Studio Creator squarely in the cor... (more)
I am a software evangelist for GigaSpaces technologies, as well as a writer and musician. I've been the editor-in-chief of Java Developer's Journal and TheServerSide.
David Lucas
Cathy Lopez
Shaul Efraim
Terence Martin Breslin
Cory Marchand
David Hughes
James Carlini
John Iffert
Dan Stolts
Joe Zeto
Ulitzer content is offered under Creative Commons "Attribution Non-Commercial No Derivatives" License.
For any reuse or distribution, you must make clear to others the license terms of this work.
The best way to do this is with a link to this web page.
Any of the above conditions can be waived if you get written permission from Ulitzer, Inc., the copyright holder.
Nothing in this license impairs or restricts the author's moral rights.