-
Bug
-
Resolution: Done
-
Major
-
None
-
None
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/
- blocks
-
JBAS-5384 Fix JBossWS regression for CR1
- Closed
- is blocked by
-
EJBTHREE-1449 Add PortComponent parsing to the EJBDescriptorHandler
- Resolved
- relates to
-
JBWS-1309 Support xml overrides for @WebContext and @EndpointConfig
- Closed