alvinalexander.com | career | drupal | java | mac | mysql | perl | scala | uml | unix  

Glassfish example source code file (LogStrings.properties)

This example Glassfish source code file (LogStrings.properties) is included in the DevDaily.com "Java Source Code Warehouse" project. The intent of this project is to help you "Learn Java by Example" TM.

Java - Glassfish tags/keywords

cddl, ejbc, ejbc, end, error, exception, gpl, gpl, jar, license, license, please, version, version

The Glassfish LogStrings.properties source code

#
# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
#
# Copyright (c) 2010 Oracle and/or its affiliates. All rights reserved.
#
# The contents of this file are subject to the terms of either the GNU
# General Public License Version 2 only ("GPL") or the Common Development
# and Distribution License("CDDL") (collectively, the "License").  You
# may not use this file except in compliance with the License.  You can
# obtain a copy of the License at
# https://glassfish.dev.java.net/public/CDDL+GPL_1_1.html
# or packager/legal/LICENSE.txt.  See the License for the specific
# language governing permissions and limitations under the License.
#
# When distributing the software, include this License Header Notice in each
# file and include the License file at packager/legal/LICENSE.txt.
#
# GPL Classpath Exception:
# Oracle designates this particular file as subject to the "Classpath"
# exception as provided by Oracle in the GPL Version 2 section of the License
# file that accompanied this code.
#
# Modifications:
# If applicable, add the following below the License Header, with the fields
# enclosed by brackets [] replaced by your own identifying information:
# "Portions Copyright [year] [name of copyright owner]"
#
# Contributor(s):
# If you wish your version of this file to be governed by only the CDDL or
# only the GPL Version 2, indicate your decision by adding "[Contributor]
# elects to include this software in this distribution under the [CDDL or GPL
# Version 2] license."  If you don't indicate a single choice of license, a
# recipient has the option to distribute your version of this file under
# either the CDDL, the GPL Version 2 or to extend the choice of license to
# its licensees as provided above.  However, if you add GPL Version 2 code
# and therefore, elected the GPL Version 2 license, then the option applies
# only if the new code is made subject to such option by the copyright
# holder.
#

enterprise.deployment_exception_classloadercouldnotbemade=DPL5001:Class loader could not be made
enterprise.deployment_cannot_add_icon=DPL5002:Cannot Add Icon
enterprise.deployment_parser_cannot_validate=DPL5003:SAX Parser cannot validate
enterprise.deployment_cannot_add_jar=DPL5004:Cannot add jar to output stream
enterprise.deployment_ioexcp=DPL5005:Unexpected I/O Exception
enterprise.deployment_read_connector=DPL5006:Error reading connector xml
enterprise.deployment_error_loading_class=DPL5007:Error loading class [{0}]
enterprise.deployment_error_loading_class_excp=DPL5008:Error loading class
enterprise.deployment_error_loading_ejbclass=DPL5009:Error loading the ejb class [{0}] in getFields on EjbDescriptor\n [{1}]
enterprise.deployment_error_loading_ejbclass_excp=DPL5010:Error loading ejb class in getFields on EjbDescriptor
enterprise.deployment_error_loading_ejbclass_getfieldname=DPL5011:Error loading the ejb class in getFieldForName on EjbDescriptor [{0}]
enterprise.deployment_error_loading_ejbclass_getfieldname_excp=DPL5012:Error loading the ejb class in getFieldForName on EjbDescriptor [{0}]
enterprise.deployment_mail_cfgexcp=DPL5013:Mail Configuration Exception
enterprise.deployment_exception_method_not_found=DPL5014:[{0}] not found in [{1}]
enterprise.deployment_exception_method_not_found_excp=DPL5015:Method not found
enterprise.deployment_cannot_instantiate=DPL5016:Cannot instantiate implementation of [{0}]
enterprise.deployment_cannot_instantiate_excp=DPL5017:Cannot instantiate implementation
enterprise.deployment_parsing_error=DPL5018:Error while parsing
enterprise.deployment_illarg=DPL5019:Illegal Argument(s)
enterprise.deployment_parser_cannot_parse=DPL5020:SAX Parser cannot parse given stream
enterprise.deployment_xml_nomethod=DPL5021:No method found for XML query element
enterprise.deployment_incorrect_descriptor=DPL5022:Supplied External Descriptors are incorrect
enterprise.deployment_class_not_found=DPL5023:class not found
enterprise.deployment_cannot_expand_jar=DPL5024:Cannot expand jar archive
enterprise.deployment_sax_parser_config=DPL5025:Error in SAX parser configuration
enterprise.deployment_sax_parser=DPL5026:Exception in SAX parser
enterprise.deployment_archive_exception=DPL5027:Cannot create package
enterprise.deployment_getMethod_exception=DPL5028:Unexpected exception in MethodDescriptor.getMethod()
enterprise.deployment_node_runtime=DPL5029:Cannot read runtime descriptor nodes
enterprise.deployment_node_ejb=DPL5030:Cannot read EJB nodes
enterprise.deployment_node_method=DPL5031:Cannot read method descriptor nodes
enterprise.deployment_no_auth_method_dfnd=DPL5032:An authentication method was not defined in the web.xml descriptor.  Using default BASIC for login configuration.
enterprise.deployment_app_xml_parse_error=DPL5033:Error parsing application.xml
enterprise.deployment_rollback_error=DPL5034:Rollback failed
enterprise.deployment_ejbc_error=DPL5035:Error while running ejbc
enterprise.deployment_dup_jar_entry=DPL5036:Duplicate entry in jar archive
enterprise.deployment_error_reading_runtime_nodes=DPL5037:Error reading runtime descriptor nodes
enterprise.deployment_verifier_result=DPL5038: Verification Results: \n\tNumber of Failure(s): {0}\n\tNumber of Warning(s): {1}\n\tNumber of Error(s): {2}
# Start of part of Bug 4974675 - missing message IDs causing odd output from log viewer
enterprise.deployment_post_deploy_event_error=DPL5039:Caught a Throwable in POST_DEPLOY Event
enterprise.deployment_pre_undeploy_event_error=DPL5040:Caught a Throwable in PRE_UNDEPLOY Event
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_ejb_descriptor=DPL5042:Construct a Dummy EJB Descriptor with name {0}
enterprise.deployment_dummy_set_trans_type=DPL5043:Setting transaction type for dummy ejb {0}
enterprise.deployment_dummy_set_type=DPL5044:Setting type for dummy ejb {0}


