[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2240) PortComponent from jboss.xml descriptor is not parsed

[Alessio Soldano (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBWS-2240?page=all ]

Alessio Soldano updated JBWS-2240:
----------------------------------

    Priority: Major  (was: Blocker)

> PortComponent from jboss.xml descriptor is not parsed
> -----------------------------------------------------
>
>                 Key: JBWS-2240
>                 URL: http://jira.jboss.com/jira/browse/JBWS-2240
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-integration
>            Reporter: Alessio Soldano
>         Assigned To: Heiko Braun
>         Attachments: JBWS-2240.patch
>
>
> I see this in EJBArchiveMetaDataAdapterEJB3.buildEnterpriseBeansMetaData(...) :
> ...
> while (it.hasNext())
>       {
>          WebServiceDeclaration container = it.next();
>          // TODO: Add PortComponent parsing to EJBDescriptorHandler
>          PortComponentSpec pcMetaData = container.getAnnotation(PortComponentSpec.class);
>          MessageDriven mdbMetaData = container.getAnnotation(MessageDriven.class);
>          EJBMetaData ejbMetaData = null;
> ...
> It seems to me the portComponent specified in jboss.xml (and available in the JBossEnterpriseBeanMetaData instance) is not read; this may result in the wrong endpoint address being set, which is the cause of this tck5 failure:
> http://hudson.qa.jboss.com/hudson/view/TCK5/job/tck5-webservices12/204/testReport/unknownTestSuite.0/packageTests/com.sun.ts.tests.webservices12.ejb.annotations.WSEjbWebServiceRefTest2/

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira