Re: Release Work

see below

Marc Palmer wrote:

> Lane Sharman wrote:
>
>> WM Faithful,
>>
>> I am undertaking Release 2 work. I would like the release to be 2.1.
>>
>> Also, eric, please get the webmacro.org site back up and announce 
>> this to the group. As soon as this is done, I would like respective 
>> authors of their pages to go in and refresh those pages.
>>
>> Also, I would strongly urge that a bridge between WM and Spring be 
>> completed. This is really important because Spring is a useful 
>> container for application execution and it supports different add-on 
>> tools. The people who have expressed interest here should do the 
>> logical thing: get an IM session running, describe the work, and, 
>> just do it.
>
>
> I have pending commits for this. If we are going to skip 2.0 and go 
> straight for 2.1 with "early access" Spring and JSP I will commit this 
> stuff tomorrow.

I would like it if you would commit this stuff right away. Be sure to 
add some unit tests.

btw: have you ever thought of just doing a WM Container? In fact, this 
might be a really nice subproject because it would show how to run WM in 
both standalone and in Web-mode.

Also, I see a limitation with XML property specification ala Spring. 
First, I do not like XML as a bean property spec. I would much rather 
use #bean to instantiate and set props . Second, it does not allow for 
the beans properties to persist in state and then evolve. Fine for the 
default settings of a bean.

I have done a lot of work over the years with property modeling and it 
drives me crazy to see static XML machinery for initializing beans. A WM 
init script using #bean would and is such a cleaner way:

#if ($Store.AppParams == null) {
    $AppParams = #defaultParameters("AppParams")
}
#else {
    $AppParams = $Store.AppParams
}

is so much more readable then a bunch of angle bracket statements and 
proprietary type definitions. I am so tired of learning yet another XML 
type schema.

Don't get me wrong though. Spring is a significant improvement over J2EE 
containers!

-Lane

>
> The WM Spring code I have is simply a conversion of the Velocity 
> Spring view for WM. There is an outstanding issue in that Velocity 
> supports a "spring.vm" macro that is on the classpath in spring.jar 
> and you can pull it in from any template as just "spring.vm" I 
> believe. We can't do this easily as far as I can see, as we need to 
> modify the WM config from within the Spring view code, which means 
> overriding any webmacro.properties etc.
>
> ...which is why for WM 2.5 or 3 I am committed to overhauling the core 
> configuration, Broker and resource handling stuff so that it is 
> bean-like, not singletons, and therefore IoC/DI friendly.
>
> Keats and I haven't merged our ideas on the JSP taglib yet. I will get 
> to this this week.
>
> Cheers


-- 
Lane Sharman
Providing Private and SPAM-Free Email
http://www.opendoors.com
858-755-2868



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click