[ESBJAVA-4901] When ESB Receiving IDocs, and if those Idocs are not valid, then ESB should send back a error message to the SAP crm Created: 23/Sep/16  Updated: 23/Sep/16

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.8.1
Fix Version/s: FUTURE

Type: New Feature Priority: Normal
Reporter: Susankha Nirmala Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

When ESB Receiving IDocs from the SAP crm, and if those Idocs are not valid, Wso2 ESB is not sending any error message to the SAP crm.
Due to that SAP crm don't know whether that IDoc sent successful or not.






[ESBJAVA-4900] Casting error in admin service Created: 22/Sep/16  Updated: 22/Sep/16

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: 4.9.0
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Irange Thenuwara Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

esb 4.9.0


Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

A casting error occurred when the passed value in the request doesn't point to a registry while accessing BAMMediatorConfigAdmin.getBamServerConfig admin service.

Passed value should be validated to check availability of a registry.






[ESBJAVA-4902] Parsing Json in response Created: 22/Sep/16  Updated: 25/Sep/16

Status: Open
Project: WSO2 ESB
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Highest
Reporter: KAMIL UCHNAST Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: ESB
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Severity: Major
Estimated Complexity: Moderate
Test cases added: Yes

 Description   

When response has content type of "application/json" and body is one of:
true
false
null
"text"

there is an error with JsonUtil like this:
ERROR - JsonUtil #getNewJsonPayload. Could not save JSON payload. Invalid input stream found.
Error Code = 401002
Error Message = Payload is not a JSON string.

and it is treated as failure(but message is delivered, only response can`t be parsed). According to RFC 4627:

A JSON value MUST be an object, array, number, or string, or one of
the following three literal names:

false null true

Source

I think you expect only arrays or objects. It can be easily fixed with wrappers if you can`t deal with these values but don`t throw an error in this case.






[ESBJAVA-4899] publishEvent Mediator not working inside sequences invoked by Clone Mediator Created: 21/Sep/16  Updated: 21/Sep/16

Status: Open
Project: WSO2 ESB
Component/s: Mediators
Affects Version/s: 5.0.0
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Heshitha Hettihewa Assignee: Chanaka Fernando
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ESB 5.0.0


Severity: Major
Estimated Complexity: Moderate
Attachment License: I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0
Test cases added: No

 Description   

publishEvent mediator works fine with a DAS when invoked through a proxy directly. But when tried to invoke it through a clone mediator (proxy->clone->sequence->publishEvent) it gives this error

ERROR - PublishEventMediator Cannot mediate message. Failed to load event sink 'sampleEventSink'. Error: Event sink "sampleEventSink" not found
org.apache.synapse.SynapseException: Event sink "sampleEventSink" not found






Generated at Mon Sep 26 00:30:40 IST 2016 using JIRA 6.0.1#6096-sha1:e4a48bd73c6b8a4d99c824976ce5808b4c85857d.