Welcome!

Java Authors: Jerry Melnick, Elizabeth White, Liz McMillan, Andreas Grabner, Tim Hinds

Related Topics: Java

Java: Article

Java Viewpoint: "I'm Starting to Like Java Studio Creator..."

Studio Creator focuses on development tasks

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 corporate developer's arena. To understand this, he said that one of the most common development tasks in Java yielded a small, one-off, pragmatic web application - not an n-tiered, scalable monster enterprise application. Developers who create things like this don't spend a lot of time mastering Struts, or EJB, or much of the other J2EE APIs. They're looking at pragmatism in programming, more than structural elegance - just "get it done," rather than "do it correctly." They're the rank and file. (If you're one of these people, don't take it as an insult - you're where the tire hits the road for Java.) The API isn't important, here: the task is. Using available resources is more important than making resources available.

Contrast that group with the more technical set - the technologists and the architects. Both of these groups tend to focus on the APIs, where doing it correctly is more important than timeliness. These people will be more of the ISO crowd, the elitists and eggheads. These groups would rather write a framework, or use an acronym API, than just talk to a database and render via JSP. While these groups will (usually) yield a more scalable application, it typically takes much longer simply because they spend more time on infrastructure than application.

The latter groups want an IDE like JBuilder, Eclipse, IDEA, or NetBeans; something that helps them write code. The corporate developers tend not to care about code; they want something that helps them write applications. If they can get away with writing absolutely no code, that's fine. (Yes, I know, I'm generalizing. Many corporate developers enjoy writing code, and some technologists would rather stay away from it.)

Studio Creator is aimed squarely at the corporate developer, meaning that it's got the primary goal of enabling component reuse, whether it's a JSF component or a web service. Pre-packaged elements are king, here; think about the impact component development had for Visual Basic. This is something Java has been looking for for a long time, and I think it's finally coming around, with a product geared for component inclusion (JSF), and an IDE designed from the ground up to use component-based development.

JSF is still in its infancy, to be sure. I've not been circumspect with my own doubts about the technology, which I feel would be far too easy to abuse. However, most infants grow over time, hopefully into functioning adults; JSF's lifecycle surely has the same potential. As a new technology, its pitfalls are still being discovered and it's certainly improving.

Studio Creator actually helps that along, by encouraging usage of JSF in ways that don't expose its weaknesses. Because it still gives developers the ability to see raw code, it also allows coders to use every feature JSF provides, which will help JSF itself improve.

Creator, too, is still new. I found a lot of small things that didn't seem intuitive: absolute positioning on the pages, package structures seem underexposed, and the snippets feature looked like a bit of an afterthought. More critically, Studio Creator feels limiting. I'm personally comfortable with leveraging the J2EE stack, and Studio Creator, with its drag-and-drop approach, seems to discourage me from really working with projects in the ways I'm familiar with.

That's all right. Mr. Inscore pointed out that Studio Creator is only in pre-release, and he detailed some features that they wanted in future releases, such as being able to create rich desktop applications and mobile applications, leveraging EJB components, publication of web services (as opposed to simply using existing services) and others. As far as my personal preferences working with Studio Creator is concerned, there are a few reasons that my response is appropriate as well. I tend to fall outside the target market for Studio Creator, and even so, I find that I might end up relying on it for more pragmatic projects - because, psychologically speaking, having choices tends to be empowering, but having an incredible array of choices is actually a source of frustration. (See The Tyranny of Choice, by Barry Schwartz, published in Scientific American, April 2004 issue.) From that vantage, Studio Creator - by providing a straight line implementation choice instead of leaving the developer to decide whether to use Velocity, FreeMarker, JSP, or Cocoon... with Struts, Tapestry, WebWork, or raw servlets... with EJB, JDO, Hibernate... and let's not forget the array of testing possibilities.

Altogether, Studio Creator is workable. It's not good yet, but its prerelease status makes that acceptable. Furthermore, Sun is expecting it to help supercharge the reusable component market that the Java community hasn't quite leveraged yet, if only by focusing attention on the components instead of the tools that use them. It's a very focused product, and in my opinion, it's focused well. I'm looking forward to final releases, as well as the competition other vendors offer it.

More Stories By Joseph Ottinger

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.

GigaSpaces Technologies is a leading provider of a new generation of application platforms for Java and .Net environments that offer an alternative to traditional application-servers. The company's eXtreme Application Platform (XAP) is a high-end application server, designed to meet the most demanding business requirements in a cost-effective manner. It is the only product that provides a complete middleware solution on a single, scalable platform. XAP is trusted by Fortune 100 companies, which leverage it as a strategic solution that enhances efficiency and agility across the IT organization.

Comments (4) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Bob Campbell 04/26/04 09:38:47 AM EDT

All I can say is about time. I''m one of those corporate developers who''s been lost far too much sleep over frameworks, methodolgies, lanaguages, open source, close source and the like. I don''t have time to learn Struts, I don''t care what an EJB is, I don''t want another application server and I definitely don''t need more choice. If what you say is true, I will bow to the Sun God and open my wallet.

Darryl Thompson 04/24/04 11:59:03 PM EDT

I was really excited about project Rave, and when I got my beta copy of Creator I was excited until I discovered I could not import and extend my existing JSF apps (hand-rolled using Beta 1.0 and later migrated to 1.0 FCS). The reason why is because Creator uses XHTML and CSS-P to provide the visual drag/drop and placement functionality. I like the drag and drop concept but not at the expense of lost backward compatibility. It seems that I cannot use regular JSP web apps or even JSF apps if they use html table placement for layout management. But all is not lost; Exadel JSF Studio provides what to me is the best of both worlds. JSF STudio provides JSF drag/drop design (at the code level) and its backwards-compatible with JSF apps written by hand using HTML table layout, and what''s more it seamlessly plugs into the Eclipse IDE. What''s more its provides the same code-level drag/drop functinality for JSTL and any Custom JSP Taglibs rolled by the IDE user. So, for now I am passing on Creator and going with JSF Studio, but I will keep an eye on Creator and see how it looks after maturing in a year or two.

Joseph Ottinger 04/24/04 10:29:09 AM EDT

Mr. Pardi, they sure did! While they don''t have the full process in place, one of their prime goals with Studio Creator is the fostering and support of a component marketplace. If you''d send me your email address (to josephottinger@sys-con.com), I can forward that and your company''s website - which looks interesting, by the way - to Mr. Inscore, and I''m sure he''d route it to the appropriate parties inside Sun.

Joe Pardi 04/23/04 11:41:41 PM EDT

Mr. Ottinger, did Sun talk about or recommend how third party vendors such as my company could integrate our products into Creator? Not the mechanics, per se, but the process. Will they offer some sort of support program for easening this process, or just consider us "on our own" and try and figure it out.

Joe Pardi
dotJ Software
http://www.dotjonline.com