Re: [Springframework-developer] Release schedule

[Paul F. <pau...@ho...>]

Juergen/group

Wow - I am very impressed with the amount of work you are contributing
towards the Spring framework - if only I could find the time I would love to
be more active.

Personally, I think it would help if tasks were cleary defined and assigned
to individuals - I am unsure what areas need looking at and am conscience
that I may be duplicating effort if I just dive in.  I know that tasks are
discussed within this list but this should be documented  - or does this go
against the open source idealogy.

BTW I have attached a struts plugin that I have written and am using with
success - it needs reviewing.

Here is a brief description of its use - I assume struts familarity:

A Struts PlugIn can be used to provide close integration with Spring's bean
based infrastructure.  The root
com.interface21.web.context.WebApplicationContext object, which defines
JavaBeans and their relationships ,can be added to a web application's
ServletContext by this PlugIn, as an alternative to using the
ContextLoaderServlet.

PlugIn modules can be configured using the <plug-in> element in the
struts-config.xml file.  Classes that implement the PlugIn interface must
have a zero-argument constructor, configuration is performed by providing
standard JavaBeans property setter methods.

The PlugIn requires a single configuration parameter to be provided in the
deployment descriptor, contextClass. This parameter is the class name of the
WebApplicationContext implementation to provide a context for this
application, in this case XmlWebApplicationContext.   The PlugIn merely
instantiates the class and provides it with the current ServletContext
object.

<plug-in className="com.phoenix.web.context.ContextLoaderPlugin">
    <set-property property="contextClass"
value="com.interface21.web.context.support.XmlWebApplicationContext"/>
</plug-in>

The WebApplicationContext requires a configUrl to be set in the web.xml
file.  This is the URL to the configuration file that defines the business
objects and their relationships.  These are exposed as JavaBeans to classes
in the web application framework, servlet filters and JSP custom tags.

<context-param>
    <param-name>configUrl</param-name>
    <param-value>/WEB-INF/applicationContext.xml</param-value>
</context-param>

Struts Actions can access these business objects by looking up the
WebApplicationContext in the ServletContext.

Note:  Certain bean names have special significance and one must be provided
in the configuration file, "messageSource".  This defines an
internationalizable repository for errors and other messages.  Even if the
application uses the Struts resource bundle, this is still required, along
with the messages.properties file in /WEB-INF/classes.

<bean name="messageSource"
class="com.interface21.context.support.ResourceBundleMessageSource">
    <property name="basename">messages</property>
</bean>


----- Original Message -----
From: "jürgen höller [werk3AT]" <jue...@we...>
To: <spr...@li...>
Sent: Thursday, March 06, 2003 10:18 AM
Subject: [Springframework-developer] Release schedule


Hi committers,

We should try to approach a 0.8 release ASAP, as the lack of a formal
distribution definitely hinders Spring adopting. IMO we should aim at end of
March.

Unfortunately, the lack of documentation is a major issue: Currently, a
potential user should have both Rod's book and the framework sources. I
consider polishing JavaDoc comments and including generated JavaDoc a must,
already for 0.8. Separate online documentation will be a must for 1.0, but
not earlier, I guess. Any volunteers for either?

The further schedule will probably consist of 0.9 at end of April and 1.0
around June. Of course, the actual dates will be determined by Spring's
quality and stability, not by a deadline. Nevertheless, I have the urge to
proceed release-oriented.

IMHO, we are easily feature-complete for 0.8 now, as multipart request
handling can also wait until 0.9. Beyond that, we should think about further
must-haves for 1.0. The Struts plugin comes to my mind, for example, and
better test coverage and homogeneous code style. Beyond the framework
itself, we will need example apps, and a nice little website with some sort
of "project identity".

What do you think?

Regards,
Juergen


DI Jürgen Höller
Senior System Architect
__________________________________

werk3ATS - division systementwicklung
part of werk3AT internetmedien oeg

europaplatz 4
A - 4020 linz

t.  +43 (0) 732 71 65 29
f.  +43 (0) 732 71 65 29 3
jue...@we...
www.werk3at.com
__________________________________
werk3ATS - WIR ENTWICKELN ERFOLG


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer