1b5a433f22
added ScheduledTaskRegistrar etc
16 years ago
636d1db36d
avoid NPE for definitions without bean class specified
16 years ago
a6124793fc
polishing
16 years ago
6930859e82
removed StandardScopes pseudo-enum (superseded by meta-annotated scopes)
16 years ago
15b33684a7
fixed JavaDoc
16 years ago
cea8f7f69e
custom stereotype annotations can be meta-annotated with @Service , @Controller etc as well; @Scope and @Transactional are now supported as meta-annotations on custom annotations
16 years ago
b5d21108da
@Configuration parsing fully relies on Spring's MetadataReader abstraction now
16 years ago
ea9d8925a2
next cut of JavaConfig metadata reading revision: using cached MetadataReaders
16 years ago
4d509cebdb
Temporarily ignoring GroovyScriptFactoryTests#testResourceScriptFromTag in order to allow more important fixes to roll out.
16 years ago
7ba4c563a6
Fixing build breakage with GroovyScriptFactoryTests.
...
The problem was that the Messenger object was not being proxed (assertTrue(AopUtils.isAopProxy(messenger)) was returning false). The cause for this seemed to be that the
pointcut was malformed / out of date, reading execution(* org.springframework.scripting.Messenger.*(..)), when the groovy Messenger class is actually declared in the org.springframework.scripting.groovy package.
I tried updating the fully-qualified package name in the pointcut expression, and this caused AspectJ matching errors saying that there was not such type that matches that FQ name.
So as a final resort, I removed the full-qualification entirely and went with execution(* *..Messenger.*(..)). All tests pass now, but it raises the question, why was AJ having matching errors? Is it because
the pointcut matching is being done before the groovy class is loaded? There could be a potential bug here.
16 years ago
7d10d05b27
(temporarily) increasing visibility of the ConfigurationClassAnnotation interface in an attempt to resolve the issue encountered at http://is.gd/tCud
16 years ago
14bd475519
revised support for annotated factory methods (merged @FactoryMethod functionality into JavaConfig facility)
16 years ago
6495bdd8c8
Added AspectJ dependency
16 years ago
1facd45c5e
switched to use XInclude
16 years ago
9baf9cdc2f
reintroduced "removeApplicationListener" method as well
16 years ago
f6ecffdba7
+ osgi manifest updates
16 years ago
73dd6c28a3
reintroduced "removeAllListeners()" method since Spring DM uses it
16 years ago
362629d03b
Change version from 3.0.0.M3 to 3.0.0.BUILD-SNAPSHOT (again)
16 years ago
859497b171
@Resource names may use ${...} placeholders (SPR-5656)
16 years ago
d08d73f274
Renamed ConfigurationPostProcessorTests -> ConfigurationClassPostProcessorTests
16 years ago
254bf7e403
Fixed SPR-5655 - dm Server issues with ConfigurationClassPostProcessor attempting to read .class files with ASM with incorrect class loader
16 years ago
e500348ca7
Fixed mystyped dependency on org.antlr 3.0.1 in context's Eclipse .classpath
16 years ago
4c5854d017
objects flowing around in expression evaluation are now TypedValue's - these carry generics info, used for conversions.
16 years ago
8f76197485
Change version from 3.0.0.M3 to 3.0.0.BUILD-SNAPSHOT
16 years ago
959cc95c3f
design change - no longer surfacing typeDescriptor through property accessor. conversion done internally in property write() code
16 years ago
00018e511d
implement new interface method
16 years ago
b85d45725d
@Value values may use ${...} placeholders (driven by PropertyPlaceholderConfigurer); @Autowired uses field/parameter name as fallback qualifier value (SPR-5152)
16 years ago
aa8bd6313b
added "unregisterManagedResource" method to MBeanExporter/MBeanExportOperations (SPR-5517)
16 years ago
1b13d8fadf
Added test using custom properties file with util:properties and dereferenced with @Value("#{...}")
16 years ago
cebc85067a
polishing @Configuration tests
16 years ago
cc713ad524
RESOLVED - issue SPR-5600: Make naming of @Configuration class processing-related artifacts consistent
16 years ago
4c7c30985f
Change antlr version to be 3.0.1 so that is consistent across the project
16 years ago
351fba1a04
POM maintenance
...
Place parent pom in publicly accessible directory (org.sf.spring-parent).
Create a component list pom in org.sf.spring-library.
16 years ago
68051ec72b
Updated BeanMethodTests to reflect change from IllegalArgumentException -> IllegalStateException
16 years ago
69a762e86a
resolved:
...
+ Provide @Primary annotation (SPR-5590)
+ Provide @Lazy annotation (SPR-5591)
+ Test @Bean initMethod/destroyMethod functionality (SPR-5592)
+ Test @Bean dependsOn functionality (SPR-5593)
16 years ago
5f21cbd9da
POM maintenance
16 years ago
82fd947712
polishing
16 years ago
225eb6bcd9
refined version ranges in OSGi manifests
16 years ago
c488f3768c
updating eclipse classpath settings
16 years ago
aee7f1ce53
RESOLVED - issue SPR-5596: Test @Autowired @Configuration class constructors
16 years ago
1697932c57
consolidated context.annotation.support -> context.annotation
16 years ago
2c0c523d70
don't assert that CGLIB must be present unless there is at least one @Configuration class found
16 years ago
af058e599d
fixing tests in .test package that were failing due to missing CGLIB dependency
16 years ago
ef41a12fea
updated to JRuby 1.2 (remaining compatible with JRuby 1.1 and above)
16 years ago
6698ed8420
IN PROGRESS - issue SPR-5599: Hook @Configuration class processing into <context:component-scan/> and <context:annotation-config/> through AnnotationConfigUtils#registerAnnotationConfigProcessors
16 years ago
77b2c4e199
SPR-5615 - Improved error message: s/is no interface/is not an interface
16 years ago
40b06b5f19
fixed broken "setManagedInterfaces" interface assertion (SPR-5615)
16 years ago
0152d8d21d
SPR-5385, SPR-5301 - initial pass completed of POMs for maven central repository upload. N.B. Can not build spring with these POMs.
...
Cleanup remains to meet maven central metadata requirements
16 years ago
e5f4b4937c
Re-adding ConfigurationPostProcessorTests after its brief removal in r814. @Ignore-ing the testCglibClassesAreLoadedJustInTimeForEnhancement() method as it turns out this was one of the culprits in the recent build breakage. The classloader hacking causes subtle downstream effects, breaking unrelated tests. The test method is still useful, but should only be run on a manual basis to ensure CGLIB is not prematurely classloaded, and should not be run as part of the automated build.
16 years ago
2db0f122c1
fixed two build-breaking issues:
...
+ reverted ClassMetadataReadingVisitor to revision 794
+ eliminated ConfigurationPostProcessorTests until further investigation determines why it causes downstream tests to fail (such as the seemingly unrelated ClassPathXmlApplicationContextTests)
16 years ago
Juergen Hoeller
Thomas Risberg
Chris Beams
Arjen Poutsma
Costin Leau
Mark Pollack
Andy Clement
Scott Andrews