Bug 781063 (SOA-3549) - Port not found: null when assigning EPR on jbossws-native
Summary: Port not found: null when assigning EPR on jbossws-native
Keywords:
Status: NEW
Alias: SOA-3549
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: unspecified
Version: 5.2.0.ER6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Jim Ma
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-02 11:20 UTC by Gary Brown
Modified: 2011-11-03 08:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
DynPartnerMain.bpel (5.55 KB, application/octet-stream)
2011-11-02 11:24 UTC, Gary Brown 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 781051 0 high VERIFIED EPR cached on first use of partner link, which makes modifying the EPR part way through a session impossible 2021-03-29 22:51:15 UTC
Red Hat Issue Tracker SOA-3549 0 Major Closed Port not found: null when assigning EPR on jbossws-native 2013-05-14 08:14:59 UTC

Internal Links: 781051

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
Note You need to log in before you can comment on or make changes to this bug.