On 3/13/07, Stine, Matt <[EMAIL PROTECTED]> wrote:
I've thought about using equinox for these projects, but of course I
have to make the case to my boss for using two different frameworks.
Let me ask you a couple of questions to see if I have a leg to stand on:
1) Does equinox use the CSS framework? If not, how easy would it be to
plug it in?
Not too difficult - I did it in the Spring-Kickstart project.
http://code.google.com/p/spring-kickstart/
Demo at http://demo.appfuse.org/spring-kickstart.
2) Is the same testing infrastructure (dbunit, base classes, etc.)
available in equinox?
No, but it wouldn't be hard to add. Equinox is more about simplicity
so its tests populate the database before running the tests.
3) Should we need to bring Acegi back into the picture, is that going to
be very difficult? We've just been commenting it out rather than
actually removing it from AppFuse as I previously stated.
Equinox has basic Acegi integration now.
4) Should a junior developer who's familiar with basic development w/
AppFuse have little trouble translating his/her skills to Equinox?
Yes.
At any rate, I've been tinkering w/ equinox-struts2-ibatis-1.7. I
noticed that "ant new" failed out b/c it couldn't find struts-2.0.2. I
switched the version to 2.0.6 and it seemed to be happy. Will this be
ok?
Sounds like a bug. I don't want to start fixing up Equinox before
finishing AppFuse 2.0 because that will likely anger folks (why don't
you finish AppFuse first!). However, I do plan on importing Equinox
into AppFuse's SVN repo and renaming it AppFuse Light (appfuse-light
in SVN). Since the communities are pretty much merged, it makes
sense. I don't expect other AppFuse developers to work on Equinox,
but the opportunity is there if they need it. Once AppFuse 2.0 is
released, I'll start working on AppFuse Light 2.0 and likely align the
two frameworks more closely.
Matt
Thanks!
- Matt
[EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt
> Raible
> Sent: Tuesday, March 13, 2007 11:29 AM
> To: [email protected]
> Subject: Re: [appfuse-user] How to remove DB connection dependency in
2.x?
>
> You could probably do this with exclusions on your appfuse
> dependencies. However, since you're removing most of the guts, why
> don't you just use AppFuse Light (Equinox)? Or start with a Struts 2
> archetype (or whatever web framework you're using). If you're ripping
> out all the features, it's probably easier to start with something
> else and copy the stuff from AppFuse into it.
>
> Matt
>
> On 3/13/07, Stine, Matt <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > I know this may sound like a strange request, but how would one
> completely
> > remove any dependency on the database from AppFuse 2.x? Some of the
> > applications we build w/ AppFuse make use of an established SOA for
> their
> > backend, so there is no need for any persistence (including the user
> > management features) in the web app. In 1.9.x I would simply remove
the
> > session factory, all DAO's and managers, and the model classes. I
would
> > only leave one DAO/Manager with an iBATIS implementation should I
need
> some
> > quick and dirty SQL. How can I do something similar in 2.x?
> >
> >
> >
> > Thanks.
> >
> >
> >
> > _____________________________________
> >
> > Matt Stine
> >
> > Senior Software Engineer
> >
> > Hartwell Center for Bioinformatics and Biotechnology
> >
> > St. Jude Children's Research Hospital
> >
> > 332 N. Lauderdale St.
> >
> > Memphis, TN 38105
> >
> > Voice: 901.495.4602
> >
> > Fax: 901.495.5108
> >
> > Pgr: 901.495.3578 #1314
> >
> > [EMAIL PROTECTED]
> >
> > http://www.hartwellcenter.org
> >
> >
>
>
> --
> http://raibledesigns.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
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]
