[
http://jira.jboss.com/jira/browse/JBWS-2240?page=comments#action_12419066 ]
Dimitris Andreadis commented on JBWS-2240:
------------------------------------------
With Heiko away I suppose Alessio is dealing with it, right?
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
Priority: Blocker
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/te...
--
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