| Package Name | Comment |
| com.alkacon.opencms.commons | |
| com.alkacon.opencms.counter |
With the Counter module, it is possible to manage multiple
counters which can be used to count page hits or download numbers for example.
@version $Revision: 1.1 $
@since 7.0.3
|
| com.alkacon.opencms.feeder |
A syndication feed generator for OpenCms XML contents with support for RSS and Atom.
@version $Revision: 1.1 $
|
| com.alkacon.opencms.formgenerator |
Classes for the Alkacon OpenCms Add-On Module Package: Webform.
The provided classes are used for the highly configurable Alkacon OAMP
web form XML contents that allows to generate web forms containing
selectable fields of various types.
@version $Revision: 1.3 $
@since 7.0.4
|
| com.alkacon.opencms.formgenerator.database |
Classes for the OpenCms 7.0 'com.alkacon.opencms.formgenerator.database' module.
This package contains the database persistance layer for the Alkacon OpenCms Module Add-On
Webform.
@version $Revision: 1.1 $
@since 7.0.4
|
| com.alkacon.opencms.formgenerator.database.export |
Classes for the OpenCms 7.0 'com.alkacon.opencms.formgenerator.database.export' module.
This package contains the CSV export functionality for the Alkacon OpenCms Module Add-On
Webform.
@version $Revision: 1.1 $
@since 7.0.4
|
| com.alkacon.opencms.newsletter |
Extends a basic OpenCms installation with the capability to send newsletter emails to subscribers of different configurable mailing lists.
Contains all classes used to generate the front end views, to send the emails and for the subscription/unsubscription functions.
It provides the following features:
- Configurable mailing list subscription/unsubscription page for website users which can be combined with an existing OpenCms JSP template
- Editable newsletter content that can be sent to different mailing lists
- Management of different newsletter units for organizational units containing their own mailing lists and subscribers in the OpenCms Administration view
- Configurable scheduled job to clean up subscribed email addresses which were not confirmed within a configurable time range
- Possibility to extend the module to send newsletters based on an own implementation using another structured XML content
|
| com.alkacon.opencms.newsletter.admin |
This package contains the tool classes for the newsletter management related administration views.
|
| com.alkacon.opencms.registration |
Classes for the Alkacon OpenCms Add-On Module Package: Webuser Registration.
The provided classes are used for the configurable Alkacon OAMP Webuser
Registration framework that facilitates the setup of a portal like site.
@version $Revision: 1.1 $
@since 7.0.4
|
| org.opencms.applet.upload |
Used to generate the OpenCms upload Applet.
To compile the Applet, use the uploadjar target in the main OpenCms build file.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.cache |
Implementations of specialized caches used in OpenCms.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.configuration |
Reads and writes the XML based OpenCms configuration files.
@version $Revision: 1.7 $
@since 6.0.0
|
| org.opencms.db |
Low-level database connection and access functionality.
You should usually not access the OpenCms database directly.
To access the OpenCms VFS repository, obtain a {@link org.opencms.file.CmsObject}
which will encapsulate the current users permissions.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.db.as400 |
AS400 implementation of the OpenCms database connector.
@version $Revision: 1.2 $
@since 7.0.4
|
| org.opencms.db.db2 |
DB2 implementation of the OpenCms database connector.
@version $Revision: 1.2 $
@since 7.0.3
|
| org.opencms.db.generic |
Generic (ANSI-SQL) implementation of the OpenCms database connector.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.db.hsqldb |
HSQLDB implementation of the OpenCms database connector.
@version $Revision: 1.2 $
@since 7.0.3
|
| org.opencms.db.mssql |
MS SQL implementation of the OpenCms database connector.
@version $Revision: 1.4 $
@since 6.2.0
|
| org.opencms.db.mysql |
MySQL4+ implementation of the OpenCms database connector.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.db.oracle |
Oracle9+ implementation of the OpenCms database connector.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.db.oracle8 |
Oracle8 implementation of the OpenCms database connector.
@version $Revision: 1.3 $
@since 6.0.0
|
| org.opencms.db.postgresql |
PostgreSql implementation of the OpenCms database connector.
@version $Revision: 1.7 $
@since 6.0.0
|
| org.opencms.editors.fckeditor |
This package contains the classes for the embedded FCK WYSIWIG editor.
@version $Revision: 1.3 $
@since 6.0.0
|
| org.opencms.file |
This important package provides the methods to access the OpenCms VFS repository with the permissions
of an authenticated user.
To access the OpenCms VFS repository, obtain a {@link org.opencms.file.CmsObject}
which will encapsulate the current users permissions.
@version $Revision: 1.13 $
@since 6.0.0
@see org.opencms.file.CmsObject
@see org.opencms.file.CmsRequestContext
@see org.opencms.file.CmsUser
@see org.opencms.file.CmsResource
@see org.opencms.file.types.I_CmsResourceType
|
| org.opencms.file.collectors |
Collectors allow to gather lists of OpenCms resources from the OpenCms VFS using specific rules.
@version $Revision: 1.7 $
@since 6.0.0
@see org.opencms.file.collectors.CmsDefaultResourceCollector
@see org.opencms.file.collectors.CmsPriorityResourceCollector
@see org.opencms.file.collectors.I_CmsResourceCollector
|
| org.opencms.file.history |
This package contains the classes to deal with the OpenCms VFS history archive.
@version $Revision: 1.4 $
@since 6.9.1
|
| org.opencms.file.types |
The implementations of the core resource types for the VFS are located here.
@version $Revision: 1.9 $
@since 6.0.0
@see org.opencms.file.types.I_CmsResourceType
|
| org.opencms.file.wrapper |
This package contains classes and interfaces used to access OpenCms through a wrapped
{@link org.opencms.file.CmsObject}.
Main entry point is the class {@link org.opencms.file.wrapper.CmsObjectWrapper}. The
CmsObjectWrapper is configured with a list of implementations
of {@link org.opencms.file.wrapper.I_CmsResourceWrapper}. So it is possible to show resources in
the VFS different as usual.
For example: If you would like that xml pages always have the correct file extension (.xml) so you
can use the {@link org.opencms.file.wrapper.CmsResourceExtensionWrapperXmlPage}. This implementation
of the interface I_CmsResourceWrapper adds to every resource of type
"xmlpage" the correct file extension ".xml".
This package is mainly used by {@link org.opencms.repository.CmsRepositorySession} to create a
simple configurable access to the resources in OpenCms.
@version $Revision: 1.5 $
@since 6.2.4
@see org.opencms.file.wrapper.CmsObjectWrapper
@see org.opencms.file.wrapper.I_CmsResourceWrapper
|
| org.opencms.flex |
Provides low-level JSP integration funtionality for OpenCms,
also implements the FlexCache, a declarative parameter-based cache.
How the JSP integration is done:
In OpenCms all resources are residing in the OpenCms Database, the so
called "Virtual File System" or VFS.
However, all JSP engines available read the JSP code from a file in the local file system.
The option to re-write a JSP engine so that it can read from the VFS would limit OpenCms
to running with this JSP engine only, which was not a choice.
So the approach that was taken is to dump the contents of the OpenCms JSP page from the VFS
to the "real" file system
and then dispatch to the standard JSP engine.
Here is a top-level description of how this works:
- OpenCms gets the request through the {@link org.opencms.main.OpenCmsServlet}
- The requested resource is identified as a JSP page (resource type {@link org.opencms.file.types.CmsResourceTypeJsp})
- The JSP loader is started up with the resource manager {@link org.opencms.loader.CmsResourceManager}
- The JSP loader implements an additional interface: {@link org.opencms.loader.I_CmsResourceLoader}
- A resource loader is a new interface that was introduced with the FLEX release. The main
difference is that the original request / response is wrapped using a Servlet standard
{@link javax.servlet.http.HttpServletRequestWrapper} / {@link javax.servlet.http.HttpServletResponseWrapper}.
- On the first call to a page, the file contents of the JSP page are read from the OpenCms VFS
using the {@link org.opencms.file.CmsObject}
- The contents of the page are written to the "real" file system of the server,
in the default configuration to the directories
{WEBAPP-PATH}/opencms/WEB-INF/jsp/online or
{WEBAPP-PATH}/opencms/WEB-INF/jsp/offline (depending if the request was for the online or the offline
version of the page). The directory used can be configured in opencms.properties.
- After the page is written to the "real" FS, the loader dispatches to the standard JSP mechanism with a simple
include() call.
- The standard JSP mechanim will handle the JSP and deliver the output through the wrapped request / response
back to OpenCms.
- OpenCms will then deliver the contents back to the user.
@version $Revision: 1.12 $
@since 6.0.0
@see org.opencms.flex.CmsFlexCache
@see org.opencms.flex.CmsFlexCacheEntry
@see org.opencms.flex.CmsFlexCacheKey
|
| org.opencms.frontend.layoutpage |
Classes for the OpenCms 6 'layoutpage' resource type module.
The provided classes are used to generate a frontend layout page that provides an easy to use form based page layout for page editors.
The XML content type 'layoutpage' configures the frontend appearance of text paragraphs together with images.
To modify the enclosing output HTML code, please edit the files in the layouts/ subfolder of the module.
The used macros were developed using the FreeMarker template engine.
You can use the following variables in the files:
${headline}: the optional headline of the paragraph${image}: the image tag for the paragraph${description}: the image description text${text}: the text of the paragraph
To add your own predefined layout pattern, do the following:
- Create a text file in the module subfolder
layouts/
- You can use the following variables in the text file: ${headline}, ${image}, ${description}, ${text}
- Use the method
addLayoutPattern to make your layout file available in the bean with the desired image width as second argument (large, medium or small)
- Edit the schema appinfo node in
schemas/layoutimage.xsd to add your layout to the alignment selector widget
- Eventually enhance the CSS style sheet
resources/style.css and include it in your template
@version $Revision: 1.5 $
@since 6.1.9
|
| org.opencms.frontend.photoalbum |
Classes for the OpenCms 6.0 'photo gallery' module.
The provided classes are used to generate a frontend photo gallery output using an existing OpenCms image gallery.
The gallery appearance is configurable using an XML content to store the gallery settings.
@version $Revision: 1.4 $
@since 6.1.3
|
| org.opencms.frontend.templateone |
Classes for the OpenCms 6.0 'templateone'.
The provided classes are used for the highly configurable OpenCms 6.0 'templateone'.
Most of them extend the org.opencms.jsp.CmsJspActionElement and provide extended functions
to build a website.
@version $Revision: 1.7 $
@since 6.0.0
|
| org.opencms.frontend.templateone.form |
Classes for the OpenCms 6.0 'templateone.form' module.
The provided classes are used for the highly configurable OpenCms 6.0 'templateone'.
Including some reusable form components and a form handler.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.frontend.templateone.modules |
Classes for the OpenCms 6.0 'templateone.modules' module.
The provided classes are used for the highly configurable OpenCms 6.0 'templateone'.
Just including some help classes.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.frontend.templatetwo |
Classes for the OpenCms 7.0 'templatetwo'.
The provided classes are used for the highly configurable OpenCms 7.0 'templatetwo'.
Most of them extend the org.opencms.jsp.CmsJspActionElement and provide extended functions
to build a website.
@version $Revision: 1.2 $
@since 7.0.4
|
| org.opencms.i18n |
Classes to handle internalization (i18n) and locale selection in OpenCms.
@version $Revision: 1.8 $
@since 6.0.0
@see org.opencms.i18n.CmsLocaleManager
@see org.opencms.i18n.I_CmsMessageBundle
|
| org.opencms.importexport |
Contains functions to import and export resources from the OpenCms VFS.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.jsp |
The implementation of the OpenCms JSP tag library, with some additional utility classes to
help in JSP scriplet code and navigation building.
Most of the classes in this package implement the <cms:> taglib.
To access the exact same functionality using scriptlets, obtain an instance
of a {@link org.opencms.jsp.CmsJspActionElement} from the current JSP.
Using the action element you can also access the current users OpenCms context
in a {@link org.opencms.file.CmsObject}, by using {@link org.opencms.jsp.CmsJspBean#getCmsObject()}.
To aid in template navigation building, have a look at the
{@link org.opencms.jsp.CmsJspNavBuilder} which provides a large selection of methods
to easily create dynamic navigations.
@version $Revision: 1.10 $
@since 6.0.0
@see org.opencms.file.CmsObject
@see org.opencms.file.types.CmsResourceTypeJsp
@see org.opencms.loader.CmsJspLoader
|
| org.opencms.jsp.decorator |
HTML postprocessor, used to tag single words or phrases in the HTML output.
@version $Revision: 1.4 $
@since 6.1.3
|
| org.opencms.jsp.parse |
API classes for the <cms:parse> tag.
The <cms:parse> tag allows to specify the fully qualified classname for a parsing configuration.
The concrete types and their signature are defined in this package.
@version $Revision: 1.4 $
@since 6.1.7
|
| org.opencms.jsp.util |
Utility classes to be used for JSP pages.
- Layout classes to be used in JSP templates, for XMLContent list generation.
- Bean for http status error handlers.
@version $Revision: 1.6 $
@since 6.0.0
@see org.opencms.jsp.CmsJspActionElement
|
| org.opencms.loader |
Low-level functions to manage the loading of resources from the OpenCms VFS.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.lock |
The lock state of the resources in the VFS is handled with these classes.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.mail |
Provides utility classes to generate email messages using the OpenCms email configuration.
There are currently 3 different mail types available:
- CmsSimpleMail: a simple text based email without attachments.
- CmsMultiPartMail: a text based email with attachments.
- CmsHtmlMail: an HTML formatted email with optional attachments.
@version $Revision: 1.8 $
@since 6.0.0
@see org.apache.commons.mail.SimpleEmail
@see org.apache.commons.mail.MultiPartEmail
@see org.apache.commons.mail.HtmlEmail
|
| org.opencms.main |
Provides the main OpenCms "operating system".
There are 3 main ways to access resources in an OpenCms System:
- Using the
{@link org.opencms.main.OpenCmsServlet}. This is the default usage of the OpenCms system.
- Using the
{@link org.opencms.main.CmsShell}. This is done for specific reasons, usually related to system configuration or setup.
- Using the
{@link org.opencms.main.OpenCms#initCmsObject(String)} from an application to obtain an initialized OpenCms user context.
I all use cases, the access to the OpenCms VFS is only possible with an initialized OpenCms user context,
this means by using a {@link org.opencms.file.CmsObject}.
@version $Revision: 1.10 $
@since 6.0.0
@see org.opencms.main.OpenCmsServlet
@see org.opencms.main.CmsShell
@see org.opencms.main.OpenCms
|
| org.opencms.module |
OpenCms modules provide a powerful, standardized way to extend
the core OpenCms functionality.
OpenCms modules provide a standard mechanism to extend the OpenCms functionality.
Modules can contain VFS data, Java classes and a number of configuration options.
@version $Revision: 1.7 $
@since 6.0.0
|
| org.opencms.monitor |
Contains functions to monitor the OpenCms system status.
@version $Revision: 1.7 $
@since 6.0.0
|
| org.opencms.newsletter |
Contains classes to distribute newsletters.
@version $Revision: 1.4 $
@since 6.0.0
|
| org.opencms.notification |
Contains classes for the automatical notification of outdated, expiring or released content.
@version $Revision: 1.3 $
@since 6.0.0
|
| org.opencms.publish |
Classes to handle the OpenCms publish process.
@version $Revision: 1.4 $
@since 6.5.5
|
| org.opencms.relations |
Classes to represent and validate the internal and external links/relations of resources in the OpenCms VFS.
@version $Revision: 1.4 $
@since 6.0.0
|
| org.opencms.report |
Classes used to generate the OpenCms reports, which are displayed during publish, import, export etc.
The resource files needed for the localization are contained in the file org.opencms.workplace.workplace.properties.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.repository |
Package contains all classes and interfaces needed to create or use a repository to
access the resources in the VFS.
A repository is an set of interfaces (and their implementations) to create a simple
access to the resources in the VFS of OpenCms. The repositories are configured in the
opencms-importexport.xml. The {@link org.opencms.file.wrapper.CmsObjectWrapper}
is used by the repositories for the access to the VFS. So it is possible to configure
the repositories to use one or more implementations of the
{@link org.opencms.file.wrapper.I_CmsResourceWrapper} to change the view to the resources
in the VFS. Additionaly it is possible to define filters to include or exclude files and
folders form being displayed.
Use the {@link org.opencms.repository.CmsRepositoryManager} to get a configured
{@link org.opencms.repository.I_CmsRepository}. There you get a
{@link org.opencms.repository.I_CmsRepositorySession} through login in. With that session
you will get the basic file and folder operations to the resources in the VFS of OpenCms.
Example:
I_CmsRepository repository = OpenCms.getRepositoryManager().getRepository(repository_name);
I_CmsRepositorySession session = repository.login(username, password);
@version $Revision: 1.5 $
@since 6.2.4
@see org.opencms.repository.I_CmsRepository
@see org.opencms.repository.I_CmsRepositorySession
|
| org.opencms.scheduler |
The OpenCms scheduler provides a facility to run jobs in a regular schedule, much
like the "cron" faciltiy in UNIX systems.
Please see the documentation of the class {@link org.opencms.scheduler.CmsScheduledJobInfo}
for a full description of the OpenCms scheduling capabilities.
@version $Revision: 1.7 $
@since 6.0.0
@see org.opencms.scheduler.CmsScheduledJobInfo
|
| org.opencms.scheduler.jobs |
Some predefined implementations for often used scheduled job tasks.
@version $Revision: 1.7 $
@since 6.0.0
|
| org.opencms.search |
Implements the main full text search and indexing functions available in OpenCms.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.search.documents |
Handles indexing different sorts of document and resource type from the OpenCms VFS for the full text search.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.search.extractors |
Contains a generic, low-level framework for extration of plain text content out of various popular file formats.
@version $Revision: 1.7 $
@since 6.0.0
|
| org.opencms.search.fields |
These classes control the mapping of the OpenCms content to the Lucene search fields.
@version $Revision: 1.4 $
@since 7.0.0
|
| org.opencms.security |
Access control and security classes for the OpenCms ACL permission system.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.setup |
Used during the initial setup of the database by the OpenCms setup wizard.
@version $Revision: 1.2 $
@since 6.0.0
|
| org.opencms.setup.comptest |
Contains classes to test components when runing the OpenCms setup.
@version $Revision: 1.2 $
@since 6.0.0
|
| org.opencms.setup.update6to7 |
Base classes for the database updater from version 6.x to version 7.x.
@version $Revision: 1.2 $
@since 7.0.0
|
| org.opencms.setup.update6to7.generic |
Default implementation of the database updater.
@version $Revision: 1.2 $
@since 7.0.0
|
| org.opencms.setup.update6to7.mysql |
MySql implementation of the database updater.
@version $Revision: 1.2 $
@since 7.0.0
|
| org.opencms.setup.update6to7.oracle |
Oracle implementation of the database updater.
@version $Revision: 1.2 $
@since 7.0.0
|
| org.opencms.setup.update6to7.postgresql |
PostgreSQL implementation of the database updater.
@version $Revision: 1.2 $
@since 7.0.0
|
| org.opencms.setup.xml |
Contains classes to adapt xml configuration files when updating OpenCms.
@version $Revision: 1.2 $
@since 6.0.0
|
| org.opencms.site |
Provides access to the multi-site configuration of OpenCms.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.staticexport |
Contains the functionality for the static HTML page export.
The static export allows the rendering of resources (including dynamic generated HTML
pages) to the file system. Resouces that are static exported will not longer be served
through the OpenCms VFS and the connected databases, but directly from the harddrive
of the system. This can dramatically improve performance for an OpenCms generated website.
Static export is only enabled for the "Online" project. When working in any offline project,
resources are served directly from the OpenCms VFS. This way changes made in the offline
mode are immediatly visible.
If your system is properly configured, you can directly serve static exported resources
with a standard webserver. This means the requests will not even be forwarded to the Java VM
based servlet container. This is the optimal configuration for maximum performance.
The link management is required in order to mix resources serves dynamically from OpenCms
with staitc exported resources. Example: A JSP based template renders a persoanlized web page
from OpenCms. This page can obviously not be static exported. However, there are a
number of images refered to on the page. These images are part of the template and also managed
inside the OpenCms VFS. By configuration you can staitc export these images. This means
that all links to the images must be adjusted, since the links must now point to a
different location. This is what the static export link management does. It adjusts links
to resources that have been static exported so that they point to the static export
location for the "Online" project, and to the OpenCms VFS location for offline projects.
Export points are not related to the static export.
An export point is simply a folder inside the OpenCms VFS that is copied 1:1 to a
location in the real file system during publishing. This is for example used to
copy Java classes, JAR files or other system resouces from the VFS to the WEB-INF/classes or
WEB-INF/lib folder. No link processing is done for resources written with export points.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.synchronize |
Classes used to synchronize the OpenCms VFS with the real file system.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.util |
Utility functions for String manipulation and other often used tasks.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.util.ant |
Classes used to facilitate to build OpenCms using ant.
@version $Revision: 1.3 $
@since 6.0.0
|
| org.opencms.webdav |
Provides a WebDAV access to OpenCms.
Handles all issues belonging to the WebDAV protocol.
The {@link org.opencms.webdav.CmsWebdavServlet} has to be configured in the web.xml,
where the name of the {@link org.opencms.repository.I_CmsRepository} has to be specified to use
with WebDAV.
Additionally it is possible to browse the resources in the VFS through a Web Browser by using the
url where the WebdavServlet is configured in the web.xml.
The following WebDAV clients were tested:
- Macromedia Dreamweaver
- Microsoft WebFolder
- WebDAV Mount in Mac OS X
- WebDrive (South River Technologies)
- DAV Explorer (http://www.davexplorer.org/)
Limitations:
- The WebDAV method PROPPATCH is not implemented yet.
- Does not work with Apache Tomcat < 5.5
@version $Revision: 1.6 $
@since 6.5.6
|
| org.opencms.widgets |
Contains the widget implementations, these are GUI elements used in editors and dialogs of the OpenCms workplace.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.workplace |
The base classes for the OpenCms Workplace
(standard dialog, tab dialog, report based dialog)
and the Workplace configuration classes are located here.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.workplace.administration |
This package contains the core classes for implementing the administration view.
This includes the frameset and the side menu.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.workplace.commons |
Contains often used OpenCms Workplace dialogs, for example
for file operations, user preferences and project based operations like publishing.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.workplace.comparison |
Contains OpenCms Workplace dialogs to compare OpenCms Xml Documents.
@version $Revision: 1.4 $
@since 6.0.0
|
| org.opencms.workplace.demos |
This package contains the workplace demos.
@version $Revision: 1.4 $
@since 6.0.0
|
| org.opencms.workplace.demos.list |
This package contains demos how to use the OpenCms lists for creating an Administration tool.
Since it is only a demo for developers, this tool should not be installed on a production OpenCms server.
@version $Revision$
@since 6.0.0
|
| org.opencms.workplace.demos.widget |
This package contains demos how to use the OpenCms input widgets for creating an Administration tool.
Since it is only a demo for developers, this tool should not be installed on a production OpenCms server.
@version $Revision$
@since 6.0.0
|
| org.opencms.workplace.editors |
Base classes for the editors (WYSIWYG, plain text, XML content) used in the OpenCms Workplace.
Also included is a handler to determine which editor is used depending on the resource type,
user preferences and the clients browser.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.workplace.editors.directedit |
Used to control the generation of the HTML for the "direct edit" buttons.
@version $Revision: 1.5 $
@since 6.2.3
|
| org.opencms.workplace.explorer |
Contains the functions that generate the Workplace "Explorer" view, also contains
the "New resource" wizard.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.workplace.explorer.menu |
Contains the functions that generate the Workplace "Explorer" context menu entries.
Menu item rules define the appearance of a single context menu item, depending on variuos preconditions like
the resource state, the current project, the current users permissions, and so on.
@version $Revision: 1.4 $
@since 6.0.0
|
| org.opencms.workplace.galleries |
Contains the various "Galleries" which are available in the editors and widgets of the OpenCms Workplace.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.workplace.help |
Generates online help available in the OpenCms Workplace.
These classes are used by the online help modules and provide the basic template for online help pages.
@version $Revision: 1.7 $
@since 6.0.0
|
| org.opencms.workplace.list |
Generates the list views commonly used in the OpenCms Workplace "Administration" tools.
@version $Revision: 1.3 $
@since 6.0.0
|
| org.opencms.workplace.search |
Contains classes for the workplace search tool.
@version $Revision: 1.4 $
@since 6.3.0
|
| org.opencms.workplace.threads |
A collection of thread classes that are used in the OpenCms Workplace,
usually in connection with a report.
@version $Revision: 1.7 $
@since 6.0.0
@see org.opencms.workplace
@see org.opencms.report
|
| org.opencms.workplace.tools |
Contains the base classes for implementing a tool in the OpenCms Workplace "Administration" view.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.workplace.tools.accounts |
This package contains the tool classes for the account management related administration views.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.workplace.tools.cache |
This package contains the OpenCms cache administration tool classes.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.workplace.tools.content |
This package contains the tool classes for the content tools administration view.
@version $Revision: 1.7 $
@since 6.0.0
|
| org.opencms.workplace.tools.content.check |
This package contains the tool classes for the content check tools administration view.
@version $Revision: 1.4 $
@since 6.1.2
|
| org.opencms.workplace.tools.database |
This package contains the tool classes for the database management related administration views.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.workplace.tools.galleryoverview |
This package contains the tool classes for the gallery administration overview.
@version $Revision: 1.3 $
@since 6.0.0
|
| org.opencms.workplace.tools.history |
This package contains the tool classes for the link checking related administration views.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.workplace.tools.link |
This package contains the tool classes for the link checking related administration views.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.workplace.tools.modules |
This package contains the tool classes for the module management related administration views.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.workplace.tools.projects |
This package contains the tool classes for the account management related administration views.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.workplace.tools.publishqueue |
This package contains the publish queue administration tools.
@version $Revision: 1.4 $
@since 6.5.5
|
| org.opencms.workplace.tools.scheduler |
This package contains the tool classes for the job management related administration views.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.workplace.tools.searchindex |
This package contains the tool classes for the management of search indexes and related administration views.
@version $Revision: 1.3 $
@since 6.0.0
|
| org.opencms.workplace.tools.workplace |
Contains the "Workplace Management" tools displayed in the Administration view.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.workplace.tools.workplace.broadcast |
Contains the "Message Broadcast" tool displayed in the Administration view.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.workplace.tools.workplace.rfsfile |
Contains the file access tool of the "Workplace Management" tools group
displayed in the Administration view.
This tool allows to view files of the real file system (RFS) on the OpenCms
server machine (as long as permissions are granted to it's process on the
current OS) online or to download them to the administrators machine.
@version $Revision: 1.6 $
@since 6.0.0
|
| org.opencms.xml |
Basic XML functionality and utilities used by OpenCms to maintain XML documents and content.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.xml.content |
Contains functions for structured content storage using XML, commonly called "XML content" in OpenCms.
A strcutured content can be defined using a specific XML schema subset.
The XML content is saved in various localized versions
for multilanguage support.
The validity of the XML data is maintained using a XML schema.
@version $Revision: 1.8 $
@since 6.0.0
|
| org.opencms.xml.page |
Contains functions for unstructured content storage using XML, commonly called "XML pages" in OpenCms.
XLL Pages are containers for "unstructured content", which is maintained in the form
of separate HTML elements that can be edited in OpenCms using a WYSIWYG editor.
HTML elements of pages can also be saved in various localized versions
for multilanguage support.
The validity of the XML data is maintained using a XML schema.
@version $Revision: 1.9 $
@since 6.0.0
|
| org.opencms.xml.types |
Contains the basic XML content type definitions, used for XML content and XML pages.
@version $Revision: 1.8 $
@since 6.0.0
|