geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ga...@apache.org
Subject svn commit: r617192 - in /geronimo/server/trunk/plugins/console: console-base-portlets/src/main/resources/consolebase.properties plugin-portlets/src/main/resources/pluginportlets.properties
Date Thu, 31 Jan 2008 19:05:59 GMT
Author: gawor
Date: Thu Jan 31 11:05:54 2008
New Revision: 617192

URL: http://svn.apache.org/viewvc?rev=617192&view=rev
Log:
fixed a few spelling mistakes, spacing

Modified:
    geronimo/server/trunk/plugins/console/console-base-portlets/src/main/resources/consolebase.properties
    geronimo/server/trunk/plugins/console/plugin-portlets/src/main/resources/pluginportlets.properties

Modified: geronimo/server/trunk/plugins/console/console-base-portlets/src/main/resources/consolebase.properties
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/console/console-base-portlets/src/main/resources/consolebase.properties?rev=617192&r1=617191&r2=617192&view=diff
==============================================================================
--- geronimo/server/trunk/plugins/console/console-base-portlets/src/main/resources/consolebase.properties
(original)
+++ geronimo/server/trunk/plugins/console/console-base-portlets/src/main/resources/consolebase.properties
Thu Jan 31 11:05:54 2008
@@ -32,7 +32,7 @@
 apache.jk.index.notes                        = </li></ul><p>Notes:</p><ul><li>Geronimo
does not remember previous settings generated using this tool;you'll need to reenter all the
data each time, or just paste the new information into your existing configuration files.</li>
 <li>Any web applications to be exposed via Apache must be running when you run this
tool, and of course must be running to be accessed from Apache.</li></ul>
 apache.jk.index.severalSteps                 = <ol><li>Configure the Geronimo
web container to support the AJP protocol</li><li>Install the <tt>mod_jk.so</tt>
Apache module (compiling it if necessary)</li><li>Create a <tt>workers.properties</tt>
configuration file to point Apache to the Geronimo AJP connector</li><li>Add Apache
configuration information indicating which URLs should be sent to Geronimo and whether Apache
should serve static content (leaving only dynamic content within the web application to Geronimo)</li></ol>
 apache.jk.results.alreadyHasAJPListener      = This Geronimo configuration already has an
AJP listener running on port {0}. Nothing further needs to be done here.
-apache.jk.results.anAJPLisstnerAdded         = An AJP lisstner was added on port {0}.  Nothing
further needs to be done here.
+apache.jk.results.anAJPLisstnerAdded         = An AJP listener was added on port {0}.  Nothing
further needs to be done here.
 apache.jk.results.canActivateIt              = Once the <tt>mod_jk</tt> RPM is
installed, you can activate it by
 apache.jk.results.followingInfoToConfig      = The following information needs to go into
your Apache Configuration.
 apache.jk.results.howToActivateOthers        = adding the following line to <tt>/etc/httpd/conf/httpd.conf</tt>:</p><pre>LoadModule
jk_module modules/mod_jk.so</pre> <p>Then you can start Apache by running <tt>service
httpd start</tt>  (or <tt>service httpd restart</tt>).
@@ -113,7 +113,7 @@
 ca.confirmCertReq.approveCSR                        = Approve CSR
 ca.confirmCertReq.confirmCertRequest                = Confirm Certificate Request
 ca.confirmCertReq.rejectCSR                         = Reject CSR
-ca.confirmCertReq.summary                           = This screen shows the details of the
Certficate Signing Request (CSR) and allows you to approve the request.Once the request is
approved, it will be considered for issue of a certificate.
+ca.confirmCertReq.summary                           = This screen shows the details of the
Certificate Signing Request (CSR) and allows you to approve the request. Once the request
is approved, it will be considered for issue of a certificate.
 ca.confirmClientCert.issueCert                      = Issue Certificate
 ca.confirmClientCert.summary                        = This screen shows the CSR details and
the certificate details entered in the previous screen.  Upon clicking the <i>Issue
Certificate</i> button, a certificate will be issued and stored.  The next screen will
show the details of the certificate issued.
 ca.confirmClientCert.title                          = <b>Issue New Certificate</b>
- Step 3: Confirm and Issue Certificate
@@ -124,7 +124,7 @@
 ca.index.publishCACert                              = Publish CA Certificate
 ca.index.requestsToBeFulfilled                      = Requests to be fulfilled
 ca.index.requestsToBeVerified                       = Requests to be verified
