+1 I'd do this as own module. It's really usable for some use cases but others do not need it at all.
I'd also go for more regular expressions in the configuration. That's something I did in my small interdyn extension where I'm able to configure all .*ServiceImpl classes as intercepted with some annotation. LieGrue, strub ----- Original Message ----- > From: Marius Bogoevici <[email protected]> > To: [email protected] > Cc: Jason Porter <[email protected]> > Sent: Friday, July 6, 2012 9:55 PM > Subject: Re: v0.4-incubating adding Seam Config (xml config) > > +1 > > On 12-07-06 3:50 PM, Jason Porter wrote: >> It's been a 10 on our list for awhile but we haven't done it yet. > Thoughts >> on adding it to v0.4? It would be a straight port from what we have in Seam >> 3 with package name changes. It's currently the only implementation in >> existence (that we know of) of the older xml config that was to be part of >> spec but was later pulled. >> >
