RE: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-15 Thread Howard M. Lewis Ship
> -Original Message- > From: Harish Krishnaswamy [mailto:[EMAIL PROTECTED] > Sent: Monday, September 15, 2003 9:46 AM > To: Jakarta Commons Developers List > Subject: Re: [HiveMind] I don like HiveMind.getDefault and > setDefault(Registry) > > > Thanks, I am not so fa

RE: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-15 Thread Howard M. Lewis Ship
arta Commons Developers List > Subject: Re: [HiveMind] I don like HiveMind.getDefault and > setDefault(Registry) > > > > What if you had two applications running under the > > same context though? > I guess they should have (as recommended by the > servlet-spec)

Re: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-15 Thread Harish Krishnaswamy
Thanks, I am not so familiar with clusters either, this is for my education. I still wondering, though, why Global is not a good place, after all Globals are context attributes also and Tapestry manages them pretty well. -Harish Christian Essl wrote: What if you had two applications running un

Re: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-15 Thread Christian Essl
> What if you had two applications running under the > same context though? I guess they should have (as recommended by the servlet-spec) have attribute names like [package-name].HiveMindRegistry. (Of course if you mean two Tapestry apps you will have to find another way). > And how will replicat

Re: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-15 Thread Harish Krishnaswamy
0:57 AM To: [EMAIL PROTECTED] Subject: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry) The reason I don't like this is because I guess it can lead to quite some problems and it is not realy needed. Just imagine your app uses HiveMind and some api uses HiveMind internall

RE: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-15 Thread Christian Essl
Yes, exactly. Like: public static Registry constructDefaultRegistry(){ ClassResolver resolver = new DefaultClassResolver(); RegistryBuilder builder = new RegistryBuilder(); builder.processModules(resolver); Registry registry = builder.constructRegistry(Lo

RE: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-15 Thread Howard M. Lewis Ship
http://javatapestry.blogspot.com > -Original Message- > From: Christian Essl [mailto:[EMAIL PROTECTED] > Sent: Monday, September 15, 2003 8:36 AM > To: Jakarta Commons Developers List > Subject: RE: [HiveMind] I don like HiveMind.getDefault and > setDefault(Registry) > > &

RE: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-15 Thread Christian Essl
I was now thinking about why I did not like getDefault(). I think the real (Freud'schen) reason was that the first time I saw it I expected it to be something I could get a default registry from. (You know I was eagar to try it out, had my head full with the new stuff and didn't want to go throu

RE: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-15 Thread Christian Essl
Yes, I would agree with this and generally would suggest to hold the registry in the ServletContext. I think the ServletContext is thought for this. I actually use as ContextListener which builds the Registry up when my web-app is started. "Howard M. Lewis Ship" <[EMAIL PROTECTED]> wrote: I thi

RE: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-14 Thread Howard M. Lewis Ship
tp://jakarta.apache.org/commons/sandbox/hivemind/ > >http://javatapestry.blogspot.com > > > > > > > >>-Original Message- > >>From: Essl Christian [mailto:[EMAIL PROTECTED] > >>Sent: Friday, September 12, 2003 10:57 AM > >>To:

Re: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-14 Thread Harish Krishnaswamy
g/tapestry http://jakarta.apache.org/commons/sandbox/hivemind/ http://javatapestry.blogspot.com -Original Message- From: Essl Christian [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 10:57 AM To: [EMAIL PROTECTED] Subject: [HiveMind] I don like HiveMind.getDefault and setDefaul

RE: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-12 Thread Howard M. Lewis Ship
ndbox/hivemind/ http://javatapestry.blogspot.com > -Original Message- > From: Essl Christian [mailto:[EMAIL PROTECTED] > Sent: Friday, September 12, 2003 1:14 PM > To: Jakarta Commons Developers List > Subject: Re: [HiveMind] I don like HiveMind.getDefault and > setDefault(Registry) &

Re: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-12 Thread Essl Christian
The reason I don't like this is because I guess it can lead to quite some problems and it is not realy needed. I'm thinking you are right ... its the balance of convienience vs. correctness. Certainly, no service implementation should ever use HiveMind.getDefault() ... the BuilderFactory means

RE: [HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-12 Thread Howard M. Lewis Ship
g/tapestry http://jakarta.apache.org/commons/sandbox/hivemind/ http://javatapestry.blogspot.com > -Original Message- > From: Essl Christian [mailto:[EMAIL PROTECTED] > Sent: Friday, September 12, 2003 10:57 AM > To: [EMAIL PROTECTED] > Subject: [HiveMind] I don lik

[HiveMind] I don like HiveMind.getDefault and setDefault(Registry)

2003-09-12 Thread Essl Christian
The reason I don't like this is because I guess it can lead to quite some problems and it is not realy needed. Just imagine your app uses HiveMind and some api uses HiveMind internally but does not document (it is just internal why should it?). Both register with setDefault(). Than you have a p