-ca.index.title                                      = This portlet allows you to setup a
Certification Authority (CA) and issue certificates in reply to Certificate Signing Requests
(CSRs).   <i>Setup Certification Authority</i> function allows to initialize the
CA by providing CA Identity details,   algorithm parameters for CA's key pair and self-signed
certificate and a password to protect the CA's private key. This password is to be used to
unlock the CA to access CA functions. Once the CA is initialized,CSRs can be processed using
<i>Issue New Certificate</i> function.  Previously issued certificates can be
viewed using <i>View Issued Certificate</i> function.
+ca.index.title                                      = This portlet allows you to setup a
Certification Authority (CA) and issue certificates in reply to Certificate Signing Requests
(CSRs).   <i>Setup Certification Authority</i> function allows to initialize the
CA by providing CA Identity details,   algorithm parameters for CA's key pair and self-signed
certificate and a password to protect the CA's private key. This password is to be used to
unlock the CA to access CA functions. Once the CA is initialized, CSRs can be processed using
<i>Issue New Certificate</i> function.  Previously issued certificates can be
viewed using <i>View Issued Certificate</i> function.
 ca.listRequestsIssue.CertRequestsAwaiting           = Certificate Requests awaiting fulfillment
 ca.listRequestsIssue.CertRequestsAwaitingExp        = This screen shows the certificate requests
waiting to be fulfilled.
 ca.listRequestsVerify.certRequestsAwaitingVerify    = Certificate Requests awaiting verification
@@ -386,7 +386,7 @@
 securityrealmmanager.se.users.help.usernameExp             = The username for the user.
 securityrealmmanager.se.users.maximized.createNewUser      = Create New User
 
-servermanager.help.shutdownHelpBody   = <p>This portlet give the admin the ability
to remotely shutdown the Geronimo server.</p><p>A shutdown will shutdown the server
and cause the JVM to exit.To continue using the Geronimo Console after a shutdown, Geronimo
must be restarted.</p>
+servermanager.help.shutdownHelpBody   = <p>This portlet give the admin the ability
to remotely shutdown the Geronimo server.</p><p>A shutdown will shutdown the server
and cause the JVM to exit. To continue using the Geronimo Console after a shutdown, Geronimo
must be restarted.</p>
 servermanager.normal.areYouSure       = Are you sure you want to shutdown the server (last
chance)?
 servermanager.normal.proceedOnlyIf    = Proceed only if you are certain you want to terminate
the server.
 servermanager.normal.shutdown         = Shutdown
@@ -419,7 +419,7 @@
 webaccesslogmanager.help.remoteAddressExp     = A specific remote host can be entered in
this field using it's IP address, e.g., 192.168.1.1.\r\n
 webaccesslogmanager.help.requestMethodExp     = This drop-down box allows the user to filter
on &quot;ANY&quot;, &quot;POST&quot; and &quot;GET&quot; methods.\r\n
 webaccesslogmanager.help.requestedURIExp      = Filtering can be done on the Requested URI
field by entering a URI, such as, http://localhost:8080/cviewer/jsp/viewclass.jsp\r\n
-webaccesslogmanager.help.title                = This portlet displays and filters the Jetty
log file. The Jetty log file contains HTTP accesses and messages from JSP and servlet applications
that are running on Geronimo. By default this portlet displays the contents of the log file
for the current date. The user can apply filtering criteria to view only data of interest.The
user may enter information into any/all/none of the fields, which are defined next.
+webaccesslogmanager.help.title                = This portlet displays and filters the Jetty
log file. The Jetty log file contains HTTP accesses and messages from JSP and servlet applications
that are running on Geronimo. By default this portlet displays the contents of the log file
for the current date. The user can apply filtering criteria to view only data of interest.
The user may enter information into any/all/none of the fields, which are defined next.
 webaccesslogmanager.view.container            = Container
 webaccesslogmanager.view.filterResults        = Filter results
 webaccesslogmanager.view.foundMatches         = Found {0} matches in logfile ({1} lines searched).
@@ -445,7 +445,7 @@
 webmanager.common.bufferSize                         = BufferSize
 webmanager.common.bufferSizeExp                      = The size (in bytes) of the buffer
to be provided for input streams created by this connector. By default, buffers of 2048 bytes
will be provided.
 webmanager.common.ciphers                            = Ciphers
-webmanager.common.ciphersExp                         = A comma seperated list of the encryption
ciphers that may be used.If not specified, then any available cipher may be used.
+webmanager.common.ciphersExp                         = A comma separated list of the encryption
ciphers that may be used. If not specified, then any available cipher may be used.
 webmanager.common.clientAuthRequired                 = Client Auth Required
 webmanager.common.compressableMimeType               = CompressableMimeType
 webmanager.common.compressableMimeTypeExp            = The value is a comma separated list
