They are roughly equivalent in visual composition, with JBuilder getting the edge mainly in handling of bean properties. (Example: try to set borders in Swing GUI) It's easier to modify grid bag constraints in JBuilder, however it is more difficult to go between controls while changing constraints.

If you are indeed creating forms using VAJ's Quick Form feature, there is no equivalent in JBuilder.

Both are equal in handling importing components (as Java Beans) and placing them on paletes. VAJ gives a visual representation to non-visual beans while JBuilder places them in a list. VAJ displays BeanInfo descriptions of bean and properties, while JBuilder doesn't.

For actions, JBuilder will do "connections" from events but not properties (you have to use the PropertyChange event and then write code to check for correct property change). There is actually no concept of a connection. You must add code (you are directed to the spot in autogenerated methods) to set target properties. Of course, connections to methods is trivial in JBuilder.

JBuilder does a better job of handling non-bean-aware properties of Swing components.

If you use factory or variable "beans" in VAJ, there is no equivalent in JBuilder, nor is there a "promote bean feature" feature.
2001-Jun-29 11:52am gyles19@visi.com

  Migrating from IBM® VisualAge® to Borland JBuilder 6
  http://www.borland.com/jbuilder/papers/jb6_migrating_visualage.pdf

  Migrating IBM VisualAge to JBuilder 5
  http://www.borland.com/jbuilder/papers/migrating_visualageto_jb5.pdf