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).
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).
Test case: https://drive.google.com/a/redhat.com/file/d/0By_A3B4ucTPCNjdGTURxNkxlTGs/edit?usp=sharing
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
I meant it needs to have a default, empty constructor. (I didn't mean "not-null", sorry...)