Hmm... OK, not Spring. I feel a little bad for jumping to that conclusion. Indeed, the OSGi Spring initiator is looking for XML documents in META-INF/spring rather than META-INF itself.
Thanks for pushing me straight, guys. On Thursday, March 16, 2017 at 11:32:34 AM UTC-5, Matt Sicker wrote: > > Spring took the name "bean" from JavaBeans which as been part of standard > Java for most of its existence. > > On 16 March 2017 at 11:29, [email protected] <javascript:> < > [email protected] <javascript:>> wrote: > >> I'm not sure that we're quite communicating-- that beans.xml file is >> _not_ Spring. It has nothing to do with Spring. It's a CDI-specific >> artifact that just happens to have the same name as a Spring artifact. If I >> understand your situation correctly (and people with more experience at CDI >> than me are invited to correct me) you aren't using Spring at all and it's >> just not an issue. >> >> You can use a Spring XML context named foo.xml or whigglesnort.xml or >> whatever. What matters is the contents. But the beans.xml for CDI _must_ be >> named that (and must be in the right place) and the contents only come into >> play if you are using alternative impl beans or other CDI features. I.e. a >> requisite for an artifact to be recognized as CDI is that name "beans.xml". >> That's not optional. The existence of a file with that name in the right >> place is what cues the CDI framework to work on the contents of that >> artifact. >> >> So, no Spring to worry about. >> >> --- >> A. Soroka >> The University of Virginia Library >> >> >> -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
