Spring Python 1.1.0 released

By Greg Turnquist

Greg L. Turnquist worked on the Spring team for over thirteen years and is a senior staff technical content engineer at Cockroach Labs. He was the lead for Spring Data JPA and Spring Web Services. He wrote Packt's best-selling title, Learning Spring Boot 2.0 2nd Edition, and its 3rd Edition follow-up along many others.



book | releases | spring python



1 Comment(s)



May 11, 2010

The final release of Spring Python 1.1.0 is out. Spring Python takes the concepts of Spring and applies them to the Python. This includes functionality like dependency injection, aspect oriented programming, data access, transaction management, security, remoting, and even python-to-java-to-python communication through JMS.

Spring Python has been growing since 2006 and was the first Spring Extension to go live. The project thrives with community involvement. The biggest thanks go to our fellow committers: Dariusz Suchojad and Sven Wilhelm. You can also follow postings at http://twitter.com/springpython.

There is also a Spring Python 1.1 book to help both Java and Python coders alike come to grips with the functionality offered by Spring Python. It covers all the major functional pieces of Spring Python (except the JMS part which is very new) and includes two case studies with lots of code and high level diagrams.

The following is a list of issues worked during this major release:

Bug

[SESPRINGPYTHONPY-99] – PyroServiceExporter daemon shutting down abruptly in Python 2.6

[SESPRINGPYTHONPY-100] – SpringWiki’s non-XML configuration doesn’t match the XML app context

[SESPRINGPYTHONPY-107] – Iterating over set configurations in the container not handled properly.

[SESPRINGPYTHONPY-113] – Break dependency of ApplicationContext on Pyro

[SESPRINGPYTHONPY-129] – Add springpython.jms to setup.py’s list of packages

[SESPRINGPYTHONPY-130] – Discovered that trying to access SecurityContextHolder information was broken inside

[SESPRINGPYTHONPY-101] – Incorrect imports and a password typo in “Data Access” docs CherryPy app

Improvement

[SESPRINGPYTHONPY-98] – Migrate modules based on amara to ElementTree

[SESPRINGPYTHONPY-106] – Add TRACE logging level

[SESPRINGPYTHONPY-111] – Move InitializingObject from springpython.factory to springpython.

[SESPRINGPYTHONPY-114] – Move amara import statement inside XML-based parsers, move pyyaml inside YamlConfig

[SESPRINGPYTHONPY-119] – List all external dependencies in the ref docs

[SESPRINGPYTHONPY-126] – Update the documentation to use v. 1.1 XMLConfig XSD schema

[SESPRINGPYTHONPY-133] – Add support for SSL JMS w/ WebSphereMQ

[SESPRINGPYTHONPY-136] – Stop using Amazon’s S3 browse site, and replace it with SpringSource’s

[SESPRINGPYTHONPY-102] – Patch to make top-level build.py OS-independent

[SESPRINGPYTHONPY-136] – Stop using Amazon’s S3 browse site, and replace it with SpringSource’s

New Feature

[SESPRINGPYTHONPY-12] – Investigate creating JmsTemplate

[SESPRINGPYTHONPY-97] – Create a YAML-based IoC configuration parser

[SESPRINGPYTHONPY-105] – Add DisposableObject

[SESPRINGPYTHONPY-108] – Add lazy_init as option to @Object

[SESPRINGPYTHONPY-121] – Add LDAP support to security module (CPython)

[SESPRINGPYTHONPY-127] – Implement abstract objects

[SESPRINGPYTHONPY-132] – Add JMS SimpleMessageListenerContainer

[SESPRINGPYTHONPY-95] – Add dictionary support to DatabaseTemplate queries

[SESPRINGPYTHONPY-103] – SQLServerConnectionFactory

Refactoring

[SESPRINGPYTHONPY-128] – Cleanup CherryPy-specific classes, dependencies and overall hierarchy

[SESPRINGPYTHONPY-137] – get_last_traceback duplicates existing functionality

1 Comment

Tweets that mention Spring Python » Spring Python 1.1.0 released -- Topsy.com on May 11, 2010 at 11:39 am

[…] This post was mentioned on Twitter by Adrian Png and Planet Python, Spring Python. Spring Python said: New blog post: Spring Python 1.1.0 released http://blog.springpython.webfactional.com/2010/05/11/spring-python-1-1-0-released/ […]
Reply