Now that Spring Security is in place, do you think the guys at SpringSource
would consider supporting the JSecurity integration classes in their
project, like they support Burlap and Hessian in addition to Spring HTTP
remoting?  The principal is the same, but I wonder if this would be a 'pain
point' for them because JSecurity is viewed as a competing API (although I
view as parts of the two frameworks overlap, but they _don't_ provide the
exact same functionality).

I ask because I love Spring, and integration is up their alley - not really
ours.  We have the Spring integration support because most of the JSecurity
developers use and prefer Spring, so we wanted that support for our own
projects.  It just seems like maintaining this JSecurity-Spring integration
source code (very small amount of code - 4 or 5 classes at most) is more
appropriate for them as opposed to us.

Should we reach out and see if they want to partener?  I've worked with them
before (JMS code), and loved working with them (great group of guys), but do
you think they'd be open to such an idea?

Reply via email to