Pramati Studio 3.0 SP1 Notification
What's New in Pramati Studio 3.0
J2EE 1.3 Component Wizards
Migrate from other Servers
QuiCodeTM coding aids
Source code browsing
Development-time JAAS framework
Source control integration
Test-deploy applications on third-party servers
In-Built Application Server, Message Server and embedded database
Run external executables
Express Development for EJB 2.0
Servlet Templates to create Filters
Platform Certification
License Requirements
Pramati Studio 3.0 SP4 Notification
Pramati Studio 3.0 SP4 release includes enhancements over Version 3.0 SP3 release and fixes to known issues. The following sections describe all the enhancements and changes in the SP4 release:
Key Fixes
The following problems have been fixed in the SP4 release:
- Trying to export Web Modules (with inlcuded items) into WARs failed at times, if the option "Auto-include EJB Reference Classes" was not checked in the Properties dialog. This has now been fixed.
- When the Security Constraint node contained a single resource collection, opening a WAR in Package tool, or a web.xml file did not allow the resource collection to be deleted. This has now been fixed.
- Debugging could not be performed if classic VM was not supported in the target VM. This was typically encountered while trying to debug on a Solaris platform with JDK1.3.1_01. This has also been fixed.
- The Order by Clause did not work in SQL queries for EJB 1.1 beans. This has now been fixed.
- MDBs which used XAQueueConnectionFactory and XATopicConnectionFactory could not be created using the BeanWizard. This has now been fixed.
Enhancements
The following are the enhancements made in SP4 release:
- J2ME Tool Kit J2ME tool has now been integrated in Studio,using which the developers can build, package, execute and debug J2ME applications.
- Web Services Web Services Tool Kit has now been integrated in Studio, and includes a run-time environment and components that aid in designing and executing Web Service applications.
- SourceSafe The MS SourceSafe 6.0 integration in Studio facilitates users to perform SourceSafe operations from within Studio on the Windows platform.
- Oracle 9ias(version 9.0.2.1.0) Studio now provides tight integration with Oracle 9iAS(version 9.0.2.1.0), and applications developed in Studio may be deployed on this version of Oracle Server.
Known issues and work arounds
- The in-built Pramati Server has deployment and runtime issues with JDBC:ODBC Bridge Driver.
- If the user tries to install Studio multiple times, Installshield creates a property file, vpd.properties.
On a Windows platform, the file is stored in the location C:\winnt\vpd.properties. Here c:\winnt is the operating system's home directory.
On a Linux platform, the file is stored in the location /home/username/vpd.properties. Here /home/username is the operating system's home directory.
Workaround After installing Studio again, delete the file from the operating system's home directory.
- When a process is started in Studio, which in turn starts another process, trying to stop the first process may hang the Studio.
Workaround Stop the second process before stopping the first one in Studio.
- The users and groups created in Studio using User Manager do not get added to WebLogic Server.
Workaround Create the user and groups on WebLogic Server using the WebLogic Console, and while deploying the application, use these names for security role mapping.
- The users and groups created in Studio using User Manager do not get added to Oracle Server.
Workaround Create the user and groups on Oracle Server in the principle.xml file, and while deploying the application, use these names for security role mapping.
- If any JMS Destination (Topic or Queue) is added to the embedded JMS server of Weblogic 6.1 SP2, the server must be restarted.
- When a JSP includes another JSP, debugging the first JSP file may not work correctly.
- Source Code Browsing cannot be used to browse for local variables.
- Package tool cannot work on WARs that use anything other than http://java.sun.com/dtd/web-app_2_3.dtd as the dtd.
Visit www.pramati.com for an update. You can also participate in forums.
Pramati Studio 3.0 SP3 Notification
Pramati Studio 3.0 SP3 release includes enhancements over Version 3.0 SP2 release and fixes to known issues. The following sections describe all the enhancements and changes in the SP3 release:
Key Fixes
The following problems have been fixed in the SP3 release:
- Migrating source files into Pramati Studio using the Migration tool, would at times remove the bean class methods that were exposed in the interfaces, from the interface files.
- Modifying the generated bean's source code and compiling it would remove the bean class methods that were exposed in the interfaces, from the interface files.
- Trying to exit from Studio would result in the Studio hanging when
- the configured Server in Studio was running in the debug mode
- the Studio was in the suspended mode,
- and an application was also being debugged.
Enhancements
The following are the enhancements made in SP3 release:
- J2EE Assistant J2EE Assistant now provides the following features:
- Bean Browser Browses for different types of enterprise beans in the Desk.
- Session Facade Selects beans and the type of interface (remote or local) that are to be included in facade.
- Value Object Creates value objects for specified CMP beans. Value Objects are objects that contain the fields that represent the EJB’s accessor methods.
- Coding Aids There are new types of coding aids provided with Studio SP3 release:
- Implement Methods Allows choosing the accessible abstract methods from the base classes/interfaces to be implemented, and creates the stubs for these methods inside the currently edited class.
- Override Methods Allows selecting the accessible methods from the base classes to be overridden, and creates the stubs for these methods inside the currently edited class.
- Previous/Next Method Helps move from the current method to the previous or the next method irrespective of class boundaries.
- Implement the Get/Set Methods Allows selecting the unimplemented getter and setter methods for all the fields in the class, and create stubs for these methods inside the currently edited class.
- Desk Merge Use the Merge Desks feature provided in Studio to merge two existing Desks into a single Desk. This feature is especially useful when upgrading to a new version.
- JDK 1.4 Studio now supports JDK 1.3.1 and JDK 1.4.
- Run the active file Use the "Run File" featire provided in Studio to run the current Java file open in the editor, if it contains a valid main method.
- Database Navigator Use the powerful utility tool, DBNavigator to navigate between tables inside a database, and perform different operations on the tables.
CMR Manager Use the CMR Manager to manage relationships between CMP 2.0 beans and simplify the complex process of building and managing such components.
- Each configured Server instance in Studio now has its own tab in the Output Panel.
- Express Development now provides improved feedback in its output Panel, each time one of the following events is triggered:
- Compilation of any one of the bean files (Home Interface, Remote Interface, Bean class, Local Interface, Local Home Interface)
- Clean Build of EJB Module
- Saving Bean Properties
- Output Panel The tabs in Output Panel now provide new functionalities and icons, in each of its tabs like Copy, Search, Delete, Hiding and Showing Tabs.
Pramati Studio 3.0 SP2 Notification
Pramati Studio 3.0 SP2 release includes enhancements over Version 3.0 SP1 release and fixes to known issues. The following sections describe all the enhancements and changes in the SP2 release:
Key Fixes
The following problems have been fixed in the SP2 release:
- The option, Auto interface generation was by default, switched on each time the Studio was started. The state of the switch is now remembered when the Studio is re-opened.
- Trying to debug an application sometimes did not highlight the line where the breakpoint was set.
- Trying to debug an application sometimes caused the Studio to hang.
- Stopping the Debugger did not stop the Debugee.
- If the number of lines in the message exceeded 2000, the first 250 lines are deleted. The complete output is now written in a log file, <program_name.log> under the Desk Root directory. Here <program_name.log> is the name of the application program.
- The OR Map node in the Bean Properties panel sometimes did not get populated with the table names.
- Adding a remote reference, and then adding a local reference in the EJB Reference panel in the Bean Properties deleted the remote reference.
- Join conditions got added multiple number of times in Bean Properties.
- Using the operator, <> in an EJB QL statement caused deployment failure.
- Setting the Select method's result type mapping in the Finder/Select Panel in Bean Properties did not save it.
- When the Desk opened was read-only, user was not informed of it. Studio now informs the user when the Desk is read only.
Enhancements
The following enhancements have been made in SP2 release:
- Editor Editor now has advanced features for searching like
- Find Previous/Next Word at Caret Searches for the previous or next word inside which the caret is positioned
- Highlight all occurrances Highlights all occurances of the selected text or word where the caret is positioned.
- Incremental Search Searches for the text being typed incrementally. As each character is typed, the search proceeds to the next occurrence in the window of the string as specified so far.
- Object Browser The Object Browser in Studio is a streamlined and logical view of the sources present in the Desk. It helps speed development time by enabling developers to filter through and then browse the hierarchy of classes, and its superclasses, implemented interfaces, fields, methods (both overridden and extended) and object members.
- Code Menu QuiCode, Method Browser and Object Browser can now be accessed from under the new menu on the toolbar called, Code.
- Changed Keyboard Shortcut The keyboard shortcut, Find has been changed to "Ctrl + Shift + F" from "Ctrl + F" to improve usability.
- Database Drivers and Resources Configured database drivers are now picked up and added automatically to the server's classpath when the server is started. To do this, use the Configure JDBC Drivers dialog, available under the Tools menu in the main menu bar. Therefore, the user does not need to add the driver JARs to the server classpath specifically.
When a server is started, all the valid resources in the current desk will automatically be added to that server. Driver classes placed under JDK's jre/lib/ext directory are not automatically picked by the Server or Studio now.
- Express Development Files can now be filtered to exclude them while exporting EJB or Web Modules archives.
- J2EE Assistant The J2EE Assistant in Studio helps the developer add references to the Bean classes, JSP Pages and Servlets. The three different types of references that can be added are EJB references, resource references, resource environment references. To use the J2EE Assistant features, use the new menu in the main menu bar called J2EE Assistant.
- CVS The CVS Preferences dialog has been modified and it now requires the password to be set here. The Login and Logout options have been removed, and to logout, just delete the password from the Preferences dialog.
- WebLogic Server 7.0 Pramati Studio now supports deployment on WebLogic 7.0 Server.
Pramati Studio 3.0 SP1 Notification
The list given below provides all the changes that were made in SP1 release over version 3.0:
Desk
- Desk state is persisted. When re-opened, the tree expands back to the state it was closed at the end of last session, and points to the node last selected.
- Item holds properties where information such as absolute path, owner module, last modified time, and MIME type can be viewed.
- MIME type refresh has been added to Item Properties. This is needed when Studio uses the MIME type to identify a Java file that has ben converted into a Servlet by changing the source. MIME type refresh added on Folder properties also. This will refresh the mimetype of all the items under this folder.
- Drag and drop has been enhanced.
QuiCode Enhancement
- With the enhanced Method Browser, one can view all methods, fields and constructors by pressing
CTRL + SHIFT + \. Search for a method or field just by typing it in after the popup is invoked.
Migration Tool
- Migration from WLS 6.1 and RI 1.2 supported.
- Migration Tool now ignores Java files present in the archives (earlier these files were placed on the Desk
- Tool creates a pending task against Resources that need to be added. This task is can be resolved from the Staging Area.
- Tool invokes Query Wizard in cases of Incomplete Query Conversion
- Tool does not validate the ejb-jar.xml prior to migration. (Earlier if validation failed, the tool treated the JAR as a utility JAR).
- "_WebJava", "_Web" and "_Java" suffixes have been removed. The Migration Estimation Report includes the type of archive (such as web, ejb11, ejb20)
What's New in Pramati Studio 3.0
Read all the new features of Pramati Studio 3.0 in the following sections.
J2EE 1.3 Component Wizards
A complete J2EE toolset that provides a highly productive environment for environment for building, testing and debugging both EJB 1.1 and EJB 2.0 components.
- Container Managed Relationships in enterprise beans for complex data modelling.
- Message Driven Beans for asynchronous messaging EJBQLTM support
- Support for Local and Remote Interfaces
- EJB 2.0 specific Deploy Tool
- Develop and deploy on any industry-standard application server
- Migration tool for importing sources from other IDE and server platforms
Migrate from other Servers
With Release 3.0, Pramati Studio provides a loose coupling with Pramati Server, and publishes an open API for developers to plug-in other J2EE compliant servers that may be installed anywhere on the network. The Studio also provides a complete migration tool to convert outside sources into Studio Desks, which can then be modified and deployed on Pramati Server 3.0, WebLogicTM Server 6.1 or any standard application server.
QuiCodeTM coding aids
By auto-completing key programming constructs, this speed coding facility reduces the fatigue involved in coding large programs. QuiCodeTM facility is available in the Editor and can be invoked while writing source. It works on a prepared index and double-checks your code for missing imports, packages, methods, and fields for Java classes.
Source code browsing
Developers often concurrently work with multiple source files. The Editor provides a Source Code Browser using which a developer can navigate from one source to another, through classes mentioned in the application code.
Development-time JAAS framework
Application developers can use the Studio’s JAAS framework to simulate real-world security realms to test out the applications. Security role references may be defined in JSP and EJB components, and mapped at deployment time.
Source control integration
Development teams need version control to maintain integrity of the project under development. Studio 3.0 framework integrates with CVSTM and VSSTM, and provides a Desk view of the source storage. Source control is typically used to integrate multiple components being developed by distributed development teams.
Test-deploy applications on third-party servers
Maintain a single code base for multiple application servers. Pramati Studio is completely server-agnostic and it allows seamless test deploying on third-party servers that are EJB Compliant 1.1 and 2.0. Studio has an in-built server that allows seamless deployment on
- Pramati Server 3.0
- BEA WebLogic 6.1and
- Oracle 9iAS
In-Built Application Server, Message Server and embedded database
Pramati Studio ships with the entire infrastructure required to make each desktop a complete, independent development and testing unit. The Studio ships with the following:
- In-Built Pramati Server for testing Web and EJB components.
- JMS 1.0.2 compliant Message Server for testing asynchronous components
- Cloudscape database
Run external executables
Use the Studio to configure and run external executables from within the Studio. The Studio allows a maximum of nine executable programs to be run at any point of time.
Express Development for EJB 2.0
The new Studio 3.0 enables the Code-Compile-Run cycle to J2EE Applications by auto-packaging J2EE components - JSPs, Servlets (both 2.2 and 2.3), Tags, EJBs (both 1.1 and 2.0) and Java Classes, into standard components and deploying these components in the built-in application server. This eliminates the tedious Packaging steps while ensuring the Developers have full control over deployment properties including transaction attributes, O-R Mapping and container managed relationship for entity 2.0 beans.
Servlet Templates to create Filters
Hassle-free Filter (Servlets 2.3) generation via templates containing skeleton code for typical Servlets to create Filters. Filters are reusable pieces of code that can transform the content of HTTP requests, responses, and header information.
Platform Certification
The platform certification report for Pramati Server that is integrated with Pramati Studio is given below:
| Platform |
JDK version |
| WinNT 4.0, SP5 |
JDK 1.3.1_01, JDK 1.3.1_02, JDK 1.4 |
| Windows 2000 |
JDK 1.3.1_01, JDK 1.3.1_02, JDK 1.4 |
| Windows XP Professional |
JDK 1.3.1_01 |
| RedHat Linux 6.2 |
JDK 1.3.1_01, JDK 1.3.1_02 |
| Caldera OpenLinux Server 3.1.1 |
JDK 1.3.1_01 |
| Solaris 7.0 |
JDK 1.3.1_01, JDK 1.3.1_02 |
| HP-UX 11i |
JDK 1.3.1_06 |
| Database |
JDBC Driver |
| Oracle 8i |
Oracle Thin driver V 8.1.5.0.0
Merant DataDirect Oracle Driver 2.2 |
| Oracle 9i |
Oracle Thin Driver Version 8.1.7 |
| Informix 7.3.0 TC3 |
Driver V 2.10.JC1N361 |
| Cloudscape 4.0 |
Cloudscape 4.0 RMI JDBC Driver |
| Microsoft SQL Server 7.0 |
Merant DataDirect SQL Server Driver 2.2
JTurbo Driver |
The above platforms are those that have been tested here at Pramati Technologies. Users may use any other valid platform and work with Pramati Studio 3.0.
License Requirements
To install and run Pramati Studio, you need a license key. For evaluation
purposes, you can get a license key by filling out a brief registration form
at Pramati's Website. The license key will be sent to you by email. If you
have purchased a license, or have received a license as part of Pramati's
Partnership programs, you will receive a license certificate that carries
the license key you must key in while installing the product. Any queries
on licensing may be sent to license@pramati.com.
© Copyright 2001-2002, Pramati Technologies.