In this interview, Ted looks at trends in J2EE development, tools in the Java and UML space and comments on reasons behind IBM's acquisition of Rational and Borland's acquisition of Togethersoft. He discusses the benefits of frameworks and looks at the Eclipse initiative, the philosophy behind it, and emphasizes the need for standards such as JSR 198, a standard extension API for IDEs.
Watch Ted Farrell's Interview
on J2EE Development
I don't get it:
<quote>You're managing your validation once. It might get deployed to the EJB tier as EJB entity bean might do a validation before Post.
<quote>It might get deployed to the Web tier as some servlet code that actually checks it so it doesn't have to go back to the server </quote>
Sorry for the confusion. The idea I was trying to get
across is that using a framework, you can define your
validation once and then choose how to deploy it. If
you want the validation to happen in the EJB, the framework
can do that before the data is committed. If you don't
want to have to go all the way to the container for validation,
you can have it done in a servlet on the web server or in
the browser itself. The user wouldn't have to manage the
different types of validation manually. The framework
could handle that.
Thanks for the clarification. I think I know what you intended to say, it was just the wording that irritated me. But then again, I only read the transcript, which might not be exact.
For an example of how a validation framework can be useful, have a look at the Struts validator.
You can set up things like conditional dependencies between rules, formatting masks, page-by-page validation of multiple page forms, and so on.
We break down validation into two types. First is the type of validation users can code. We have well-defined extension points in the framework where users can add any type of validation that they want via Java code. This method would obviously be much harder to manage across different tiers of the architecture per my previous description.
The second type of validation is metadata. In one of our current frameworks (BC4J) we provide both some canned validation rules as well as let users define their own. They are stored in XML. These types of validations are usually more well defined, like RangeValidator (make sure a number is withing a range), ListValidator (compare the value to a list of values), ComparitorValidator (compare the value to another value), etc.
> RangeValidator (make sure a number is withing a range),
> ListValidator (compare the value to a list of values),
> ComparitorValidator (compare the value to another value), etc.
So, let's say I have "Address" as one of my business objects. In one of the sub systems, I want to constrain the "address line #1" to 40 character and in another sub system to 50 character. Would I be able to deploy my "Address" business object and set 2 different constraints on one of its fields within the same system?
> So, let's say I have "Address" as one of my
> business objects. In one of the sub systems,
> I want to constrain the "address line #1" to
> 40 character and in another sub system to 50
> character. Would I be able to deploy my "Address"
> business object and set 2 different constraints
> on one of its fields within the same system?
Sure. This is really up to the framework. You
should be able to define different instances of
validation, including multiple validations on a single
business object attribute and then decide how each of
those validations gets deployed.
The BC4J framework allows you to add multiple validations
to a single attribute and we are continuing to add different
deployment mechanisms as implementation choices.
Where can we find out more about BC4J? Anything better then this link, http://otn.oracle.com/products/jdev/htdocs/j2ee_bc4j.html
I think that Borland just wanted to kill a strong competitor of JBuilder - Together CC. They both were "high end" (according to price) development tools.
I have to agree. We were supposed to have version 6.5 last summer. At this point Control Center is so far behind the current generation of IDEs (in terms of the Web tier and java editor not UML) I can't imagine how they could catch up. My prediction is the integration of the UML side of Control Center with JBuilder will become the Control Center product.
It's a shame. I've been using Togethersoft's products since version 1, and have been accustomed too three or four stable releases a year.