...
|
|
|
*[#Why does this even exist, hasn't someone solved this problem]*?
*[#What are the requirements to run JGUM]*?
|
... *[#What are JGUMs major limitations]*?
\\
{anchor:Why does this even exist, hasn't someone solved this problem}
h5. Why does this even exist, hasn't someone solved this problem?
Yes! :) Practically every major application that's written solves this problem for their own purposes, but generally not in a reusable fasion. Before I started writing this in 2002 spent hours if not days combing for this solution which seemed like it should already exist. I even hacked together something based on the user management system embedded in Apache's Turbine and Fulcrum projects. [OSUser|http://wiki.opensymphony.com/display/OS/OSUser] has some very similar goals but its hard to tell where its currently at. See more at [The JGUM vision and purpose]. Also now that I've written the core, deployed it successfully to a couple of projects AND continue to gather requirements for important enterprise features I believe JGUM has potential to become THE user management system.
{anchor:What are the requirements to run JGUM}
h5. What are the requirements to run JGUM?
|
* JDK1.4 tested, will probably work with JDK1.2, JDK1.3 and JDK5.0
* Admin UI now requires Tomcat 5.x, but only because of Struts lib requirements.
|
* Any relational [database supported by Hibernate|http://www.hibernate.org/80.html]
|
{anchor:What are JGUMs major limitations}
|
... h5. What are JGUMs major limitations?
* Currently some data is cached in memory making the system VERY fast. However a separte process writing to the GUM tables would cause the server to get out of synch. This will be fixed in a future release toggling caching.
* The system has not been rigorously tested for security holes. There are no known security holes but they likely exist.
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
|
Page Operations
Browse Space