| Summary: | Calling deliverSync on mep="OneWay" service causes handling the EPR as unresponsive | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | JBossESB | Assignee: | Mark Little <mark.little> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 Beta 1 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.2 Beta 2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-272 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-01-07 21:43:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jiri Pechanec
2008-01-04 10:09:12 UTC
Link: Added: This issue depends JBESB-1436 Specifying the EPR as unresponsive is the correct response. It is a coding error to make a synchronous call to an asynchronous service. Once we have proper service contract support then it will be possible to support this, until that point it is the developer's responsibility to be aware of the service contract. |