Bug 1138605

Summary: Exception not thrown when remote SCA fails while unmarshalling object
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Martin Swiech <mswiech>
Component: SwitchYardAssignee: Tomohisa Igarashi <toigaras>
Status: MODIFIED --- QA Contact: Matej Melko <mmelko>
Severity: medium Docs Contact:
Priority: high    
Version: 6.1.0CC: dward, mvecera, rcernich, soa-p-jira
Target Milestone: DR4   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
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:
Embargoed:

Description Martin Swiech 2014-09-05 09:53:00 UTC 
Description of problem:
Remote SCA service is called with null object instead of throw exception. In case when unmarhalling input object fails.

Version-Release number of selected component (if applicable):
2.0.0.alpha2

How reproducible:
always

Steps to Reproduce:
1. Create some POJO class without default public contructor and use it as input parameter to remote Switchyard SCA service (using Java interface). 
2. Call this remote service (using HttpInvoker) with some not null input object.

Actual results:
Service is called with null parameter.

Expected results:
Some exception is thown about problematic POJO class (missing default constructor).
Comment 1 Martin Swiech 2014-09-05 10:14:30 UTC 
Description of problem:
Remote SCA service is executed with null object instead of throw exception. In case when unmarhalling input object fails.

Version-Release number of selected component (if applicable):
2.0.0.alpha2

How reproducible:
always

Steps to Reproduce:
1. Create some POJO class without default public contructor and use it as input parameter to remote Switchyard SCA service (using Java interface). 
2. Call this remote service (using HttpInvoker) with some not null input object.

Actual results:
Service is executed with null parameter.

Expected results:
Some exception is thown about problematic POJO class (missing default constructor).
Comment 2 Martin Swiech 2014-09-08 08:15:22 UTC 
Test case: https://drive.google.com/a/redhat.com/file/d/0By_A3B4ucTPCNjdGTURxNkxlTGs/edit?usp=sharing
Comment 3 David Ward 2014-10-29 20:39:47 UTC 
This is expected behavior.  The object should have a not-null constructor, as per the javabeans specification.  Please see my detailed notes on the attached jira: https://issues.jboss.org/browse/SWITCHYARD-2416
Comment 4 David Ward 2014-10-29 20:41:02 UTC 
I meant it needs to have a default, empty constructor. (I didn't mean "not-null", sorry...)