LOL, great bug with faces-config.xml

Ok, its third time that I reinstall these stuff called JDeveloper.
Im tired of this! Unfortunately I cant work with Eclipse cauz it doesnt works with OC4J embed....
Image as follows shows these freakin' bug... LOL
http://img154.imageshack.us/img154/6268/jsfbugjn1.jpg

xml as follows:
there is no error! OMG... =/
<?xml version="1.0" encoding="windows-1252"?>
<!DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
"http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config xmlns="http://java.sun.com/JSF/Configuration">
<managed-bean>
<managed-bean-name>ProcessoCompraInit</managed-bean-name>
<managed-bean-class>com.seedts.cvc.site.processocompra.backbean.ProcessoCompraInit</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>ProcessoCompraSelecaoHoteis</managed-bean-name>
<managed-bean-class>com.seedts.cvc.site.processocompra.backbean.ProcessoCompraSelecaoHoteis</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>DestinosInit</managed-bean-name>
<managed-bean-class>com.seedts.cvc.site.destinos.backbean.DestinosInit</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>BuscaInit</managed-bean-name>
<managed-bean-class>com.seedts.cvc.site.busca.backbean.BuscaInit</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>TematicasInit</managed-bean-name>
<managed-bean-class>com.seedts.cvc.site.tematicas.backbean.TematicasInit</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>WebServiceConteudoBackBean</managed-bean-name>
<managed-bean-class>com.seedts.cvc.webservices.WebServiceConteudoBackBean</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>ProcessoCompra</managed-bean-name>
<managed-bean-class>com.seedts.cvc.site.processocompra.backbean.ProcessoCompra</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
<application>
<locale-config>
<default-locale>pt_BR</default-locale>
</locale-config>
<message-bundle>com.seedts.cvc.site.messageresource.MessageResources</message-bundle>
</application>
</faces-config>

Similar Messages

Problem w.r.t. JSF 2.0 with faces-config.xml

Hi All,
I am trying to evaluate the features of JSF2.0.
For that, I have created a very simple application with "JSF 2.0.2".
There is a page that displays a composite component and some other form related components (inputtext, commandbutton).
When I deploy my application without any faces-config.xml file, everything renders perfectly fine.
When I deploy the app with faces-config.xml (even an empty one without any configuration), none of the components get rendered.
Only the html elements get displayed.
I need to define some navigation-rules in my config file. I am not sure how to go further from here.
The app server I am using for deploying my app is GlassFish(v3).
Any help or pointers towards solving my problem are highly appreciated.
You can find the xhtml file, etc of my project below.
Thank you,
With best regards,
Praveen
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app 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-app_2_5.xsd" version="2.5">
     <context-param>
          <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
          <param-value>.xhtml</param-value>
     </context-param>
     <servlet>
          <servlet-name>Faces Servlet</servlet-name>
          <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
          <load-on-startup>1</load-on-startup>
     </servlet>
     <servlet-mapping>
          <servlet-name>Faces Servlet</servlet-name>
          <url-pattern>*.jsf</url-pattern>
     </servlet-mapping>
</web-app>
faces-config.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN" "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config xmlns="http://java.sun.com/JSF/Configuration">
</faces-config>
resources->acicomp->namesection.xhtml
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:ui="http://java.sun.com/jsf/facelets"
      xmlns:f="http://java.sun.com/jsf/core"
      xmlns:h="http://java.sun.com/jsf/html"
      xmlns:composite="http://java.sun.com/jsf/composite">
<composite:interface>
</composite:interface>
<composite:implementation>
     <h:panelGroup>
     <h:panelGrid columns="2">
          <h:outputText value="Name: "/>
          <h:inputText value="myName"/>
          <h:outputText value="Company: "/>
          <h:inputText value="myComp"/>
     </h:panelGrid>
     </h:panelGroup>
</composite:implementation>
</html>
index.xhtml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:h="http://java.sun.com/jsf/html"
      xmlns:aci="http://java.sun.com/jsf/composite/acicomp">
<h:head>
     <title>JSF Test Program</title>
</h:head>
<h:body>
     <p>My Simple Test Program</p>
        <h:form id="testForm" >
            <p>TEST</p>
            <aci:namesection></aci:namesection>
            <h:inputText id="username" value="John" />
            <h:commandButton id="submit" action="response" value="Submit"/>
        </h:form>
