Thought about this some more and I have a pretty darn easy solution. I found that I can't use class loading to handle my problem with this.
As an aside, I think it's antithetical to have a framework which (in part) is designed to get rid of singletons to rely on singletons - just seems dead wrong to me. The solution is as simple as naming the registries. The replacement ServiceTokens will have the name of the registry and just pull the appropriately named registry from a class variable map. Sound like a decent compromise? Also, wouldn't it make more sense to add the serialization enhancement as a separate interceptor rather than building it into the base? It could then be managed separately using the mechanisms we already have for managing interceptors. . . Just a thought. It seems like this would fit more into the hivemind philosophy. -----Original Message----- From: Hal Hildebrand [mailto:[EMAIL PROTECTED] I went searching around and found setting the singleton to null stopped the error messages. At issue in my usage is that these registries are around at the same time, so it seems likely that this is going to break things. I'm not likely to use serialization of the objects in the registries, but I can't restrict it either. Perhaps I can deal with it through class loader manipulation. Kind of ugly, though. -----Original Message----- From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Hm. This needs pondering. It's related to serialization of objects which contain referencesto services... i.e., object stored into HttpSession. Have to dig around the the servlet APIs to see if there's a way to get a thread local initialized to the right value at the right time; perhaps there's some kind of listener. On Sat, 8 Jan 2005 19:22:13 +0100 (CET), Hal Hildebrand (JIRA) <[email protected]> wrote: > Multiple Hivemind registries no longer supported > ------------------------------------------------ > > Key: HIVEMIND-83 > URL: http://issues.apache.org/jira/browse/HIVEMIND-83 > Project: HiveMind > Type: Bug > Components: framework > Versions: 1.1 > Reporter: Hal Hildebrand > > I just updated from CVS and now get a SEVERE error in the log: > > SEVERE: Replacing ServiceSerializationSupport instance RegistryInfrastructureImpl[locale=en_US] with RegistryInfrastructureImpl[locale=en_US]; this indicates that multiple HiveMind Registies have been created, and conflicts may occur. > > This is caused by the use of a singleton in ServiceSerializationHelper. I started poking around and started scratching my head over this one. > > I have a need for multiple registries, and this puts a severe cramp in my usage of Hivemind. Is this a feature which can be seperated? Can we get rid of this singleton and move it to the RegistryImpl? > > I'd really hate to have to run with a hacked version. . . > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > If you want more information on JIRA, or have a bug to report see: > http://www.atlassian.com/software/jira > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
