Home Page / Documentation / Download / BetaCMS 2.1.0.GA / Release Notes for 2.1.0.GA

Release Notes - BetaCMS - Version 2.1.0.GA

Bug

• [BCMS-160] - Delete action appears in web console's edit form inside single value property of ContentObject type.
• [BCMS-165] - All types defined inside the same XSD file (ContentType, Complex global type) should have the same namespace URI and prefix when exported to XML
• [BCMS-170] - BinaryChannel.getDirectURL() returns wrong URL
• [BCMS-175] - Taxonomies 'fileResourceContentType', 'contentDesignation' do not exist and therefore users cannot create contentObjects of type genericContentResourceObject or fielResourceObject
• [BCMS-184] - CriterionParser should not add a content type name criterion when reserved property name 'contentTypeName' is used to criteria list. It simply must return it

• [BCMS-189] - ViewCountPersistanceScheduler and WebPublicationScheduler cannot login to a remote BetaCMS repository

Improvement

• [BCMS-107] - Remove deprecated BetaCMS principal AuthorizedRepositories
• [BCMS-161] - Replace method toXml provided in APIs ContentObject, Topic, RepositoryUser, Space and Taxonomy with method xml declared in parent interface CmsRepositoryEntity
• [BCMS-163] - ContentObject interface should provide methods for exporting specific properties to xml and json
• [BCMS-168] - Provide the ability to dump search results eported as XML or JSON to an OutputStream
• [BCMS-169] - BetaCMS repository client should provide a method to inform whether client is connected to a remote server or not
• [BCMS-174] - TopicCriteria and ContentObjectCriteria should provide methods which will create a criterion for a built in property without adding the criterion to criteria list
• [BCMS-176] - Description of a content type or a property should be provided in more than one languages
• [BCMS-177] - Remove deprecated XML attribute bccmsmodel:description from all built in definition schemas
• [BCMS-179] - New methods isTypeOf and getSuperContentTypes() for ContentObjectTypeDefinition
• [BCMS-180] - Moved method CmsDefinition.getDescription() to LocalizableCmsDefinition.getDescription()
• [BCMS-181] - Access to localized content type or property definition should be more obvious and user friendly
• [BCMS-182] - Add method in DefinitionService to obtain content type hierarchy
• [BCMS-183] - ContentObjectCriteria should be able to recognize whether a specified content type is a base type or not in order to produce the proper criterion
• [BCMS-192] - Enhance internal schema named 'resourceRepresentationTemplateObject' with an extra property that stores a template for generating RSS Feeds
• [BCMS-193] - Fix maxStringLength of string properties in internal schema named 'resourceRepresentationTemplateObject'
• [BCMS-194] - Enhance simpleCmsPropertyValueWrapper.xhtml to handle string properties with with unlimited number of chars
• [BCMS-204] - Allow users to specify offset and limit on AbstractContentObjectResource in cases where default values are not sufficient
• [BCMS-206] - Change cardinality for built in property administrativeMetadataType.language

• [BCMS-209] - Various Enhancements to BinaryChannel Class

New Feature

• [BCMS-162] - BetaCMS content model entities (ContentObject, Topic, Taxonomy, etc) should export to JSON format
• [BCMS-164] - ContentService should be able to export query results to JSON
• [BCMS-166] - Resource API should provide methods for exporting a content object in XML and JSON format
• [BCMS-167] - Create BetaCMS EL resolver to resolve EL expressions related to BetaCMS API
• [BCMS-178] - Support for content type extended another content type and not only contentObjectType
• [BCMS-185] - Implement the provision of JSON with Padding (JSONP) and XML with Padding in Resource API
• [BCMS-191] - Implement RESTful access to Taxonomies and their Topics (GET)
• [BCMS-195] - BetaCMS administration console should have a content type editor in order to manage XSD schemas for all content types
• [BCMS-196] - DefinitionService should provide a method for validating XSD schemas in respsect to existing schemas for a repository
• [BCMS-201] - Portal query API should take into account active locale when querying a repository
• [BCMS-202] - Improve template selection mechanism to be able to identify locale specific templates
• [BCMS-203] - Create a BetaCMS Resource Bundle to be used along with JSF Resource Bundle, in order to serve messages from a taxonomy