Skip to Main Content

Java Development Tools

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

How to resolve “Duplicate managed bean definition for XXX Class detected” (JDev 12c & JSF 2.2)

Mike IT GeekJan 14 2017 — edited Jan 15 2017

down votefavorite

I am pretty new to ADF and I developing a sample application with it. I just moved my code on another machine and started getting the below error. I tried hard to find out the root cause of it but no success as of now.

I have importing couple of JAR files offered by the head developer and built on top of it but as moved the code to another machine I started getting the bellow error.

The thing is that the imported JAR files are supposed to some bean classes for a unified toolbar stuff like that.

For some reason I started to get the bellow error message in the WebLogic log and tired hard to find and remove any possible double import of the JAR files but no luck as of now.

Your help and clues are much appreciate it.

Thank you,

Target URL -- http://127.0.0.1:7101/AssetVW-AssetVW-context-root/faces/testIndex.jsf
<oracle.adf.controller> <MetadataServiceImpl$Bootstrap> <logBeanWarnings> <ADFc: /META-INF/adfc-config.xml: Duplicate managed bean definition for CommonBean detected. Also defined in /META-INF/adfc-config.xml.>
<oracle.adf.controller> <MetadataServiceImpl$Bootstrap> <logBeanWarnings> <ADFc: /META-INF/adfc-config.xml: Duplicate managed bean definition for TabManagerBean detected. Also defined in /META-INF/adfc-config.xml.>
<oracle.adf.controller> <MetadataServiceImpl$Bootstrap> <logBeanWarnings> <ADFc: /META-INF/adfc-config.xml: Duplicate managed bean definition for KeyboardBean detected. Also defined in /META-INF/adfc-config.xml.>
<oracle.adf.controller> <MetadataServiceImpl$Bootstrap> <logBeanWarnings> <ADFc: /META-INF/adfc-config.xml: Duplicate managed bean definition for ToolbarFunctionsBean detected. Also defined in /META-INF/adfc-config.xml.>
<org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl> <ViewHandlerImpl> <_isTimestampCheckEnabled> <Apache Trinidad is running with time-stamp checking enabled. This should not be used in a production environment. See the org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION property in WEB-INF/web.xml>
line
1:6 no viable alternative at character ' '
line
1:10 no viable alternative at character ' '
line
1:22 no viable alternative at character ' '
line
1:6 no viable alternative at character ' '
line
1:10 no viable alternative at character ' '
line
1:22 no viable alternative at character ' '
line
1:6 no viable alternative at character ' '
line
1:10 no viable alternative at character ' '
line
1:22 no viable alternative at character ' '
line
1:6 no viable alternative at character ' '
line
1:10 no viable alternative at character ' '
line
1:22 no viable alternative at character ' '
line
1:6 no viable alternative at character ' '
line
1:10 no viable alternative at character ' '
line
1:22 no viable alternative at character ' '
line
1:6 no viable alternative at character ' '
line
1:10 no viable alternative at character ' '
line
1:22 no viable alternative at character ' '
line
1:6 no viable alternative at character ' '
line
1:10 no viable alternative at character ' '
line
1:22 no viable alternative at character ' '
line
1:6 no viable alternative at character ' '
line
1:10 no viable alternative at character ' '
line
1:22 no viable alternative at character ' '
line
1:6 no viable alternative at character ' '
line
1:10 no viable alternative at character ' '
line
1:22 no viable alternative at character ' '
<Jan 14, 2017 10:27:48 PM IRST> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read from it on 127.0.0.1:54,991 during the configured idle timeout of 5 seconds.>
<Jan 14, 2017 10:27:48 PM IRST> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read from it on 127.0.0.1:54,994 during the configured idle timeout of 5 seconds.>
<Jan 14, 2017 10:27:48 PM IRST> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read from it on 127.0.0.1:54,990 during the configured idle timeout of 5 seconds.>
<Jan 14, 2017 10:27:48 PM IRST> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read from it on 127.0.0.1:54,992 during the configured idle timeout of 5 seconds.>
<Jan 14, 2017 10:27:48 PM IRST> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read from it on 127.0.0.1:54,993 during the configured idle timeout of 5 seconds.>

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 12 2017
Added on Jan 14 2017
5 comments
1,088 views