readme.txt 2.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445
  1. ===============================================================================
  2. ACEGI SECURITY SYSTEM FOR SPRING - EXTRACTOR
  3. ===============================================================================
  4. *** OVERVIEW ***
  5. To compile container adapters, it is necessary to have classes from each
  6. container on the classpath. Because container JAR files are usually quite
  7. large, including them in the "with dependencies" release ZIPs would rapidly
  8. bloat the file size.
  9. Under this solution, the extractor Ant build file takes a container JAR file
  10. and extracts only those classes required by the Acegi Security System for
  11. Spring. The full container JARs will be provided by the relevant container at
  12. deployment time.
  13. Of course, the classes are extracted from specific versions of the container
  14. JAR files. The resulting "extracted" JAR files (named in the format
  15. container-extracted.jar), include in their manifest file various information
  16. about the source JAR. A copy of the container license is also provided.
  17. If you run a different container version than those the extracted JARs were
  18. built from, you can create a build.properties that specifies your
  19. source.dir.container. Running "ant extract-container" will then cause your
  20. exact container JAR file to be used to build the extracted JAR, which will be
  21. written to the Acegi Security System for Spring main lib directory. You can
  22. then recompile the Acegi Security System for Spring and you should end up
  23. with compatible versions.
  24. Two unavoidable issues from doing this include your version might package
  25. required classes differently (so the files referred to by the Ant build file
  26. are incorrect) or your container JAR might implement different inheritance
  27. orders, interface requirements or method signatures than those the Acegi
  28. Security System for Spring was coded for. In such cases, please let us know or
  29. contribute a patch that supports your container version.
  30. *** THE "SOURCE" DIRECTORY ***
  31. The "source" directory contains the full container JAR files that the
  32. container-extracted.jar files are created from. We do not include these in the
  33. "with dependencies" releases. If you need these files, please download them
  34. from the container vendor sites (refer to project.properties for URLs) or
  35. checkout the project from CVS.
  36. $Id$