Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1092577

Summary: WAR deployment not possible when BPEL component is included
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Anton Giertli <agiertli>
Component: BPEL Integration, SwitchYardAssignee: tcunning
Status: CLOSED WORKSFORME QA Contact: Jiri Sedlacek <jsedlace>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: aileenc, atangrin, kejohnso, mbasovni, oskutka, soa-p-jira
Target Milestone: ---   
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: 2015-07-13 20:10:34 UTC 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 - say_hello none

Description Anton Giertli 2014-04-29 13:42:55 UTC 
Created attachment 890794 [details]
reproducer - say_hello

Description of problem:

It is not possible to deployed switchyard application package as war.

Version-Release number of selected component (if applicable):
FSW 6.0.0

How reproducible:
always

Steps to Reproduce:
1. Download attached reproducer
2. Deploy it onto running FSW instances


Actual results:
 Following exception will be displayed:
Caused by: java.lang.IllegalArgumentException: URI scheme is not "file"
        at java.io.File.<init>(File.java:421) [rt.jar:1.7.0_45]
        at org.switchyard.component.bpel.riftsaw.RiftsawBPELExchangeHandler.getDeployment(RiftsawBPELExchangeHandler.jav
a:196)

Deployment will not be succesfull.

Expected results:

Deployment is successful.

Additional info:

Culprit can be found probably here

https://github.com/jboss-switchyard/components/blob/master/bpel/src/main/java/org/switchyard/component/bpel/riftsaw/RiftsawBPELExchangeHandler.java
Comment 1 Anton Giertli 2014-04-29 14:37:28 UTC 
Please check also following combination

ear packaging jar with BPEL component
ear packaging war with BPEL component

Thanks,
Anton
Comment 2 Martin Basovník 2014-04-29 20:47:02 UTC 
One dirty workaround for this bug is adding of substring ".jar" into final archive name.
e.g.
<finalName>${project.artifactId}.jar</finalName>

@see https://github.com/jboss-switchyard/components/blob/master/bpel/src/main/java/org/switchyard/component/bpel/riftsaw/RiftsawBPELExchangeHandler.java#L164
Comment 3 Martin Basovník 2014-04-30 08:08:54 UTC 
1. ear packaging jar with BPEL component - WORKS
2. ear packaging war with BPEL component - DOES NOT WORK

There is similar workaround for usecase #2. There must be substring ".jar" in webModule bundle name.
Comment 5 tcunning 2015-07-13 20:10:34 UTC 
We are moving to JIRA to track issues with Fuse 6.2.1.   Logged https://issues.jboss.org/browse/ENTESB-3612 to track the handling of SY WAR deployments with BPEL components included.
Comment 6 JBoss JIRA Server 2015-07-20 15:50:04 UTC 
Tom Cunningham <tcunning> updated the status of jira ENTESB-3612 to Resolved