Release Notes - dm Server - Version 2.0.0.M2 - HTML format

Sub-task

  • [DMS-5] - Issue log message listing cloned bundles and trace bundles as they are cloned
  • [DMS-6] - Clone extender when one of its dependencies is manually cloned, included in the application, or imported by the application at a different version to the extender
  • [DMS-389] - Instrumented Spring Travel fails to deploy on Java 5
  • [DMS-468] - Create documentation
  • [DMS-469] - Create test cases
  • [DMS-470] - Create the project SVN
  • [DMS-471] - Implement test cases
  • [DMS-472] - Create API RFC 66
  • [DMS-473] - Create the Spring Build
  • [DMS-474] - Creat tomcat bootstrap bundle
  • [DMS-475] - Write manifest rewriting url stream handler
  • [DMS-476] - Create WAR URL encoder
  • [DMS-477] - Create extender
  • [DMS-480] - Create test cases
  • [DMS-481] - Implement test cases
  • [DMS-482] - validate and re-run testImportOldSpring test method
  • [DMS-483] - diagnose initial symptoms
  • [DMS-484] - Fix for initial symptoms
  • [DMS-487] - Diagnose and fix bug
  • [DMS-488] - Create Official Spring DM 1.2 Build with wider version ranges for Spring
  • [DMS-489] - Update documentation
  • [DMS-490] - Diagnose and fix bug
  • [DMS-491] - Upgrade build to use new version of Spring DM and Spring
  • [DMS-492] - Fix bugs
  • [DMS-493] - Diagnose and fix bug
  • [DMS-494] - Update graphic
  • [DMS-495] - Config reader to recognise Watched repos
  • [DMS-496] - Add current version number
  • [DMS-497] - Fix with best-effort information
  • [DMS-498] - Update startup scripts
  • [DMS-499] - Create watcher (See pickup) and service events
  • [DMS-500] - Get from new JMX MBeans.
  • [DMS-501] - Verify watcher support in hosted repos
  • [DMS-502] - Add watched repo support to hosted repo (config code reduction)
  • [DMS-503] - Extract information from blog entry and put in Programmer Guide
  • [DMS-505] - Write rippling script
  • [DMS-506] - Update modules to look for dependencies in variable locations
  • [DMS-507] - Devise schema
  • [DMS-508] - Publish schema
  • [DMS-510] - Create documentation
  • [DMS-514] - Add validation of repo names to Config reader
  • [DMS-517] - Unify windows and UNIX behavior
  • [DMS-518] - Diagnose and fix bug
  • [DMS-519] - Create strawman
  • [DMS-520] - Discuss and refine design
  • [DMS-529] - Diagnose and Fix Bug
  • [DMS-531] - do work associated with the top level task
  • [DMS-536] - Recreate and fix if needed
  • [DMS-541] - Rework the BundleManifest API
  • [DMS-545] - Create test-cases
  • [DMS-546] - Implement test-cases
  • [DMS-551] - Update page with new information
  • [DMS-552] - Update Guide with new information and screenshots
  • [DMS-557] - Update and release GreenPages
  • [DMS-559] - Diagnose and fix bug
  • [DMS-561] - Diagnose and fix the bug
  • [DMS-574] - Re-read rfc122
  • [DMS-576] - Create Medic proposal
  • [DMS-577] - Discuss and refine proposal
  • [DMS-578] - Write up final proposal
  • [DMS-579] - Stories for Medic
  • [DMS-586] - Finish case insensitive map code
  • [DMS-587] - Test case insensitive map - full coverage
  • [DMS-588] - Integrate case-insensitive map into Bundle Manifest implementation
  • [DMS-589] - Ripple up code in DMS-131
  • [DMS-590] - Get Felix ConfigAdmin into EBR
  • [DMS-597] - Perform comparative analysis and document results
  • [DMS-598] - Scope pipeline proposal
  • [DMS-599] - Discuss and refine proposal
  • [DMS-600] - Document outcome
  • [DMS-601] - Create stories and story points
  • [DMS-607] - Petclinic
  • [DMS-611] - Formtags
  • [DMS-612] - Wicket Framework sample
  • [DMS-613] - Struts Framework Sample
  • [DMS-614] - Instrumented Spring Travel Sample
  • [DMS-616] - Discuss and refine proposal
  • [DMS-617] - Discuss and refine proposal
  • [DMS-618] - Discuss and refine proposal
  • [DMS-619] - Stories for Medic
  • [DMS-620] - Stories for Medic
  • [DMS-621] - Stories for Medic
  • [DMS-623] - grails sample
  • [DMS-624] - Discuss and refine proposal
  • [DMS-625] - Hello World shared services sample
  • [DMS-626] - Discuss and refine proposal
  • [DMS-627] - formtags email service app
  • [DMS-629] - Discuss and refine proposal
  • [DMS-630] - Discuss and refine proposal
  • [DMS-631] - Create stories and story points
  • [DMS-632] - Create stories and story points
  • [DMS-633] - Create stories and story points
  • [DMS-634] - Create stories and story points
  • [DMS-637] - Roughly split apart install and start
  • [DMS-641] - Document and Publish
  • [DMS-643] - Establish and document scope
  • [DMS-644] - Establish and document scope
  • [DMS-645] - Create stories and size them
  • [DMS-646] - Create stories and size them
  • [DMS-647] - Create stories and size them
  • [DMS-650] - jamwiki sample
  • [DMS-652] - petclinic openJPA war sample
  • [DMS-654] - Spring Travel: Spring Faces Reference war
  • [DMS-655] - Spring Travel: Spring and JSF Reference war
  • [DMS-656] - Spring Travel: Spring MVC and Web Flow Reference war
  • [DMS-660] - activemq war sample
  • [DMS-662] - webwork framework sample war

