Maybe this is in interest of somebody out there. Going away from the spring social sample i now introduced my own repositories to work with magnolia. As this module normally should not do any presentation on the website i don't have any presentation classes here, maybe i do something completely wrong, then tell me, but first let's take a look of what works for now.
there's a root context, setting up my beans: http://nopaste.info/01a5804521.html repository.xml is my own implementation of JdbcConnectionRepository and JdbcUsersConnectionRepository http://nopaste.info/16ca9c6674.html security for now is empty. i am thinking of what i have really to do here, as i have direct access to all magnolia things, which is not what i have, if i'd setup a simple spring social webapp. last theres social connect, which simply follows the rules of what u need to connect with spring social http://nopaste.info/d6679cb325.html I know there's still missing parts in here, but for that i got a cool running instance, which told me, that it started without errors. I moved forward and thought of what i need to store that data in magnolias datastore, i looked around very much but if we blend out se-jcr, i did not find that much vital things on how i would now access the datastore. As i now have direct access on magnolias context and so on it also told me to make my own implementation of that, but this would lead to a rewrite of the vital parts, that were JdbcConnectionRepository and JdbcUsersConnectionRepository before. Here's my UserConnection interface: http://nopaste.info/8fc4276972.html and the actual implementation of that: http://nopaste.info/b0a4bbb264.html The written MagnoliaUsersConnectionRepository: http://nopaste.info/a6a2b75e61.html And the written MagnoliaConnectionRepository: http://nopaste.info/546994e9e3.html Because i need to keep sight of all things i implemented an abstract Utils class to handle, what goes into the database and comes out of it to let the logic behind that as it was before, which leads to the last part of this configuration, the ConnectionRepositoryUtils class: http://nopaste.info/d8f8f9470f.html As everybody can see, here's real work to do now, and i go on to that challenge. If this topic is in interest to anybody, get in touch, share knowledge or what u got out of this approach, what should be done better, just tell me, i will be very happy to have at least one feedbackpartner to compete here. Actually i don't have one. Later there also comes in the sign in component, which shouldn't be that tricky as it doesn't really shares that much different logic to what is implemented yet. if a connection is added, the controller will move to the magnolia register section to add a new user with some predefined values, which are already given, to connect that two together for the time of usage. Greets, Yves -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=635df27b-ecea-429b-bbe4-352bb95854fd ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
