Glassfish example source code file (LocalStrings.properties)

This example Glassfish source code file (LocalStrings.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, cluster, destination, gpl, host, host, jms, jms, license, license, please, resource, resource, version

The Glassfish LocalStrings.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.
#

#create-jms-dest
create.jms.destination.CannotCreateJMSDest=Unable to create JMS Destination.

#create-jms-host
create.jms.host.noJmsHost=No JMS Host name specified.
create.jms.host.duplicate=A JMS Host named {0} already exists.
create.jms.host.fail=Unable to create jms host {0}.
create.jms.host.success=Jms Host {0} created.
create.jms.host=Creates a JMS host

#create-jms-resource
create.jms.resource.noResourceType=No Resource Type specified for JMS Resource.
create.jms.resource.noJndiName=No JNDI name specified for JMS Resource.
create.jms.resource.InvalidResourceType=Invalid Resource Type specified for JMS Resource.
create.jms.resource.cannotCreateConnectionPool=Unable to create connection pool.
create.jms.resource.cannotCreateConnectorResource=Unable to create connection resource.
create.jms.resource.cannotCreateAdminObject=Unable to create admin object.
admin.mbeans.rmb.destination_name_invalid=Destination Resource {0} has an invalid destination name {1}
create.jms.resource=Registers the JMS resource

delete.jms.resource=Removes a JMS resource
list.jms.resources=Gets all the JMS resources

#delete-jms-host
delete.jms.host.noHostName=No JMS Host Name specified for JMS Host.
list.jms.host.invalidTarget=Invalid Target specified.
list.jms.host.noJmsHostFound=JMS Host {0} does not exist.
delete.jms.host.fail=Unable to delete jms host {0}.
delete.jms.host=Deletes a JMS Host
list.jms.hosts=Lists all the existing JMS Hosts

#delete-jms-resource
delete.jms.resource.noJndiName=No JNDI name defined for JMS Resource.
delete.jms.resource.cannotDeleteJMSAdminObject=Unable to Delete Admin Object.
delete.jms.resource.cannotDeleteJMSResource=Unable to Delete Connector Resource.
delete.jms.resource.cannotDeleteJMSPool=Unable to Delete Connector Connection Pool

#list-jms-hosts
list.jms.host.noTarget=No Target specified for JMS Host.
nothingToList=Nothing to list
list.jms.host.fail=Unable to list JMS Hosts

#list-jms-resource
list.jms.resources.fail=Unable to list JMS Resources

#jmsdestination
create.jms.dest=Creates the JMS physical destination
list.jms.dests=Lists the existing JMS physical destinations
delete.jms.dest=Removes a JMS destination
admin.mbeans.rmb.invalid_jms_destname=Invalid JMS destination name: {0}
admin.mbeans.rmb.invalid_jms_desttype=Invalid JMS destination type: {0}. JMS destination type has to be either ''topic'' or ''queue''
admin.mbeans.rmb.error_obtaining_jms=Error obtaining JMS Info
mqjmx.no_jms_hosts=Invalid jms-service configuration. Please configure one or more JMS hosts in the target's jms-service.
list.jms.dest.fail=Unable to list JMS Destinations
delete.jms.dest.noJmsDelete=Delete JMS Destination failed. Please verify if the JMS Destination specified for deletion exists.
create.jms.dest.noDestType=No Destination type specified for JMS Destination.
flush.jms.dest.failed=Flush JMS Destination failed due to {0}
admin.mbeans.rmb.error_purging_jms_dest=An error occurred while purging the JMS physical destination. Configured MQ system may not be running or not responding. Please check the server log for more information

#jms-ping command
jms-ping.cannotCreateJMSResource=Unable to create a temporary Connection Factory to the JMS Host
jms-ping.pingConnectionPoolFailed=Pinging to the JMS Host failed.
jms-ping.pingConnectionPoolException=An exception occurred while trying to ping the JMS Host. Exception Message - {0}
jms-ping.cannotdeleteJMSResource=Unable to delete the temporary JMS Resource {0}. Please delete this manually.
jms-ping.pingConnectionPoolSuccess=JMS-ping command executed successfully

#configure-jms-cluster
configure.jms.cluster.invalidClusterName=No Cluster by this name has been configured
configure.jms.cluster.clusterWithInstances=The cluster has existing instances configured. This command should be run before adding instances to the cluster. To force run this command, please follow the instructions in the documentation and use the --force=true option
configure.jms.cluster.nojmsservice=No JMS Service element in config
configure.jms.cluster.wrongClusterType=Invalid option sepecified for clustertype. Valid options are conventional and enhanced
configure.jms.cluster.wrongConfigStoreType=Invalid option sepecified for configstoretype. Valid options are masterbroker and shareddb
configure.jms.cluster.wrongStoreType=configstoretype option is not configurable for Enhanced clusters.
configure.jms.cluster.wrongMessageStoreType=Invalid option sepecified for messagestoretype. Valid options are file and jdbc
configure.jms.cluster.wrongmsgStoreType=messagestoretype option is not configurable for Enhanced clusters.
configure.jms.cluster.remoteMode=JMS integration mode should be either EMBEDDED or LOCAL to run this command. Please use the asadmin.set command to change the integration mode
configure.jms.cluster.noEmbeddedModeForEnhancedClusters=EMBEDDED JMS integration mode is not supported for Enhanced clusters. Please use the asadmin.set command to change the JMS integration mode
configure.jms.cluster.invalidDboptions=Database options should not be specified for this configuration
configure.jms.cluster.nojdbcurl=No JDBC URL specified
configure.jms.cluster.nodbvendor=No DataBase vendor specified
configure.jms.cluster.noConfigStoreType=No configstoretype specified. Using the default value - masterbroker
configure.jms.cluster.noMessagetoreType=No messagestoretype specified. Using the default value - file
configure.jms.cluster.fail=Unable to Configure JMS Cluster for cluster {0}.
configure.jms.cluster.clusterWithInstances=WARNING: Please ensure that you have followed the instructions specified in the documentation before running this command with this option. Running this command without the required precautions can lead to inconsistent JMS behavior and corruption of configuration and message stores.
configure.jms.cluster.success=JMS Cluster Configuration updated for Cluster {0}

#change-master-broker
change.master.broker.invalidServerName=Invalid server name specified. There is no server by this name
change.master.broker.invalidClusterName=The server specified is not associated with a cluster. The server assocaited with the master broker has to be a part of the cluster
change.master.broker.CannotChangeMB=Unable to change master broker.
change.master.broker.fail=Unable to update the domain.xml with the new master broker
change.master.broker.success=Master broker change has executed successfully for Cluster {0}.