Bug 779866 (SOA-2225) - Riftsaw is unable to invoke services exposed via SOAPProcessor.
Summary: Riftsaw is unable to invoke services exposed via SOAPProcessor.
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-2225
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.1.0.dev2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-11 11:00 UTC by Marek Baluch
Modified: 2010-08-19 15:35 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-19 15:34:29 UTC
Type: Bug

Attachments (Terms of Use)
reproducer.zip (893.92 KB, application/zip)
2010-08-11 15:53 UTC, Marek Baluch 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


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

Description Marek Baluch 2010-08-11 11:00:31 UTC 
project_key: SOA

See linked issue.
Comment 1 Marek Baluch 2010-08-11 11:00:49 UTC 
Link: Added: This issue depends JBESB-3457
Comment 2 Kevin Conner 2010-08-11 12:48:01 UTC 
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 12:53:08 UTC 
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 14:58:52 UTC 
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 15:53:30 UTC 
Attached reproducer.

1) unzip to samples dir
2) ant deploy
3) ant deploy-process
4) ant sendhello
Comment 6 Marek Baluch 2010-08-11 15:53:31 UTC 
Attachment: Added: reproducer.zip
Comment 7 Marek Baluch 2010-08-19 15:35:15 UTC 
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.