Hi,

I am most interested in an application with JSF, Spring, iBatis. I would
like to know what is the difference between mvn appfuse:full-source and mvn
war:inplace ? I am not sure I understand the difference. 

In the tutorial it also says this 
"One of the nice features of AppFuse 2.x is you no longer need to create a
DAO or Manager for type-safe CRUD functionality. You merely need to create
Spring bean definitions. This means you should be able to easily develop a
front-end without worrying about writing code for the backend (until you
need customized functionality of course)."

But then we see a tutorial that creates a dao and manager both right after
that linking from same page. Was that just to show what is referred to as
"customized functionality"? if so then its good, i would also like to see an
example of how we no longer need those both. i have no problems creating
daos but i was just surprised if we can do it otherwise why waste time. 

Currently in my projects, we have model/dto beans, daos for ibatis, spring
service, and backing beans for jsf. I prefer however moving on to the
appfuse style as its more clean and standard lets say.

Appfuse light does not have annotations. So thats why i was thinking of
leveraging the benefits of using annotations by going with appfuse (strong -
i guess thats the opposite of light), but please feel free to advise on how
should i go forward. 

I got a project built and deployed using hibernate though in appfuse
yesterday and i saw it uses velocity templates for menu. Is there any added
benefit of using velocity over facelets ? I have a few other questions that
i can ask as a follow up. 

Thanks,
-saeed
 
-- 
View this message in context: 
http://www.nabble.com/Questions-about-appfuse---understanding-some-key-points-in-faq-tutorials-tf4122367s2369.html#a11723759
Sent from the AppFuse - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to