Bug 974079

Summary:	Namespace for bpel is of older version than for sca
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Jiri Sedlacek <jsedlace>
Component:	SwitchYard	Assignee:	Keith Babo <kbabo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Sedlacek <jsedlace>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.0 GA	CC:	kconner, ncross, oskutka, sdorfiel, soa-p-jira
Target Milestone:	DR6
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Users encountered problems when using BPEL in previous versions. The BPEL namespace in BPELComponentImplementationModel.java was not valid. This was due to an outdated SCA address. The issue has been fixed for this release.	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:

Description Jiri Sedlacek 2013-06-13 11:51:54 UTC

In org/switchyard/component/bpel/config/model/BPELComponentImplementationModel.java, 
namespace for bpel is http://docs.oasis-open.org/ns/opencsa/sca/200903.

If I use it in switchyard.xml, document is not valid (it can be seen in quickstarts/bpel_service/say_hello example, if I use http://docs.oasis-open.org/ns/opencsa/sca/200912 for bpel prefix (which is exactly the same as for sca prefix), service cannot be deployed. 

Can it be unified (probably on version 200912)?

Comment 1 Keith Babo 2013-06-18 19:53:04 UTC

This was fixed in 1.0.  In fact, the referenced class does not exist in 1.0 (it was moved to core with the other SCA standard schema).

Comment 2 Jiri Sedlacek 2013-07-01 10:21:28 UTC

verified in DR6

Comment 6 JBoss JIRA Server 2014-06-16 23:48:51 UTC

Keith Babo <kbabo> updated the status of jira SWITCHYARD-737 to Closed