[EJB/JBoss] - Re: Migrating from jBoss4.0.5GA to 4.2.2GA
by nsmith80
"nsmith80" wrote : I'm trying to use 4.2.2GA for an EJB3 application that currently runs in 4.0.5GA without any major issues. I'm running into an issue where the app server is trying to use ejb-jar.xml file even though I don't use it. I get the following warnings when I start the server:
|
|
| | 008-02-26 13:34:22,737 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionRegionAdminDMALocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionRegionAdminStatsLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionRegionAdminUserLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionRegionAdminRegionLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAMgrCoachLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAMgrSchoolLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,752 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAMgrUserLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,768 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAMgrDMALocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,784 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserPlayerLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,784 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserCoachLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,784 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserGroupLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,784 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserGameLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,799 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserStatsLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,799 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserVenueLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,799 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserSchoolLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,815 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserSportLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,815 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserDMALocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,815 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserSeasonLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| | 2008-02-26 13:34:22,831 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.belo.leaderboard.ejb.session.function.ISessionDMAUserUserLocal in ejb-jar.xml of BeloAdminFactoryBeanduplicated in LeaderboardEJB.jar
| |
|
| It finally throws up toward the end of the deployment with the following error:
|
|
| | 2008-02-26 13:34:36,984 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
| |
| | --- MBeans waiting for other MBeans ---
| | ObjectName: jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminFactoryBean,service=EJB3
| | State: FAILED
| | Reason: java.lang.RuntimeException: could not resolve global JNDI name for @EJB for container BeloAdminFactoryBean: reference class: com.belo.leaderboard.ejb.session.function.ISessionDMAUserSeasonLocal ejbLink: duplicated in LeaderboardEJB.jar
| | I Depend On:
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminDMABean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminStatsBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminCoachBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserRegionBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAMgrAthleticDirectorBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserPositionBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAMgrDiv1AthleteBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=RegionAdminSeasonBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=RegionAdminGroupBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAMgrAlumBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminUserBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAMgrReportingGroupBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminSportBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserTeamBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=AuthenticationBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserMeetBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserTournamentBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=RegionAdminSchoolBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=RegionAdminVenueBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=DMAUserRosterBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminPlayerBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminGameBean,service=EJB3
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminRegionBean,service=EJB3
| | Depends On Me:
| | jboss.j2ee:ear=Leaderboard.ear,jar=LeaderboardEJB.jar,name=BeloAdminBean,service=EJB3
| |
|
| Does anyone have any ideas? Is there a way to keep jBoss from looking for the ejb-jar.xml file altogether?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132942#4132942
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132942
18 years, 1 month
[Remoting] - P2P Client Callback with streaming
by pat.chang1973
Hi,
We are keen to build a P2P server which allows multiple clients to register to the server. Each client call to the server should evoke a push to zero or many peers, who would have registered to the group chat earlier.
Question 1:
Is it possible to have each clients socket context connection saved in the server so that the server can do a push to the registered clients? I am not too sure if the pull / push callbacks are the right way to go forward. The "Mina" framework offers this feature, if I can remember right.
Question 2:
Will the client push from the server work for clients behind NAT firewall.
Question 3:
Secondly, we would also like to utilize the streaming feature to distribute documents among peers. Can the similar solution be used for streaming documents among group
Kindly advice,
Pat
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132930#4132930
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132930
18 years, 1 month
[JBoss Portal] - Re: How can I to include JavaScript files in Portlets to JBo
by swisst
Yeah, linking to a specific theme sounds like a bad idea as well!
I guess my point is that I have always treated each portlet as a unique entity, so the thought of one portlet being in charge of loading all of the JS for other portlets just feels really wrong.
For example, we use some JS libraries in our application, almost every portlet uses them, and they include the files in their jsp. We have taken the position that each portlet should be able to stand on its own, and we don't want to write a bunch of framework code to handle duplicate js files.
I guess that is an interesting question though, we better be sure that the JS namespace is not polluted with multiple functions of the same name. Additionally, different versions of the same library could cause issues as well. Even though our portlets stand on their own, the end javascript is all mingled together and processed by the browser. Maybe that's the reason for the JBoss javascript injection code!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132929#4132929
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132929
18 years, 1 month