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

[Juergen H. <ju...@in...>]

James, everybody,

After a few private discussions with people that are working on extensible
XML bean definition models as well, I have decided to defer the entire topic
to Spring 1.3 (with RC1 scheduled for August). I hope that's OK with you,
James...

The approaches that are currently in discussion are quite different, so we
shouldn't ship anything in 1.2.2 that might get completely reworked in 1.3.
Consequently, I've removed the prototype from CVS again, as we are about to
ship 1.2.2 this week. We shouldn't ship any such extension that we need to
remain backwards-compatible with - at this point of time.

I hope you understand our reasoning here. For the time being, you can of
course create your own ApplicationContext subclass that uses a custom
XmlBeanDefinitionParser, or use a GenericApplicationContext in conjunction
with a custom XmlBeanDefinitionParser:

  GenericApplicationContext ctx = new GenericApplicationContext();
  XmlBeanDefinitionReader xmlReader = new XmlBeanDefinitionReader(ctx);
  xmlReader.setValidating(false);
  xmlReader.setNamespaceAware(true);
  xmlReader.setParserClass(MyXmlBeanDefinitionParser.class);
  xmlReader.loadBeanDefinitions(new ClassPathResource("myBeans.xml"));
  ctx.refresh();

I've kept the new basic processing hooks in XmlBeanDefinitionReader and
DefaultXmlBeanDefinitionParser, although in a slightly reworked fashion.
This should make it as seamless as possible to plug in a custom extension
for the meantime, no matter which XML extension model you're using.

We need to start a discussion on this as we move forward towards Spring 1.3,
involving everybody who's interested. Among others, Erik Wiersma and Aleks
Seovic have been working on this topic as well. Guys, let's start a concrete
discussion on this right after JavaOne - and create a unified solution for
Spring 1.3 that addresses everyone's needs!

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of jas...@ma...
Sent: Tuesday, June 14, 2005 12:20 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Extensible XML processing in
Spring: prototype version available in CVS HEAD



On 14 Jun 2005, at 09:05, jas...@ma... wrote:

> On 14 Jun 2005, at 08:37, Juergen Hoeller wrote:
>
> Its worth stressing, this is a pretty trivial change - has minimal
> coding impact and adds a pretty trivial plugin interface.

A couple more examples to show the kind of things possible with CVS
HEAD of Spring.

We've done the JBI deployment descriptor as a Spring XML extension,
which is a bit more hardcore XML mapping...

here are the POJOs
http://cvs.servicemix.codehaus.org/servicemix/base/src/main/java/org/
servicemix/jbi/deployment/

with the Spring XML extension implementation classes
http://cvs.servicemix.codehaus.org/servicemix/base/src/main/java/org/
servicemix/jbi/deployment/impl/

these classes rely on these generic Spring helper classes, which we
could move into Spring for others to reuse
http://cvs.servicemix.codehaus.org/servicemix/base/src/main/java/org/
servicemix/jbi/config/spring/

finally, here's an example of a deployment descriptor we can parse
(with embedded Spring XML being possible within  the XML of course :)

http://cvs.servicemix.codehaus.org/*checkout*/servicemix/base/src/
test/resources/org/servicemix/jbi/deployment/example.xml?rev=HEAD

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



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
shotput
a projector? How fast can you ride your desk chair down the office luge
track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer