Rose J Add-In

The Rose J Add-In supports true round-trip engineering and has support for large frameworks.

The following sections provide information on the Rose J Add-In:

• New Rose J Add-In Features and Enhancements
• Known Rose J Add-In Problems and Limitations
• Fixed Rose J Defects

---

New Rose J Add-In Features and Enhancements

The Rose J add-in supports true roundtrip engineering and provides support for large frameworks. This release of the Rose J add-in provides the following new capability:

• Added support for Remote Interfaces.

Rose J Design Pattern Support (Not Available on HP-UX 10.20)

When you apply a design pattern to your model, Rose J adds it in the form of new classes and components for each participant in the design pattern. Rose J places new Rose elements (classes, methods, packages, relations, etc.) in the Logical View and adds a component in the Component View for every added or updated class. The component name also appears in parentheses beside the class name in the Logical View.

When you forward engineer your model into Java code, Rose J populates the design pattern participant classes with methods that have complete code bodies, as well as methods with empty code bodies to be filled in by you.

Rose J includes support for the following design patterns covered in the book, Design Patterns, Elements of Reusable Object-Oriented Software (ISBN 0-201-63361-2), by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, often referred to as the "The Gang of Four."

• Creational Patterns
  • Abstract Factory
  • Factory Method
  • Prototype
  • Singleton
• Structural Patterns
  • Adapter
  • Bridge
  • Composite
  • Decorator
  • Facade
  • Flyweight
  • Proxy
• Behavioral Patterns
  • Chain of Responsibility
  • Command
  • Iterator
  • Observer
  • State
  • Strategy
  • Template Method
  • Visitor

---

Known Rose J Add-In Problems and Limitations

The following table contains known Rose J problems and limitations in Rose for UNIX/Linux.

Defect	Description
09370	In Operation specification Window under Code tab the read only field is not greyed out.
10988	Get/set operations are not visible in Sequence Diagrams.
11721	Unable to create directory on an NFS mounted disk when defining source directory using Java or CORBA project specification.
12950	Rose J uses a code generation property to indicate if an operation is abstract, rather than the model property used by the Rose specifications. For this reason when you specify an operation as abstract in the Standard Specification this is not reflected in the Custom dialog box. The reverse is also true.
13935	Utilizing tabs in the Rose J style specification causes errors when round trip engineering. Workaround - Utilize spaces instead of tabs.
14628	Reverse engineering of very large Java files, can cause memory issues.
15420	Code generating for EJB's does not prompt user for all classes at the same time (only prompts for one at a time).
15481	No warning dialog to indicate there are warnings in log if in Java Auto Sync Mode.
15487	Java code gen does not begin when class is created with Auto Sync already enabled.
15554	When reverse engineering .cab files (which include .java and/or .class files), the method body contents of the source files is missing.
15891	Reverse engineering of .cab files may produce unpredictable results. When reverse engineering .cab files (which include .java and/or .class files), the resulting Rose model may not be correct. The Rose log records errors, but does not alert the user.
16021	No context sensitive help for object finders labels in EJB Persistence Properties window.
16037	If you have a package in your model that has a space in its name, for example "w p" and a class attribute references a type defined in that package, the generated code will include the space and will be incorrect.
16295	JavaDoc tags are not generated correctly.
17256	Unable to create new EJB/Servlet from statechart icon.
18195	The Java code generation OK prompt (modal dialog) can infrequently go behind Rose. If this occurs, it will be necessary to move Rose to respond to the modal dialog - before proceeding with Rose activities.
20257	Pattern Support -> Singleton - Singleton interface should implement java.lang.RunTimeException when exception is thrown.
21096	For J2EE, EJB classes and the diagrams that contain them must be in the same package in order for the EJB Update to work.
31374	Unable to delete Finalizer method from browser after turning on Autosync.
57390	Rose may crash when switching EJB type with Forte IDE.
64316	Rose may crash after saving a message EJB in the editor and bringing up the EJB
74071	No documentation in online Help about the Reference checkbox placed in the specification of a class. The Reference checkbox is used to mark a class as a reference in order to prevent modifying the source code of the class by generating code. When the Reference checkbox in the specification of a class is checked, Rose J cannot generate code (forward engineer) for this class. The Reference checkbox can be checked in two ways. Open the class specification and checked the checkbox. Reverse engineer a class from a Reference classpath. When the class is created in Rose, it is automatically marked as reference.

---

Fixed Rose J Defects

Fixed Rose J Defects in This Release

The following table contains Rose J Add-In defects that have been fixed since the previous release.

