--- Berin Loritsch <[EMAIL PROTECTED]> wrote: > J Aaron Farr wrote: > > Hello. > > > > I'm having a bit of trouble using the FortressServiceSelector. Let me put > it > > in the context of the current Fortress Swing example: > > > > Suppose we have two translator components: translator1 and transator2 > listed in > > the SwingContainer.xconf file. For simplicity they're exactly the same > except > > for the 'id' attribute. Nothing else in the xconf file is changed. > > Additionally, the .roles file is not touched either. > > > > If I add a line or two in the SwingContainer.java class to check what class > is > > now returned from > > <snip/> > > > > > I'm not sure if I'm just misunderstanding how to use the ServiceSelector or > if > > it has to do with the difference between ECM and Fortress, or what. Anyone > > have any insight? > > > Yes, there is a difference in the way that ECM and Fortress handle the > selectors. > > ECM requires the + "Selector", where Fortress tries to provide a > migration path. > > Now, I believe that I used to have it respect the + "Selector" approach > of ECM and return the default component if the + "Selector" did not > exist. > > I am not sure when that changed. I will re-enable that approach. >
So to clarify: 1. The "prefered" method of Fortress is to just use "ROLE" not "ROLE + Selector" to return a Selector. 2. I don't need to define selectors in the .role file. 3. I use a component's "id" attribute as the "hint" for Selector lookups. Thanks, jaaron __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
