Bug 780633 (SOA-3073)

Summary: Please make Seam compatible with jBPM and ESB
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Rick Wagner <rwagner>
Component: SwitchYardAssignee: Keith Babo <kbabo>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: atangrin, ldimaggi, mrietvel, rwagner
Target Milestone: ---   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3073
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 780634 (view as bug list) Environment:
SOA-P, using Seam (all features), jBPM and ESB
Last Closed: 2014-02-25 13:16:58 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
EsbServiceHandler.java none

Description Rick Wagner 2011-05-16 20:13:03 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007Ax7SIAS&sfdc.override=1
project_key: SOA

In SOA-P 5.x there are classloader issues with jBPM, Seam and ESB.  (See https://issues.jboss.org/browse/SOA-1673 ).

Please make this right in SOA-P 6.0.  Users want to use all the features of Seam and jBPM, without compromises.  Thanks!
Comment 1 Rick Wagner 2011-06-08 21:07:52 UTC 
Customer-supplied fix, please consider this when crafting the Product solution.
Comment 2 Rick Wagner 2011-06-08 21:07:52 UTC 
Attachment: Added: EsbServiceHandler.java
Comment 3 Rick Wagner 2011-06-08 21:09:31 UTC 
Please note the above attached sample provided by our customer.  This client is happy with this solution, please consider it for inclusion (or it's behaviour for inclusion) when this feature is implemented.  Thanks.
Comment 5 Marco Rietveld 2014-02-24 20:49:40 UTC 
This bug should probably be closed before it gets too confusing: this had to do with jBPM *3* and jBoss *ESB*. 

As far as I know, both jBPM *5+* and *Switchyard* have nothing to do with this problem. This is strictly a SOA 5.x problem.
Comment 6 Rick Wagner 2014-02-25 13:16:58 UTC 
Hi Marco,

Agreed, thanks for the suggestion.

Regards,

Rick