Paolo;
I'm used to seeing constructor methods inside of the class they instantiate, not outside of it. It looks like they are generating two constructors. What I'm getting is two classes in the same source file (a no no where I come from because of the problems that creates, but allowed by Java) and both classes have the same name!! I think c++ allows this type of class specification resumption, but I'm not aware that Java does.
[size=13][SNIP][/size]
Jim,
I think you have fallen foul of EA's UI (
Unique Interface). My version only has the one constructor, inside the class. You may have got a left over from a previous emission. When I was doing my preliminary testing of EA code emission, I couldn't get it to reliably locate and update the right stuff in various files, especially if I tried round-tripping. If you delete the file and recreate, you should find all is fine.
My testing was another reason I decided to go the route of decoupling code generation from model management. Again, I don't think EA is worse than any other tool, I just think round tripping to pure code is fatally flawed.
I agree. Most texts are too patronizing about the instantiation process, especially about what goes on behind the scenes. However, in your code you have placed the constructor inside of the class, which is where I expect to find it.
As I said, try it again and it should be in yours also.
Another unique EA interface then as EA allows them both to be independently Stereotyped. These extensions to UML might be nice, but they are really confusing if Sparx does not document them as such. 
Here, It's not EA's fault. This is my private view (that they are one and the same) - I've explained the reasons in other posts. Given the current state of the UML 2 specification, EA is quite within its rights to see them as separate elements. Again, EA isn't alone in this.
For the sake of consistency in our goal to demonstrate the six meronymies, can we put one on this association too?
Do you mean the new 1:0..1 be made from \ be made into? I put the «portionOf» stereotype on the other one. The reason I didn't put one on the Association I just mentioned is that I don't think it's a meronymy. In my view the relationship between the BreadProductDough and the BreadProduct is between two wholes and therefore not a meronymy.
Can you republish the original diagram (used in the reply #32 of this thread) so that that reply will always contain the current version? It would be nice to keep the current drawing published in one place for reference from the other threads forked from here.
I'm happy to publish the current diagram in one place, but #32 shouldn't be it (In my view). I think it's good to show the evolution. Also, the diagram and discussion wouldn't make sense if it wasn't static.
Paolo