> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ingo Bruell
> Sent: Wednesday, August 23, 2000 4:16 AM
> To: jBoss
> Subject: Re: [jBoss-User] ejb-ref question
>
>
> Hi
>
> Ok, "fixed". I actually did what I told Sebastien not to do: use
> LinkRefs to the global JNDI namespace. Works, but not perfect since it
> assumes globally bound JNDI beans (ok, a pedantic thing, but still).
>
> Also, while doing this I noticed that BeanMetaData holds way too many
> variables that are not common to all beans. In particlar it has many
> settings which do not apply to MessageBeans.
hmmmm design by exception raising its ugly head again...
you do that in other parts of the code (factor out metadata information) and
I don't think it is a good idea. Byproduct of "design talk" but not real.
So if the variable is in the metadata and you don't need it for
MessageBeans? well don't use it!!! but don't put a hierarchy of 10 depth
just to cover simple metadata squeakiness not worth it, really not.
Flat metadata is good (simple), metadata with gazillion hierarchy classes is
silly... we have been there, done that (twice!) and we know it's useless.
Even though I am no expert on non-object languages, I can relate to the
critics of java and OO in general that "extensive" hierarchies is OO-goop...
A little is good, most notably interfaces are good, but the 10 depth
metadata structures only impress little girls.
marc
>
> Thanks
>
> CU
>
> ---
> Ingo Bruell
> OBL GmbH ([EMAIL PROTECTED])
> Hude (Oldenburg)
> Germany
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
