Bug 1087856

Summary: Local (non clustered) SCA invocation of service in different SwitchYard app runs in context of the invoker app
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Václav Chalupa <vchalupa>
Component: SwitchYardAssignee: Rob Cernich <rcernich>
Status: MODIFIED --- QA Contact: Matej Melko <mmelko>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: mvecera, oskutka, soa-p-jira
Target Milestone: DR1   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
reproducer none

Description Václav Chalupa 2014-04-15 13:04:00 UTC
Created attachment 886485 [details]
reproducer

When you have two SwitchYard applications deployed on the same server in non-clustered environment, first app defines SCA service binding and second references this service, ClassLoader in first app has the context of second (invoker) app.

Please see attached reproducer.

1 - sca-service-app defines sca service binding and reference to jpa binding to save received command.
2 - client app references sca-service-app and invoke it locally.

You can add breakpoint to Ejb3Configuration.java:315 and see the issue with ClassLoader. EntityManager for sca-service-app PU is creating and pom.xml in this app should be found, but pom.xml is looked in client-app, not in sca-service-app.