Bug 780502 (SOA-2930) - Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears successful - but the service is actually not deployed (Riftsaw tech preview)
Summary: Deploying a misconfigured BPEL project to a SOA-P 5.1 server in JBDS 4.0 appe...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2930
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA
Assignee: Robert (Bob) Brodt
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-18 03:27 UTC by Len DiMaggio
Modified: 2011-09-30 20:09 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
JBDS 4.0, SOA-P 5.1 CR1
Last Closed: 2011-09-30 20:09:58 UTC
Type: Bug


Attachments (Terms of Use)


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

Description Len DiMaggio 2011-02-18 03:27:10 UTC
project_key: SOA

Platform issue for JBDS JIRA:  https://issues.jboss.org/browse/JBDS-1573

Comment 1 Len DiMaggio 2011-02-18 03:28:57 UTC
Link: Added: This issue is a dependency of JBDS-1573


Comment 2 Robert (Bob) Brodt 2011-04-04 17:41:20 UTC
fixed

Comment 3 Robert (Bob) Brodt 2011-04-04 17:41:20 UTC
Release Notes Text: Added: This error was caused by a missing deployment descriptor file (deploy.xml). A BPEL project must have a deployment descriptor file in order for the runtime to determine the process endpoints.


Comment 4 David Le Sage 2011-09-02 04:41:20 UTC
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Removed: This error was caused by a missing deployment descriptor file (deploy.xml). A BPEL project must have a deployment descriptor file in order for the runtime to determine the process endpoints. Added: https://issues.jboss.org/browse/SOA-2930

A missing deployment descriptor file (deploy.xml) was causing deployments to fail. (A BPEL project must have a deployment descriptor file in order for the runtime to determine the process end-points.) This file has now been added to the software.


Comment 5 Len DiMaggio 2011-09-30 20:09:58 UTC
Verified in JBDS 4.1


Note You need to log in before you can comment on or make changes to this bug.