com.sun.logging.enterprise.system.tools.deployment.LogStrings.properties Maven / Gradle / Ivy
The newest version!
#
# Copyright (c) 2010, 2018 Oracle and/or its affiliates. All rights reserved.
#
# This program and the accompanying materials are made available under the
# terms of the Eclipse Public License v. 2.0, which is available at
# http://www.eclipse.org/legal/epl-2.0.
#
# This Source Code may also be made available under the following Secondary
# Licenses when the conditions for such availability set forth in the
# Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
# version 2 with the GNU Classpath Exception, which is available at
# https://www.gnu.org/software/classpath/license.html.
#
# SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
#
enterprise.deployment_ioexcp=DPL5005:Unexpected I/O Exception
enterprise.deployment_error_loading_class=DPL5007:Error loading class [{0}]
enterprise.deployment_error_loading_class_excp=DPL5008:Error loading class
enterprise.deployment_mail_cfgexcp=DPL5013:Mail Configuration Exception
enterprise.deployment_class_not_found=DPL5023:class not found
# Start of part of Bug 4974675 - missing message IDs causing odd output from log viewer
enterprise.port_component_name_unknown=DPL5041:Unknown port-component-name {0} port, all sub elements will be ignored"
# End of bug 4974675
enterprise.deployment_dummy_set_trans_type=DPL5043:Setting transaction type for dummy ejb {0}
# messages from com.iplanet.ias.ejb
## messages used in IASEJBC.java (message id from DPL5100)
ejbc.end=DPL5110: EJBC - END of EJBC for [{0}]
## messages used in ReadOnlyBeanNotifierImpl.java (message id from DPL5150)
# messages from com.sun.ejb (message id from DPL5200)
ejb.classnotfound_exception=DPL5206: Class not found
ejb.illegal_ejb_interface_override=DPL5212:Attempt to override reserved ejb interface method [{0}] in [{1}]. Override will be ignored.
# messages from com.iplanet.ias.ejb.codegen.ProcessExecutor (message id from DPL5300)
enterprise.deployment.endpoint.registration=DPL5306:{0} Web Service Endpoint [{1}] listening at address [{2}]
# Start of part of bug 4974675 - missing message IDs
enterprise.deployment.backend.optionalpkg.dependency.exception=DPL5400:Exception occurred : {0}.
enterprise.deployment.backend.optionalpkg.dependency.notexist=DPL5401:Optional package {0} does not exist or its Specification-Version does not match!! Unable to satisfy dependency for {1}
enterprise.deployment.backend.optionalpkg.dependency.satisfied=DPL5402:Optional package dependency satisfied for {0}
enterprise.deployment.backend.optionalpkg.dependency.specversion.null=DPL5404:Specification-Version for the optional package [ {0} ] in the jarfile [ {1} ] is not specified. Please provide a valid specification version for this optional package
# End of partial fix to 4974675
enterprise.deployment.class.not.found=DPL5405:Class {0} is not found
enterprise.deployment.backend.optionalpkg.dependency.error=DPL5410:Skipping extension processing for {0} due to error: {1}
enterprise.deployment.backend.optionalpkg.invalid.zip=DPL5411:Error in opening optional package file {0} due to exception: {1}.
# Deployment backend logging messages start here @ 8001
enterprise.deployment.backend.descriptorFailure=DPL8001: descriptor failure {0}
DPL8001.diag.cause.1=Archivist.setDescriptor() failed
DPL8001.diag.cause.2=The instance may not be of expected type
DPL8001.diag.check.1=Ensure that the descriptor type is set as expected
DPL8001.diag.check.1=Turn log level for deployment to see more details
enterprise.deployment.backend.fileCopyFailure=DPL8002: file copy failure
DPL8002.diag.cause.1=Copying of files failed
DPL8002.diag.cause.2=May be because of lack of space or permission
DPL8002.diag.check.1=Ensure that there is enough disk space
DPL8002.diag.check.1=Ensure that the permissions are set as expected
enterprise.deployment.backend.fileOpenFailure=DPL8004: file open failure; file = {0}
DPL8004.diag.cause.1=Opening of files failed
DPL8004.diag.cause.2=May be because of lack of permission or wrong file name
DPL8004.diag.check.1=Ensure that the file name is correct
DPL8004.diag.check.2=Ensure that the permissions are set as expected
enterprise.deployment.backend.invalidDescriptorMappingFailure=DPL8007: Unsupported deployment descriptors element {0} value {1}
DPL8007.diag.cause.1=Failed to find the resource specified in the deployment descriptor
DPL8007.diag.cause.2=May be because of wrong specification in the descriptor
DPL8007.diag.check.1=Ensure that the resource specified is present
DPL8007.diag.check.2=Ensure that there is no typo in the resource specified in the descriptor
enterprise.deployment.backend.methodClassLoadFailure=DPL8008: method/class loading failure : {0} \n method/class name - {1}
DPL8008.diag.cause.1=Failed to load the class / method
DPL8008.diag.cause.2=May be because of wrong class/method name
DPL8008.diag.check.1=Ensure that the class / method specified is present
DPL8008.diag.check.2=Ensure that the path info is correct
enterprise.deployment.backend.deplyomentManagerLoadFailure=DPL8009: deployment manager load failure : unable to load - {0}
DPL8009.diag.cause.1=Failed to load the deployment manager
DPL8009.diag.cause.2=May be because of wrong uri specification or deployment factory not installed at all
DPL8009.diag.check.1=Ensure that the resource specified is present
DPL8009.diag.check.2=Ensure that there is no typo in the URI specified
enterprise.deployment.backend.autoDeploymentFailure=DPL8011: autodeployment failure while deploying the application : {0}
DPL8011.diag.cause.1=Failed in autodeployment of applications
DPL8011.diag.cause.2=Mostly because of application specific failure
DPL8011.diag.check.1=Ensure that the application can be deployed using CLI
DPL8011.diag.check.2=Ensure that there autodeploy config info is set properly and the server is up and running
enterprise.deployment.backend.ejbRefTypeMismatch=DPL8017: Ejb-ref type mismatch for ejb reference {0}. Reference declares type {1} but target ejb {2} has {3} interface of type {4}.
DPL8017.diag.cause.1=Possible type mismatch in ejb-ref/ejb-local-ref/@EJB
DPL8017.diag.cause.2=May be because of wrong specification in the descriptor
DPL8017.diag.check.1=Ensure that the type associated with the ejb reference is the correct one.
DPL8017.diag.check.2=Ensure that there is no typo in the resource specified in the descriptor
invalidSpecVersion=DPL8018: Invalid spec version {0}, reset to value {1}
enterprise.deployment.backend.emptyRoleName=DPL8020: The role-name is empty. The may not be what the developer had in mind. Please check this.
enterprise.deployment.backend.invalidWsdlURL=DPL8021: Invalid URL {0} specified for WSDL location
DPL8021.diag.cause.1=Failed to create a URL from the wsdl location specified
DPL8021.diag.cause.2=May be because of wrong specification in the descriptor
DPL8021.diag.check.1=Ensure that the resource specified is a valid URL
DPL8021.diag.check.2=Ensure that there is no typo in the resource specified in the descriptor
enterprise.deployment.backend.urlcontainscrlf=DPL8023: URL Pattern contains CR(#xD) or LF(#xA): [{0}]. Leading and trailing whitespace will be ignored.
enterprise.deployment.backend.appClientArtifactOutOfOrder=DPL8022: Artifact {0} identified for inclusion in app clients after one or more app clients were generated.
DPL8022.diag.cause.1=The application might specify that modules are to be processed in the order they appear in the application and an app client module appears before a module that creates an artifact to be included in app clients.
DPL8022.diag.check.1=Make sure, if the application specifies initialize-in-order as true, that the app clients appear after other modules which generated artifacts that should be accessible to app clients.
enterprise.deployment.backend.appClientArtifactMissing=DPL8024: Artifact with relative path {0} expected at {1} but does not exist or cannot be read
DPL8024.diag.cause.1=The server is attempting to register an artifact to be included in the generated app client JAR but the artifact does not exist or cannot be read
DPL8024.diag.check.1=This is an internal server error. Please file a bug report.
enterprise.deployment.backend.appClientArtifactCollision=DPL8025: Artifact with relative path {0} from {1} collides with an existing artifact from file {2}
DPL8025.diag.cause.1=The server has created more than one artifact with the same relative path to be included in the generated app client JAR file
DPL8025.diag.check.1=This is an internal server error. Please file a bug report.
enterprise.deployment.backend.badSubModPackaging=DPL8026: Submodule {0} has been expanded from the EAR into the same relative location as the location where it would be copied for internal use, but is of the type {1} which is not the type the rest of deployment will expect.
DPL8026.diag.cause.1=A submodule in an EAR can have the same name as its expansion location but the submodule must be of the correct storage type (such as a directory, not a JAR) as well.
DPL8026.diag.check.1=Rename the submodule JAR in the application so it is not the same name as the expansion directory the server uses, or keep the same name but package it in the EAR as a subdirectory and not as a JAR file.
counterpart.configdd.exists=DPL8027: Ignore {0} in archive {1}, as higher precendence runtime xml {2} is present in the same archive.
invalidwlmoduletype=DPL8028: [{0}] is not an allowed WebLogic module type. Allowed module types are JMS, JDBC and Interception.
sun.configdd.deprecate=DPL8030: Sun specific deployment descriptor ({0} in archive {1}) is deprecating, please use GlassFish specific deployment descriptor {2} in the future.
enterprise.deployment.filePredatesArchive=DPL8031: Ignoring {0} because the containing archive {1} recorded it as a pre-existing stale file
DPL8031.diag.cause.1=A file inside a file archive predates the archive and is therefore being hidden and will appear not to exist in the archive
DPL8031.diag.check.1=The file might have been opened but never closed, for instance during an earlier deployment of an application, and incorrectly remains in the archive after an undeployment.
enterprise.deployment.nullFileList=DPL8032: Attempt to list files in {0} failed, perhaps because that is not a valid directory or because file permissions do not allow GlassFish to access it
DPL8032.diag.cause.1=The file should have been a directory which GlassFish could read; instead it might not be a directory or it might be a directory which GlassFish cannot access
DPL8032.diag.check.1=Make sure the file is a directory and that its file protections permit GlassFish to list the files in it
enterprise.deployment.deleteFailed=DPL8033: Attempt to delete file {0} failed; no further information.
DPL8033.diag.cause.1=The file could not be deleted and no further information about the failure is available.
DPL8033.diag.check.1=Make sure the directory containing the file allows GlassFish to delete the file and that no other processes have the file open.
enterprise.deployment.mkdirsFailed=DPL8034: Attempt to create directory {0} failed; no further information.
DPL8034.diag.cause.1=The directory {0} and/or intervening directories could not be created and no further information about the failure is available.
DPL8034.diag.check.1=Make sure the directory containing the directory being creating allows GlassFish to create the directory.
enterprise.deployment.createFailed=DPL8035: Attempt to create file {0} failed; no further information.
DPL8035.diag.cause.1=The file {0} could not be created and no further information about the failure is available.
DPL8035.diag.check.1=Make sure the directory containing the file allows GlassFish to create the file.
enterprise.deployment.setLastModFailed=DPL8036: Attempt to set last modified date/time of file {0} failed; no further information.
DPL8036.diag.cause.1=The last modified date/time for file {0} could not be set and no further information about the failure is available.
DPL8036.diag.check.1=Make sure the file permissions allow GlassFish to change the last modified date/time.
wls.counterpart.configdd.exists=DPL8037: Ignore {0} in archive {1}, as WLS counterpart runtime xml {2} is present in the same archive.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy