Put several message-bundle in faces-config.xml

Hello,
I want to put several message bundle in faces-config.xml.
How can I do that?
I tried the following but it didn't worked
<application>
     <locale-config>
          <default-locale>fr</default-locale>
     </locale-config>
     <message-bundle>
          messages.Messages_fr
     </message-bundle>
     <message-bundle>
          messages.Messages_en
     </message-bundle>
</application>

the system will get automatically the right file depending on the Locale object , so you do not have to mention each file in the faces-config.xml
<locale-config>
<default-locale>fr</default-locale>
<supported-locale>en</supported-locale>
the supported locale is used by JSF when readind the HTTP header and depending on the language, it will choose the right mesages bundle
The best way to process is to bind the locale property of the tag <f:view locale=#{Bean.locale}> and to change it dynamically (see class Locale in the sun API)

Similar Messages

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>
.....

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.

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>

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>

Making navigation to an external page in faces-config.xml

Hi all,
I want to make a navigation to an external page in faces-config.xml, or for example to an absolute URL like www.oracle.com. Is there a way to put a navigation like this in faces-config.xml? As I know the <to-view-id> tag only references a relative page address on the ViewController project.
Thanks in advance,
S/\EE|)

I want to go to a page of another application (I've split my application into several applications) so I need to use absolute address. As the external page is part of my application, I want to see it in my faces-config in order to know the outgoing pages from my page and manage them when necessary.

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?

Splitting faces-config.xml into multiple parts

Hey Everybody,
I'm trying to split up my faces-config.xml file into application specific and deployment specific parts. I've managed to everything set-up so far but I'm having a problem with beans. I've got a bean which contains most of the application specific attributes but the problem is that some of the attributes are deployment specific and some are application specific.
In the past, I could get around this by having two faces-config.xml files which each defined the bean but only specified "their" attributes. But I've now found that I can only define the bean only once. The bean will get the attributes from one file but not the other. So how can I get around this? Could I do a faces-config.xml include statement? Do I have to create a deployment-specific bean?
Mark

We have been referencing the same managed bean in different faces-config.xml files for a couple of years and it really did work until the latest release of JDeveloper. What we had been doing was to put properties that would change between the development and deployed versions in different faces-config.xml files; the goal being to isolate all the properties that needed to be changed for deployment in a single file that we could automatically replace with Ant when we build the production release.
But just because it worked in the past doesn't mean that it was supposed to work.
Thanks,

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.

Forward to Tiles definition from faces-config.xml

Hello,
can anybody explain me how to make a forward to a Tiles definition from the faces-config.xml file? I�m using MyFaces with Tomahawk and Tiles, but I also tried with Jsf without myFaces and lots of combinations but I can�t fix it.
Here is my faces-config file:
<faces-config>
<navigation-rule>
<from-view-id>/pages/JP000.jsp</from-view-id>
<navigation-case>
<from-outcome>loginFrm</from-outcome>
<to-view-id>/JP002.tiles</to-view-id>
</navigation-case>
</navigation-rule>
<application>
<view-handler>org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl</view-handler>
</application>
</faces-config>
and this is the tiles-defs.xml:
<tiles-definitions>
     
     <definition name="general.menu"
          path="/pages/tiles/templates/general.menu.jsp">
          <put name="titleHTML" type="string"     value="mi_title" />
          <put name="menu" value="/pages/tiles/menu.jsp" />
     </definition>
     
     <definition name="JP002.tiles" extends="general.menu">
          <put name="titleHTML" type="string"     value="mi_title" />
          <put name="content" value="/pages/menus/JP002.jsp" />
          <put name="menu" value="0" />
     </definition>
</tiles-definitions>
Lots of thanks!!!!

Today I downloaded tomahawk-examples-1.1.5-bin. (http://myfaces.apache.org/download.html). They have one example with tiles, and it works the way I want it to.
I'm still trying to figure it out what is causing this behaviour.
At least, I tried to change the value they're using for linkage between <to-view-id> and tiles definition, and found that JSF is still ignoring the real value in <to-view-id>
: it was originally 'blah.jsp', but 'blah' or 'blah.tiles' worked the same way, while in tiles definition the corresponding name was always blah.tiles.
It seems that they are looking into tiles definitions first with the key composed of the first part of the value in <to-view-id> (before the dot) concatenated with hardcoded '.faces'.
I tried to change the key value in both config files to something like 'blah.ttt', and it did not work.
I'm not sure at the moment if this would be a problem for me, I may use this framework, knowing the limitations.
Also, I'll look into the code, if this may be altered and at what cost.
Still, the basic jsf problem with always interpreting the value in <to-view-id> as blah.jsp remains.

Muliple faces-config.xml

I am interesting in one web application project Can I have a 2 or 3 faces-config.xml? IF it possible, need anything additional configuration or parameters in xml file?

You can.
If the faces-config file is in the same project, then do:<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/faces-config.xml, /WEB-INF/another-faces-config.xml</param-value>
</context-param>If the faces-config file is in another imported JAR, then just put this one file in the META-INF of the JAR. In this case make sure that you have the DTD set to web-facesconfig_1_1.dtd and not 1_0.

Component and renderer can't share the same name in face-config.xml

Hi All,
I've noticed that a component and a renderer can't share the same name in <face-config.xml>.
For instance,
<component>
<component-type>tree</component-type>
<component-class>com.xxx.tree.component.Tree</component-class>
</component>
<render-kit>
<renderer>
<renderer-type>tree</renderer-type>
<renderer-class>com.xxx.tree.renderer.Tree</renderer-class>
</renderer>
</render-kit>
generates a cryptic error message.
It's not a big deal but would be nice to support it.
The workaround of course is to use a different name for the component and renderer (tree and treeRenderer for instance)
Stephane

i dont know why it doesn't work for you. It works for me alright. Can u elaborate on what error messages you are getting? It maybe some other problem.

Localization of adf faces-config.xml

I have defined my ADF process train component and menu items in my faces-config.xml. The definition has got the label for these components in the faces-config.xml How can I localize these labels so that I can support multiple languages. The managed bean for my process train component is
<managed-bean>
<managed-bean-name>customerInfo</managed-bean-name>
<managed-bean-class>view.faces.menu.PersonalTrackerMenuItem</managed-bean-class>
<managed-bean-scope>none</managed-bean-scope>
<managed-property>
<property-name>viewId</property-name>
<value>/customerinfo.jsp</value>
</managed-property>
<managed-property>
<property-name>label</property-name>
<value>Customer Information</value>
</managed-property>
<managed-property>
<property-name>outcome</property-name>
<value>guide.customerinfo</value>
</managed-property>
</managed-bean>
I would like to know how to get the Customer Information label from a properties file instead of hardcoding it in the faces-config.xml

Hi Frank
Thanks for your response. I understand that we need to use different locales but for this to work all the labels need to be parameterized to the properties file. This is straight forward when it comes to labels in the JSP pages where we load the bundle with
<f:loadBundle basename="myBundle.myBundle" var="sampleBundle"> and refer to a property as <f:commandButton value="#{sampleBundle.myButtonText}"/> my problem is how to do this when the label I want to parameterize is in the faces-config.xml

Parse error on adf-faces-config.xml

When I try to include the "adf-faces-config.xml" I get XML parse errors (see stack trace below). I'm using Jboss. ADF faces works fine, it's just when I try to include ths adf-faces-config.xml in web.xml.
Anyone sees what is wrong here? The web.xml entry does get read, and it does find the adf-faces-config.xml file mentioned, and it does start to parse. I also know that the config file is OK (I tried several sample files I found on the web, and I even manually verified againt the schema) ...
Rgds,
Falco Paul
web.xml:
<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/adf-faces-config.xml</param-value>
</context-param>
adf-faces-config.xml:
<?xml version="1.0"?>
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/view/faces/config">

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

<accessibility-mode>default</accessibility-mode>

<skin-family>oracle</skin-family>
</adf-faces-config>
Stack:
13:56:30,171 ERROR [Digester] Parse Error at line 2 column 73: Document root element "adf-faces-config", must match DOCT
YPE root "null".
org.xml.sax.SAXParseException: Document root element "adf-faces-config", must match DOCTYPE root "null".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at com.sun.faces.config.ConfigureListener.parse(ConfigureListener.java:1188)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:314)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
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:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5441)
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:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:332)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:85)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:374)
at org.jboss.web.WebModule.startModule(WebModule.java:62)
at org.jboss.web.WebModule.startService(WebModule.java:40)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy28.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:360)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:20
4)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
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:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:413)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
at org.jboss.Main.boot(Main.java:162)
at org.jboss.Main$1.run(Main.java:423)
at java.lang.Thread.run(Thread.java:534)
13:56:30,249 ERROR [Digester] Parse Error at line 2 column 73: Document is invalid: no grammar found.
org.xml.sax.SAXParseException: Document is invalid: no grammar found.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at com.sun.faces.config.ConfigureListener.parse(ConfigureListener.java:1188)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:314)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
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:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5441)
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:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:332)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:85)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:374)
at org.jboss.web.WebModule.startModule(WebModule.java:62)
at org.jboss.web.WebModule.startService(WebModule.java:40)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy28.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:360)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:20
4)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
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:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:413)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
at org.jboss.Main.boot(Main.java:162)
at org.jboss.Main$1.run(Main.java:423)
at java.lang.Thread.run(Thread.java:534)
13:56:30,483 WARN [Digester] [ManagedBeanRule]{faces-config/managed-bean} Merge(midmsClassification)

I found the "solution" myself.
You can't actually rfer to adf-faces-config.xml from web-inf.
I got this info from some website, but that was plain wrong.
The ad-faces-config.xml location is hardcoded (WEB-INF/ad-faces-config.xml).
Regards,
Falco

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

Put several message-bundle in faces-config.xml

Similar Messages

Maybe you are looking for