</h:body>
</html>

I found the problem.
The dtd location of the faces-config.xml had to be changed. It was pointing to the schema of 1.1.
With the following faces-config.xml, my application worked perfectly fine.
<?xml version="1.0"?>
<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">
</faces-config>

Bug in faces-config.xml parser?

According to the spec, the FactoryFinder is supposed to call the one-arg constructor taking the Abstract factory. For instance, I have this factory class:
public class ExtendedLifecycleFactory extends LifecycleFactory {
public ExtendedLifecycleFactory(LifecycleFactory base) {
    // this is supposed to be called by the FactoryFinder
public ExtendedLifecycleFactory() {
    // this is not
}And I have the following definition in my faces-config.xml:
<faces-config>
<factory>
    <lifecycle-factory>com.foo.ExtendedLifecycleFactory</lifecycle-factory>
</factory>
</faces-config>For some reason, my one-arg constructor isn't being called.
According to the FactoryFinder source, it appears that it maintains an internal list of all of the factories of a given type passed to it via the setFactory() method. Then, it starts at the last entry in the list (which should be the default implementation) and iterates through to the first one passing the previous implementation to each one in the iteration. Here is pseudo-code:
Factory prev = list.get(list.size() - 1);
for (int i = list.size() - 2; i >= 0; i--) {
prev = callOneArgFirstAndNoArgSecond(list.get(i), prev);
return prev;When I debugged the FactoryFinder, it appears that the parser for the faces-config.xml file never calls FactoryFinder.setFactory() with the default implementation. It seems that this is a bug since the JSF 1.0 spec lists this as the last step in finding a factory for the faces application.
Am I correct in this assumption?
I'm hoping Craig will answer this one as I've thoroughly done my homework! :-)

Hello,
Yes, you are correct, this was a problem with the 1.0 RI and has been corrected.
This fix will be made available with the next release.

Issue with faces-config.xml file

Hi,
I'm working on a project which needs more no. of JSF Pages and JSF Navigations,
But when i trying to creat pages more than 25 pages,the process becoming too slow,does this
effects the Application performance?Can any one suggest me why it happens and what are the
limitations for creating the JSF pages.
Does their any alternative to solve this Issue,I'm thing to create more faces-config.xml files as the
Jsf pages increases,does this solves?
Please suggest me.
Thank you,
Bandaru,

Hi Bandaru,
Are you trying to use the visual diagram option of faces-config? Coz i encountered difficulties when using it with many pages (more than 40) and the faces-config.oxd_faces was no longer able to support the diagram. "Solution" was to use only the overview and the sources of the faces-config. I don't know exactly but my problems were caused by the faces-config.oxd_faces and i don't think it affects performances for the application.
For information, that was on a Jdev 10.1.3.0.4
Regards,
Tif

How to configure multiple jsp files with diff beans in faces-config.xml??

Hi All,
I have 2 seperate jsp pages one is a login page and the other is the main application page.Now i am handling both the pages with seperate Bean class with respective setter and getter methods.How can i state the same in faces-config.xml file???..
Is the below way correct???
<?xml version='1.0' encoding='UTF-8'?>

<faces-config version="1.2"
    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_1_2.xsd">
    <managed-bean>
            <managed-bean-name>LoginForm</managed-bean-name>
            <managed-bean-class>useraccess.LoginForm</managed-bean-class>
            <managed-bean-scope>request</managed-bean-scope>
    </managed-bean>
    <navigation-rule>
            <from-view-id>/login.jsp</from-view-id>
        <navigation-case>
            <from-action>#{LoginForm.CheckValidUser}</from-action>
            <from-outcome>success</from-outcome>
            <to-view-id>/success.jsp</to-view-id>
        </navigation-case>
        <navigation-case>
            <from-action>#{LoginForm.CheckValidUser}</from-action>
            <from-outcome>fail</from-outcome>
            <to-view-id>/fail.jsp</to-view-id>
        </navigation-case>
    </navigation-rule>
    <managed-bean>
            <managed-bean-name>DSRApplication</managed-bean-name>
            <managed-bean-class>DSRApplication.LoginForm</managed-bean-class>
            <managed-bean-scope>request</managed-bean-scope>
    </managed-bean>
    <navigation-rule>
            <from-view-id>/DSR.jsp</from-view-id>
        <navigation-case>
            <from-action>#{DSRApplication.checkValidDateInAllFields}</from-action>
            <from-outcome>alldatasuccess</from-outcome>
            <to-view-id>/success.jsp</to-view-id>
        </navigation-case>
        <navigation-case>
            <from-action>#{DSRApplication.checkValidDateInAllFields}</from-action>
            <from-outcome>datafail</from-outcome>
            <to-view-id>/fail.jsp</to-view-id>
        </navigation-case>
    </navigation-rule>
</faces-config>Thanks in advance to all.
regards,
Viswanadh.

Thanks ejp for the reply.
Since i am a beginner even i dont know the exact reason to answer you for why am i using JSP with Facelets.Kindly provide me the suggestion and valuable information you have so that i can learn.
Apart from this i want to know whether the way provided in that faces-config.xml is possible or do we have a way to make that possible???
regards,
Viswanadh.

Error with adf-faces-config.xml file in myEclipse

hello,
i'm trying to customize appearance of my JSF/ADF Faces app (which worked fine until now), and tried to insert a adf-faces-config.xml file in my WEB-INF directory, this is it (copied from a tutorial) :
<?xml version="1.0"?>
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/view/faces/config">

<debug-output>true</debug-output>

<accessibility-mode>#{user.accessibilityMode}</accessibility-mode>


<skin-family>
#{view.locale.language=='en' ? 'minimal' : 'oracle'}
</skin-family>
</adf-faces-config>
after saving the file (in myEclipse) i get the following error message on the second line :
cvc-elt.1 : Cannot find the declaration of element 'adf-faces-config'
what does that mean and what should i do ?
thx...

hello,
i'm trying to customize appearance of my JSF/ADF
Faces app (which worked fine until now), and tried to
insert a adf-faces-config.xml file in my WEB-INF
directory, this is it (copied from a tutorial) :
<?xml version="1.0"?>
<adf-faces-config
xmlns="http://xmlns.oracle.com/adf/view/faces/config">

<debug-output>true</debug-output>

<accessibility-mode>#{user.accessibilityMode}</accessi
bility-mode>


<skin-family>
#{view.locale.language=='en' ? 'minimal' : 'oracle'}
</skin-family>
</adf-faces-config>
after saving the file (in myEclipse) i get the
following error message on the second line :
cvc-elt.1 : Cannot find the declaration of element
'adf-faces-config'
what does that mean and what should i do ?
thx...Hello again,
i'm still stuck with this, could somebody PLEASE give me a hint ?
thx,
dom.

Working with multiple faces-config.xml files

I would organize the menu definitions of my application in different faces-config.xml files. I would also put the label in different properties files.
The SRDemo application uses a unique properties file for the menu used in the el expression from the faces-config.xml.
Is it possible to have the same approach with not only one faces-config.xml file but has many faces-config.xml i want for my application.
If yes does the binding name to be different or may be the same for each file ?

We still have a litlle problem we don't find the reason. May be you can help us.
The second menu level never appear in the menu list. The menu list appear as empty.
The menu bar seem to be correct. We put twice the same model tree to be sure it was working well. Both menu appears. It is correct.
Here is our faces-config-menu-flexsystem.xml file
<?xml version="1.0" encoding="windows-1252"?>
<!DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
"http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config xmlns="http://java.sun.com/JSF/Configuration">
<managed-bean>
<description>Create menu item for flex system management</description>
<managed-bean-name>menu_menuitem_FlexSystem_Create</managed-bean-name>
<managed-bean-class>flex.view.util.MenuItem</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>label</property-name>
<value>#{resources['menu.FlexSystem.menuItem.create']}</value>
</managed-property>
<managed-property>
<property-name>viewId</property-name>
<null-value/>
</managed-property>
<managed-property>
<property-name>outcome</property-name>
<value>linkToCreateNewFlexSystem</value>
</managed-property>
</managed-bean>
<managed-bean>
<description>Manage menu item for flex system management</description>
<managed-bean-name>menu_menuitem_FlexSystem_Manage</managed-bean-name>
<managed-bean-class>flex.view.util.MenuItem</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>label</property-name>
<value>#{resources['menu.FlexSystem.menuItem.manage']}</value>
</managed-property>
<managed-property>
<property-name>viewId</property-name>
<value>\FlexHome.jspx</value>
</managed-property>
<managed-property>
<property-name>outcome</property-name>
<value>linkToManageFlexSystem</value>
</managed-property>
</managed-bean>
<managed-bean>
<description>Root menu item for flex system management</description>
<managed-bean-name>menu_menuitem_FlexSystem_Root</managed-bean-name>
<managed-bean-class>flex.view.util.MenuItem</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>children</property-name>
<list-entries>
<value-class>flex.view.util.MenuItem</value-class>
<value>#{menu_menuitem_FlexSystem_Create}</value>
<value>#{menu_menuitem_FlexSystem_Manage}</value>
</list-entries>
</managed-property>
<managed-property>
<property-name>label</property-name>
<value>#{resources['menu.FlexSystem.menuItem.root']}</value>
</managed-property>
</managed-bean>
<application>
<message-bundle>flex.view.resources.MenuFlexSystemProperties</message-bundle>
<locale-config>
<supported-locale>fr_CH</supported-locale>
</locale-config>
</application>
<managed-bean>
<managed-bean-name>resources</managed-bean-name>
<managed-bean-class>flex.view.util.ResourceAdapter</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
<navigation-rule>
<from-view-id>/FlexHome.jspx</from-view-id>
<navigation-case>
<from-outcome>linkToCreateNewFlexSystem</from-outcome>
<to-view-id>/CreateNewFlexSystem.jspx</to-view-id>
</navigation-case>
</navigation-rule>
<navigation-rule>
<from-view-id>/FlexHome.jspx</from-view-id>
<navigation-case>
<from-outcome>linkToManageFlexSystem</from-outcome>
<to-view-id>/ManageFlexSystem.jspx</to-view-id>
</navigation-case>
</navigation-rule>
<managed-bean>
<managed-bean-name>menu_FlexSystem</managed-bean-name>
<managed-bean-class>flex.view.util.MenuTreeModelAdapter</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>childProperty</property-name>
<value>children</value>
</managed-property>
<managed-property>
<property-name>listInstance</property-name>
<list-entries>
<value-class>flex.view.util.MenuItem</value-class>
<value>#{menu_menuitem_FlexSystem_Root}</value>
<value>#{menu_menuitem_FlexSystem_Root}</value>
</list-entries>
</managed-property>
</managed-bean>
<managed-bean>
<managed-bean-name>menuModel</managed-bean-name>
<managed-bean-class>flex.view.util.MenuModelAdapter</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>viewIdProperty</property-name>
<value>viewId</value>
</managed-property>
<managed-property>
<property-name>instance</property-name>
<value>#{menu_FlexSystem.model}</value>
</managed-property>
</managed-bean>
</faces-config>

Errors with jMaki faces-config.xml - Application won't run.

I'm getting a couple errors when trying to run my jMaki enabled applications. I tried for a week to find a solution, but not luck. Below is the server log. Does anyone have any ideas?
validateJarFile(C:\Documents and Settings\grover\netbeans\6.0\workspace\dAdmin\build\web\WEB-INF\lib\servlet.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Initializing Sun's JavaServer Faces implementation (1.2_04-b20-p03) for context '/dAdmin'
Attempt to set unsupported feature on XMLReader necessary for validation. Validation will bedisabled.
WebModule[/dAdmin]PWC1275: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
javax.faces.FacesException: Can't parse configuration file: jar:file:/C:/Documents%20and%20Settings/j/netbeans/6.0/workspace/dAdmin/build/web/WEB-INF/lib/jsfcompounds-core-0.0.6.jar!/META-INF/faces-config.xml: Error at line 4 column 99: Element type 'faces-config' was not declared
at com.sun.faces.config.ConfigureListener.parse(ConfigureListener.java:1438)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:348)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4515)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
[REMOVED LINES]
at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
PWC1306: Startup of context /dAdmin failed due to previous errors

ok, I changed the value to false. This all started when I updated my plugins. The original offending plugin appeared to jMaki.
Here is the version information for glassfish:
Starting Sun Java System Application Server 9.1 (build b58g-fcs) ...
CORE5098: AS Socket Service Initialization has been completed.
MBeanServer started: com.sun.enterprise.interceptor.DynamicInterceptor
CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.6.0_06] from [Sun Microsystems Inc.] Here is my original post, so you can see the evolution of this problem:
[http://forums.java.net/jive/thread.jspa?threadID=43941&tstart=0|http://forums.java.net/jive/thread.jspa?threadID=43941&tstart=0]
Here is the error after making the suggested changes to domain-web.xml:
validateJarFile(C:\Documents and Settings\grover\netbeans\6.0\workspace\dAdmin\build\web\WEB-INF\lib\servlet.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Initializing Sun's JavaServer Faces implementation (1.2_04-b20-p03) for context '/dAdmin'
WebModule[/dAdmin]PWC1275: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
javax.faces.FacesException: Can't parse configuration file: jndi:/server/dAdmin/WEB-INF/faces-config.xml: Error at line 17 column 9: Error at (17, 9: already parsing
        at com.sun.faces.config.ConfigureListener.parse(ConfigureListener.java:1438)
        at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:376)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4515)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:5176)
        at com.sun.enterprise.web.WebModule.start(WebModule.java:327)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
        at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1581)
        at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
        at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:182)
        at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:278)
        at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:974)
        at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:961)
        at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:464)
        at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
        at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
        at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)
        at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
        at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
        at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
        at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
        at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
        at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
        at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:744)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375)
        at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358)
        at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
        at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
        at $Proxy1.invoke(Unknown Source)
        at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
        at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
        at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
        at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
        at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
        at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:317)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198)
        at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:196)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:288)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:270)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
        at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
