Bug 779229 (SOA-1622)

Summary: jboss-as/client dir should contain jars to enable applications to interact with ESB
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jiri Pechanec <jpechane>
Component: Build Process, DeploymentAssignee: Julian Coleman <jcoleman>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER3   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1622
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Jiri Pechanec 2009-11-20 12:44:04 UTC
Date of First Response: 2009-12-03 08:48:36
project_key: SOA

If a user is developing an application that interacts with ESB using ESB API it has to put on classpath different jars scattered all around the server.
It would be useful to have one directory that will contain all necessary JARs for this purpose in the similar manner as EAP client dir.

Comment 1 trev 2009-12-03 13:48:36 UTC
Leaving this till ESB 5 is incorporated, at the moment this would ivolve duplicating too many jars

Comment 2 Anne-Louise Tangring 2010-09-10 20:19:48 UTC
Moving to SOA 5.1.0 so that we can investigate if something can be documented while waiting for ESB 5.

Comment 3 Anne-Louise Tangring 2010-12-02 15:36:17 UTC
PM team decided this is a nice to have,  that will be done if time permits.

Comment 5 Dana Mison 2011-01-05 00:14:30 UTC
Writer: Added: dlesage


Comment 6 David Le Sage 2011-07-19 23:17:24 UTC
Release Notes Docs Status: Added: Not Yet Documented


Comment 7 David Le Sage 2011-09-27 23:50:56 UTC
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-1622

To make it easier for users to develop applications that interact with the ESB via the ESB API, all of the required JARs have now been relocated to a central jboss-as/client directory.  Previously, they had been scattered, requiring the user to add them to the class-path individually.