2 Replies Latest reply on Nov 5, 2008 9:34 PM by Gerry Matte

    2.1.0.SP1 Generate package name and then imports also

    Gerry Matte Newbie

      For some reason, my entityHome classes are now including both a package name and then an import statement for the same package.  This is new behavior not present in 2.1.0.CR1.


      It's not normally a problem - causes eclipse to spit out warnings that the imports are never needed....

        • 1. Re: 2.1.0.SP1 Generate package name and then imports also
          Dan Allen Master

          There is a reason for this. The home classes are in the action package whereas the entity classes are in the model package. However, due to the fact that there can be complex associations between components, it's very difficult for the generator to know which entity classes need to be imported specifically when generating the home (the generator is not aware of the context in this case). Thus, we simply import the entire entity package so that it compiles. Eclipse should be able to clean this up in one quick refactor, so it isn't a bug (just an extra step for the meticulous).

          • 2. Re: 2.1.0.SP1 Generate package name and then imports also
            Gerry Matte Newbie

            Thanks Dan.
            During SEAM setup I used the same package name for all three packages - that tended to obscure the necessity for each package to be accessible to others since they all generated into the same package in my case.
            Thanks.