Re: [Springframework-developer] Extensible XML processing in Spring: prototype version available in CVS HEAD

[<jas...@ma...>]

On 14 Jun 2005, at 08:37, Juergen Hoeller wrote:
> Hi James,
>
> Interesting stuff :-)
>
> However, this needs to be aligned with whatever general way we'll  
> go for XML
> extension stuff in Spring 1.3. Your approach looks reasonably  
> simple, but
> hard-codes a few assumptions, such as the lookup mechanism (even  
> the lookup
> path prefix).

Its using the standard META-INF/services/* approach folks use to  
dynamically resolve extensions on the classpath. See JAXP and heaps  
of other libraries which use this mechanism.

Erik Wiersma offered some interesting comments on my recent blog post...
http://radio.weblogs.com/0112098/2005/06/10.html#a527



> We need to be careful regarding what we ship in 1.2.2 here, in  
> particular if
> things are still subject to change. This is not about a release  
> candidate
> for Spring 1.3; it's only a point release for 1.2...
>
> I'm not opposed to shipping that stuff in 1.2.2 as long as it received
> proper review. I'm gonna have a deep look at it myself, but I would  
> also be
> grateful for any further feedback - both by yourself and by other  
> interested
> people :-)
>
> Spring 1.2.2 is scheduled for next week; it will definitely be  
> released
> before JavaOne. So if we can't agree on that level of XML extension
> mechanism in the given timeframe, we need to reconsider on how to  
> proceed
> with the current stuff.

OK.

Its worth stressing, this is a pretty trivial change - has minimal  
coding impact and adds a pretty trivial plugin interface.

James
-------
http://radio.weblogs.com/0112098/