PWC1306: Startup of context /dAdmin failed due to previous errors

Can i make more than one faces-config.xml file ?

Can i make more than one faces-config.xml file under one project or application, if yes than how it will link.

Just that you know,
In the second week of july I was taking the Jdeveloper/Jheadstart course at Oracle Netherlands. During that course we were asked to split the faces-config. After splitting it, we were not able to find the navigation rules that were defined in the first faces-config in the web.xml. The Jdeveloper IDE was confused........
However, we were able to use the navigation rules (type in manualy) and that worked in the application.
I talked about it with Steven Davelaar and he thought it might be a bug. I don't know if it's reported, and I don't know if it's fixed.
So, if you get confused.... it works, but Jdeveloper might have some problems with it.
Luc Bors

Problem in faces-config.xml cycle detection

Hi,
I'm having the following problem in my jsf application. I have a loginMangager bean which holds a reference to the logged user and which is used by many other beans in my application. But in a particular situation I'm getting the following error:
SEVERE: JSF will be unable to create managed bean listaChecagemBean when it is requested. The following problems where found:
     - Managed bean mesaTarefasBean contains cyclic references. Evaluation path: mesaTarefasBean -> loginManager -> listaChecagemBean -> loginManager.My faces-config.xml looks like this:
<managed-bean>
    <managed-bean-name>loginManager</managed-bean-name>
    <managed-bean-class>
      br.gov.pgfn.efdv.mesa.view.login.LoginManagerBean
    </managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
