Oracle published a fantastic document describing how Oracle converted from Classic to Fluid. This very educational document is available at Doc ID 1984833.1. Oracle's solution makes sense for Oracle because it offers customers a choice: migrate to Fluid or stay Classic. As customers, do we need to offer that same flexibility? If so, then Oracle's approach is fantastic. I find most customers are either Fluid or Classic (or some derivative thereof), and when we convert a component to Fluid, it stays Fluid. We don't, for example, have part of an organization using a Classic version while another part of the organization uses the upgraded Fluid version. With that in mind, we developed a simpler approach to Fluid conversion: the in-place conversion. This stands in contrast to the clone-and-recreate approach. We put together a playlist with several videos describing our approach:
Be sure to subscribe to our channel so you don't miss future updates!
Want to learn more? Check out our vast Fluid training library, including recorded and live virtual events, online!
No comments:
Post a Comment