What's New in Pramati Studio 3.5 SP3 J2EEâ„¢ Centric Power Editing JavaTM coding aids - Online validation of compilation errors based on Java version 1.4 specification. Deviations from the specifications are treated as errors and are identified when the editor checks input or when code is modified. Force-validate code if necessary. Studio prompts corrective action where possible.
- Code completion of various types of code fragments. Completion of class names, methods and variable names used in the source. Prompts completion of frequently used field and variable names.
- Custom Java code formatting rules. Development teams often follow certain look and feel rules while formatting code. Set Java code formatting rules as preferences in the IDE.
- Extensive browsing of standard Java sources. Source code browsing can be invoked on fields, classes, constructors, and methods. Browse methods in same file or inside a class hierarchy. Browse files located inside a JAR. For example, you can locate java.lang.String in the src.jar inside the JDK directory.
A J2EE Enhancement: If Foo is a bean interface, then other beans that have Foo as an interface are also shown in a popup list, allowing you to navigate based on a J2EE framework that goes beyond just standard Java inheritance rules. - Mark and surround code block with standard expressions such as if/else and try/catch. Studio checks for errors in the block before accepting code change. For example, if a code block is surrounded with a try/catch, the body of catch statement is filled with the corresponding code template automatically.
| Â |  | Surround code blocks with standard expressions | | Â | - Method and declaration browsing.. Declaration Browser gives faster access to methods and fields. Single-click listing of all the fields, methods and classes present in sources in the active Desk. Incremental search of field, method and class names through the list.
- Overriding method from a superclass and implementing method from an interface. Select accessible methods from the base classes targetted for overridding. Generate stubs for the method inside a chosen class. View all abstract methods of superclasses and all non-overridden methods that have been inherited by the selected class.
- JavaDoc support. Editor creates JavaDoc stubs for a method. Parameters, and return and throws tags are added to the Javadoc for the method.
JSPTM coding aids - Online validation of compilation errors. JSP code is validated for syntactic, semantic and resolution errors during code generation. Studio's built-in JSP parser checks for semantics during JSP to servlet translation and servlet compilation.
- Java code completion. JSP is structured from Java and HTML. HTML completion is provided in template text. All HTML and JSP tag completion options appear when code completion is invoked after the typing the JSP start token. For Java part of the JSP, standard Java code completions are provided in scriptlets and declaration blocks of a JSP.
- Source code browsing in Java code, custom tags, and linked resources.
XML coding aids - Online validation of XML code having a DTD. Validation is compatible with a wide range of dynamic pages, multimedia presentations, scripting and active content. Studio validates an XML against the corressponding DTD. The parser used for XML parsing is Xerces 2.4.
- Tag, attribute and value completion. For an XML, the tag list is filtered based on the DTD. All tags suitable at the cursor position are shown. Placing the cursor inside the tag completes the attribute.
HTML coding aids - Online validation of configurable errors that are HTML 4.0 compliant. Common errors covered by validation are writing HTML in SCRIPT element, ampersands in URLs, incorrect nesting of elements, using a NAME attribute with IMG or FORM, and using lowercase for DOCTYPE.
- Tag, attribute, and value completion. Studio provides HTML tag, attribute, and value completion facility. It also indicates an empty tag.
- Formatting to set the code layout.
J2EETM refactoring for managing component-level changes and impacts Studio provides J2EE aware refactoring in addition to Java refactoring. All references to a renamed element are updated in the ejb-jar.xml, web.xml and application.xml. For example, suppose ejbCreateCustomer in a bean class is renamed to ejbCreateNewCustomer. Then, in addition to Java refactoring, the appropriate create method is renamed to createNewCustomer in Home and LocalHome. All references in the active Desk and deployment descriptors are updated. Refactoring usages The following usages in Studio can be refactored in a J2EE context: - Rename package, class, methods and fields
- Change method signature
| Â |  | | Change method signature | | Â | - Extract superclasses and interfaces
| Â |  |  | | Extracting Interface | Extracting Superclass | | Â | - Move anonymous class to inner
| Â |  | | Anonymous > Inner | | Â | Rename refactoring Rename refactoring has been extended to cover all aspects of J2EE. At the end of the refactoring the application will again be ready to deploy with all information completely transformed and in accordance with J2EE specifications. - CMF/CMR Rename
- Business Method Rename
- EjbHome Method Rename
- EjbSelect Method Rename
- Create Method Rename
- Finder Method Rename
- Class Rename
- Package Rename
Integrated J2EE semantic validation and correction Online validation based on J2EE 1.4, EJB1.1, and EJB 2.0 specifications. Any deviation from the bean provider contract given in EJB specification is marked as an error in the editor. - Live validation for spec-mandated naming and semantics in the editor
- Validation of integrity of the components and meta-data in the application
Record and playback application test runs with JSPTestTool - Functionality testing of JSP pages
- Tests HTMLs and JSP pages
- Captures and replays every operation performed on Server
| Â |  | | JSP test playback | | Â | CactusTM and JUnitTM integration - Jakarta Cactus to generate Cactus test cases for EJB, servlet, JSP, and filter
- JUnit to generate JUnit test cases for Java classes
| Â |  | | Integrated JUnit & Cactus | | Â | Full feature J2EE Debugger, revamped with new features - Enhanced evaluate expressions
- Support for exception and method breakpoints
- Conditional breakpoints
- Watch points
- Persistent configuration of debug settings
J2EE application analyzer - Transparent diagnostics for analysing execution
- Drill down execution paths
- Identify problematic code-paths in the application
UML support through ArgoUMLTM and RoseTM import - Create structures to maintain, update the sources while importing XMI
- Convert application data to XMI version 2.0
- Convert view details to XMI
| Â |  | | Integrated ArgoUML |
|