</managed-bean>
<managed-bean>
    <managed-bean-name>listaChecagemBean</managed-bean-name>
    <managed-bean-class>
      br.gov.pgfn.efdv.mesa.view.ListaChecagemBean
    </managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    <managed-property>
      <property-name>loginManager</property-name>
      <value>#{loginManager}</value>
    </managed-property>
    <managed-property>
      <property-name>mesaTarefasBean</property-name>
      <value>#{mesaTarefasBean}</value>
    </managed-property>
    <managed-property>
      <property-name>listaChecagemFacade</property-name>
      <value>#{listaChecagemFacade}</value>
    </managed-property>
</managed-bean>
<managed-bean>
    <managed-bean-name>mesaTarefasBean</managed-bean-name>
    <managed-bean-class>br.gov.pgfn.efdv.mesa.view.MesaTarefasBean</managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    <managed-property>
      <property-name>loginManager</property-name>
      <value>#{loginManager}</value>
    </managed-property>
    <managed-property>
      <property-name>mesaTarefasFacade</property-name>
      <value>#{mesaTarefasFacade}</value>
    </managed-property>
</managed-bean>As you can see, there is not really a cycle here since the loginManagerBean does not depend on any other bean. If you think of it as directed graph, listaChecagemBean is connected to mesaTarefasBean and both of them are connected to the loginManagerBean, which is not connected to any other bean, it's a sink node.
I'm a missing something? Is this a bug?
I'm using JSF 1.2 RI 1.2_05 and Tomcat 6.0.
Thanks in advance,
Andr� Rodrigues