Defect	Description
16593	EJB DocComment - extra newline erroneously inserted and inconsistent indentation in code. To reproduce: Create a class and convert it to EJB. Enter multiline comments in the DocComment fields for the class, for the operation and attributes. Generate code. Extra new lines are inserted between consecutive lines of comment in the model. The indentation is also inconsistent.
24832	New EJB CREATE method cannot be created.
30858	Error when reverse engineering java files with comment in if / else statement (in multiline statement).
61221	Error message (Enumerated value public does not exist) may occur upon reverse engineering a servlet.
66132	Parser error may occur when comment (i.e., //) is before closing brace.
66786	Generic servlet icons are available, but is missing the "GS" text.
67314	Comments below Model ID are removed after Round Trip Engineering.
69341	Convert to EJB assumes class diagram is open and is currently the diagram in focus, when attempting to display the newly created EJB.
69564	EJB*Local*Interface options not available from Stereotype selection list.
70075	Code generation for package names (i.e. those including spaces) may not be handled correctly (i.e. the space may be deleted).
70076	Signature of operation are not preserved when commented out at the end of the file.
70206	Java Component Specification Imports tree sorting not sorting correctly.
70359	Reverse engineering can give a reference to a class in the Java or Rose notation.
70901	Autosync does not update a class when drawing a generalize from the interface it implements to another interface with an operation.
71212	Java file is not moved into new directory when moving the package that contains it to another package.
71676	EJB Local and LocalHome suffix fields lose their default values.
72794	Code generation may cause loss of data if both the *.sub and *.mdl files are read only. If only the *.cat and/or *.java files are read only - the problem will not occur. This is resolved by checking whether the file for the model file of the component is read only, prior to modifying the *.java file.
73587	Operation in nested class with argument not fully qualified will reverse engineer incorrectly.
75052	Reverse engineering the rt.jar file may produce the error - "Wrong file format... [path to *.class file[".
75210	Incorrect code generated for arrays in EJB business methods.
75873	Create EJB version 1.1 utilizes EJB 2.0 dtd in the descriptor file.
77011	Support for the Java SDK 1.4 assert statement.
77050	Error (Error resolving qualified name */IOException occurred in File C:\path\x.java) on comment between throws and exception, if comment contains a comma.
77112	Error (Parser Error: near token ) on line n occurred in File C:\path\x.java) on comment inside an empty operation parameter list.
77113	Error (Parser Error: near token if on line n occurred in File C:\path\x.java) on comment between else and if
77361	Error (Parser Error: near token { on line n occurred in File C:\path\x.java) on comment for an anonymous inner class.
77639	Reverse engineering error (Parser Error: near token char on line occurred in File C:\path\x.java) on a comment in front of a method argument list.
78100	Code generation performed incorrectly on array parameter (two brackets instead of one will be generated).
78454	Round trip engineering will cause data loss if ")" is included in code.
79333	J2EE Framework model references J2SE 1.2 components instead of correctly referencing the J2SE 1.3 components.
79480	Incorrect code generated upon reverse engineering code when there are brackets in one line of code.
79733	Warning message added to log when Rose J Add-in does not update getter and setter code.
80317	Significant performance degradation when attempting to reverse engineer Java files.
80697	Location for ejb-jar_2_0.dtd should be updated in EJB 2.0 deployment descriptor.
81861	Unable to reverse engineer xerces.jar. Errors may occur, i.e. Cannot assign a public class to more than one component). Rose may crash.

Fixed Rose J Defects in Service Release v.2002.05.01

Defects	Description
27765	Rose cannot automatically update fully qualified paths for argument types of classes relocated from one package to another.
54211	Rose J handles white space and "&" characters in Logical View package names inconsistently.
57137	JBuilder class in package is not deleted in Rose even with autosync on (JBuilder 6 is required for this fix to take effect).
58432	Generating Java code for setters places custom source code in comments. Upon fixing this defect, the following will apply: The Rose J Add-In will only add default code body for getter/setter if and only if the method body in the code file is EMPTY. In this way, any user-defined code will remain. This is also a consistent behavior with the "generate default return line" feature. If there is ever a case you change the attribute from one bean property type (i.e. Simple) to another (i.e. Bound) and would like a new getter/setter method to be generated in the code file, you may either: - remove the getter/setter method in the code file; OR - remove the method body in the getter/setter method in the code file
58944	Support for roundtrip engineering using the JBuilder "Folder" specific feature.
60169	Rose J loss of implementation when Logical and Component views differ.
64897	When reverse engineering a parser error occurs when there is a comment between the variable initializers.
65574	Turning on GenerateFullyQualifiedTypes for attributes from model properties causes Rose to stop using default.
66704	Creating a final argument in a servlet operation (while autosync is active) will generate the code in the argument name twice.
68506	Rose unable to correctly locate the JDK that JBuilder installs.
68949	Crash upon activating autosync and deleting component.
69539	Error occurs ("an unnamed file was not found") when relocating a module, while utilizing the JBuilder IDE Link.
70059	Reverse engineering Java class with association to itself, presents a class with an association to an unspecified class.
70215	Static initializers blocks may be deleted during code generation.
70753	Rose may crash when changing the name of an entity EJB Primary Key class.
70755	J2EE EJB - Converting to EJB can create duplicate attributes.
71523	When round -trip engineering, if the class contains an operation with arguments referencing other classes without being fully qualified - method bodies may be deleted.
71785	Java parser errors occur when trying to reverse engineer a java interface that has "//" style comments on the line preceding the close brace.
71877	Dragging a unidirectional association from a class to a servlet may leave rose process running after exiting Rose.
72290	Slow performance when reverse engineering.
73819	When using JBuilder integration, Rose may erroneously indicate the project does not contain any source files.
74262	Round trip engineering Http Servlet may cause a loss of implementation code.