Peter, >On Wed, 6 Feb 2002 11:21, Paul Hammant wrote: > >>You can start that tree Berin but I cannot use it. EOB sits on Phoenix >>and that already has the existing framework jar in the classpath. I >>could not replace that beacue it would barf without a complete rework of >>phonix. In short I'll stick to my own framwork interfaces and not use >>those from a fledling framework 5.0 >> > >Im not entirely sure where the problem is. Are you talking about using the CM >within Phoenix or within the EOB application. ie Do you want EOB objects >exposed to blocks or something or are you just using the CM abstraction >within EOB. > Within EOB and to expose Blocks, EOB beans (not Components) or remote AltRMI services (not Components). I am in effect treating the CM as more of an IoC replacement for JNDI. JNDI returns Object, if someone suggested it returns JNDIObject instead, there would be a revolution.
>If it is the second then it may be best for the time being to create your own >interface. When we evolve to Framework 5 you can choose to (or not to) adopt >those interfaces. > That's what I'm doing. I'd almost certainly adopt the framework method when finalised. What scares me most is not knowing whether this is one month or one year (given the amount of other changes that might be implemented at the same time. Regards, - Paul H -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
