Paddling In The K2 Pool - Part 3 - Let The Hacking Begin

David Horwitz 12 May, 2009 17:06 Sakai Permalink Trackbacks (0)

So stage one of the port to K2 of polls has started - this stage consists of turning the tool into a standalone app prior to wiring in the k2 components. This is being done in the SAK-16313 branch. Some notes:

  1.  Remove the parent declarion in the base pom. 
  2. Remove all sakai dependencies from poms.
  3. Mock the external service - like a test mock you need most of the methods to return true or a string (not false and null)
  4. Update the entity broker code to use the entitbus - in the case of the polls ones AbstractEntityProvider will no longer be needed.
  5. Comment out the EntityBroker definitions (we will re-enable them when we wire up the sling kernel)
  6. Move the components xml files to tool/webbap/WEB-INF/
  7. add hibernate settings and define a transaction manager and session facory
  8. add the mysql driver to the tool pom so it gets deployed
  9. Update the RSF dependencies to to non-sakai versions
  10. Update the web.xml to remove the sakai references. I simply used the one from the RSF hello world app and added context loads for components.xml and the RSF evelovers
  11. there is no non sakai rich text evolver in RSF so you need to change your injection of richTextEvolver to plainTextEvolver.
  12. Added a plugin definition to target Java 1.5 in the poms
  13. add dependency management to the projects base pom for the dependencies that where defined in the Sakai master pom.
Since all the build definitions inherited the Sakai poms are lost it will actualy save time to refactor the project to use maven defaults for source code location (src/main/java).

comments


Add comment

Topic

Text

Your name

Your email address (if any)

Your personal page (if any)

authimage


Powered by LifeType
© 2006 - Design by Omar Romero (all rights reserved)