[jboss-dev] Re: AS 5.1.Beta1 testsuite release criteria
Carlo de Wolf
cdewolf at redhat.com
Wed Mar 11 06:58:00 EDT 2009
The relevant bits:
10:18:11,223 WARN [MappedReferenceMetaDataResolverDeployer] Unresolved
references exist in
JBossWebMetaData:[#web-app:AnnotatedEJBReferenceMetaData{name=org.jboss.test.ejb3.servlet.servlets.EJBServlet/injectedSession,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
org.jboss.test.ejb3.servlet.Session30BusinessRemote},
#web-app:AnnotatedEJBReferenceMetaData{name=org.jboss.test.ejb3.servlet.servlets.EJBServlet/injectedStateful,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
org.jboss.test.ejb3.servlet.StatelessLocal}]
10:18:11,246 INFO [TomcatDeployment] deploy, ctxPath=/ejb3-servlet
10:18:11,280 WARN [WebEJBRemoteHandler] EJBTHREE-1289: Using legacy
EjbEncInjector, because mappedName for enc
"env/org.jboss.test.ejb3.servlet.servlets.EJBServlet/injectedSession",
field "null" is null
(container.environmentRefGroup.annotatedEjbReferences =
[AnnotatedEJBReferenceMetaData{name=org.jboss.test.ejb3.servlet.servlets.EJBServlet/injectedSession,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
org.jboss.test.ejb3.servlet.Session30BusinessRemote},
AnnotatedEJBReferenceMetaData{name=org.jboss.test.ejb3.servlet.servlets.EJBServlet/injectedStateful,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
org.jboss.test.ejb3.servlet.StatelessLocal}])
10:18:11,281 WARN [WebEJBRemoteHandler] EJBTHREE-1289: Using legacy
EjbEncInjector, because mappedName for enc
"env/org.jboss.test.ejb3.servlet.servlets.EJBServlet/injectedStateful",
field "null" is null
(container.environmentRefGroup.annotatedEjbReferences =
[AnnotatedEJBReferenceMetaData{name=org.jboss.test.ejb3.servlet.servlets.EJBServlet/injectedSession,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
org.jboss.test.ejb3.servlet.Session30BusinessRemote},
AnnotatedEJBReferenceMetaData{name=org.jboss.test.ejb3.servlet.servlets.EJBServlet/injectedStateful,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
org.jboss.test.ejb3.servlet.StatelessLocal}])
10:18:11,291 ERROR [TomcatDeployment] ENC setup failed
java.lang.IllegalStateException: Resolution should not happen via
injection container
at
org.jboss.web.tomcat.service.TomcatInjectionContainer.getEjbJndiName(TomcatInjectionContainer.java:654)
It's a war deployment which want references from a jar that's previously
deployed. Since the MRMDRD doesn't do cross deployment resolving the
test fails.
The idea is to have an EjbReferenceResolver in the same way there is a
PeristenceUnitDependencyResolver which can search the whole application
server for EJBs. Don't use the FirstMatchEjbReferenceResolver, because
it doesn't take scoping rules into account.
Carlo
Carlo de Wolf wrote:
> After that one, injection in servlets fails. The deployment fails
> because the environment entries from
> MappedReferenceMetaDataResolverDeployer don't line up and thus it
> rumbles into legacy code which is dependant on the deployment order.
>
> Carlo
>
> Carlo de Wolf wrote:
>> Jason T. Greene wrote:
>>> Dimitris Andreadis wrote:
>>>> Given the current good status of the TCK (near 100%), are we
>>>> shooting for "clean" runs for the rest of the testsuites (minus the
>>>> jdk specific/transient failures):
>>>>
>>>> JBoss-AS-5.1.x-testSuite-openjdk6
>>>> JBoss-AS-5.1.x-testSuite-sun15
>>>> JBoss-AS-5.1.x-testSuite-sun15-jts
>>>> JBoss-AS-5.1.x-testSuite-sun15-secmgr
>>>> JBoss-AS-5.1.x-testSuite-sun15-sun16
>>>> JBoss-AS-5.1.x-testSuite-sun16
>>>>
>>>> Currently, we are roughly at ~15 failure each, so we should start
>>>> working on those ASAP.
>>>
>>> Yeah I was just started looking into these today. Most of these are
>>> related to the currently in-progress profile service work.
>>>
>>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.1.x-testSuite-sun15/lastBuild/testReport/
>>>
>>>
>>> The rest are:
>>> 2 transaction failures - (likely due to the upgrade to 4.6)
>>> 2 EJB3 issues - both failing to access a servlet
>> Old leftover fork of HttpUtils, removing it now.
>> https://jira.jboss.org/jira/browse/JBAS-6556
>>> 1 serial UID mismatch - This looks like a problem with endorsed libs
>>>
>> Carlo
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
More information about the jboss-development
mailing list