23
I Use This!
High Activity

News

Analyzed 1 day ago. based on code collected 2 days ago.
Posted over 16 years ago by lhazlewood
Some really cool news about a feature I've wanted for quite a while now: As of JSecurity subversion revision 407, I just recently finished JSecurity's initial implementation of the Servlet Specification for Sessions (Spec final release 2.4, chapter ... [More] 7). It supports all required features, including session id cookies, URL rewriting, SessionBinding events, etc. What does this mean for you? It means that the ServletRequest/Response/HttpSession API can be used directly in code, and those APIs will use JSecurity 'under the hood'. That is, your web tier and your server tier will be transparently use the same session infrastructure. This has big implications: read more [Less]
Posted over 16 years ago by [email protected] (Les Hazlewood)
Released at Thu, 20 Sep 2007 18:24:53 GMT by pharaohhIncludes files: jsecurity.src.zip (326696 bytes, 3 downloads to date), jsecurity-0.2.0-PR1-with-dependencies.zip (12134063 bytes, 5 downloads to date), jsecurity.jar (237277 bytes, 3 downloads to date)[Download] [Release Notes]
Posted over 16 years ago
/jsecurity/0.2.0-PR1/jsecurity.src.zip
Posted over 16 years ago
/jsecurity/0.2.0-PR1/jsecurity.src.zip
Posted over 16 years ago
/jsecurity/0.2.0-PR1/jsecurity.jar
Posted over 16 years ago
/jsecurity/0.2.0-PR1/jsecurity.jar
Posted over 16 years ago
/jsecurity/0.2.0-PR1/jsecurity-0.2.0-PR1-with-dependencies.zip
Posted over 16 years ago
/jsecurity/0.2.0-PR1/jsecurity-0.2.0-PR1-with-dependencies.zip
Posted over 16 years ago by lhazlewood
Finally, after a lot of hard work and juggling crazy schedules, our first 0.2 Preview Release is out. We'll be looking for the community to try it out and recommend any suggestions before we go to a Release Candidate and then to 0.2 final. Please visit the Download page to download, and the Docs page for JavaDoc. Best regards, The JSecurity Team
Posted over 16 years ago by lhazlewood
We expect to release 0.2 this week! To help you better understand the refined architecture, I've included a simple '10,000 foot' overview diagram of the default JSecurity component architecture. But remember, JSecurity is 100% interface-driven. ... [More] The diagram only shows our default implementation strategy. If you really wanted to change it, you could (but we suspect that the default is good for 99% of use cases out there). The diagram shows what JSecurity would look like if using one or more clients and one or more realms. Most applications out there have only one realm (JDBC, JPA, Hibernate, or iBatis, etc) and probably use only one client medium (e.g. web MVC framework). But, I wanted to show what is possible nonetheless.read more [Less]