Sparx Systems Forum

Enterprise Architect => Suggestions and Requests => Topic started by: WardB on February 09, 2006, 11:52:00 pm

Title: UML Profile for Java
Post by: WardB on February 09, 2006, 11:52:00 pm
Hello,

I have a request for the following features:
- UML Profile for Java 1.4
- UML Profile for Java 5

So that other stereotypes than boolean, byte, char, double, float, int, long and short are available. But all the Java types, such as String and Date.

If these UML Profiles already exist, where can I get them?

Thanks,

Ward
Title: Re: UML Profile for Java
Post by: «Midnight» on February 10, 2006, 08:47:47 am
The EA support for Java was 1.4 back in the latter 4.x days. Sometime since then EA provided support for 1.5; not too long after the production 1.5 release from JavaSoft if memory serves.

Did we somewhere lose the 1.4 Stuff, Sparxians?

I can second the idea of having something like multiple language versions, along the lines of VB.Net and VB 6 now. For Java and probably many others, surely the bulk of the work would be a common core, which could be quickly copied.

David
Title: Re: UML Profile for Java
Post by: Eve on February 12, 2006, 01:05:09 pm
Both versions of the language are supported without any use of profiles.  As far as code engineering goes, it's just a matter of not using the unsupported features when modelling 1.4.

The basic types are unchanged between versions, and you just need to import the version of the library that you wish to use.
Title: Re: UML Profile for Java
Post by: WardB on February 19, 2006, 12:37:41 am
Thanks for giving a solution simonm.

With "just need to import the version of the library that you wish to use" you mean import the jdk1.4 into the model?
The disadvantage of that solution is that the model gets very, very big (about 30 Mb).

Is there another solution?

Thanks,

Ward
Title: Re: UML Profile for Java
Post by: Eve on February 19, 2006, 01:02:21 pm
Yes, the model does get very big with the JDK imported into it.  You can import only the parts you're interested in (or remove the parts that you aren't after importing them.)

There isn't really any other alternative than that.