of MIME types for which HTTP compression may be used. The default value is text/html,text/xml,text/plain.

Modified: geronimo/server/trunk/plugins/console/plugin-portlets/src/main/resources/pluginportlets.properties
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/console/plugin-portlets/src/main/resources/pluginportlets.properties?rev=617192&r1=617191&r2=617192&view=diff
==============================================================================
--- geronimo/server/trunk/plugins/console/plugin-portlets/src/main/resources/pluginportlets.properties
(original)
+++ geronimo/server/trunk/plugins/console/plugin-portlets/src/main/resources/pluginportlets.properties
Thu Jan 31 11:05:54 2008
@@ -62,7 +62,7 @@
 car.downloadStatus.processing                 = Processing {0}...
 car.index.assembleServerLong                  = Assemble a server from plugins in this one
 car.index.assembleServer                      = Assemble a server
-car.index.createGeronimoPluginExp             = Choose a configuration in the current Geronimo
server to export as a Geronimo plugin.  The configuration will be saved as a CAR file to your
local filesystem.<i>Note: at present, you must manually add a <tt>META-INF/geronimo-plugin.xml</tt>
file to the CAR  after you export it in order for it to be a valid plugin.</i>
+car.index.createGeronimoPluginExp             = Choose a configuration in the current Geronimo
server to export as a Geronimo plugin.  The configuration will be saved as a CAR file to your
local filesystem. <i>Note: at present, you must manually add a <tt>META-INF/geronimo-plugin.xml</tt>
file to the CAR  after you export it in order for it to be a valid plugin.</i>
 car.index.optionalAuthentication              = Optional Authentication
 car.index.removePluginsExp                    = To remove a plugin, use the categories under
<b>Applications</b> to locate the plugin module and uninstall it.
 car.index.summary                             = <p>This portlet lets you install or
create Geronimo plugins. This can be used to install new features into a Geronimo server at
runtime.</p> <h2>Install Geronimo Plugins</h2> <p>Choose a remote
repository to inspect for available Geronimo plugins.  The repository must have a <tt>geronimo-plugins.xml</tt>
file in the root directory listing the available plugins in the repository.</p> <p>You
can also download running configurations from another Geronimo server  just as if you're browsing
and installing third-party plugins.  If you want to point to a remote Geronimo server,  enter
a URL such as <tt>http://geronimo-server:8080/plugin/maven-repo/</tt>  and the
enter the administrator username and password in the optional authentication fields.</p>
@@ -75,7 +75,7 @@
 car.list.noPlugins                            = No plugins are listed at this repository.
 car.list.pluginLocal                          = Plugins in local server
 car.list.pluginRepo                           = Plugins listed at
