As I'm working with a variety of frameworks together with ColdSpring
and using the parent bean factory a lot (to share an application-scope
ColdSpring factory with a bunch of Model-Glue applications), I keep
bumping up against two things I can't do:

1. Bean aliases

Model-Glue defines the ORM factory object as "ormService" inside it's
Configuration.xml (ColdSpring) file but I need to use the same
phsyical instance of the ORM across all my Model-Glue instances as
well as my application-scope instance. What I really want to be able
to do is say:

<bean id="ormService" bean="transferFactory" />

and just have ColdSpring recognize "ormService" as an alias for
"transferFactory". The only workaround I've come up for this would be
to define "ormService" as a proxy factory bean with a target of
"transferFactory" but not actually apply any advice. Each Model-Glue
application would then have (effectively) a delegate object for the
parent bean factory's actual ORM bean.

2. Include

I'm finding that I have some standard bean definitions that I want in
all my Model-Glue applications and so I'm copying and pasting the same
XML into multiple locations. Note that in this case I *do* want
distinct bean instances in each factory (unlike aliases above). I just
want a way to avoid the duplication of the XML. Model-Glue let's you
<include> XML files and both Reactor and Transfer are considering this
enhancement.

Thoughts?
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood

Reply via email to