Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, I don't see any logical reason to separate the domain code from the controller code. Keep in mind, I say this from the perspective of someone that has worked on a HUGE application comprising tens-of-thousands of classes, all sorted into about 15 different sub-projects in Eclipse. This is all build using Spring, mostly, but no Roo.</p> <p>I think what you need to do is this. First off, you need to create a master Maven project. Not a JAR or WAR project, just a master "container". I forget the exact maven command, but there is one that creates an empty parent POM and all.</p> <p>Once you have the "master" setup, you create two sub-POMs, one for the domain stuff, one for the WAR stuff. The master will dictate the order in which you need to compile things. Typically its low-level libs first, higher-level projects next, and ultimately some WAR project. Your WAR projects POM should be set to pull in the higher-level projects, and the higher-level project POMs should pull in your low-level libraries.</p> <p>What we use as our basic hierarchy is this:</p> <pre><code>'master' - components - 'lib 1' - 'lib 2' - apps - 'app 1' - 'app 1'_jar - 'app 1'_war - 'app 2' - 'app 2'_jar - 'app 2'_war </code></pre> <p>This is the basic layout for out project at work, with the items in the '' to be substituted for whatever names you are using. Don't ask me why we laid things out this way, it was discussions made many years ago that may or may not be relavant any longer. Bottom line: Its excessive, but it works.</p> <p>Once you get your project hierarchy setup, then you need to remove all the projects from Eclipse. Just delete them...they are setup with Roo and such in mind, and it wont play will doing non-Roo stuff with Roo stuff. Then run your:</p> <pre><code>mvn eclipse:clean eclipse:eclipse </code></pre> <p>Usually you can do this from the top-level project, but sometimes you have to do each sub-project separately.</p> <p>I would also recommend you looking at how Spring Roo handles Spring MVC. It's really a nice implementation, uses Aspects quite well, and is SUPER easy to learn and use.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload