February 2008 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Seeing incomplete deployment not failing again

by scott.stark＠jboss.org

I'm looking at why the javaee clients don't appear to be working, and again I'm seeing incomplete deployments not generating an exception. The client container has demands on beans that are not being satisfied, and is not being started. Because of that the clients fail to see any of the expected ENC entries. | 13:02:32,534 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=app-client.ear,jar=app-client.jar,name=test-client,service=EJB3 | 13:02:32,534 INFO [MCKernelAbstraction] with dependencies: | 13:02:32,534 INFO [MCKernelAbstraction] and demands: | 13:02:32,534 INFO [MCKernelAbstraction] jboss.j2ee:ear=app-client.ear,name=StatelessSessionBean,service=EJB3,* | 13:02:32,534 INFO [MCKernelAbstraction] Class:org.jboss.test.cts.interfaces.StatelessSession | ... | | There are all of these context that are in the notInstalled set: | [ServiceControllerContext@3f1e86da{name=jboss.j2ee:binding=message-driven-bean,jndiName=local/SubclassMDB@668531077,plugin=invoker,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@4d7456ab{idependOn=[]}}, AbstractKernelControllerContext@55006eec{ metadata=AbstractBeanMetaData@10e61c47{name=jboss.j2ee:ear=app-client.ear,jar=app-client.jar,name=test-client,service=EJB3 bean=org.jboss.ejb3.clientmodule.ClientENCInjectionContainer properties= constructor=MCKernelAbstraction$AlreadyInstantiated@6c3044f9{parameters= factory=AbstractValueMetaData@734a81fb{value=org.jboss.ejb3.MCKernelAbstraction$AlreadyInstantiated$Factory(a)209bc0df} factoryClass=org.jboss.ejb3.MCKernelAbstraction$AlreadyInstantiated$Factory factoryMethod=create} autowireCandidate=true demands=[jboss.j2ee:ear=app-client.ear,name=StatelessSessionBean,service=EJB3,*, Class:org.jboss.test.cts.interfaces.StatelessSession] supplies=[] depends=[]}name=jboss.j2ee:ear=app-client.ear,jar=app-client.jar,name=test-client,service=EJB3 target=null state=PreInstall depends=AbstractDependencyInfo@51938132{idependOn=[EjbLinkDemandMetaData$EjbLinkDemandDependencyItem@2b072375{name=jboss.j2ee:ear=app-client.ear,jar=app-client.jar,name=test-client,service=EJB3 dependsOn=null whenRequired=Described resolved=false demand=jboss.j2ee:ear=app-client.ear,name=StatelessSessionBean,service=EJB3,*}, AbstractDemandMetaData$DemandDependencyItem@61a8ec64{name=jboss.j2ee:ear=app-client.ear,jar=app-client.jar,name=test-client,service=EJB3 dependsOn=null whenRequired=Described resolved=false demand=Class:org.jboss.test.cts.interfaces.StatelessSession}] unresolved=[EjbLinkDemandMetaData$EjbLinkDemandDependencyItem@2b072375{name=jboss.j2ee:ear=app-client.ear,jar=app-client.jar,name=test-client,service=EJB3 dependsOn=null whenRequired=Described resolved=false demand=jboss.j2ee:ear=app-client.ear,name=StatelessSessionBean,service=EJB3,*}, AbstractDemandMetaData$DemandDependencyItem@61a8ec64{name=jboss.j2ee:ear=app-client.ear,jar=app-client.jar,name=test-client,service=EJB3 dependsOn=null whenRequired=Described resolved=false demand=Class:org.jboss.test.cts.interfaces.StatelessSession}]}}, ServiceControllerContext@db25e1a{name=jboss.j2ee:binding=message-driven-bean,jndiName=local/SubclassMDB@1597557146,plugin=invoker,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@1937cb53{idependOn=[]}}, ServiceControllerContext@3e0c192f{name=jboss.j2ee:jndiName=local/StrictlyPooledMDB@1346358504,plugin=pool,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@1e05c314{idependOn=[]}}, ServiceControllerContext@3976d4a4{name=jboss.j2ee:jndiName=local/SubclassMDB@1597557146,plugin=pool,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@c4a6572{idependOn=[]}}, ServiceControllerContext@f398e0b{name=jboss.j2ee:binding=message-driven-bean,jndiName=local/StrictlyPooledMDB@779224170,plugin=invoker,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@684a25ab{idependOn=[]}}, ServiceControllerContext@71d8c699{name=jboss.j2ee:jndiName=local/StrictlyPooledMDB@606641551,plugin=pool,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@5bef330a{idependOn=[]}}, ServiceControllerContext@4ade2483{name=jboss.j2ee:jndiName=local/SubclassMDB@131296547,plugin=pool,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@350004ad{idependOn=[]}}, ServiceControllerContext@29fc9a67{name=jboss.j2ee:binding=message-driven-bean,jndiName=local/StrictlyPooledMDB@606641551,plugin=invoker,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@1433150a{idependOn=[]}}, ServiceControllerContext@ec11fc2{name=jboss.j2ee:binding=message-driven-bean,jndiName=local/SubclassMDB@131296547,plugin=invoker,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@25aa4de2{idependOn=[]}}, ServiceControllerContext@1732e9d5{name=jboss.j2ee:binding=message-driven-bean,jndiName=local/StrictlyPooledMDB@1346358504,plugin=invoker,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@4fdf43bf{idependOn=[]}}, ServiceControllerContext@24762cda{name=jboss.j2ee:jndiName=local/StrictlyPooledMDB@779224170,plugin=pool,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@4ad8d990{idependOn=[]}}, ServiceControllerContext@374f2c8b{name=jboss.j2ee:jndiName=local/SubclassMDB@668531077,plugin=pool,service=EJB target=null state=Configured mode=Manual requiredState=Configured depends=AbstractDependencyInfo@62b3a353{idependOn=[]}}] | I'm assuming there is some change in naming that is causing the problem, but this should be resulting in a failed deployment. I thought we had that issue fixed? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132998#4132998 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132998

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: webservices ejb3 api usage

by ALRubinger

"heiko.braun(a)jboss.com" wrote : Andrew, can you confirm that an indirect MC invocation is equivalent to an invocation through the EJB container? I cannot. Ping me online and we'll talk about it. "heiko.braun(a)jboss.com" wrote : One idea was to use something similiar to Container.resolveAnnotation(...), however I see that this part has been deprecated. What's the replacement for it? Container.getAnnotation(). "heiko.braun(a)jboss.com" wrote : I havn't spent much time on these issues lately, so any comments and ideas are welcome. Let me know what you need and I'll work with you to get you started. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132997#4132997 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132997

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: webservices ejb3 api usage

by ALRubinger

"heiko.braun(a)jboss.com" wrote : As long as EJB3 is in a state of flux I don't put my fingers on. I was going to wait until it consolidates and there's one codebase left. Pretend EJB3 Code in trunk doesn't exist, Heiko. At this point most of the stuff in there is just for compile-time constraints. The Projects location is where everything lives now. So go ahead and touch it, we won't bite. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132995#4132995 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132995

17 years, 10 months

1
0
0 / 0

[Design of JBoss Build System] - Re: source in localRepository

by pgier

There isn't any way to do it from settings.xml. You can use mvn dependency:sources Other than that I think you would have to modify the pom to have it done automatically. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132992#4132992 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132992

17 years, 10 months

1
0
0 / 0

[Design of JBoss Build System] - Re: source in localRepository

by scott.stark＠jboss.org

Can I enable this by default in my local settings.xml? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132976#4132976 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132976

17 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MC + JAXB (JBossXB Builder)

by alesj

This is now commited, and all the jaxb tests pass. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132972#4132972 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132972

17 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Implementing JAXB style parsing for aop-mc-int

by kabir.khan＠jboss.com

Related thread http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132662#4132662 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132964#4132964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132964

17 years, 10 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JcaXAResourceRecovery

by jhalliday

Right, time for a spot of thread necromancy... How is this going to work in AS 5.0? Having parts of the app server be aware of the recovery implementation in JBossTS is nasty. Likewise for having JBossTS be configured with recovery information for e.g. xa-datasource deployments in the AS. Personally I'd like to see an extension of the transactions spi to encompass an interface through which recovery information could be registered with the transaction manager. The alternative would seem to be holding that information on the AS side and defining the way in which the transaction manager accesses it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132941#4132941 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132941

17 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: FYI: MetaDataRepository will become a seperate project s

by kabir.khan＠jboss.com

"adrian(a)jboss.org" wrote : On a related issue, do you still reference this legacy class in AOP? | /quote] | | No View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132940#4132940 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132940

17 years, 10 months

1
0
0 / 0

[Design of POJO Server] - New ClassLoader project in JIRA

by adrian＠jboss.org

I've created a top level JIRA project for the ClassLoader. [url]http://jira.jboss.com/jira/browse/JBCL[url] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132932#4132932 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132932

17 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2008