This document summarizes the
main features of Together releases from version 4.0, beginning with the
release previous to the one that contains this file.
EJB1.0, EJB1.1 generation can
be configured in Options dialog. Select target server in EJB options and
the appropriate specification-aware templates are used for class generation.
Multiple configuration
definitions for supporting different operating systems is implemented.
New option in EJB Deployment
Expert to launch a visual editor dialog and manually edit the generated
XML Deployment Descriptor before final deployment of the EJB.
New XML Structure diagram:
Visually model XML elements to
create Data Type Definitions (DTD).
Export diagram to DTD contained
in an XML file
Enhanced property Inspectors
Inspector customizations from
Together version 3.x are now recognized and supported. See
%TOGETHER_HOME%/inspector.config
for further information.
Expanded information in many
Inspectors (EJB, Class, UseCase, and others), and improved stability of
all Inspectors
Custom Code Templates:
These replaced "blueprint" options
for customization of code construction in versions 2 and 3.
Create your own custom code templates
in addition to modifying the "stock" templates.
New IDL templates.
Patterns:
New C++ patterns
GoF for C++.
Class with constructors
Enhanced QA features:
Save sets of Metrics as files
Save sets of Audits as files
Reuse saved sets in any
project.
Other new items
New Version Control configuration
option "Use dialog before operation on files" enables optional skipping
of dialogs for version control operations. (Dialogs are always used for
operations on a directory, however.)
New documentation: Adding
App Server Support to Together 4.2 is available for download at www.togethersoft.com/downloads/.
This document explains how to create a Together plugin for an application
server.
New module "WLE CORBA Wizard"
simplifies the development of CORBA application for BEA Weblogic Enterprise.
See HowToCreateCorba_Application.html
for further information.
New module "Set US Locale as
Default" allows users to set the default US locale for instance of the
Java Virtual Machine in process of Together startup.
Together 4.0
Expanded EJB support:
One-click creation of entity
and session beans from class diagram toolbar. Customization of the bean
is done with a new Class Inspector with dynamic
pages appropriate to the type of bean. EJB creation from pattern of previous
release is dropped in favor of this new approach.
Automated deployment of finished
EJBs to supported application servers. EJB Deployment Expert handles compilation
of bean and container-specific classes, generation of XML serialized deployment
descriptors and manifests, JAR file packaging, and optional "hot" deployment
to server.
New EJB Assembly diagram supports
EJB Deployment Expert to provide for specification of security roles, method
permissions, and container transaction properties.
Deployment support for BEA WebLogic
Server, BEA WebLogic Enterprise 4.5,5.0,5.1; WebSphere; iPlanet; SilverStream
3.0; Generic 1.0, 1.1
New Role-based Workspace:
Together automatically optimizes
the user interface when you need to work in a specific role, adjusting
tool bar content, menu content, and workspace layout accordingly.
Change roles any time with simple
configuration setting. Changes go into effect when you restart Together.
Choose from these "roles":
Business Modeler : Diagram
editor central, text editor upon demand. Minimal menus for simplicity's
sake.
Designer: Both diagram
editor and text editor central. Everything up to the point of compilation
yet no further.
Developer : Default role.
Both diagram editor and text editor central. Compile, debug, assemble,
deploy, and run.
Programmer: Text editor
central, diagram editor on demand. Compile, debug, assemble, deploy, and
run.
New Development features:
Full-featured editor for source
code and text.
Separately customizable for multiple
languages:
keystrokes
font/color schemes, indentation
and tabbing
Selectable CodeSense code-completion feature.
Printing from text editor.
Full-featured integrated Java debugger.
Improved version control dialogs
Global text search.
New inspector model
Inspector is removed from Explorer pane of main window.
Invoke Inspector only when needed: speedmenu Properties or keyboard
Alt+Enter
New underlying model provides different Inspectors appropriate to different
elements, rather than "one fits all".
Custom inspectors can be created as a simple Java module based on a clearly
documented API:
Use standard property-sheet component or to develop from scratch.
The Apply button is no more. Changes to properties in Inspectors take effect
immediately on field exit or dialog close.
Improved Javadoc support is provided on two Inspector pages for documentation
of each element:
Javadoc page contains a set of tag editors
Htmldoc page provides a formatted preview.
New Code Templates:
These replace "blueprint" options for customization of code construction.
Edit template code using the Together Editor. In Directory tab of Explorer,
select in "Source Code Templates" node and load using speedmenu.
Backward compatibility with "blueprint" options.
Simpler data file format promotes speed and editing as text.
Patterns:
Use the new custom inspectors instead of "one inspector fits all"
C++ support for Coad patterns.
Sequence diagram improvement:
Statement blocks.
Generation of implementation/generate sequence diagram is improved.
C++ support is added.
XMI import export:
Support for Unisys, IBM, and OMG XMI specifications for Class and UseCase
diagram.
Because Rose supports Unisys format it is possible to import/export from/to
Rose through XMI.
Improved JavaBeans support:
Toggle bean recognition from main toolbar
New bean inspector (speedmenu Properties)
Improved CVS and SCC support:
VCS navigator allows user to visually manage source control and perform
any VCS operation.
Generic VCS provider supports any command-line VCS tools, fully configurable
from options dialog. By default SourceSafe commands are used.
Support of these SCC providers:
MS SourceSafe
StarBase StarTeam
Rational ClearCase
Perforce
PVCS VM 6.6
SourceIntegrity MKS
Continuus
PVCS dimension
Round-trip IDL:
Create projects with IDL as the default language
CORBA (OMG) IDL round-trip engineering
Export class diagram to CORBA IDL
Updated module implementation:
Support for modules as JAR files.
Backward compatibility with old-style module descriptor file. Both .def
file and new manifest (.mf) file are supported.
Capability to declare multiple modules' entry point in one manifest.
Modules can be loaded on startup, on first usage, or on explicit demand.
It is possible to declare path to module's documentation in manifest.
Open API extension for config and resources loading.
Possibility to declare libraries for modules, additionally to declare in
classpath, in manifest files.
Support of dependencies between modules - on module can declare "service"
in manifest file and another declare (again in its manifest) that it is
depends on some "service".
New DOORS(tm) integration
Model in Together can be joined with user requirements and be traceable.
User can link requirements to every model component and check whether it
satisfies them or not.
Navigation from Together to DOORS and vise versa.
Help system is implemented with JavaHelp 1.1:
Launch from Help menu when Together is running.
Launch "stand-alone" with command files provided
HTML and PDF formats will be available online shortly after release.
Changed JDK requirement
Sun Java2 (tm) SDK version 1.3 is automatically installed
with Together on Windows platforms, and Together is pre-configured to run
under this JRE, and invoke compile and make using these libraries.
Together should still run with JDK 1.2.2 under Windows, but the later version
is recommended if you plan to use integrated compile and make.
No SDK or runtime is included for UNIX.
Other changes:
Improved New Project Expert
New status bar with resizable progress and status panels.
Windows installer has reverted to Install Shield 6.1.
New web-style About dialog with web and e-mail links to product information,
sales, and support.
Open API documentation is updated and expanded.
Some system modules require manual activation
A number of modules in the Modules tab no longer load on startup of
Together. You activate and deactivate them as needed. This results in faster
startup and better overall performance. If a module that you expect to
appear in the Tools menu does not show up, locate it in the Modules tab
and check if it's speedmenu has the activate command. After activating,
you can run from Modules tab or Tools menu. Use the Modules tab to deactivate
when the module is no longer needed. Integrations with third-party systems
are all on-demand activated.