JSecurity

Dear JSecurity Community,

We have some very exciting news!

We're proud to announce that JSecurity has been voted in to the the Apache Incubator!

This will be a great benefit to you, our community, in many ways:

• Further community adoption from the Apache organization, its members, and Apache end-users, engaging a wider user base.
• Better and more diverse support as more people become contributors in the project
• Apache infrastructure support (mailing lists, Jira, Confluence Wiki, etc).

Hi all,

I made a quick Spring/Hibernate sample application last night. After doing an SVN update, you'll see it in the samples/spring-hibernate directory. This directory has the format of an exploded .war.

I highly encourage everyone to check it out and look through the files. It has many best practices employed and convenient features like:

• A good Entity base class for 'hibernated' POJOs
• Hibernate *.hbm.xml mapping files for User/Role database relationships
• A UserDAO using a nice base 'springified' HibernateDAO

When I released 0.9.0-beta2, I forgot to upload the jsecurity.jar to the Maven repo.

The .jar is now in our local Maven 2 repo, located here: http://jsecurity.sourceforge.net/m2repo/.

It should be propagated to the master Maven2 repo within 24 hours if you'd rather use that one.

Cheers,

Les

Dear JSecurity Community,

A quick point release was made from 0.9.0-beta to the latest 0.9.0-beta2. Download.

It includes a single bug fix related to RememberMe cookies not being set correctly. If you use the RememberMe feature, you will need to upgrade to 0.9.0-beta2 as soon as possible.

Release early, Release often, right? :)

Dear JSecurity community,

We're proud to announce that JSecurity 0.9.0-beta has been released! Download

This release constitutes numerous bug fixes from 0.9.0 alpha and features the following:

• Enhanced support for multiple realms: coding and using more than one realm is easier than before with a type-safe PrincipalCollection.
• Remember Me serialization now defaults to standard JDK serialization, allowing serialization of any Serializable principal (previous implementation only supported JavaBeans-compliant classes).

Last night's JSecurity presentation went well and it was great getting to know the Charlotte JUG group - really nice folks.

For everyone's benefit, I've posted the presentation slides PDF on the Documentation page directly under the Quickstart link at the top.

We also videoed the presentation, and we hope to have the edited video online as soon as possible (maybe a week or two, depending on our time/availability). I'll make another announcement when that happens.

Regards,

Les

I've been kindly asked to present JSecurity at this month's Charlotte JUG presentation on Wednesday April 16th, 2008.

3 other JSecurity team members will probably come as well, assisting by filming the presentation with two cameras in High Definition 1080p as well as maybe jump in to present some topics. We hope to have the video up within a week of the presentation.

I hope to see many of you there!

- Les

Previously I didn't enable mailing lists because I wanted the forums to catalog all questions for users. That way, future users could search the forums and it could quickly become the primary knowledge repository.

But I do realize the benefit of mailing lists and wikis as well, so we're starting to use them again. Some people just prefer mailing lists over forums as well. So we now provide both to allow you to use what you want. The wiki will be online soon.

Please visit the Mailing Lists page for more.

Cheers,

Les

Now that our Ant+Ivy setup is complete, it is generating pom.xml files for the Maven 2 repository. Now you can use either Ivy or Maven 2 to automatically download JSecurity!

The Maven Upload maintainers have added our repository to those that are synchronized automatically. JSecurity is now available in the main maven 2 repository under http://repo1.maven.org/maven2/org/jsecurity (and here is the mvnrepository.com search result).

The JSecurity development team recently discussed on which of the two choices we should use in our project moving forward.

I outlined it in my latest blog post for those interested.

Les