<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to spring framework</title><link>https://sourceforge.net/p/ximl/wiki/spring%2520framework/</link><description>Recent changes to spring framework</description><atom:link href="https://sourceforge.net/p/ximl/wiki/spring%20framework/feed" rel="self"/><language>en</language><lastBuildDate>Sat, 22 Dec 2012 13:20:48 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/ximl/wiki/spring%20framework/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage spring framework modified by aappddeevv</title><link>https://sourceforge.net/p/ximl/wiki/spring%2520framework/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -1,7 +1,4 @@
 You can also use XIML and the spring framework. The most common scenario is to ensure that the spring application context (through the autowire bean factory) can create some of the objects in the XIML description. To do this, merely override the getTypeInvoker in the context configuration object and create an invoker that delegates some, but not all, of the doCreateInstance calls to the bean factory.

-The second scenario is to have objects name in the the XIML specification to be found in the context. I'm still working on this scenario.
+The second scenario is to have objects name in the the XIML specification to be found in the context. You can do this but its generally a bad idea. Why? You do not want all the object creations to go through a spring context, its too slow. Instead, I have written a smaller invoker filter that merely checks the package. If the package of the type is in the package of my application, the object is created or found in the application context. This works fine and is very spring-like.

-Code for the first scenario will be posted to the forum but here's the sketch of it:
-
-...insert code from SpringBaseXimlInvoker here...
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">aappddeevv</dc:creator><pubDate>Sat, 22 Dec 2012 13:20:48 -0000</pubDate><guid>https://sourceforge.netad72873e971eeeaa036ae21fbf08cfbc70be792d</guid></item><item><title>WikiPage spring framework modified by aappddeevv</title><link>https://sourceforge.net/p/ximl/wiki/spring%2520framework/</link><description>You can also use XIML and the spring framework. The most common scenario is to ensure that the spring application context (through the autowire bean factory) can create some of the objects in the XIML description. To do this, merely override the getTypeInvoker in the context configuration object and create an invoker that delegates some, but not all, of the doCreateInstance calls to the bean factory.

The second scenario is to have objects name in the the XIML specification to be found in the context. I'm still working on this scenario.

Code for the first scenario will be posted to the forum but here's the sketch of it:

...insert code from SpringBaseXimlInvoker here...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">aappddeevv</dc:creator><pubDate>Fri, 23 Nov 2012 17:11:30 -0000</pubDate><guid>https://sourceforge.netf85fc4b3f117a5ff62db8859c01f216731173703</guid></item></channel></rss>