Hide Forgot
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.
Leaving this till ESB 5 is incorporated, at the moment this would ivolve duplicating too many jars
Moving to SOA 5.1.0 so that we can investigate if something can be documented while waiting for ESB 5.
PM team decided this is a nice to have, that will be done if time permits.
Writer: Added: dlesage
Release Notes Docs Status: Added: Not Yet Documented
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.