The Samples project was intended as a validation of the SPI inside
social.
IMHO, Spring/Hibernate and AOP all make a jar/subsystem harder to
embed in other projects, that don't use the same version of Spring/
Hibernate[1]
So I think:
WIki Documentation +1
A project on code.google.com that depends on Shindig and shares how to
integrate with Spring +0
Add Spring to Samples -0.5 (on the grounds of distraction, code base
size & potential jar conflicts)
Convert Shindig to Spring (not that you were suggesting this) -1
Thats just my view based on having used Spring[2] for the past 4 years
and recently converted to Guice[3].
Ian
[1] Try embedding Alfresco compared to embedding Jackrabbit
[2] https://www.ohloh.net/p/3551
[3] https://www.ohloh.net/p/sakai-kernel
On 10 Feb 2009, at 14:39, chico charlesworth wrote:
Hi all,
As you know shindig relies on guice as the preferred dependency
injection
framework, and that is all good. Yet we've gone with the approach of
using
both spring and guice, simply because spring offers us great support
for JPA
(e.g. transaction management) and AOP, and it's likely that we'll be
using
other Spring features down the line. There has been a couple of
challenges
in getting the project working nicely with these two technologies
side by
side, but we're fairly happy as things stand right now. Note that the
integration doesn't include any changes to the shindig codebase,
that is, we
still let shindig use guice as expected.
My question to the community is, first and foremost, do you think
this would
be beneficial to other people? And if so, what is the best approach in
contributing the shindig/spring integration work we've done?
At the minimum we would like to document this integration work and
make it
available to the community, either in a WIKI or as a tutorial. Another
approach would be to include the code in the samples module, but
then I
guess we would have to consider splitting the samples module into sub
projects?
Cheers,
Chico
