- Alle anderen static initalizers haben jetzt am Anfang und Ende eine Log-Ausgabe (Level debug), in Klassen die bisher keinen Logger hatten wurde ein Logger eingebaut
- log4j.properties in ccm-core enthält jetzt vorbereitetet, auskommentierte Zeilen für alle Klassen mit static Blöcken
git-svn-id: https://svn.libreccm.org/ccm/trunk@748 8810af33-2d31-482b-a856-94f89814c4df
es in einer mit spezializierten Objekten einen anderen TraversalAdapter als für die Detailansicht zu verwenden.
git-svn-id: https://svn.libreccm.org/ccm/trunk@667 8810af33-2d31-482b-a856-94f89814c4df
kleinere Änderungen in ArticleSectionPanel notwendig, unter anderem die Möglichkeit den anzuzeigenden MultiPartArticle von außen zu setzen. Das ist notwendig, da
sich das Index-Item nicht über einen der im Modul MultiPartArticle verfügbaren Wege abfragen lässt.
git-svn-id: https://svn.libreccm.org/ccm/trunk@622 8810af33-2d31-482b-a856-94f89814c4df
- Die Templates werden im Navigation-Admin in der Auswahlbox für den Template Dispatcher Context jetzt nach Titel sortiert (vorher wurden sie unsortiert angezeigt).
git-svn-id: https://svn.libreccm.org/ccm/trunk@601 8810af33-2d31-482b-a856-94f89814c4df
- Some changes on the renders to make some parts of the rendering overwritable in a child class
- Added a browse button Xinha
git-svn-id: https://svn.libreccm.org/ccm/trunk@600 8810af33-2d31-482b-a856-94f89814c4df
independently from the actual content-section configuration.
Now uses the content-section parameter to automatically reflect
configuration changes.
git-svn-id: https://svn.libreccm.org/ccm/trunk@470 8810af33-2d31-482b-a856-94f89814c4df
* Die Konfigurations-Parameter waf.categorization.supported_languages und com.arsdigita.cms.languages zu waf.kernel.supported_languages zusammengefasst
* In DispatcherHelper eine Methode getNegotiatedLocale eingeführt, die beim Aushandeln der Locale zwischen Browser und CCM auch dem Konfigurations-Parameter waf.kernel.supported_languages respektiert
* Alle Aufrufe von DispatcherHelper.getRequest().getLocale() auf die neue Methode DispatcherHelper.getNegotiatedLocale() geändert.
* Konfiguration von Categorization geändert. Verwendet jetzt keinen eigenen Eintrag für die unterstützten Sprachen mehr. Stattdessen wird die Konfiguration von Kernel verwendet.
* ContentSectionInitializer geändert, so daß er nun Kernel.getConfig().getSupportedLanguages() verwendet.
Außerdem diverse Aufräumarbeiten (Unnötige Imports entfernt, Reformat, Annotationen hinzugefügt, Klammern bei If-Anweisungen) in den Sourcen, wo immer sie mir in die Händegefallen sind.
git-svn-id: https://svn.libreccm.org/ccm/trunk@419 8810af33-2d31-482b-a856-94f89814c4df
Filter geändert, so daß er bei einer nicht unterstützten Sprache die Standardsprache verwendet. Eingestellt wird das über waf.categorization.supported_languages
git-svn-id: https://svn.libreccm.org/ccm/trunk@360 8810af33-2d31-482b-a856-94f89814c4df
Ich konnte zwar nicht alle Stellen im laufenden System verifizieren, aber nach meinen Verständnis sollte die Unterstützung nun vollständig sein.
git-svn-id: https://svn.libreccm.org/ccm/trunk@271 8810af33-2d31-482b-a856-94f89814c4df
Beitrag von Terry:
- Neues Import Format fuer terms: SKOS
- Keyphrase extraction utility, nutzbar um Kategorien vorschlagen zu lassen,
die zu einem content item passen.
Update Script:
ccm upgrade ccm-ldn-terms --from-version 6.5.0 --to-version 6.5.1
Es sind Änderungen am theme erforderlich, um die Funktionen nutzen zu können:
siehe:
ccm-ldn-aplaws/src/com/arsdigita/aplaws/ui/TermWidget.java
ccm-ldn-aplaws/web/__ccm__/themes/aplaws/types/ContentTypes.xsl
ccm-cms/web/__ccm__/static/cms/admin/category-step/category-step.xsl
ccm-ldn-navigation/src/com/arsdigita/london/navigation/cms/CategoryDataCollectionDefinition.java
Damit ist trunk hb auf Stand r1902 aplaws trunk
(1871 bis 1876 waren eigene patches, die bereits enthalten sind, ebenso 1894)
Patch 1879 uebersprungen, fuegt dictionary fuer eclipse in das root Verzeichnis
von trunk ein. Da gehoert aber nichts hin, ausserdem Eclipse im Moment nicht
in Benutzung hier.
git-svn-id: https://svn.libreccm.org/ccm/trunk@235 8810af33-2d31-482b-a856-94f89814c4df
r1795: First part of the conversion of CCM to be deployed in a standard way
r1796: Multilanguage categorization (already local, but upgrade script
added, comments and translation added)
First part of the conversion of CCM / APLAWS to be deployed in a standard way
by a *.war file.
Backwards compatible to the procedures so far. The ccm scripts can be used
as used to. Only difference is the location of some files (see below).
As an alternative the webapps directory created by the ccm scripts can be
moved into a standard tomcat container or can be added as a virtual host.
APLAWS no longer depends on all the environment variables. For detailed
instructions see documentation on the WIKI. This is a temporary solution,
further enhancements are on the way!
No update script required for this part.
Modifications:
- Creation of a c.ad.runtime.CCMResourceManager class, which currently
handles just the file locations. It replaces the dependency from the
CCM_HOME environment variable. It is initialized during startup of the
servlet container or by the entry point of the installation tools (i.e.
c.ad.packaging.mastertool). It replaces the c.ad.packaging.CCM class
as well. Currently contains backwards compatibility code to check the
runtime environment just in case the initialization is missing (will be
removed later).
- Creation of c.ad.web.CCMApplicationContextListener class which is
notified by the servlet container at the beginning of the startup procedure.
Initialises CCMResourceManager. Must be configured by web.xml (if a contributed
package overwrites the trunk values)!
- File location changes:
- Configuration registry moved to [appbase]/WEB-INF/conf/registry
- ps2fs files moved to [appbase]/ps2fs
(can be modified by configuration parameter)
- lucene index files moved to [appbase]/WEB-INF/work/lucene
(can be modified by configuration parameter)
Developers watch out! ant clean now removes these files, too (esp. registry)!
- XML factory classes are now determined by configuration parameters
- waf.xml.xsl_transformer=[saxon (default)|jd.xslt|resin|xalan|xsltc]
- waf.xml.dom_builder=[xerces (default) | resin]
- waf.xml.sax_parser=[xerces (default) | resin]
- Package c.ad.packaging reorganized so it contains just installation
related code. Runtime configuration related code moved to c.ad.runtime.
Code is not part of the API.
- log4j configuration file is still at the old location, but is not used
anymore! It will be moved to [appbase]/WEB-INF/conf/ in the future.
Developers, modify the file ~/webapps/WEB-INF//classes/log4j.properties
in the meantime.
- While working on the code some deprecated classes and method invocations
replaced by supported API. If a class is no longer used by any module in
trunk, the class has been removed by appending "nolongerInUse" to the file
name. If any of the contributed modules is still depending on deprecated code
it is easy to find and to follow the recommended replacement instructions. Do
not re-incorporate deprecated code! We have to clean up the code base!
Second part: Multilanguage categories
Added update script
Translation of some comments, added comments
version number bumped to reflect the major changes
git-svn-id: https://svn.libreccm.org/ccm/trunk@73 8810af33-2d31-482b-a856-94f89814c4df
r1727: Fixed NPE when Content Item List portlet had no category selected.
r1748: Added DataCollectionDefinition.setBlackListTypes() to filter for
for content types which are blacklisted in the AtoZ module
r1749: Bumped version number from 6.5.1 to 6.5.2
git-svn-id: https://svn.libreccm.org/ccm/trunk@64 8810af33-2d31-482b-a856-94f89814c4df
Folgendes funktioniert:
- Anlegen und Löschen von Sprachversionen per Adminoberfläche
- Config-Parameter für Fallback-Modus, unterstützte Sprachen und
Standard-Sprache
- Lokalisierte URLs in navigation
- Dekativieren von Sprachversionen
Folgendes funktioniert noch nicht:
- Bearbeiten von Sprachversionen per Adminoberfläche
- evt. ist die Untersützung von lokalisierten URLs noch nicht vollständig
d.h. in anderen Anwendungen als navigation
Quasimodo
git-svn-id: https://svn.libreccm.org/ccm/trunk@41 8810af33-2d31-482b-a856-94f89814c4df
r1666 | chrisg23 | 2007-09-19 12:40:53 +0200 (Mi, 19 Sep 2007)
Currently date order categories work fine unless you have more than one page of objects - as the ordering is only done in xsl, when you have pagination, the java side returns a subset of objects ordered according to order set in jsp page (eg alphabetical) and then that subset is date ordered, but that means that as you page back and forth the date ordering is completely wrong. This change fixes that by enforcing date ordering in the java code if the current category is date ordered. Different object types have different attribute names for date - and only the renderer knows which attributes are available. I have added a method to the definition that gives the definition a reference to the renderer - the renderer now returns a list of attributes which the definition looks through and finds the first attribute that is of type date and uses that as the basis for date ordering if the current category is date ordered.If there is more than one date ordered attribute output in the list, then ensure the one used for ordering in xsl is the first one specified in jsp. I could have just made a setDateOrderAttribute method that takes a string attribute name argument and called that from the jsp page - it would have made the code quite a bit simpler. I chose this route to ensure that the date attribute specified for ordering in java was present in the datacollection, and so that there is no need to edit existing jsp pages. That is probably being overcautious though. Never mind, this works fine anyway - maybe one day I will refactor it to use the simpler approach
------------------------------------------------------------------------
r1667 | chrisg23 | 2007-09-19 12:48:36 +0200 (Mi, 19 Sep 2007)
Continuation of changes in r1651 - output publisher flag on index pages too
------------------------------------------------------------------------
r1668 | chrisg23 | 2007-09-19 12:53:08 +0200 (Mi, 19 Sep 2007)
See r1661 - ensure that this version of object-list.xsl caters for all listed objects, not just content pages, by referring to displayName (defined in ACSObject and now output on all object lists in default navigation jsp page
git-svn-id: https://svn.libreccm.org/ccm/trunk@28 8810af33-2d31-482b-a856-94f89814c4df
r1661 | chrisg23 | 2007-09-19 09:33:20 +0200 (Mi, 19 Sep 2007)
Include applications on navigation pages where they have been assigned to navigation categories
(currently possible for forums if the optional ccm-categorised-forum module in contrib/wsx is loaded).
git-svn-id: https://svn.libreccm.org/ccm/trunk@26 8810af33-2d31-482b-a856-94f89814c4df
SVN-Version 1.0.5 Rev 1603 + alle meine Änderungen
- Navigation (Adaptive Mode)
- Paginator angeglichen
- Paginator <NoContent> -Tag eingeführt
- manipulate-input.js erweitert für deutsche Umlaute (erste Version)
und vielleicht noch ein paar andere Dinge...
git-svn-id: https://svn.libreccm.org/ccm/trunk@1 8810af33-2d31-482b-a856-94f89814c4df
jensp
pb
quasi