TogetherSoft posts details on system requirements and virtual machine recommendations on the Worldwide Web. For the latest system requirements and virtual machine recommendations for all supported platforms, please visit: www.togethersoft.com/together/requirements/. At the time of release the following information is current:
Other operating systems require that you obtain the necessary JDK. You can obtain these as separate downloads from various sources on the Web. For requirements information please see sysrequire.html. Information in that file is current as of release date. Note that virtual machine or JDK recommendations can change between Together releases if new versions become available. The most current information on VMs and system requirements is posted on www.togethersoft.com.
Installation archives for other operating systems are provided in tar.gz and JAR archives containing the entire Together directory structure. You extract the archive into a directory on your computer. A launcher file Together.sh is extracted to the bin directory of the installation. You should review the command line and comments in the Together.sh file to see how your environment variables need to be set so that you can execute Together.sh to launch Together.
Note about JAR installation archive
Because jar archival doesn't save
permissions of the archived files, a script for setting permissions is
provided in the installation. After unjarring the installation archive,
do the following to complete installation:
Server installation
If you want to
do a server based installation, please install on a local drive first and
review the installation topic in Together Help.
On-line
Installation & startup notes
Installation
Help for all supported platforms is on-line at www.togethersoft.com/readme/.
You'll also find information on how to start Together on each of the supported
operating systems.
| Issue | Description |
| Editor pane keyboard shortcuts work only after speedmenu access | The Editor pane's keyboard shortcuts do not work until the pane's right-click menu has been invoked one time. We chose not to allow this minor defect to delay delivery of other important functionality our customers have urgently asked for in this release. We apologize for any inconvenience. This problem will be fixed in the next release (scheduled for early Q1/01). |
| Problems with running Together under Linux with some locales | Different locale settings which have no support in the JVM may exhibit problems. For example, if you start Together under Linux and have an environment variable set: LC_*=ru_RU.KOI8-R, then Together will crash (under Sun vm1.3) or will work, but often throw exceptions (IBM vm1.3). The workaround is to unset the locale variables. (LC_*). |
| Diagram Printing Problems under Windows 98/95 |
|
| Assembly diagram doesn't reference Home/Remote interfaces for JSP test client | A new feature
of v.4.2 is optional generation of a JSP client (for testing a running
EJB) during EJB deployment. (See What's New
for details.) For this release, it is preferable to initiate the deployment
process from a Class diagram rather than an Assembly diagram if you
plan to generate the JSP test client because the deployment engine does
not spot the Home and Remote interfaces of the EJB implementation class
in the Assembly diagram. (This will be fixed in the next release.)
Workaround: It is still possible to use an Assembly diagram as basis for deployment. But in order for JSP client generation to work, you will need to explicitly add shortcuts for the EJB's Home and Remote interfaces to the diagram, since these are not automatically referenced when you add the EJB implementation class to the diagram. |
| Unexpected Breakpoint Behavior | When using
the Debugger with the HotSpot VM (which is how Together is configured by
default when it uses JRE 1.3), there are some differences in behavior from
the standard 1.2 VM. For example, the HotSpot VM doesn't support the synchronization
monitors, fields' breakpoints, and so on. Thus, you may see seemingly strange
behavior when stepping through and into code (remember, Hotspot may be
doing some optimizations under the covers). To get the breakpoints to work
as you expect, go to your Debugger config options (Options | Default:
Debugger: Arguments and parameters: Application: VM options) and enter
-classic
in the VM options field. For Applet debugging, do the same for
Options | Default: Debugger: Arguments and parameters: Appliet: VM options
Note:This value can also be entered directly in the VM options field of the Arguments and Parameters dialog, invoked by the Run in Debugger menu/shortcut command. |
VM crashes when Debugger gets empty this variable |
It has been reported that the Debugger can crash the VM (both the JDK1.2 version and the JDK 1.3 Classic). Investigation shows that such crash can occur when you attempt to get the value of a this variable of type String which has a value of "" (i.e. empty string). This is Sun's bug, and one which we do not attempt to get around. That is why the HotSpot VM is preferable to be used by default. |
| Full-text search in Help does not work under JDK 1.3 | This is a known problem documented by Sun: full-text search in JavaHelp does not work under JDK 1.3. It does work under JDK 1.2x. Until this problem is fixed by Sun, TogetherSoft will provide a searchable version of Together Help in an alternative format at the Together Community website (www.togethercommunity.com). |
If you have changes pending in any field and you click the dialog's Close button (x), pending changes are not saved. This is a change in behavior from previous version 4.1.
In this field type -classic for classic debug mode. Otherwise, the debugger does not function properly under HP-UX.
For Windows users who download the full installation of Together, this is not an issue... the installer configures the required location. Those who download the Windows installer minus SDK/JRE, and users of non-Win32 operating systems should check for the correct setting of this configuration option before using make.
%TGH%/lib/pi_vc_stl.inc
%TGH%/lib/pi_vc_stdlib.inc
They contain set of #include directives for certain Microsoft Visual C++ headers.
pi_vc_stl.inc:
13 headers related only VC's STL (according to MSDN)
pi_vc_stdlib.inc:
complete VC's Standard c++ library (according to MSDN)
The installation also contains include files
%TGH%/lib/pi_bcpp_stl.inc
%TGH%/lib/pi_bcpp_stdlib.inc
%TGH%/lib/pi_bcb_stdlib.inc
that store the sets of #include directives for Borland C++ and Borland C++ Builder headers.
With appropriately modified preinclude.inc files, these provide the possibility to make defines and symbols from Visual C++ STL, Standard C++ Library, or Borland C++ libraries available in a Together model.
To include this support, you should add the folder with the relevant headers to the Search/Classpath (File | Project Properties - Advanced) in a Together project. Then define the wrapped Together macros
TS_PREINCLUDE_VC_STL
TS_PREINCLUDE_VC_STDLIB
TS_PREINCLUDE_BCPP_STL
TS_PREINCLUDE_BCPP_STDLIB
TS_PREINCLUDE_BCB_STDLIB
respectively, using Options | [level] - Source Code page - C++ -