On 3/26/07, nos <[EMAIL PROTECTED]> wrote:
Hi all,
I'm writing because I'm considering adapting an existing app to use AppFuse.
The app lightly uses Spring and Hibernate, but I would like to migrate to
AppFuse over time because it will provide a focused community, common and
up to date components, and hopefully I can avoid messing around with low
level library details.
I want to release a functional demo within three weeks. The existing app has
a lot of specialized functionality that I'd need to retain, so I just plan
to "port" the essentials at this point - mainly the DAOs and model - and
leave my service classes and front end as they are.
There is a data model and a simple front controller servlet in front of
JSPs, but I am not using a MVC framework. I am assuming I can continue using
my FC servlet and gradually migrate over to something (probably struts 2).
I've done something similar in the past couple weeks - taking an
Ant-based project (with no front-end) and porting it to a Maven build.
Most of it was pretty straightforward - the biggest gotchas I found
was that some property files were being filtered by Maven and my
Spring Ant-style placeholders were being filled in with real values.
Other than that, it was just a matter of figuring out what
dependencies the project had.
I have taken a look at some of the AppFuse source code, using M4 of
struts2-modular, and am familiar with some of the pieces that are used, but
have some concerns and would appreciate any comments.
Specific questions:
Part of the essentials of the current design is similar to the BaseObject,
but requires a little more infrastructure. For that reason, I'd have to
create my own model hierarchy, using the design DAO / model design of
AppFuse as much as
possible, and reintegrate later.
Any advice on upcoming changes to the source code. I would need to get
access to and create my own version of the back-end classes. I see I have to
check them out separately, but even recent instructions on how to do so seem
be out of date.
There shouldn't be many more code changes - just adding code
generation and XDoclet at this point. With that being said, there's
still 20+ open issues we need to fix for both M5 and Final.
2.0-M5 issues:
http://issues.appfuse.org/secure/IssueNavigator.jspa?mode=hide&requestId=10090
2.0 Final:
http://issues.appfuse.org/secure/IssueNavigator.jspa?mode=hide&requestId=10072
The code could change if we need to fix any bugs related to it.
Assuming I'm using Hibernate, can my app safely mix "Hibernated" objects and
direct SQL queries? I'm concerned about, for example, Hibernate caching
getting out of sync.
Yes, you might experience issues with caching, but I wouldn't worry
about it. I would worry about performance tuning when you get closer
to production (or your demo).
How does AppFuse handle transactions? Through Spring, Hibernate, or
otherwise?
We use Spring and its declarative transactions to wrap a
PROPAGATION_REQUIRED transaction around all managers in the "service"
package that end in Manager.
<aop:advisor id="managerTx" advice-ref="txAdvice"
pointcut="execution(* *..service.*Manager.*(..))" order="2"/>
Any consultants in the Toronto or Ottawa areas who'd be available for a bit
of bootstrap consulting?
Thank you sincerely for any answers or advice.
Thanks for using AppFuse!
Matt
David
--
View this message in context:
http://www.nabble.com/migrating-to-appfuse-tf3468715s2369.html#a9678654
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]
