|
|
 |
 |
|
 |
 |
|
|
LATEST NEWS:
JTransit will soon announce that JTransit 2.0 will be the first product to convert tag-based source code directly into JSP pages. Unlike JTransit 1.x, which converted Tango code into JAR files that required a separate, proprietary servlet to be able to execute, JTransit 2.0 creates standard JSP pages, so no additional servlet is needed. Early versions will still require the JTransit Runtime library, but this is expected to be phased out across several updates, eventually producing pure JSP code with absolutely no proprietary runtime library required.
If you hire five engineers to come up with a new JSP architecture for your existing tag-based application, you will likely come up with five different designs, or patterns, for the finished product. Because of this, JTransit 2.0 will also allow you to adjust several parameters that will inform the translater how to separate the various layers of the application. These layers include business logic, presentation logic, and the presentation itself. Combinations of the three can be output as JSP code, JSP includes, JavaBean code, or servlet code. This allows engineers and architects to have fine-grained control over the finished product (.java and/or .jsp files), which will then truly be able to be maintained and extended by Java programmers and experienced web GUI designers. It even allows for changing a bad architecture (common with ColdFusion applications which don't allow for easy model-view-controller separation) into a maintainable one.
This new functionality will be available in a new beta release soon.
JTransit 2.0 beta is currently available as a part of our public beta program. This program is currently open to all developers. To join, simply download the JTransit installer now. |
|
Download JTransit 2 Public Beta |
Reference Materials:
- JTransit Quickstart
- http://docs.jtransit.com. |
|
Thank you for your interest in participating in the JTransit version 2 Public Beta Program. To participate download the installer, read the quickstart, test the JTransit software and keep us posted on your progress. We look forward to your feedback with as much detail as you can provide.
We are here to help! If you have questions, run into problems, discover bugs or have any suggestions don't hesitate to contact us at support@jtransit.com or post a message to the JTransit Talk List (we highly recommend you subscribe).
Version 2 has significant enhancements and new features including the ability to run ColdFusion® applications. The JTransit FrontLine http-based remote Installer makes it very easy to get JTransit up and running whether you are sitting at the server or halfway around the world. Watch this section for future updates and be sure to subscribe to the JTransit Talk List.
INSTALLING THE JTRANSIT BETA SOFTWARE
FrontLine is used to install both the production releases and the beta releases of JTransit software. All modules must be at the same release level under a given install directory (ie, you can't use the same FrontLine instance to update both a production Runtime and a beta Compiler).
To install the beta software, simply follow the link above to download the jtransit-frontline.zip file and follow the installation instructions. After you have configured all the relevant files using the FrontLine remote installer, you must change your frontline.xml file to point to the beta software release folder on our web site instead of the production folder. You can make this change (or any other change) to the frontline.xml file while FrontLine is still running; it will detect your changes and redirect itself accordingly.
There are instructions inside the frontline.xml file itself to help you change the release level for updates. Search for "update-url" in your text editor and you'll see a line like: update-url="http://frontline.jtransit.com/distribution/production/frontline-updates.tml". Just change "production" in that URL to "beta" and FrontLine will download the beta files.
|
|
|
|
|
|
|
|
