Migrating to facelets

What is the recommended strategy for migrating from one view technology, tiles, to another, facelets? More specifically, can I set the default suffix to .jsp instead of .xhtml while I'm making the transition? What are the ramifications of going for it and changing my .jsps to .xhtml (since I'm not really using jsp for anything except the root tag and a few directives that can be done in other ways)?
My application is JSF 1.2 with tiles. There is a need to move to facelets rather quickly. So I'm wondering if it's possible to start using facelets without changing all of my filename extensions from jsp to .xhtml? Since facelets is the view technology developed for JSF, and it now seems to be the view technology of choice and most supported by component/framework developers, it is important to do this. For example, I want to use the IceFaces framework on my site and IceFaces does not really support tiles.
So can I set the default suffix to .jsp instead of .xhtml?
Thanks!
..\Wendy

The answer is yes, you can use jsps until you have time to migrate to xhtml.
The default suffix is still .xhtml.

Similar Messages

  • OEPE support for ADF 11.1.2.x (11g R2)

    Hi there,
    Are there any plans to release a (preview) version of OEPE that supports ADF 11.1.2.x (i.e. ADF with JSF 2.0 / facelets)?
    Thanks,
    Murray
    Edited by: 974848 on Dec 4, 2012 2:56 AM

    In ADF 12c there would be conversion from JSPX to Facelets. Hence, you could create JSPX-based templates today in OEPE and they would be migrated to facelets in the moment we support ADF 12 in OEPE.
    Nonetheless, to set up the right expectations: ADF Faces templates will work on facelets which does not imply ADF Faces template = Facelets Templates. As you might now we provide templating capabilities since the first release of ADF 11g. Are you looking into specific features of Facelets templating? perhaps I can validate internally if we cover them on our side on the ADF Faces templating.
    By the way are you currenly using OEPE with ADF?
    - Juan Camilo
    Edited by: Juan Camilo Ruiz on Dec 13, 2012 2:18 PM

  • Migrating from JSP to Facelets

    Hello,
    we have an old application based on JSPs which we like to migrate to JSF and Facelets.
    For a phase 1 we decided to leave the JSPs as untouched as possible, but establish the use of JSF and the Facelet templating mechanism.
    So the question is, how can we keep the content of the JSP page for a first step and use that within a part of the template, e.g. the ui-composition "content"?
    I found some articles about the general transition to Facelets, but I have problems with the details, especially, how to deal with all that Java-Code within <% ... %> blocks?
    Thanks in advance,
    Geziefer

    Thanks for the clear answer - although I'd wish it was different.
    Well, basically the existing application must be reimplemented. But as it is still important, heavily in use and the logic within the pages should be kept, we plan to do a page-by-page migration to JSF/Facelets.
    And that's why I hoped to be able to do the templates and the navigation and all the framework stuff in a step 1 and keep all the rest, and only after finishing that do the page-by-page migration.
    Is it possible to kind of call or include the old jsp as an intermediate step within the facelet?
    Geziefer

  • Application is not working after migrated to 11.1.2.4

    Hi expterts,
    I developed an adf application on JDeveloper 11.1.1.6. It works without problem on 11.1.1.6.
    Briefly uses following technologies: ADF faces, facelets and taskflows, EJB, hibernate...
    When i wanted to go on develop with 11.1.2.4, I copied my App root folder to another folder. And chosed .jws application file from 11.1.2.4 version. Then IDE wants me to confirm about migration, then i accepted.
    I develop a supplierList structure for feeding the select one choice components' selectItems. These provide load the db objects on the first calling and manages by my ListManager class.
    These supplier classes initialize on the MBean init method. MBean init method calls on taskflow initializer. The project (VCUtil) that includes Supplier classes is on my main ViewController project as ADFLibrary.
    But after migration when i deploy the application on my Integrated weblogic Server. oops does'nt seen my jspx screens properly on first attempt which includes supplier classes. But when i refresh the screen it can be loaded properly.
    The log contains only that line:
    <20-Sep-2013 10:33:31 o'clock EEST> <Notice> <Stdout> <BEA-000000> <10:33:31,189 DEBUG [PerformanceMonitor_lsr6sq_Impl] Method public java.util.Collection com.acme.model.domain.ad.sessionbean.ADManagerBean.findCurrencies() took 167 (ms)>
    <20-Sep-2013 10:33:31 o'clock EEST> <Info> <ServletContext-/RestAutomation> <BEA-000000> <JspServlet error: Servlet unable to dispatch to the following requested page: The following exception occurred:oracle.adf.controller.activity.ActivityLogicException: ADFC-06015: An exception occured when invoking a task flow initializer.>
    My first supplier class is CurrencySupplier, and i can see acc.to the log it works, the second one is DepartmentSupplier class. So i expect log stdout about findDepartments() method too. But nothing, i guess when executing on CurrencySupplier there might be a wrong, that's why can not go on. But when i refresh the page at that time executes the DepartmentSupplier class. If i refresh page for Supplier class count times then page loads.
        public void init()
            try
                if (ObjectUtil.isNull(currencySupplier = (CurrencySupplier)ListManager.getInstance().getSupplier("currencies")))
                    currencySupplier = new CurrencySupplier();
                if (ObjectUtil.isNull(departmentSupplier = (DepartmentSupplier)ListManager.getInstance().getSupplier("departments")))
                    departmentSupplier = new DepartmentSupplier(false);
                if (ObjectUtil.isNull(countrySupplier = (CountrySupplier)ListManager.getInstance().getSupplier("countries")))
                    countrySupplier = new CountrySupplier();
                if (ObjectUtil.isNull(cityForCountrySupplier = (CityForCountrySupplier)ListManager.getInstance().getSupplier("citiesforcountry")))
                    cityForCountrySupplier = new CityForCountrySupplier(false, null);
                else
                    cityForCountrySupplier.refreshList(null);
                if (ObjectUtil.isNull(districtForCitySupplier = (DistrictForCitySupplier)ListManager.getInstance().getSupplier("districtsforcountry")))
                    districtForCitySupplier = new DistrictForCitySupplier(false, null);
                else
                    districtForCitySupplier.refreshList(null);
    public class CurrencySupplier extends SimpleListSupplier
        public CurrencySupplier(boolean blankItemApplied)
            super(blankItemApplied);
        public CurrencySupplier()
            super();
        @Override
        public void loadList()
            try
                UtilBean utilBean = new UtilBean();
                clearList();
                list.addAll(utilBean.findCurrencies());
                Collections.sort(list);
                itemList.addAll(ConversionUtil.getConvertedToSelectItemList(list, isBlankItemApplied()));
            catch (Exception exc)
                exc.printStackTrace();
        public String getListName()
            return "currencies";
    I hope that i could explain the problem
    Thx, bgrds

    Are there missing / invalid entries in Settings >> General >> About ?

  • ER's for Facelet Support, or "why facelets is a 2nd class citizen in JDev"

    Hello all,
    After an [url http://forums.oracle.com/forums/thread.jspa?threadID=873997]interesting journey getting Facelets, Trinidad, and JDeveloper 11g to play nicely together, I thought I'd post some thoughts on the sort of things that (IMHO) JDeveloper 11 needs in order to offer real, true Facelets support. I'll offer my list below, which will include observations as well as suggestions:
    1). If we are going to use true .xhtml files, JDeveloper 11g doesn't support drag-and-drop from the data control pallette on to the .xhtml page (I do have a workaround that I'll detail below, but that has its own issues).
    2). It's literally impossible to mix JSP and Facelets in a single project. As soon as you configure your project for JSP (by adding taglibs, for instance), you can no longer create a Facelets page from the "New" gallery, as JDeveloper will tell you "Cannot add a facelets page to a project configured for JSP." It works both ways, too - if you add a Facelets file to your project, no longer can you create a JSP.
    3). Even if I manually try to get data bindings (page definitions) working with .xhtml files, it doesn't seem to work (I did this by creating a jspx file and page definition and copying files / changing the data binding registry).
    4). Because ADF Faces is so intertwined with Trinidad, it would be nice if faces-config.xml and web.xml would be properly configured automatically (as an option) for Trinidad. If I manually configure faces-config.xml by ensuring the view handler is not defined there, define an alternate view handler in web.xml, and then add a new Facelets page to my project, JDeveloper undoes all my work and puts the view handler back in faces-config.xml, causing major problems.
    5). To work-around the poor support for drag-and-drop from data controls onto .xhtml files, I have just decided to use .jspx as my default suffix for Facelets files. I create them via picking "JSF Page" from the new gallery, and then I manually mess around with the source so that it's not really a JSPX anymore. However, if I do this, I don't have any tag completion support for the Facelets tags. If I download the TLD from [url https://facelets.dev.java.net/servlets/ProjectDocumentList?folderID=4190&expandFolder=4190&folderID=0]here, JDeveloper complains about not having a tag handler class.
    6). Two words: WYSIWYG Editing. There isn't any for Facelets pages. I have ADF Template envy. As soon as you configure web.xml and faces-config.xml for Facelets, all WYSIWYG is broken. Now, I know "real" coders don't use WYSIWYG, but it's sure darn nice to switch from source view and take a quick peek at the layout. For new-to-JSF/new-to-Trinidad/new-to-ADF Faces developers, it's almost a hard-and-fast necessity.
    7). Would be nice to have page definition inheritance working like for ADF Templates too.
    8). Drag-and-dropped things from the data control tend to include f:validator tags. No problems there, but the tags don't include an validatorId. Facelets needs them. I work around this manually by adding validatorId="" to each of the tags. I know there is a velocity template somewhere that JDeveloper uses for this drag-and-drop, but I cannot find them - does anyone know where they are?
    9). If, in a project with no ADF Faces - only Trinidad, if I drag-and-drop from the data control on to an ui:define tag in the structure window, I get all kinds of ADF Faces options for the drop, nothing for trinidad.
    10). Facelets < 1.1.15 has a tiny bug with the ui:debug tag (you cannot expand the component tree). It would be nice to update the one included with JDev (1.1.12) - I have done this and it appears to work fine.
    From a productivity point of view - #6, together with drag-and-drop support on to true .xhtml files (not .xhtml files with a .jspx extension) would elevate the game leaps-and-bounds.
    I'm interested in any of the following:
    a). Some wonderful news from Oracle that they already know all of these limitations and they are fixed in a patch release which was just uploaded to OTN 5 minutes ago ;)
    b). Insight on better ways of working with ADF BC / ADF Bindings / Trinidad / Facelets in JDeveloper 11
    c). Feedback and experiences from other people using Facelets in JDeveloper, particularly with ADF Data Binding.
    Depending upon the level of interest, perhaps we can migrate the discussion over to the [url http://groups.google.com/group/adf-methodology]ADF Enterprise Methodology group and produce a Wiki page out of it.
    Best regards,
    John

    Nice post John,
    Here are some of my comments on those issues:
    +1). If we are going to use true .xhtml files, JDeveloper 11g doesn't support drag-and-drop from the data control palette on to the .xhtml page (I do have a workaround that I'll detail below, but that has its own issues).+
    +3). Even if I manually try to get data bindings (page definitions) working with .xhtml files, it doesn't seem to work (I did this by creating a jspx file and page definition and copying files / changing the data binding registry).+
    I tried that a while back too because Facelets is so much more powerful than anything else to achieve high performance and powerful templating in JSF, but it's completely unsupported. I tried all possible combination of servlet-mapping aand servlet-filter-mapping. AFAIK there's no way to do it yet and Oracle will most likely delay the support of Facelets + Databindings until JSF 2.0 where there won't be much choice. If you got them working somehow in 11g, I would be very very interested in getting a small demo project.
    +2). It's literally impossible to mix JSP and Facelets in a single project. As soon as you configure your project for JSP (by adding taglibs, for instance), you can no longer create a Facelets page from the "New" gallery, as JDeveloper will tell you "Cannot add a facelets page to a project configured for JSP." It works both ways, too - if you add a Facelets file to your project, no longer can you create a JSP.+
    I can understand that one, I'm sure it comes from a a very good intention from Oracle as Facelets actually replace the JSP engine, meaning the pages don't get parsed by JSP, thus tag classes don't get called. So I assume that limitation was to prevent people from thinking that Facelets integrates with JSP while it's not at all. However, I can understand that some applications might want to leverage both technologies at the same time
    Regards,
    ~ Simon

  • Error while migrating from JDev 11.1.1.3 environment to 11.1.1.6

    Hi,
    I have developed a BPEL process including Human task and Business rules on JDeveloper 11.1.1.3. The human task worklist page and its project were autogenerated and then I was deploying both the projects from Jdeveloper to weblogic 10.3.3 server and it was working fine.
    We needed to migrate the same project to JDev version 11.1.1.6 and for this I have imported the two projects into the new workspace and JDeveloper itself migrated the project to thie higher version.
    However, while using the same deployment process and deploying on compatible weblogic server, I am facing issue while deploying worklist application and following appears on the domain log:-
    There was a failure when processing annotations for application /u01/oracle/SOA/SOA_INST/user_projects/domains/base_domain/servers/AdminServer/upload/ApprovalPage/app/WorklistADFPage.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet
    Failure occurred in the execution of deployment request with ID '1352977219006' for task '29'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'WorklistADFPage.war'' weblogic.application.ModuleException: Failed to load webapp: 'WorklistADFPage.war' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused By: java.lang.ClassNotFoundException: oracle.adf.library.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:108) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1370) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:452) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:497) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    In JDeveloper it says:-
    Weblogic Server exception: weblogic.application.ModuleException: Failed to load webapp: "WorklistADFPage.war"
    Caused by: java.lang.ClassNotFoundException: oracle.adf.library.webapp.ResourceServlet
    Also when I see the libraries and classpath of my project I see ALE components jar marked in red.
    My Composite gets deployed, and the issue comes only with worklist project.
    Please suggest how to approach to resolve this issue.
    Thanks in advance.

    Hi,
    actually there is no backward migration path if you used Facelets for building your pages. For page fragments you will need to manually change ui:composite to jsp:root tags. To ensure web.xml is setup correctly you should create a new project in 11.1.1.6 and copy the web.xml over (ensuring the web.xml is configured for ADF use). Probably copying the content of the JDeveloper 11g R2 project into the 11g R1 project and then fixing problems is the way to go. As said, there is no automated backward migration path
    Frank

  • MIGRATING FROM JSF 1.2 TO JSF 2.0.1 WITH PRIMEFACES

    HELLO!
    I'm migrating to JSF 2.0.1 (mojarra 2.0.1) using PrimeFaces 2.0.
    As I'm comming from JSF 1.2, I still have some libs in my project as jsf-facelets.jar, jstl.jar.
    With JSF 1.2 I was using Tomcat v6 1.4, but I upgrated to Tomcat v6 2.0
    I decided to use primeFaces for my uiComponents and this requires JSF 2.0
    I install primeFaces.jar and download jsf-api.jar and jsf-impl.jar
    I changed my config to 2.0 in my faces-config and the weapp works fine! I'm tryin' to Login using <p:commandButton> (from PrimeFaces) with action attribute, but when the app calls the action from my managedBean, an error appears....
    javax.servlet.ServletException: Erro de argumento: The parameter viewId is null
         javax.faces.webapp.FacesServlet.service(FacesServlet.java:323)
         br.com.webtraffic.big.filter.ExpireFilter.doFilter(ExpireFilter.java:27)
         org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
         org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
         br.com.webtraffic.big.controller.authorization.AuthorizationViewRedirectionFilter.doFilter(AuthorizationViewRedirectionFilter.java:24)
         org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)
         org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
    root cause
    java.lang.NullPointerException: Erro de argumento: The parameter viewId is null
         com.sun.faces.util.Util.notNull(Util.java:221)
         com.sun.faces.application.view.MultiViewHandler.getActionURL(MultiViewHandler.java:270)
         org.springframework.faces.webflow.FlowViewHandler.getActionURL(FlowViewHandler.java:50)
         com.sun.faces.renderkit.html_basic.FormRenderer.getActionStr(FormRenderer.java:234)
         com.sun.faces.renderkit.html_basic.FormRenderer.encodeBegin(FormRenderer.java:137)
         javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:823)
         javax.faces.component.UIComponent.encodeAll(UIComponent.java:1608)
         javax.faces.component.UIComponent.encodeAll(UIComponent.java:1613)
         com.sun.faces.application.view.JspViewHandlingStrategy.doRenderView(JspViewHandlingStrategy.java:415)
         com.sun.faces.application.view.JspViewHandlingStrategy.renderView(JspViewHandlingStrategy.java:204)
         com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:126)
         org.springframework.faces.webflow.FlowViewHandler.renderView(FlowViewHandler.java:90)
         com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:127)
         com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
         com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
         javax.faces.webapp.FacesServlet.service(FacesServlet.java:311)
         br.com.webtraffic.big.filter.ExpireFilter.doFilter(ExpireFilter.java:27)
         org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
         org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
         br.com.webtraffic.big.controller.authorization.AuthorizationViewRedirectionFilter.doFilter(AuthorizationViewRedirectionFilter.java:24)
         org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)
         org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)I think I'm having a Navigation problem, because Navigation of JSF2.0 has new features but I did search and research about it and nothing worked.
    I deleted the FaceletViewHandler tag from faces-config 'cause is not compatible with JSF2.0
    <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
    Anyone knows what possible I can be doing wrong?
    Here's my faces-config:
    <?xml version="1.0" encoding="UTF-8"?>
    <faces-config xmlns="http://java.sun.com/xml/ns/javaee"
                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd"
                  version="2.0">
    <application>
         <el-resolver>org.springframework.web.jsf.el.SpringBeanFacesELResolver</el-resolver>
         <locale-config>
              <default-locale>pt_BR</default-locale>
              <supported-locale>en</supported-locale>
              <supported-locale>es</supported-locale>
         </locale-config>
         <message-bundle>messages</message-bundle>
    </application>
         <navigation-rule>
              <from-view-id>/tools/formLogin.xhtml</from-view-id>
              <navigation-case>
                   <from-outcome>success</from-outcome>
                   <to-view-id>/tools/index.xhtml</to-view-id>
                   <redirect />
              </navigation-case>
         </navigation-rule>
         <navigation-rule>
              <from-view-id>/tools/formForgotPassword.xhtml</from-view-id>
              <navigation-case>
                   <from-outcome>success</from-outcome>
                   <to-view-id>/tools/forgotPasswordSuccess.xhtml</to-view-id>
                   <redirect />
              </navigation-case>
         </navigation-rule>
    </faces-config>Please I'm trying about 2 days...any ideas?
    TKS!

    so once the VM Enviroment is set for 11.1.2.1
    i can just used the Essbase EAS Wizards
    to bring the Applications and Other Objects into the new Enviroment 11.1.2.1
    and then Export the Data from the old Enviroment 11.1.2
    and import into the new Enviroment 11.1.2.1
    Correct ????
    Edited by: Next Level on Jul 28, 2011 7:53 AM
    Edited by: Next Level on Jul 28, 2011 7:57 AM
    Edited by: Next Level on Jul 28, 2011 7:57 AM

  • ADF Faces (Trinidad?) & Facelets Support

    This is long, but help and advice is very much needed.
    My programming team is facing a migration from UIX to JSF (ADF Faces) for future applications and we have hit a road block in regards to a template structure that is easy to use and maintain. We had gone through official Oracle training with JSF, however the trainer's answer to templates was to "create a template and copy and paste for every new file". For our team this is unacceptable so I've been charged with figuring out how to simply templates for our team. Not only do we need to make this easy for our application developers but we need to keep it simple for web developers to create "simple" survey-like applications.
    From what I've come across the answers seems to be either Facelets or Regions.
    Working with Regions seem to be over-complicated, requiring too much replication (basically back to copy/pasting an entire template) or passing the panelPage's content as a java object (bad for our web developers). I presented the combinations to my team and supervisor and it was agreed that Regions are impractical for our development practices.
    So it seems the answer is with Facelets. The problems I have with this is that:
    1. JDeveloper doesn't appear to natively handle Facelets, or include the libraries.
    2. From what I've learned, the ADF Faces library that comes with JDeveloper doesn't have Facelets support either.
    3. Looking into Trinidad, Facelets support exists but there is a lack of the Oracle skin.
    Facelets support is really what my team needs, as it's the closest thing to the old UIX templates I've seen so far.
    I've followed instructions/examples on several posts here, but I've yet to come across an example that works. I've Googled countless pages and examples, but when it comes down to ADF Faces and Facelets, it seems I'm at a dead end.
    So, can anyone help me with this?
    Thanks in advance,
    Rick
    PS:
    Using JDeveloper 10.1.3.2.0.4066 with stock ADF Faces
    External libraries used:
    Facelets 1.1.11
    Trinidad 1.0.1-incubating

    It just so happens that not long after I posted, I catch the "adf-facelets.jar" on the facelets site.
    dvohra, I had seen the links you've pasted however none of them described the actual process to get it to work, it's all been segmented copy/paste instructions. This doesn't really help someone who is struggling.
    So... I'll paste what my solution was, hopefully this will help others:
    1. Download and install the Facelets 1.1.11 library
    https://facelets.dev.java.net/servlets/ProjectDocumentList?folderID=3635&expandFolder=3635&folderID=0
    2. Download and install the ADF Facelets library
    https://facelets.dev.java.net/servlets/ProjectDocumentList?folderID=3990&expandFolder=3990&folderID=0
    3. In web.xml add the following:
    <context-param>
    <param-name>oracle.adf.view.faces.ALTERNATE_VIEW_HANDLER</param-name>
    <param-value>com.sun.facelets.FaceletViewHandler</param-value>
    </context-param>
    4. Make sure your project's libraries have loaded your Facelets and ADF Facelets, as well as ADF Faces Runtime.
    5. Begin using UI Components as desired.
    Example: http://eugeneciurana.com/pastebin/pastebin.php?show=1308
    Extra notices:
    I had to comment out the following in my faces-config.xml as it conflicted with the web.xml setting:
    <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
    This is what worked for me, I hope this helps others out there.
    Thanks,
    Rick

  • Cannot create a region from a task flow containing facelets fragments in a

    hi
    Please consider ADF applications migrated from JDeveloper 11g R1 to 11g R2 [1].
    When using JDeveloper 11g R2 to create a task-flow containing facelets fragments and dropping it on an existing/migrated page (created using JDeveloper 11g R1) results in a message :
    "Cannot create a region from a task flow containing facelets fragments in a jspx page.".
    What would be "good guidelines" (do's and don't's) of using facelets aspects in an ADF application migrated from JDeveloper 11g R1 to 11g R2?
    - [1] e.g. specifically JDeveloper 11.1.1.6.0 to JDeveloper 11.1.2.4.0, see also forum thread "migration support from 11.1.1.6.0 to 11.1.2.4.0"
    at migration support from 11.1.1.6.0 to 11.1.2.4.0
    many thanks
    Jan Vervecken

    Thanks for your reply Timo.
    Timo Hahn wrote:
    ... just a wild guess: Oracle is lazy here. They did not expect too many people migrating from a running 11.1.1.6.0 or 11.1.1.7.0 to 11.1.2.4.0. ...Hmm ... maybe.
    ... We had this discussion before: is 11.1.2.4.0 a good migration target? ...Can you refer to that discussion exactly.
    It is not the same as in forum thread "choosing JDeveloper 11g R1 or JDeveloper 11g R2 "
    at choosing JDeveloper 11g R1 or JDeveloper 11g R2
    which does not talk about migration to 11g R2.
    ... My answer was and still is: No. ... I don't see a reason why to do a migration to 11.1.2.x. ...We are considering if a migration to 11g R2 will allow us to make our application "facelets ready", which could potentially allow easier migration to 12c .
    Altough Brian Fry (Oracle) wrote "Re: choosing JDeveloper 11g R1 or JDeveloper 11g R2", the "facelets considerations" in this current forum thread could suggest something different.
    ... I know that we have to migrate to 12c once it'll be available so why the extra step? ...There could be layout requirements that can be perceived to be more easily/flexibly implemented using facelets.
    A team could have resources available now, and maybe not in a couple of months (related to wanting/needing to use facelets, and related to the "perceived/expected complexity" of an 11g R1 to 12c migration compared to an 11g R2 to 12c migration).
    ... (you know how complex this can be) ...Maybe less knowing, and more trying to find out.
    ... in a couple of month when 12c is available. ...How do you know it will be only "a couple of month" before 12c is available. Do you have specific references that confirm this?
    many thanks
    Jan

  • Migrating from JSF 1.1 to 1.2

    Hi folks,
    My curent app uses JSF 1.1. I want to move to JSF1.2 which is the latest release. But when I try to deploy my app in Oracle App server after replacing new libs, I am getting error as
    Exception: NoClassDefFoundError: javax/el/ExpressionFactory
    Operation failed with error: javax/el/ExpressionFactory
    I am not able to go farward and I am complete stuck here. Please help me out how solve this migration problem,
    These are the steps I follwed in mgrating,
    1. Download JSF1.2 from net.
    2. Replace old jsf-api.jar , jsf-impl.jar with new jars.
    3. Packed(creating ear) and deployed...
    Please let me know whetehr any wrong in this process..
    Fast respose will be great !!!

    Thanks for your quick replay,
    Currently I don't know, whether My app server supoorts JSP2.1 and servlet2.5. I will check out this.
    Could you please tell how to add facelets to my app server. What are these facelet?
    Once agaian thanks for replay

  • Facelets + OGNL?

    I've migrated an older JSF app to Jdev 11 and run into a few problems with facelets, upgrading ADF Faces, etc.
    Most recently, all calls to Backing Bean methods fail because they are not requesting objects through standard getters/setters. On page load, some of these calls return strings, sets, even through taking parameters. I believe this was originally achieved using OGNL support.
    Is this correct?
    How can I get these calls to work again?
    Thanks for your time.

    Thanks John. I understand this may be a problem, so... assuming I'm prepared to migrate it to a technology that works well and will be around for many years, what should I do from here?
    It uses ADF Faces, with a Hibernate controller. Should I redesign it from the ground up with JSF?
    If possible it would be nice to reuse most of the xhtml code that I have.
    Two end questions:
    1. What technology to use for application longevity + ease of migration? straight JSF, Facelets, Struts etc.
    2. What kind of coding strategy can I use to accomplish calls like the one above? It calls a function to check a collection of permissions for a particular entity.

  • Technology migration and Project setup quick advice

    I'm working with a JDeveloper 10g Application Web application that uses the following technologies:
    JSF
    Oracle ADF
    Facelets
    Hibernate
    Bear with me, I'm fairly new to ADF and Jdeveloper. What is the best way to make a new project for this and migrate these technologies to current versions?
    Current Work:
    I have backed up the original project, but thought it would be best to start with a clean slate.
    1. I made a new Fusion Web Application and moved all of the source and resources over.
    2. I updated my old web.xml file to use trinidad and moved faces-config.xml to new project
    3. I edited the project properties so that the appropriate Libraries were included
    4. Then I moved other (jars) libraries over individually until all of the deps worked out
    5. Modified the adf imports in .java files to match the new trinidad paths
    End Goals:
    1. Edit .xhtml facelet files, easily drag/drop ADF components into them
    2. Not have some of my javascript show up as unreachable (mostly those in onclicks)
    3. Have the smoothest development process possible
    4. You tell me
    5. Use best practices and slowly eliminate deprecated calls
    6. Possibly fix PathSet class that is no longer found in trinidad
    Edited by: user12181728 on Nov 9, 2009 11:49 AM

    That seems to break facelets, not remove any old libraries, tags libs are not updated, java imports to faces still have to be changed, web.xml isn't updated for trinidad, and there is still no support for ADF drag and drop into facelet xhtmls. I might be over complicating the problem, but if that's the best way to go about it I would be glad to do that.
    On a side note, is facelets still good practice? If not is there any easy way to convert it to something else.

  • Trinidad Dialog Not Opening in new Window- 10 to 11g Migration

    I have an ADF 10 application, which has been migrated into 11g (Trinidad).
    I have an issue where my dialog window is opening in the same window, and not a new one. I have used the useWindow parameter and set ENABLE_LIGHTWEIGHT_DIALOGS to false so that a new window and not an Iframe is used. I have tried both true/false on this parameter.
    .jspx page
       <tr:commandNavigationItem text="Help" action="dialog:help"
                                              binding="#{backing_mainmenu.commandMenuItem11}" id="commandMenuItem11"
                                              useWindow="true" windowHeight="500" windowWidth="500"/>
    faces-config.xml
      <navigation-case>
          <from-outcome>dialog:help</from-outcome>
          <to-view-id>/help.jspx</to-view-id>
        </navigation-case>
    web.xml
        <context-param>
            <param-name>org.apahce.myfaces.trinidadinternal.renderkit.USER_DIALOG_POP</param-name>
            <param-value>true</param-value>
        </context-param>
        <context-param>
        <param-name>org.apache.myfaces.trinidad.ENABLE_LIGHTWEIGHT_DIALOGS</param-name>
        <param-value>false</param-value>
        </context-param>
        <context-param>
        <param-name>org.apahce.myfaces.trinidad.CACHE_VIEW_ROOT</param-name>
        <param-value>false</param-value>
        </context-param>
    Jdev: 11.1.2.4
    Java: 1.6.0_43
    Trinidad: 11.1.2.4

    Hi,
    doesn't sound right. Why is the Facelet setting added to your web.xml file? Did you mix Facelet files with JSPX documents? If so then this could be a cause
    Frank

  • 10.1.3 ADF migration & regions

    Hi,
    I've noticed that the ADF regions taglibs are not migrated to Trinidad. My applications make an extensive use of regions. Is there any future support planned for migrating adf regions ?
    Thanks,
    Seb.

    Hello Sebastien,
    Sorry for the late answer, I was actually browsing about regions because I failed to have Facelets work easily with data bindings and found this thread. Actually, Trinidad does support regions (not sure how functional it is either), but it's a secret feature that's flagged experimental, undomcumented and deprecated. Actually it's more than deprecated, it's not officially supported at all and, because of that, might get dumped at any time without any notice. It's so mainly because Trinidad has native Facelets support, which is superior and has community acknowledgment, whereas regions remains marginal. You can use the equivalent of region using the following (can be found in Trinidad demo code):
    In your page
    <tr:componentRef id="reg1" componentType="org.apache.myfaces.trinidaddemo.region.stock"
                  value="Watch this stock">
      <f:attribute name="symbol" value="XYZ"/>
      <f:attribute name="company" value="XYZ Incorp"/>
      <f:attribute name="amount" value="13.66"/>
      <f:facet name="action">
        <tr:commandButton text="Buy" disabled="true"/>
      </f:facet>
    </tr:componentRef>In WEB-INF/region-metadata.xml:
    <faces-config>
      <component>
        <component-type>org.apache.myfaces.trinidaddemo.region.stock</component-type>
        <component-class>
          org.apache.myfaces.trinidad.component.UIXRegion
        </component-class>
        <component-extension>
          <region-jsp-ui-def>/components/regions/stock.jspx</region-jsp-ui-def>
        </component-extension>
        <attribute>
          <attribute-name>symbol</attribute-name>
          <attribute-class>java.lang.String</attribute-class>
          <attribute-extension>
            <required>true</required>
          </attribute-extension>
        </attribute>
        <attribute>
          <attribute-name>amount</attribute-name>
          <attribute-class>float</attribute-class>
          <default-value>0</default-value>
        </attribute>
        <attribute>
          <attribute-name>company</attribute-name>
          <attribute-class>java.lang.String</attribute-class>
          <default-value>Default Company</default-value>
        </attribute>
        <attribute>
          <attribute-name>description</attribute-name>
          <attribute-class>java.lang.String</attribute-class>
          <default-value>Default Description</default-value>
        </attribute>
      </component>
    </faces-config>In the region page (here /components/regions/stock.jspx):
    <tr:componentDef var="stuff">
      <tr:panelBox text="Symbol:#{stuff.symbol} Company:#{stuff.company}">
        <tr:outputText value="#{stuff.description}"/>
        <tr:outputFormatted
          value="<br>Current Value:<b>$#{stuff.amount}</b>"/>
        <tr:outputFormatted rendered="#{not empty bindings}"
          value="<br>Value attribute is:#{bindings}"/>
        <tr:facetRef facetName="action"/>
      </tr:panelBox>
    </tr:componentDef>For now it's part of the JAR, so it's available. It's far from the best solution, but it'll most likely provide what you need for a first migration phase. Moving to either Facelets or 11g templates is probably going to be mandatory in the future but, who knows, if you're lucky enough, that future could be far enough for some templating standard to emerge, possibly with JSF 2.0, see https://javaserverfaces-spec-public.dev.java.net/proposals/JSF-2_0-draft.html.
    Regards,
    ~ Simon

  • Help on deciding version for migration

    Hi,
    Currently we are having a commissions applications developed in ADF 11.1.1.4. This application has 200+ pages and has around 150-200 users during peakload time.
    The database consists of 10's of millions of records in few tables and performance is very critical for users to process commissions and promo's.
    Now we are planning to migrate from ADF 11.1.1.4 to ADF 11.1.2.3.0 or ADF 11.1.2.2.0. Please let us know which one is better in terms of View layer performance and also suggest which version is more safer to migrate.
    It would be great If you can provide references or pointers which will help me decide the version.
    Thanks,
    Naresh

    The improvements from 11.1.1.7.0 are not available in 11.1.2.x. They use current techniques to improve performance. The R1 (11.1.1.x) version use a new skin which is smaller and more responsive java script. R2 uses jsf2.0 and facelets but are on the older skin.
    Hard to tell which one will perform better, as this depends on your ui and how you built it.
    Before you migrate I would advise to make a small test car in each version. Then you see first hand what task you have to do and which version suits your needs better.
    My personal view is that you should stay with R1. This is because going to R2 it's not as easy as just open the project in a new Jdev version. There are many changes under the hood which might cause trouble and are not always obvious. The R1 versions are used b by fusion applications, do you can assume that new features from the upcoming 12c version will be back ported to R1. This has been the case for many features you now see in 11.1.1.7.0. R2 is not feature complete, meaning that it only comes with adf, no soa and other stuff. Right now out does not matter to you, but once you started migration to R2 and you get a requirement which best is done with soa, you are struck.
    Timo

Maybe you are looking for