Hello,
in the version 1.0.3 as well as in 1.1.0 beta you have a document which tries to explain the integration of jGuard into a Struts webapp: http://jguard.sourceforge.net/mvnsite/docbook/en_jguard_step_by_step_eclipse.html
As it is now, it turns out that the real difficulties in using jGuard is the non existing documentation of the semantics contained in the two xml files JGuardUsersPrincipal/Permissions.
Furthermore, the document needs an introduction to the "business case". I mean, for example: "the Guest user may access this and that pages with this/that credentials. The admin user may access this/that page with this/that credentials ..." so that the reader gets a clearer notion of what actually happens and why it happens the way it does.
What would be good is the explaination of the modeling of the authentication data. It remains unclear what features can be used in which way, and so on.
... So far.
Regards, Christian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1859282
Originator: NO
Hello,
in the version 1.0.3 as well as in 1.1.0 beta you have a document which tries to explain the integration of jGuard into a Struts webapp: http://jguard.sourceforge.net/mvnsite/docbook/en_jguard_step_by_step_eclipse.html
As it is now, it turns out that the real difficulties in using jGuard is the non existing documentation of the semantics contained in the two xml files JGuardUsersPrincipal/Permissions.
Furthermore, the document needs an introduction to the "business case". I mean, for example: "the Guest user may access this and that pages with this/that credentials. The admin user may access this/that page with this/that credentials ..." so that the reader gets a clearer notion of what actually happens and why it happens the way it does.
What would be good is the explaination of the modeling of the authentication data. It remains unclear what features can be used in which way, and so on.
... So far.
Regards, Christian