Hi Ryan,
I still problems with the release 1.2_07 which works fine with 1.2_04 when I use external beans through a custom el-resolver.
<?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_1_2.xsd"
     version="1.2">
     <application>
          <el-resolver>net.t_mobile.test.resolver.TestELResolver</el-resolver>
     </application>
     <managed-bean>
          <managed-bean-name>sessionBean</managed-bean-name>
          <managed-bean-class>net.t_mobile.test.beans.SessionBean</managed-bean-class>
          <managed-bean-scope>session</managed-bean-scope>
          <managed-property>
               <property-name>externalBean</property-name>
               <value>#{externalBean}</value>
          </managed-property>
     </managed-bean>
     <managed-bean>
          <managed-bean-name>dummyA</managed-bean-name>
          <managed-bean-class>net.t_mobile.test.beans.DummyBean</managed-bean-class>
          <managed-bean-scope>session</managed-bean-scope>
          <managed-property>
               <property-name>sessionBean</property-name>
               <value>#{sessionBean}</value>
          </managed-property>
     </managed-bean>
     <managed-bean>
          <managed-bean-name>dummyB</managed-bean-name>
          <managed-bean-class>net.t_mobile.test.beans.DummyBean</managed-bean-class>
          <managed-bean-scope>session</managed-bean-scope>
          <managed-property>
               <property-name>sessionBean</property-name>
               <value>#{sessionBean}</value>
          </managed-property>
          <managed-property>
               <property-name>parentBean</property-name>
               <value>#{dummyA}</value>
          </managed-property>
     </managed-bean>