# messages from com.iplanet.ias.ejb

## messages used in IASEJBC.java (message id from DPL5100)
ejbc.codegen_src=DPL5100: EJBC - Could not generate new source
ejbc.codegen_rmi=DPL5101: EJBC - Could not invoke rmic
ejbc.codegen_rmi_fail=DPL5102: EJBC - rmic compilation failed
ejbc.codegen_compile_failed=DPL5103: EJBC - compilation failed
ejbc.codegen_checkerror=DPL5104: EJBC - code gen required check error
ejbc.processing_cmp=DPL5105: EJBC - Start of CMP section for [{0}]
ejbc.done_processing_cmp=DPL5106: EJBC - End of CMP section for [{0}]
ejbc.done_gen_local_impls=DPL5107: EJBC - Generated code for EJBLocalHOme, EJBLocalObject implementations for [{0}]
ejbc.done_gen_remote_impls=DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [{0}]
ejbc.begin=DPL5109: EJBC - START of EJBC for [{0}]
ejbc.end=DPL5110: EJBC - END of EJBC for [{0}]

## messages used in ReadOnlyBeanNotifierImpl.java (message id from DPL5150)
ejb.robean_rte=DPL5150: Run time exception during R/O bean notifier initialization

# messages from com.sun.ejb (message id from DPL5200)
ejb.rmic_invoke_exception=DPL5200: Could not invoke rmic
ejb.rmic_compilation_exception=DPL5201: rmic compilation failed...
ejb.compile_exception=DPL5202: Exception occurred compiling ejb
ejb.jarfile_exists=DPL5203: Output jarfile [{0}] already exists
ejb.classloading_exception=DPL5204: Exception occurred while loading class [{0}]
ejb.generator_exception=DPL5205: Exception occurred while generating ejb
ejb.classnotfound_exception=DPL5206: Class not found
ejb.io_exception=DPL5207: Some IO exception occurred
ejb.some_generic_exception=DPL5208: Some exception occurred
ejb.addto_genfile=DPL5209: Adding to generated files: [{0}]
ejb.generate_error=DPL5210: Error generating code: [{0}]
ejb.messagestatus_exception=DPL5211: Error in setting message status
ejb.notification_error=DPL5212: Error in notification
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)
process.waiter_interrupted=DPL5300: Interrupted while waiting for execution of [{0}]
process.interrupting=DPL5301:Timeout [{0}] milliseconds reached, Interrupting execution of command [{1}].
process.creation_failed=DPL5302:Process creation failed.
process.stream_close_error=DPL5303:Error in closing process output or error stream.
process.interrupted=DPL5303:Execution of command in a sub-process interrupted.
process.execution_failed=DPL5304:Execution of process failed
process.stream_read_error=DPL5305:Error reading from process output or error stream
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.null.error=DPL5403:Either Extension-Name or Specification-Version for the optional package is not specified 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.method.not.found=DPL5406:Method {0} is not found
enterprise.deployment.default.web.xml.not.parsed=DPL5407:Exception in populating default WebBundleDescriptor from default-web.xml {0}
enterprise.deployment.ignore.sun.resources.xml=DPL5408:Ignore: {0}
enterprise.deployment.error.get.resources=DPL5409:Exception in getting resources: {0}

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}. 

