ACDEPL

ACDEPL001 Directory URL {0} in the manifest Class-Path for {1} will not be honored; it does not end with a slash.

Cause: Default class loaders will not include files from this directory at runtime; also, as a result, these files be not downloaded to clients.

Solution: Please make sure all such directory URLs in the Class-Path entry of JAR manifests have a trailing slash.

ACDEPL002 Cannot process archive {0} as an application client; it does not contain the required manfest at META-INF/MANIFEST.MF

Cause: All legal JARs, including Java EE components such as app clients, are required to have a manifest.

Solution: Make sure all JARs, specifically the one logged in the message, include valid manifests.

ACDEPL003 Cannot process archive {0} as an application client; its manifest does not contain main attributes (such as "Main-Class")

Cause: An app client JAR must specify the main class using the Main-Class setting in the manifest

Solution: Make sure the manifest of each app client JAR specifies the Main-Class

ACDEPL101 Java Web Start services not started for the app client {0}; its developer has marked it as ineligible

Cause: The developer's sun-application-client.xml file marks the app client as ineligible for Java Web Start support.

Solution: If users should be able to launch this client using Java Web Start, change the <java-web-start-support> 'enabled' attribute.

ACDEPL102 Java Web Start services not started for the app client {0}; the administrator has disabled Java Web Start support for it

Cause: The administrator disabled Java Web Start launches for the app client, either using '--properties java-web-start-enabled=false' during deployment or changing the properties afterwards.

Solution: If users should be able to launch this client using Java Web Start, either deploy the application again without --properties or adjust the configuration using the admin console or the asadmin 'set' command

ACDEPL103 Java Web Start services started for the app client {0} (contextRoot: {1})

Description: TBD

ACDEPL104 Java Web Start services stopped for the app client {0}

Description: TBD

ACDEPL105 Error starting the adapter to serve static system-level content

Cause: An unexpected internal system error occurred

Solution: Please consult the exception stack trace

ACDEPL106 Attempt to replace existing static content for {0} with {1} which does not match the existing content {2}

Cause: This is an internal error.

Solution: Please file an issue with a reproducible test case.

ACDEPL107 Attempt to add or retrieve content with URI {0} to HTTP adapter with context root {1} and user-friendly context root {2} rejected; URIs must fall within the adapter context root

Cause: This is an internal error.

Solution: Please file an error with a reproducible test case.

ACDEPL108 Config file for client JNLP not found: {0}

Cause: The config file does not exist.

Solution: The file is part of the installation so this might be an internal error. Make sure you have not accidentally removed or renamed the config file. If not, please file an error with a reproducible test case.

ACDEPL109 The config file for client JNLP {0} exists but could not be read.

Cause: The config file might be protected from reading.

Solution: Make sure the config file protection settings permit the server to read it.

ACDEPL110 Error processing client JNLP config file {0}

Cause: An error occurred attempting to process the config file's contents.

Solution: The contents of the file might be invalid or incorrectly formatted. Check to make sure the file includes valid property settings.

ACDEPL111 Client JNLP document {0} refers to the static resource {1} that does not exist or is not readable.

Cause: The developer-provided JNLP content refers to a file as if the file is in the application but the server could not find the file.

Solution: Make sure the file is packaged in the application and that the reference to the file is correct. Then rebuild and redeploy the application.

ACDEPL112 The following extensions or libraries are referenced from the manifest of {0} but were not found where indicated: {1}; ignoring and continuing

Cause: The server could not open the JAR file(s) or process the extension(s) listed in its manifest.

Solution: Make sure the manifest of the JAR file correctly lists the relative paths of library JARs and the extensions on which the JAR depends.

ACDEPL113 Error preparing to server JARs referenced by app client; referenced JAR file {0} contains no manifest; continuing

Cause: A JAR file which an app client directory or indirectly refers to contains no manifest, in violation of the JAR specification, so it cannot be checked for further dependencies.

Solution: Check that the referenced JAR file has been built correctly. It should contain a manifest but does not.

ACDEPL114 The ApplicationSignedJARManager for a nested app client deployer helper is unexpectedly null.

Cause: During deployment of nested app clients (those inside EARs), the system should use an ApplicationSignedJARManager but it is null.

Solution: This is a system error. Please report this as a bug.

ACDEPL115 Tbe custom JNLP document {0} in a stand-alone app client incorrectly refers to a JAR {1}

Cause: The app client includes a custom JNLP document which refers to a JAR. Stand-alone app clients cannot refer to other JARs because they are self-contained deployment units.

Solution: Remove references to JAR from the custom JNLP document or package the app client inside an EAR that also contains the referenced JAR.

ACDEPL116 The manifest in dependent JAR {0} contains no main attributes, such as Class-Path, and so is an invalid JAR. Continuing.

Cause: The JAR specification requires JARs to have a main attributes section, which this JAR does not have.

Solution: Make sure the JAR was created correctly with a main attributes section and has not been corrupted.