Book a Demo

Author Topic: Namespace (package) dependencies  (Read 7792 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Namespace (package) dependencies
« on: August 18, 2005, 06:40:42 pm »
I've reverse engineered some C# code.  Since, in UML, a package IS a namespace, EA correctly created a package for each namespace I have defined in the directory structure (although as I noted elsewhere, it gave them the Java Language type! :()

Anyway, it didn't create any package dependencies (defined via the using keyword in C#).

Should I have expected it to?  Since the project is small, I've put them in.  I also had to add the nesting relationships which EA doesn't create when you have a package and its parent in the same diagram... :(

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

winterhalder

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Namespace (package) dependencies
« Reply #1 on: October 11, 2005, 08:29:54 pm »
I'm also interested in package dependencies.  I'm guessing this is not currently supported.

Are there any plans to add it?


thomaskilian

  • Guest
Re: Namespace (package) dependencies
« Reply #2 on: October 13, 2005, 01:07:27 am »
Quote
...
although as I noted elsewhere, it gave them the Java Language type! :()
...

I noticed there is a Code Generation toolbar where you can select a default language. Don't know whether that helps.

winterhalder

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Namespace (package) dependencies
« Reply #3 on: October 13, 2005, 06:27:45 am »
Are you suggesting that selecting the language before reverse-engineering would set the package "language" setting correctly?

Yes, I'd say you're correct.

But are you also suggesting that this might generate the desired package dependencies?  [Which is the bigger issue being discussed here]

I'm doubting it - I'm guessing EA doesn't support this capability for some reason -- which is a huge hole in the feature set...

Any help would be appreciated - it's imperitive to be able to see package dependencies when you're auditing a design...

thomaskilian

  • Guest
Re: Namespace (package) dependencies
« Reply #4 on: October 13, 2005, 06:40:52 am »
Just meant the language :-X