On 1/25/07, molecool <[EMAIL PROTECTED]> wrote:
Excellent :-) that was actually one of my suspicions but I had no idea how you guys are folding this in exactly. Seems I have only touched the tip of the iceberg when it comes to using maven. As I think about this: this whole archetype module paradigm could have some major implications on how software is being built. An enabling key consideration is to define each module's 'interface specifications' and 'component specifications', as for instance defined in 'UML Components' by Cheesman & Daniels (the title is deceptive - the book doesn't really focus on UML but on system architecture). The reason why I bring this up is because the one problem many will run into is to how exactly build one's application around the core modules. By providing the usage contracts via the interface specifications and optionally the realization contracts via the component specifications clear integration points can be established. The emphasis should be on 'pluggable' appfuse modules that can be easily updated and extended (according to the Liskov substitution principle). I wonder if it might make sense to derive and produce the appropriate artifacts in order to communicate how to interact with your respective modules. Appfuse could then encourage a collection of pluggable modules which can be used to assemble the skeleton of an entire application. Hope I'm not offroading here ;-)
You're not offroading at all, but you are using some pretty fancy sentences. ;-) We hope to develop (or integrate) some sort of plugin api in 2.2 that allows you to easily add and remove features. http://raibledesigns.com/wiki/AppFuseRoadmap.html
Oh, yeah - one more question: how do I change the L&F of the JSPs? I assume in order to make layout changes I would have to run mvn war:inplace?
You should be able to override any web files by putting them in your src/main/webapp directory. The war plugin currently operates off of timestamps, so as long as AppFuse artifacts are older, they won't overwrite your local files. We're hoping to make this overlay process a little smarter than just timestamps eventually. So, yes - you can run "mvn war:inplace", or you can run "mvn package" and then copy web files from target/appname-versionnumber/* to src/main/webapp. Matt
Michael Matt Raible-3 wrote: > > They're "merged" in from AppFuse WARs thanks to the Maven War Plugin. > This allows us to package "core" features in AppFuse and inject them > into your project at build time. If you want to modify JSPs and web > files, you can put get them in your project by running "mvn > war:inplace". > > WARNING: This injects everything, including .class files and JAR > files. We recommend you check your project into version control before > running it. Deleting src/main/webapp/WEB-INF/lib and > src/main/webapp/WEB-INF/classes is recommended as duplicate JARs in > your classpath causes issues with some frameworks. > > Here's how to modify the model objects: > > http://appfuse.org/display/APF/AppFuse+Core+Classes > > We're still working on a way for you to customize other source files. > If you're Maven 2 savvy, you can probably build your own project by > piecing together AppFuse's modules from SVN. > > We could distribute a "full source" archetype, but that goes against > the whole "here's an easily upgradable system" that we're trying to > create with AppFuse 2.0. ;-) > > Matt > > On 1/25/07, molecool <[EMAIL PROTECTED]> wrote: >> >> Okay, I'm confused - I was able to deploy and the good old appfuse >> interface >> popped right up. However, all of this seems to be happening automagically >> - >> where are all the sources and the jsps? >> >> find -name '*.java' produces: >> >> ./core/src/main/java/Core.java >> ./core/src/test/java/CoreTest.java >> ./web/src/main/java/App.java >> ./web/src/test/java/AppTest.java >> ./web/target/work/jsp/org/apache/jsp/common/footer_jsp.java >> ./web/target/work/jsp/org/apache/jsp/common/header_jsp.java >> ./web/target/work/jsp/org/apache/jsp/common/menu_jsp.java >> ./web/target/work/jsp/org/apache/jsp/decorators/default_jsp.java >> ./web/target/work/jsp/org/apache/jsp/index_jsp.java >> ./web/target/work/jsp/org/apache/jsp/login_jsp.java >> ./web/target/work/jsp/org/apache/jsp/scripts/validator_jsp.java >> ./web/target/work/jsp/org/apache/jsp/WEB_002dINF/pages/mainMenu_jsp.java >> ./web/target/work/jsp/org/apache/jsp/WEB_002dINF/pages/userForm_jsp.java >> >> Where does all that deployed stuff in target come from? I don't see any >> templates anywhere either. If someone could explain this to me or point >> me >> to the appropriate documentation I would be grateful. >> >> Thanks, >> >> Michael >> -- >> View this message in context: >> http://www.nabble.com/Appfuse-2.0---where-are-the-sources-jsps--tf3119998s2369.html#a8643984 >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > http://raibledesigns.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Appfuse-2.0---where-are-the-sources-jsps--tf3119998s2369.html#a8644476 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
