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 Defects in Rose J Version 2002.05.00

---

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.
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.
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
66786	Generic servlet icons are available, but is missing the "GS" text.

---

Fixed Defects in Rose J Version 2002.05.00

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

Defect	Description
13584	Removing roseuid during Java reverse engineering will delete activity diagram attached to an operation.
16018	No context sensitive help for EJB & Servlet Class Properties treeview items.
16032	Generate Fully Qualified Type does not work for Container Class type causing incorrect code to be generated.
16391	In the Rose J online help, obsolete Java frameworks are mentioned. When you start Rose, check the Frameworks dialog to see the extant Java frameworks.
16498	The error "Parser Error: near token }" could occur when attempting to reverse engineer the code: public interface test { public char opname(); /** * comment here */ }
16517	The online Help states that the EJBHomeMethod is updated using the Update EJB to Interace and Update Interface to EJB. However, the stereotype with this version of the specification is an abstract sterotype that is specialized by EJBcreateMethod and EJBFinderMEthod where an update of the model is available This stereotype is not related to the concept of Home Method introduced by version 2.0 of the EJB specification.
16663	No context sensitive help for EJB & Servlet Class Properties treeview items.
16665	Incorrect EJBHomeMethod information in Rose J help. The online help states that the EJBHomeMethod is updated using the Update EJB to Interface and Update Interface to EJB. However, the stereotype with this version of the spec is an abstract stereotype that is specialized by EJBCreateMethod and EJBFinderMethod where an update of the model is available. This stereotype is not related with the concept of Home Method introduced by the 2.0 EJB spec. As a reminder the version supported by the Add-in is the 1.1 EJB spec.
19219	File incorrectly saved with absolute path when relative path should be used.
22906	Java/J2EE -> Apply Design Patterns on class does nothing
24511	When static attributes are reverse engineered they become non-static and public.
26170	Inserting new EJB method when autosync is activated may cause Rose to crash.
29117	Reverse engineering may cause compartment items to disappear.
29181	equals() method in entity EJB is missing the obj:Object parameter.
29426	Redundant parentheses around operation statment results in the following parser error during reverse engineering: "Parser Error near token; on line ... "
29530	Missing javadoc for simple property in j2ee
29864	Java's "strictfp" causes parser error
30858	Error when RE java files with comment in if/else statement -- in multiline statement
30949	Name conflict errors occur when reverse engineering *.java file which includes duplicate package names in different namespaces.
31038	J2EE icons in toolbox are incorrect when set to large icons.
31538	Double clicking on the title bar of the Rose editor may cause the editor to go behind Rose. This only occurs on Solaris 7 and 8 displays. Will not occur on PC using Exceed.
31620	Changing a class attributes Bean Property after saving the file in the editor does not update the code correctly.
53787	Code generation of a new EJB can result in duplication of statements (i.e. import statements).
53982	When using JBuilder IDE Link and attempting to Reverse Engineer, the following error message ma occur: "Project contains no file. Project files directories will not be added to classpath for reverse engineering". This occurs even though the Project files directory is correctly set in the classpath and reverse engineering is succesful.
54211	Java Add-In handles white space and characters such as "&" inconsistently for Logical view package names.
54211	Java Addin handles package name in Logical View inconsistently.
54274	J2EE does not recognize Component View package structures.
54278	Java Add-In incorrectly reverse engineers "java.sql.Date" to "java.util.Date".
54359	Container class option for aggregation to nested classes generate incorrect code.
54786	Relationship disappears after converting a class to EJB.
54791	Parser Error: near token // on line... occurs in Rose J when a comment is placed in the middle of a Java line (code).
54803	When attempting to reverse engineer *.class files, using Rose J, the following error can occur: Module dependency on self is illegal occurred in File...
54566	Add and Repair EJB may produce incorrect dependencies when repairing a Rose 2001 model.
57845	ejbCreate method is not created after adding new EJB method (Business) and accepting the default operation name.
54853	Forward Engineering of EJB does not produce expected results when using remote references as return types.
55345	Java specification settings are not retained upon saving and reloading model.
55432	Throw statements do not appear in the model when an EJB is created after loading J2EE framework.
55440	SetSessionContext method is duplicated at code geneeration time when using the J2EE framework.
55557	Unable to stereotype subsystem as <<EJBSessionBean>> as only <<EJBEntityBean>> is provided as a stereotype for a package in Rose.
55563	Javadoc comments generated for J2EE code that cannot be turned off.
55766	Java reverse engineering fails with parser error.
55802	Getters and setters set via Bean properties are not considered as inherited operations.
56133	Java does not record paths to generated source files using virtual path map symbols.
56137	AutoSync doesn't work if JBuilder project under ClearCase control.
56167	Newly added EJB method is applied to a different Bean component than the one selected.
56550	Class loses DocComments upon reverse engineering Java files.
56813	Unable to view try-catch code block in the Code tab of the operation specification
57424	Comment placed after a synchronized statement will cause the following error: Parser Error: near token // on line 24 occurred in File XXX.java.
57558	Import statements get dropped when opening and closing the component specification
57564	Method bodies are lost after regeneration of code
57621	Renaming of Java class in Rose, causes JBuilder to create a new class without deleting the old class.
57845	ejbCreate method is not created after adding new EJB method (Business) and accepting the default operation name.
57848	Upon deleting a component from component view, update not performed correctly when autosync is enabled.
58229	The list of the files contained in a jar file does not get refreshed in the upper right window of the reverse engineer dialog
58417	Multiple classes (also class + interface) in the same file do not properly get reverse engineered
58582	Static roles are not generated as static attributes.
58673	Method bodies can be lost upon round-trip engineering Java classes.
60169	Implementation and import statements may be lost when logical view differs from the component when reverse and forward engineering.
60212	The return signature is not correct after reverse engineering.
60528	Reverse engineering Java code always resolves class names according to the component vs logical view hierachy.
61923	A member having the same type as the class is deleted from the code during forward engineering.
65630	Autosync does not update code when moving a component to another package.