[
http://jira.jboss.com/jira/browse/JBWS-2240?page=comments#action_12419158 ]
Alessio Soldano commented on JBWS-2240:
---------------------------------------
I've built the ejb3 core module with the patch, however it doesn't solve the issue
because it adds the PortComponentSpec MD to the container, while the WebServiceDeclaration
looks for the annotation in the endpoint bean.
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: Alessio Soldano
Priority: Blocker
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/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