On Jul 17, 2007, at 5:54 PM, David Jencks wrote:
OK, one more idea :-)
Jetspeed could have an expressive schema for its spring
configuration file(s) using xbean-spring. Activemq and servicemix
are the main users of this today. What you do is:
-- annotate your spring "beans" with javadoc style psuedo-annotations
-- run the maven xbean spring plugin to generate one or more
schemas for the configuration (plus some other configuration
metadata files, and documentation).
-- write the spring configuration in the language defined by the
schema
-- change one line in the spring startup stuff.
Here's a link...
http://geronimo.apache.org/xbean/custom-xml.html
I really like this, very cool
+1 for adopting it in .2.2
We use constructor dependency injection quite a bit, so I guess we
will need quite a few kind of mappings such as these:
# Mapping of constructor argument names
org.apache.xbean.spring.example.SaladService
(java.lang.String,java.lang.String,boolean).parameterNames=dressing
size crouton
This is pretty easy to do. I converted the apache directory spring
config file to xbean spring in a couple of days, including figuring
out how xbean spring works and extending it to deal with lots of
source modules.
this does pretty much depend on a working (i.e. maven 2) build :-)
(sorry, couldn't resist)
Yeah I know. We need your help. Lets get it right this time!
As far as the m2 build goes....
I'm not sure that it's a good idea to insist that current portal m1
and m2 customization procedures continue to work unmodified. I
would prefer to have as a goal that they are easier to understand
and use and are less coupled to the actual jetspeed build.
Agreed. With 2.2, my vote is to drop the m1 build, and rewrite the M2
build, and from there figure out a better way to do custom m2 builds
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