-car.pluginParams.JVMVersionsExp               = An optional list of JVM version prefixes
supported by this plugin.  If no values are listed, the plugin can be installed in Geronimo
running in any version of the JVM.  Otherwise, list one acceptable JVM version perfix per
line, like "1.4.2&nbsp;\r\n&nbsp;1.5&nbsp;\r\n&nbsp;..." (ideally, of course,
this means you've actually tested the plugin with Geronimo on each JVM version listed here).
+car.pluginParams.JVMVersionsExp               = An optional list of JVM version prefixes
supported by this plugin.  If no values are listed, the plugin can be installed in Geronimo
running in any version of the JVM.  Otherwise, list one acceptable JVM version prefix per
line, like "1.4.2&nbsp;\r\n&nbsp;1.5&nbsp;\r\n&nbsp;..." (ideally, of course,
this means you've actually tested the plugin with Geronimo on each JVM version listed here).
 car.pluginParams.authorExp                    = The author of the plug, which may be a person,
company, open source project, etc.
 car.pluginParams.categoryExp                  = The category this plugin falls into.  Plugins
in the same category will be listed together. If this plugin is intended to be listed on geronimoplugins.com
then you should use one of the category names there if any of them fit.  Otherwise, you can
select this freely, or according to the categories acceptable to the repository where you
plan to post this.
 car.pluginParams.dependenciesExp              = A list of JARs or other module IDs that this
plugin depends on.  These will be downloaded automatically when this plugin is installed.
 Normally you shouldn't change this list.  However, you can move entries from the dependency
list to the <b>prerequisite</b> list if the user must install the dependency manually
before installing the plugin  (e.g. for a database pool where a plugin wouldn't know what
server to connect to).<br /><br />  Each entry in this list should use the Unique
ID format like is used for this plugin above. You may remove the version number if you'd like
to work with any version of the dependency, though that may be risky. Each value should be
on a separate line.
@@ -89,7 +89,7 @@
 car.pluginParams.openSourceExp                = Check this box if the license is an OSI-approved
open source license (see <a href="http://www.opensource.org/licenses/index.php">http://www.opensource.org/licenses/index.php</a>).
 car.pluginParams.pluginURLExp                 = A URL to get more information about the plugin
(e.g. the plugin home page).
 car.pluginParams.prereqDescriptionExp         = A longer description of what the user needs
to do to comply with this prerequisite (for example, instructions to set up a database pool
listing the supported database products and telling the user where to find a script to initialize
the database).  This should be plain text with empty lines to separate paragraphs.
-car.pluginParams.prerequisiteIDExp            = The module ID of a prerequisite for this
plugin.  This is a module that must be present in the server before the plugin can be installed.
 It may be something like a specific web container for a web application (<tt>geronimo/jetty/*/car</tt>)
or something like a database pool or security realm that the user must install  because the
plugin author can't create a value that will be valid in the destination server.  You may
want to leave out as many segments of the module ID as possible in order to accomodate more
users (e.g. <tt>*/mypool/*/*</tt> rather than <tt>myapp/mypool/1.2/car</tt>).
+car.pluginParams.prerequisiteIDExp            = The module ID of a prerequisite for this
plugin.  This is a module that must be present in the server before the plugin can be installed.
 It may be something like a specific web container for a web application (<tt>geronimo/jetty/*/car</tt>)
or something like a database pool or security realm that the user must install  because the
plugin author can't create a value that will be valid in the destination server.  You may
want to leave out as many segments of the module ID as possible in order to accommodate more
users (e.g. <tt>*/mypool/*/*</tt> rather than <tt>myapp/mypool/1.2/car</tt>).
 car.pluginParams.prerequisiteTypeExp          = A brief description of the type of prerequisite
this is (for the benefit of the user).  Examples could include <tt>Database Pool</tt>
or <tt>Web Container</tt>.
 car.pluginParams.title                        = <b>Export Plugin</b> -- Configure
Plugin Data
 car.pluginParams.uniqueIDExp                  = The globally unique ID for this plugin. 
This is determined from the installation in the server you're exporting.  This defines the
version number for the plugin, so make sure it's correct.
@@ -112,7 +112,7 @@
 configmanager.common.plan                        = Plan
 configmanager.common.startAppAfterInstall        = Start app after install
 configmanager.deploy.migratedPlan                = Migrated plan
-configmanager.deploy.migratedPlanSummary         = The deployment plan you provided appears
to be for a previous version of the application server.A migrated version of your plan is
provided below for your convenience.  Not all deployment plans can be fully migrated so some
manual editing may be required before the migrated plan can be deployed.
+configmanager.deploy.migratedPlanSummary         = The deployment plan you provided appears
to be for a previous version of the application server. A migrated version of your plan is
provided below for your convenience.  Not all deployment plans can be fully migrated so some
manual editing may be required before the migrated plan can be deployed.
 configmanager.deploy.originalPlan                = Original plan
 configmanager.deploy.redeployApplication         = Redeploy application
 configmanager.deploy.saveLocally                 = Save this plan locally
@@ -234,7 +234,7 @@
 realmwizard.showPlan.deployCommandExp            = To deploy a security realm from the command
line using this plan, copy and paste it to a file (say, <tt>security-realm.xml</tt>)
and save it.  Then run a command like:
 realmwizard.showPlan.title                       = <b>Create Security Realm</b>
-- Show Deployment Plan
 realmwizard.testLogin.passwordExp                = The password to use to log in to the realm.
-realmwizard.testLogin.summary                    = From here you can enter a username and
password for the main login module in the realm, and see if the login is successful and which
Principals are generated for the user. This is menat to be an indication of whether the settings
for the main login module are correct.  It does not invoke advanced features such as auditing
or lockout.
+realmwizard.testLogin.summary                    = From here you can enter a username and
password for the main login module in the realm, and see if the login is successful and which
Principals are generated for the user. This is meant to be an indication of whether the settings
for the main login module are correct.  It does not invoke advanced features such as auditing
or lockout.
 realmwizard.testLogin.title                      = <b>Create Security Realm</b>
-- Step 4: Test Login
 realmwizard.testLogin.usernameExp                = The username to use to log in to the realm.
 realmwizard.testResults.testResults              = Test Results



Mime
View raw message