This morning I created a DAO layer for the mySQL DB created from the Open_Social.sql <http://chrisschalk.com/shindig_docs/io/shindig-io.html#lab3> script on Chris Schalk's website (in a separate project outside of the Shindig source). Standard [JAVA] Spring/Hibernate stuff with DAOManagers and JUNIT tests for all the methods.
After a few hours of trial-&-error, and after reading the 26 messages here (Working on Integration Guide...) <http://shindig-dev.markmail.org/search/?q=DAO#query:DAO+page:1+mid:2jis ibeusp4btlmm+state:results> : I'm unclear on how to configure Shindig source to use the DAOMangers (services). Here is where I ran into "Guice configuration errors": * I installed the DAO layer (jar) into my local maven repository. * Added it as a dependency into Shindig * DID NOT edit SocialApiGuiceModule (i.e. bindings still point to SQLPeopleService, SQLDataService, SQLActivitiesService .class) * Inside the above SQL*Service classes is where I want to call the services of the DAOMangers in lieu of the JDBC code I'm not clear on how to inject the SQL*Service classes with DAOManagers. Looks like I might need to create this DAOLayer as a separate maven module inside Shindig - that way I can let Spring manage the transactions and such??? I though it would be a good idea to ping the group before going down this path. I'd also like to try the approach mentioned in the email thread as to dropping the shindig.jar into an existing web app and wire it up to an existing DAO layer. Any guidance on either of these two scenarios (Data layer added to Shindig -or- Shindig dropped into existing web app)? Or: should I be toying with a RESTFul approach? Just trying to get my hands dirty. Thanks, John Ruffin This email and its attachments are confidential, subject to copyright and may be legally privileged. If they have come to you in error you should take no action based upon the contents nor should you copy or show them to anyone. Please delete the email and its attachments and inform [EMAIL PROTECTED] Any views or opinions expressed are those of the author and do not necessarily represent those of ACH Food Companies, Inc. Security: Internet email is not a completely secure medium, please note this when considering the content of your message. Viruses: We take precautions to ensure email is free of viruses but cannot make a guarantee. Accordingly we advise scanning all email and attachments.