</faces-config>
The dependencies are like follows:
dummyB.parentBean = dummyA
dummyB.sessionBean = sessionBean
dummyA.sessionBean = sessionBean
sessionBean.externalBean = externalBean (resolved through external el-resolver)
If I remove "dummyB" or the reference to externalBean no cycles are detected anymore.
Could you confirm this bug?
Regards,
Marc

How to specify multiple message bundles in faces-config.xml

Hi
I have different properties file which I want to use as message bundle.
Message.properties
Help.properties
When I specify this in faces-config.xml
<application>
<message-bundle>/Message</message-bundle>
<message-bundle>/Help</message-bundle>
</application>
and now when I try to use that in my jsp page like this
<f:loadBundle basename="/Message" var="message"/>
<f:loadBundle basename="/Help" var="help"/>
and access any messagestring from those files I can not excess either of them. But when I use only one of them it works fine.
Am I doing something wrong or I can not do this thing at all??
Thanks in advance.

I only specify one properties file in the <application> tag. That one is used for system messages. I have other properties files for labels, and another for just standard app text, so in my faces-config.xml I have something like this:
<application>
<message-bundle>message</message-bundle>
<locale-config>
<default-locale>en</default-locale>
</locale-config>
</application>
where my message.properties is used for system messages (validation, etc).
I don't list the other property files there. I have two more that I use, labels_en.properties, and standard_en.properties. Labels are words that have a : at the end or a *: for required fields. Standard are just other words that I use in my application. So on every page that I have, I start out with the following header:
<html>
<f:view locale="en_US">
<head>
<f:loadBundle basename="label" var="label"/>
<f:loadBundle basename="standard" var="standard"/>
<title>
.....

ADF:How to use NavigationHandler in Phase-Listener with adfc-config.xml

Hi,
in our application a user should be navigated to the login-page, when he tries to navigate directly to a page where he has no right for or if the session is expired.
Our navigation is complete in the adfc-config.xml. So I created a phase-listener, which is called by the adf-settings.xml.
Inside the phase-listener I'm checking the rights. If the user doesn't have the needed rights, he should be linked to the login page. But how can I do that?
Some days ago our navigation has been complete in the faces-config.xml. But now we moved the navigation to the adfc-config.xml, because we are sure that it's better. E.g. for using the dialog framework.
In the face-config.xml we had also the call of the phase-listener. There we did the forwarding like this and it worked:
FacesContext facesContext = FacesContext.getCurrentInstance();
facesContext.getApplication().getNavigationHandler().handleNavigation(facesContext, null, "login_page");But now I think I have to use the ADFContext somehow, or?
So how can I do that with the adfc-config.xml?
Thanks a lot for your help,
Bastian
I'm using JDeveloper 11g Release 1 (11.1.1.3.0)

