Bug 781063 (SOA-3549)

Summary: Port not found: null when assigning EPR on jbossws-native
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Gary Brown <gary.pi4tech>
Component: unspecifiedAssignee: Jim Ma <mail2jimma>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0.ER6   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3549
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
DynPartnerMain.bpel none

Description Gary Brown 2011-11-02 11:20:09 UTC 
project_key: SOA

This problem has been investigated as part of issue SOA-3466, although that issue now seems to be a different problem, so creating a separate bug report.

When running the dynpartner example (modified version attached), it results in the following exception:

6:36:32,500 ERROR [WebServiceClient] WS invocation failed
javax.xml.ws.WebServiceException: Cannot find port: null
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getEndpointMetaData(ServiceDelegateImpl.java:356)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.createDispatch(ServiceDelegateImpl.java:530)
at javax.xml.ws.Service.createDispatch(Service.java:437)
at org.jboss.soa.bpel.runtime.ws.WebServiceClient.getDispatcher(WebServiceClient.java:467)

This example works fine with riftsaw-2.3.1.Final on AS5.1+jbossws-native-3.4.0.SP1, with the modified xalan.jar from RIFTSAW-325.
Comment 1 Gary Brown 2011-11-02 11:24:40 UTC 
Modified version of example to use an explicitly provided URL straightaway, to overcome the cached EPR issue.
Comment 2 Gary Brown 2011-11-02 11:24:40 UTC 
Attachment: Added: DynPartnerMain.bpel
Comment 3 Douglas Palmer 2011-11-02 11:35:55 UTC 
Link: Added: This issue relates to SOA-3535