CWSAJ

CWSAJ0001E: The name parameter has not been specified and is required.
CWSAJ0002E: A bundle repository with the name {0} already exists.
CWSAJ0003E: The bundle repository at {0} is already defined as name {1}.
CWSAJ0006E: The bundle repository {0} does not exist.
CWSAJ0008E: The specified file {0} does not contain a valid bundle manifest.
CWSAJ0009E: The bundle {1} with version {2}, defined in the file {0}, already exists in the repository.
CWSAJ0010E: The specified bundle {0} with version {1} does not exist in the local bundle repository.
CWSAJ0011E: An internal error occurred. The repository generator service is not available from the OSGi service registry.
CWSAJ0012E: An internal error occurred. Cannot find the Launcher service.
CWSAJ0013E: Unable to obtain required feature capabilities for features like the JPA2 feature.
CWSAJ0014E: An internal error occurred. Attempted to generate an AriesApplicationModel object from a null application manifest.
CWSAJ0015E: An internal error occurred. Attempted to generate an AriesApplicationModel object from a null deployment manifest.
CWSAJ0016E: The name parameter has not been specified and is required.
CWSAJ0017E: The URL parameter has not been specified and is required.
CWSAJ0018E: It is not possible to model the Aries application {0} because some of its required components are still being downloaded.
CWSAJ0019E: An internal error occurred. Attempted to generate an AriesApplicationModel object from a non-file URL {0}.
CWSAJ0020E: An internal error occurred extracting bundle {0} from the Composite Bundle Archive, {1}.
CWSAJ0021E: A problem occurred processing the manifest for the Composite Bundle Archive, {0}.
CWSAJ0022E: Composite Bundle Archive, {0}, has a deployment dependency on another Composite Bundle Archive, {1}.
CWSAJ0023E: The following bundles that the Composite Bundle Archive, {0}, requires cannot be found in the internal bundle repository: {1}.
CWSAJ0024E: The CompositeBundle-Content header in Composite Bundle Archive {0} must contain only bundles with an exact version. The following entries are not valid: {1}.
CWSAJ0025I: OSGi application console Display commands: These commands work only if connected to a framework ss() - This command gives the summary information about the installed bundles. bundles() - This command gives comprehensive information about the installed bundles. packages() - This command gives information about the imported/exported packages. services() - This command gives information about the registered Services. bundle(<bundleID>) - This command gives information about the specified bundle headers(<bundleID>) - This command gives information about the headers associated with the specified bundle packages(<bundle ID>) - This command gives information about the exported packages for this bundle. packages(<package Name>) - This command gives information about the specified package. services(<service ID>) - This command gives information about the specified service. services(<OSGI Filter>) - This command gives information about the services matching the filter. refresh() - This command refreshes the internal OSGi application console cache with the latest information about the state of the framework. Framework commands: list() - This command lists the available frameworks that you can connect to. connect(<Framework id>) - This command connects to the specified framework. connect(<Bundle Name>, <Bundle Version>, <Node Name>, <Server Name>) - This command connects to the specified framework. Controlling Bundles: start(<bundleID>) - This command starts the requested bundle. stop(<bundleID> - This command stops the requested bundle.
CWSAJ0026E: Unable to get bundle information because you have not connected to a framework.
CWSAJ0027E: Unable to get service information because you have not connected to a framework.
CWSAJ0028E: Unable to find bundle with bundle ID {0}.
CWSAJ0029E: Unable to find service with service ID {0}.
CWSAJ0030E: Unable to get header information because you have not connected to a framework.
CWSAJ0031E: Bundle {0} is already started.
CWSAJ0032I: Bundle {0} started successfully.
CWSAJ0033E: Bundle {0} is already stopped.
CWSAJ0034I: Bundle {0} stopped successfully.
CWSAJ0035I: Connecting to framework {0} on node {1} and server {2}.
CWSAJ0036I: Successfully connected to framework {0}.
CWSAJ0037E: Unable to connect to a framework with ID {0}.
CWSAJ0038E: Unable to connect to a framework with framework name {0}, node name {1} and server name {2}.
CWSAJ0039I: Valid frameworks are:
CWSAJ0040I: Starting Bundle {0}.
CWSAJ0041E: Bundle {0} cannot start. It is currently in {1} state.
CWSAJ0042I: Stopping Bundle {0}.
CWSAJ0043E: Bundle {0} cannot stop. It is currently in {1} state.
CWSAJ0044E: Unable to find package with package ID {0}.
CWSAJ0045E: Unable to find package with location {0}.
CWSAJ0046E: Unable to find package with package name {0}.
CWSAJ0047E: Service filter is not valid: {0}.
CWSAJ0048E: Unable to get package information because you have not connected to a framework.
CWSAJ0049E: Cannot delete the bundle {0} because the following Composite Bundle Archives have a dependency on the bundle: {1}.
CWSAJ0050E: The connection is no longer available. Please check available connections and reconnect if required.
CWSAJ0051E: The asset {0} supplied is not an EBA asset.
CWSAJ0052E: An internal error has occurred. Unable to find the deployment manifest from the EBA asset {0}.
CWSAJ0053E: Unable to find the deployment manifest from the location {0}.
CWSAJ0054E: The deployment manifest content is not correct. The following extra bundles are required {0}.
CWSAJ0055E: The deployment manifest content is not correct. The following bundles are redundant: {0}.
CWSAJ0056E: An internal error occurred. The resolving process does not generate a list of bundles to be installed.
CWSAJ0057E: The deployment manifest to import cannot be resolved. The unsatisfied requirements are {0}.
CWSAJ0058E: The deployment manifest to import is not valid for the asset {0} because it does not meet the requirements in the application manifest.
CWSAJ0059E: The {0} parameter has not been specified and is required for the command {1}.
CWSAJ0060E: Unable to create the directory structure {0}.
CWSAJ0061E: Unable to create the directory structure {0}.
CWSAJ0062E: Unable to find the EBA asset {0}.
CWSAJ0063E: Cannot install the Composite Bundle Archive, {0}, because the following export packages differ from those contained by the Composite Bundle Archive: {1}
CWSAJ0064E: The specified file {0} is not a JAR or a Composite Bundle Archive.
CWSAJ0065E: The specified file {0} cannot be parsed as a manifest file because of exception {1}
CWSAJ0066E: The string {0} does not match the correct syntax of symbolicname;version.
CWSAJ0067E: An internal error occurred. Metadata for the bundles {0} could not be removed from the internal bundle repository. The exception was {1}
CWSAJ0068E: An internal error occurred. Metadata for the bundles {0} could not be removed from the internal bundle repository. Also, the bundles {1} could not be deleted from the repository. The exception was {2}
CWSAJ0069E: The bundles {0} could not be removed from the internal bundle repository. All other bundles {1} have been successfully removed.
CWSAJ0070E: The bundle {0} contained in the composite bundle archive {1} does not contain a valid bundle manifest.
CWSAJ0071E: An internal error occurred. A runtime service is not available from the OSGi service registry: {0}
CWSAJ0072E: The cuName parameter has not been specified and is required.
CWSAJ0073E: The symbolicName parameter has not been specified and is required.
CWSAJ0074E: The version parameter has not been specified and is required.
CWSAJ0075E: The extension with symbolic name {0} and version {1} has already been added to the composition unit.
CWSAJ0076E: The symbolic name {0} and version {1} do not match any available extension in any available bundle repository.
CWSAJ0077E: The symbolic name {0} and version {1} do not match any existing extension.
CWSAJ0078E: A resolution problem has occurred while adding an extension to composition unit {0}. The exception is: {1}
CWSAJ0079E: A resolution problem has occurred while removing an extension from composition unit {0}. The exception is: {1}
CWSAJ0080E: The Composite Bundle Archive (CBA) {0} is not valid. Packages imported by bundles in the CBA are missing from the Import-Package header of the CBA manifest file. The following problems were reported: {1}
CWSAJ0081E: Cannot add extension(s) because the composition unit is deployed on the following targets, which do not support application extension: {0}
CWSAJ0082W: The application extension functionality is not available for this composition unit because the composition unit is deployed on the following targets, which do not support application extension: {0}
CWSAJ0083W: The Composite Bundle Archive (CBA) {0} exports services that are not provided by bundles contained in the CBA. These services will not be available for use by bundles outside the CBA. The following problems were reported: {1}
CWSAJ0084W: Service references in the contents of the Composite Bundle Archive (CBA) {0} cannot be resolved. If these services are provided by bundles that are not included in the CBA, then the CBA must import them. The following service dependencies were unresolved: {1}


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.eba.admin.messages.EBAADMINMessages.dita
File name: com.ibm.ws.eba.admin.messages.EBAADMINMessages.html