Hello Frank,
thanks for your answer, but it doesn't really help me, because I'm a newbie, sorry.
Does your answer mean, that I should leave the call of the phase-listener in the faces-config and then I would also have access to the login-page, which is in the adfc-config?
Or does it mean, that I call now my phase-listener by adf-settings but don't have to change the phase-listener itself and can still use my code (FacesContext...)? But that's not working. I get no error but he is also not redirecting.
Maybe my problem starts on an earlier point.
Is it better to create all pages in the adfc-config or faces-config? (Maybe you have a good reference for reading about such a basic discussion)
I thought adfc-config would be the better one. But there I'm not able to redirect to another page (login) if somebody calls a special page without rights for example.
So my second basic question would be about the relation of adfc-config, faces-config and ADFContext and FacesContext.
Because I think it's not a short answer I hope you could give me also for this a reference so that I can read these basics myself.
Thanks a lot for helping a newbie becoming better :-)
Bastian

Error message in adf-faces-config.xml file in myEclipse

hello,
i'm trying to customize appearance of my JSF/ADF Faces app (which worked fine until now), and tried to insert a adf-faces-config.xml file in my WEB-INF directory, this is it (copied from a tutorial) :
<?xml version="1.0"?>
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/view/faces/config">

<debug-output>true</debug-output>

<accessibility-mode>#{user.accessibilityMode}</accessibility-mode>


<skin-family>
#{view.locale.language=='en' ? 'minimal' : 'oracle'}
</skin-family>
</adf-faces-config>
after saving the file (in myEclipse) i get the following error message on the second line :
cvc-elt.1 : Cannot find the declaration of element 'adf-faces-config'
what does that mean and what should i do ?
thx...

hello,
i'm trying to customize appearance of my JSF/ADF
Faces app (which worked fine until now), and tried to
insert a adf-faces-config.xml file in my WEB-INF
directory, this is it (copied from a tutorial) :
<?xml version="1.0"?>
<adf-faces-config
xmlns="http://xmlns.oracle.com/adf/view/faces/config">

<debug-output>true</debug-output>

<accessibility-mode>#{user.accessibilityMode}</accessi
bility-mode>


<skin-family>
#{view.locale.language=='en' ? 'minimal' : 'oracle'}
</skin-family>
</adf-faces-config>
after saving the file (in myEclipse) i get the
following error message on the second line :
cvc-elt.1 : Cannot find the declaration of element
'adf-faces-config'
what does that mean and what should i do ?
thx...Hello again,
i'm still stuck with this, could somebody PLEASE give me a hint ?
thx,
dom.

Faces-config.xml XML parser problem ???

I'm taking below error message when I was opening faces-config.xml file with diagram view, what's the exact solution of this problem???
Message
BME-99100: An error has been reported from the XML parser
Cause
The parse has reported the following error:
<Line 24, Column 2>: XML-20201: (Fatal Error) Expected name instead of <.
Action
Thanks for all...
Message was edited by:
user559176

I looked very well, there was'nt any error on line 24 about "<", I think if the size of faces-confic.xml file increased JDeveloper XML Parser cannot parse with high file size, what're other solutions?

More than one faces-config.xml

hi!
i am working in a big team, and would like to create more than one faces-config.xml file.
is it possible? how?

Yes!! You can create multiple faces-config.xml files.
Make changes in your deployment descriptor to include multiple faces config files:
<context-param>
     <param-name>javax.faces.CONFIG_FILES</param-name>
     <param-value>/WEB-INF/config/faces-config-one.xml,
     /WEB-INF/config/faces-config-two.xml,
     /WEB-INF/config/faces-config-three.xml,
     /WEB-INF/config/faces-config-four.xml</param-value>
</context-param>When there are too many modules, with many people working on the project simultaneously, having multiple faces config files makes it a lot more easier to manage.

LOL, great bug with faces-config.xml

Similar Messages

Maybe you are looking for