Defect

  • [DMS-47] - missing package import errors not reported when using component-auto-scan
  • [DMS-57] - DefaultManagedResourceExporter should handle bean names bundle specific
  • [DMS-162] - Scope service repository not cleaned up when an app is undeployed
  • [DMS-164] - No error communicated when syntax error in .libd exists
  • [DMS-174] - update of bundle version in the bundle manifest file is not reflecting on the admin console unless the platform restart.
  • [DMS-175] - com.springsource.server.deployer.core.FatalDeploymentException on deployment recover
  • [DMS-176] - Getting the exception "org.springframework.context.ApplicationContextException" when trying to remove the clash of application context of two bundles after the clash of application context happened
  • [DMS-177] - Server is giving the different log output on Solaris platform upon restart of Server which is having set of installed applications.
  • [DMS-178] - Admin console is showing the entries of application trace under the Serviceability Destinations even if the particular application trace file is deleted from the SERVER_HOME/serviceability/trace directory
  • [DMS-181] - Investigate problem with runtime creation of CGLib proxies
  • [DMS-237] - Instrumented Spring Travel fails to deploy on Java 5
  • [DMS-394] - Deployment recovery of scoped application is failing upon manual cloning on Import-Library
  • [DMS-403] - org.springframework.osgi.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed on shutdown of dm Server
  • [DMS-419] - start of dm Server with -clean option not able to clear the work directory and all trace, log and dump files
  • [DMS-420] - No Information found under Server Properties and Serviceability Destinations of admin console screen upon start of dmServer
  • [DMS-422] - Failed to get class loader for bundle error - Internal org.eclipse.osgi NPE
  • [DMS-433] - dm Server user guide needs to upated in the section "2.4.2 Microsoft Windows" to startup.bat for Microsoft Windows
  • [DMS-434] - unable to connect to JConsole using local JMX connection
  • [DMS-437] - dm Server splash screen includes a "1.0.0" version rather than "2.0.0"
  • [DMS-438] - "Origin" of an artifact deployed using Admin Console displays the full filepath rather than the text "Admin Console" (which is what appeared in 1.0)
  • [DMS-527] - server.serviceability.tracing.internal.TracingPrintStreamWrapper throws NullPointerException on System.out(null)
  • [DMS-535] - Documentation error and path reference in getting started guide needs correcting
  • [DMS-537] - The 2.0 splash screen's documentation links link to out-of-date versions of some of the documentation
  • [DMS-538] - Problems with the 2.0.0.M1 version of the getting started guide
  • [DMS-542] - inconsistent dump behaviour during deployment failure in normal and recovery
  • [DMS-543] - dm Server 1.0 download page (http://www.springsource.com/node/485) does not list getting started guide or greenpages sample.
  • [DMS-555] - There is no information displayed in the log messages when an application fails to deploy due to dependency satisfaction failed.
  • [DMS-558] - scoped application fails to deploy that is using different version of spring than the spring version used by dm Server
  • [DMS-560] - Any Web module with a Bundle-Classpath header in its manifest fails to deploy
  • [DMS-566] - Potentially incorrect wiring for javax.mail bundle
  • [DMS-567] - Import-Bundle generated bundle-version attribute is incorrectly an open range
  • [DMS-636] - Problems with pages on springsource.org
  • [DMS-638] - java.lang.OutOfMemoryError: PermGen space on repeating the deployment and undeployment of war personalities
  • [DMS-639] - Not able to deploy spring travel app(1.2.0.RELEASE) on 2.0.0.x version of dm Server by providing 2.5.6.A version of spring framework libraries to the dm Server repository
  • [DMS-653] - StandardBundleManifest.toString is no longer useful

Story

  • [DMS-34] - Enable application programmer to import a Spring framework bundle with a distinct version from the version used by the kernel
  • [DMS-37] - Enable administrator to see, in the log, which bundles have been cloned
  • [DMS-192] - As a user, I can deploy a Servlet 2.4 WAR file using RFC 66
  • [DMS-452] - As a user I'd like to use a watched repository
  • [DMS-455] - As a user to be notified if my repository name is not valid
  • [DMS-550] - As a user I want to be able to obtain and use a Getting Started Guide appropriate to the Milestone release.

Task

  • [DMS-16] - Reinstate cloning support for web modules
  • [DMS-38] - Enable support personnel to observe the cloning of bundles in the trace
  • [DMS-74] - Document import-scope header of Import-Bundle in Programmer's Guide
  • [DMS-131] - Support case-insensitive header names in Dictionary form of a BundleManifest
  • [DMS-397] - Update GreenPages sample application to create an M2 project and add Bundle nature after the fact after DMST have been updated to no-longer add classpath container on this action.
  • [DMS-404] - Upgrade to Spring 3.0 Mx
  • [DMS-446] - Automate the version rippling behavior
  • [DMS-453] - Design an publish an open repository index format for access via REST
  • [DMS-459] - Document plan support
  • [DMS-461] - Design and document the install pipeline for the deployer
  • [DMS-462] - Create automated functional tests for the admin console deployment functionality
  • [DMS-463] - Create automated functional tests for the admin console undeployment functionality
  • [DMS-464] - Create automated functional tests for the admin console server admin metadata
  • [DMS-467] - Document and blog proxy creation semantics in Programmers Guide
  • [DMS-479] - Create RFC66 infrastructure
  • [DMS-485] - Create RFC 66 internals
  • [DMS-530] - Update the admin console and splash screen jsps with the more textual infromation of each and every division,table e.t.c
  • [DMS-540] - Rework the BundleManifest API
  • [DMS-549] - Evaluate the current commercial release and the forked ASL version of the Java Service Wrapper to decide which to use for service startup.
  • [DMS-568] - Size and scope Medic
  • [DMS-569] - Size and scope the deployer pipeline
  • [DMS-573] - Complete and ripple Bundle Manifest implementation
  • [DMS-602] - Design and Document Config properties required for all subsystems
  • [DMS-605] - Automate testing of all dm Server sample applications
  • [DMS-606] - Automate testing of external sample apps
  • [DMS-642] - Size and scope the modular micro kernel

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.