True about the RI, though I'm a bit surprised that Tobago really needs its own UIViewRoot implementation - what for? Overriding createView() in a non-decorator sense is a risky thing to do.
(FWIW, ADF doesn't replace the default components - we do replace default converters and validators, mostly to get client-side validation into the mix.) -- Adam On 12/30/05, Volker Weber <[EMAIL PROTECTED]> wrote: > Hi, > > the problem is (or was, i didn't check this recently) that the > UIViewRoot is *not* created via application by the RI implementation, > but tobago needs to have his own UIViewRoot component. > > Regards > > Volker > > [EMAIL PROTECTED] wrote: > > Hmmm, I thought contractually, UIComponent creation must be delegated to > > the Application to allow for extension/replacement by 3rd party libraries. > > I know this came up and was enforced since frameworks like ADF do > > replace/extend the default Component Types. Adam, correct me on this one > > if I've misspoke. > > > > -- Jacob > > > > > >>See the comment in tobago ViewHandlerImpl line 71 > >> > >>// ensure tobago UIViewRoot RI don't create the component via application > >> > >>[EMAIL PROTECTED] schrieb: > >> > >>>What bug specifically? > >>> > -- > Don't answer to From: address! > Mail to this account are droped if not recieved via mailinglist. > To contact me direct create the mail address by > concatenating my forename to my senders domain. >
