[13:08:46 CDT(-0500)] <drewwills1> morning... anybody ever heard of a method of allowing a spring bean to be accessable to multiple webapps?
[13:16:47 CDT(-0500)] <athena> no . . . seems like that might not be a good idea, either
[13:17:21 CDT(-0500)] <holdorph> Sakai does it, but in a vary Sakai-specific way
[13:17:30 CDT(-0500)] <athena> well, yes
[13:17:33 CDT(-0500)] <holdorph> they have a whole components infrastructure built to support that
[13:17:37 CDT(-0500)] <athena> but i'm not sure that's really something we'd want to emulate
[13:17:56 CDT(-0500)] <holdorph> wasn't saying it was. but drew didn't specify what kind of method he was after
[13:18:08 CDT(-0500)] <holdorph> his statement seemed of general inquiry
[13:19:07 CDT(-0500)] <holdorph> and for as many problems as the sakai way has, I have to admit it also has some nice parts to it as well.
[13:20:19 CDT(-0500)] <athena> perhaps, though i'm not sure it's worth the classloader hell, etc. that results from it
[13:20:36 CDT(-0500)] <holdorph> once you try sharing something amongst webapps
[13:20:36 CDT(-0500)] <athena> drewwills1: do the things using the beans definitely need to be separate webapps?
[13:20:47 CDT(-0500)] <holdorph> it doesn't matter what way you do it, you're going to get into classloader hell
[13:21:54 CDT(-0500)] <athena> yes