Brian, ADF Faces is a set of extensions to the Faces standard and does not provide an implementation of the Faces runtime.
ADF Faces can be used with any compatible implementation of the Faces specification, including the Sun RI, and MyFaces. There is a known bug in MyFaces that makes an assumption in the ResponseWriter that currently breaks ADF Faces. http://www.mail-archive.com/[email protected]/msg01182.html This has recently come up again in other discussion threads on this mailing list. On your point about aggregation - it is fair comment to say that JSF needs to go further to simplify the definition of aggregated component sets (and renderkits). This is why most people who write components simply do not specify a custom renderkit-id, and are automatically included with the standard HtmlBasic RenderKit. If you wanted to programmatically aggregate a few different RenderKits together, you could create an AggregatingRenderKit that is registered under its own renderkit id (which would be the default renderkit id for the web application) and which then delegates to a defined set of other RenderKits (by renderkit id) either in precedence order or via some mapping from renderer type to renderkit id. Hope this helps. Kind Regards, John Fallows. On 6/9/05, Brian Abbott <[EMAIL PROTECTED]> wrote: > This reminds me of something I was thinking about this > morning. I will start by saying at the outset that I > am very new to JSF and have not yet wrapped myself > entirely around all aspects of the technology. > However, with what I am familiar with to date, I think > JSF represents generally a good step for the Java > Community. Overall, I feel that this was a positive > step in aggregating framework technologies and > providing an answer to MS's ASP.NET. However, I think > we've missed a subtle turn in the road and have since > been veering down the wrong path. > > JSF needs to go further to encourage users to develop > their own components and, allow for those components > to be easily integrated or consumed by JSF Framework > implementations. With the present situation (AFAIK), I > have to make a choice on an implementation and am > limited to the components provided by that > implementation (unless I develop my own components > using that framework's APIs). There is no way to use > ADF components and MyFaces within the same > JSF-Distribution/Runtime. In other words, I can't run > ADF and incorporate MyFaces components or, vice-versa. > (AFAIK) > > I would like to see core frameworks that differentiate > themselves on backend functionality such as > performance, configuration techniques, and integration > capabilities. These frameworks would include only a > standard set of UI components. Vendors would then > distribute their more appealing component sets as a > standalone package. Applications would inform the > JSF-Implementation about components it wants to load > and use through its faces-config.xml file. So, perhaps > I might add the following entries to faces-config.xml: > > <component-set name="AquaHtml" vendor="CompanyX" > packageFile="ahcomponents.jar"> > <component name="ahCalendar" > registrationClass="com.companyx.ah.reg.Calendar" /> > </component-set> > > That would then make a new JSF tag available as > "<prefix:ahCalendar />" where prefix is defined by the > TLD import directive. > > I think this would create an environment where you > have fewer JSF implementations but, a much more active > world of components and component development. > > Thoughts? Can we already do this with JSF? Did I miss > something? > > Thanks, > > Brian A. > > > --- Werner Punz <[EMAIL PROTECTED]> wrote: > > > Mariano Petrakovsky wrote: > > > I won't create a component like selectManyShuttle > > of ADF Component. > > > Is posible in short time? > > > > > Depends on how good you are at the api, have you > > created components > > already. If not give yourself a few days to learn > > the componet api and > > to try yourself on a few test components. > > > > If you dont have the time, checking out the > > x:aliasBean might solve > > your problem also for the short term. > > (Tiles also might solve your problem) > > > > > > > > > __________________________________ > Discover Yahoo! > Use Yahoo! to plan a weekend, have fun online and more. Check it out! > http://discover.yahoo.com/ >
