Bug 777756 (SOA-272) - Calling deliverSync on mep="OneWay" service causes handling the EPR as unresponsive
Summary: Calling deliverSync on mep="OneWay" service causes handling the EPR as unresp...
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-272
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 Beta 1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 Beta 2
Assignee: Mark Little
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-04 10:09 UTC by Jiri Pechanec
Modified: 2008-01-07 21:43 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-07 21:43:46 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-272 0 None None None Never

Description Jiri Pechanec 2008-01-04 10:09:12 UTC 
Date of First Response: 2008-01-04 05:26:26
project_key: SOA

See JBESB-1436
Comment 1 Jiri Pechanec 2008-01-04 10:09:29 UTC 
Link: Added: This issue depends JBESB-1436
Comment 2 Kevin Conner 2008-01-04 10:26:26 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.