enterprise.deployment_badformat_checkpointedmethods=DPL5412: Bad format: checkpointed-methods [{0}]

# 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.archivistInstantiationFailure=DPL8003: archivist instantiation  failure for {0}; type = {1}
DPL8003.diag.cause.1=ArchivistFactory.getArchivist() failed
DPL8003.diag.cause.2=the module type may not be as expected
DPL8003.diag.check.1=Ensure that the module type is one of the supported types
DPL8003.diag.check.2=Ensure that the module type is one of the supported types

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.saxParserError=DPL8005: Deployment Descriptor parsing failure : {0}
DPL8005.diag.cause.1=Error while parsing the deployment descriptor
DPL8005.diag.cause.2=May be because of malformed descriptor or absence of all required descriptor elements
DPL8005.diag.check.1=Ensure that the descriptor is well formed and as per specification
DPL8005.diag.check.2=Ensure that the SAX parser configuration is correct and the descriptor has right permissions

enterprise.deployment.backend.addDescriptorFailure=DPL8006: get/add descriptor failure : {0} TO {1}
DPL8006.diag.cause.1=Adding or getting a descriptor failed
DPL8006.diag.cause.2=May be because the node / information to be added is not valid; may be because of the descriptor was not registered
DPL8006.diag.check.1=Ensure that the node to be added is valid
DPL8006.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.autoDeploymentStartFailure=DPL8010: autodeployment startup failure
DPL8010.diag.cause.1=Failed in autodeployment
DPL8010.diag.cause.2=May be because of failure in creating the autodeployer or while reading the autodeploy config info
DPL8010.diag.check.1=Ensure that the autodeploy is enabled properly
DPL8010.diag.check.2=Ensure that there autodeploy config info is set properly

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.directoryRenameFailure=DPL8012: directory rename failure : {0} TO {1}
DPL8012.diag.cause.1=Failed to rename directory
DPL8012.diag.cause.2=May be because of lack of permissions
DPL8012.diag.check.1=Ensure that the permissions are set as expected
DPL8012.diag.check.2=Ensure that there is no directory name clash

enterprise.deployment.backend.jarCreationFailure=DPL8013: JAR file creation failure : {0}
DPL8013.diag.cause.1=Failed to create JAR file
DPL8013.diag.cause.2=May be because of lack of permissions or lack of space
DPL8013.diag.check.1=Ensure that the permissions are set as expected
DPL8013.diag.check.2=Ensure that there is enough space

enterprise.deployment.backend.appDeploymentFailure=DPL8014: Application deployment failure
DPL8014.diag.cause.1=Failed to complete application deployment
DPL8014.diag.cause.2=May be because of lack of permissions or lack of space or wrong application
DPL8014.diag.check.1=Ensure that the permissions are set as expected
DPL8014.diag.check.2=Ensure that there is enough space

enterprise.deployment.backend.invalidDescriptorFailure=DPL8015: Invalid Deployment Descriptors in {0} \nLine {1} Column {2} -- {3}
DPL8015.diag.cause.1=Failed to find the resource specified in the deployment descriptor
DPL8015.diag.cause.2=May be because of wrong specification in the descriptor
DPL8015.diag.check.1=Ensure that the resource specified is present
DPL8015.diag.check.2=Ensure that there is no typo in the resource specified in the descriptor


enterprise.deployment.backend.norolemapperfactorydefine=DPL8015: This application has no role mapper factory defined

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.computeRunAsPrincipal=DPL8019: The run-as principal {0} was assigned by the deployment system based on the specified role.  Please consider defining an explicit run-as principal in the sun-specific deployment descriptor.
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
deployment.no_xmldir=DPL8022: Failed to load deployment descriptor files from directory: {0}. Load them from directory : {1} instead.
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.

gf.counterpart.configdd.exists=DPL8027: Ignore {0} in archive {1}, as GlassFish counterpart 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.counterpart.configdd.exists=DPL8029: Ignore {0} in archive {1}, as Sun counterpart runtime xml {2} is present in the same archive.
sun.configdd.deprecate=DPL8030: Sun specific deployment descriptor ({0} in archive {1}) is deprecating, please use GlassFish specific deployment descriptor {2} in the future.

Other Glassfish examples (source code examples)

Here is a short list of links related to this Glassfish LogStrings.properties source code file:

... this post is sponsored by my books ...

#1 New Release!

FP Best Seller

 

new blog posts

 

Copyright 1998-2021 Alvin Alexander, alvinalexander.com
All Rights Reserved.

A percentage of advertising revenue from
pages under the /java/jwarehouse URI on this website is
paid back to open source projects.