Ahhh. To add a few lines ...
There are different spring social examples and i every example has its 
problematic case for me, as i am unused to it too.
The example which is really near to magnolias blossom module is called 
spring-social-showcase-xml, and it uses this §$)"(§&/$)&.-tiles setup. I hate 
it. Another is using Thymeleaf, this is looking funny, but i don't need it too.
There is Petri Kainualainen having a real nice approach on implementing spring 
social, but he uses sitemesh.
http://www.petrikainulainen.net/programming/spring-framework/adding-social-sign-in-to-a-spring-mvc-web-application-configuration/#comment-365552
And as they all are JDBC based and i don't really want to make a jdbc 
connection next to my session manager i also looked up spring-social-roo, which 
has a really nice approach to make a template that fits well to use with 
magnolia.
I can't see to take any of those things away, but parts here and there are 
making sense.
If i could snip three times to get my wished result, i would say making up the 
base application with xml like spring-social-showcase-xml(maybe sec) and use 
controllers like in this example or kainulainen and make usage of a special 
template to make up ConnectionRepositories would fit.
And everything else inside magnolia even needn't to be touched, if i just adapt 
the user table a little bit.

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=4c991416-7b54-4125-8508-760baf46d7b3


----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to