Bug 779866 - (SOA-2225) Riftsaw is unable to invoke services exposed via SOAPProcessor.
Riftsaw is unable to invoke services exposed via SOAPProcessor.
Status: CLOSED NOTABUG
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB (Show other bugs)
5.1.0.dev2
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Default User
http://jira.jboss.org/jira/browse/SOA...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-11 07:00 EDT by Marek Baluch
Modified: 2010-08-19 11:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-19 11:34:29 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
reproducer.zip (893.92 KB, application/zip)
2010-08-11 11:53 EDT, Marek Baluch
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker SOA-2225 None None None Never

  None (edit)
Description Marek Baluch 2010-08-11 07:00:31 EDT
project_key: SOA

See linked issue.
Comment 1 Marek Baluch 2010-08-11 07:00:49 EDT
Link: Added: This issue depends JBESB-3457
Comment 2 Kevin Conner 2010-08-11 08:48:01 EDT
The body contents are not Serializable, so cannot be marshalled by the ESB.

JBESB issue has been rejected.
Comment 3 Kevin Conner 2010-08-11 08:53:08 EDT
The question that needs to be answered is what is being places in the body to prevent this?

The response from the SOAPProcessor action should be a String or byte[], both Serializable.  Add a SystemPrintln to your service and see what is being passed within the body.
Comment 4 Marek Baluch 2010-08-11 10:58:52 EDT
The SOAPProcessor action will not be executed. The quickstart fails when the message is passed into the ESB from the jbr listener.
You are right that the object within the body is not serializable. It's a SOAPMessageImpl object. 
Comment 5 Marek Baluch 2010-08-11 11:53:30 EDT
Attached reproducer.

1) unzip to samples dir
2) ant deploy
3) ant deploy-process
4) ant sendhello
Comment 6 Marek Baluch 2010-08-11 11:53:31 EDT
Attachment: Added: reproducer.zip
Comment 7 Marek Baluch 2010-08-19 11:35:15 EDT
I have a working sample now so this issue is not relevant amymore.

Note You need to log in before you can comment on or make changes to this bug.