a6124793fc
polishing
2009-05-05 09:36:53 +00:00
6930859e82
removed StandardScopes pseudo-enum (superseded by meta-annotated scopes)
2009-05-05 09:32:55 +00:00
15b33684a7
fixed JavaDoc
2009-04-29 21:12:45 +00:00
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
2009-04-26 11:41:06 +00:00
b5d21108da
@Configuration parsing fully relies on Spring's MetadataReader abstraction now
2009-04-24 11:16:46 +00:00
ea9d8925a2
next cut of JavaConfig metadata reading revision: using cached MetadataReaders
2009-04-22 10:46:24 +00:00
4d509cebdb
Temporarily ignoring GroovyScriptFactoryTests#testResourceScriptFromTag in order to allow more important fixes to roll out.
2009-04-21 18:14:08 +00:00
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.
2009-04-21 17:20:39 +00:00
7d10d05b27
(temporarily) increasing visibility of the ConfigurationClassAnnotation interface in an attempt to resolve the issue encountered at http://is.gd/tCud
2009-04-21 16:24:54 +00:00
14bd475519
revised support for annotated factory methods (merged @FactoryMethod functionality into JavaConfig facility)
2009-04-19 23:45:31 +00:00
9baf9cdc2f
reintroduced "removeApplicationListener" method as well
2009-04-12 20:59:52 +00:00
73dd6c28a3
reintroduced "removeAllListeners()" method since Spring DM uses it
2009-04-09 18:18:54 +00:00
859497b171
@Resource names may use ${...} placeholders (SPR-5656)
2009-04-09 09:14:06 +00:00
d08d73f274
Renamed ConfigurationPostProcessorTests -> ConfigurationClassPostProcessorTests
2009-04-06 21:29:30 +00:00
254bf7e403
Fixed SPR-5655 - dm Server issues with ConfigurationClassPostProcessor attempting to read .class files with ASM with incorrect class loader
2009-04-06 21:23:37 +00:00
4c5854d017
objects flowing around in expression evaluation are now TypedValue's - these carry generics info, used for conversions.
2009-04-03 23:39:14 +00:00
959cc95c3f
design change - no longer surfacing typeDescriptor through property accessor. conversion done internally in property write() code
2009-04-01 23:27:49 +00:00
00018e511d
implement new interface method
2009-04-01 21:58:24 +00:00
b85d45725d
@Value values may use ${...} placeholders (driven by PropertyPlaceholderConfigurer); @Autowired uses field/parameter name as fallback qualifier value (SPR-5152)
2009-03-31 20:27:42 +00:00
aa8bd6313b
added "unregisterManagedResource" method to MBeanExporter/MBeanExportOperations (SPR-5517)
2009-03-31 14:28:14 +00:00
1b13d8fadf
Added test using custom properties file with util:properties and dereferenced with @Value("#{...}")
2009-03-30 17:17:44 +00:00
cebc85067a
polishing @Configuration tests
2009-03-30 16:02:04 +00:00
cc713ad524
RESOLVED - issue SPR-5600: Make naming of @Configuration class processing-related artifacts consistent
2009-03-30 15:26:21 +00:00
68051ec72b
Updated BeanMethodTests to reflect change from IllegalArgumentException -> IllegalStateException
2009-03-28 22:29:28 +00:00
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)
2009-03-28 22:21:50 +00:00
82fd947712
polishing
2009-03-27 17:41:03 +00:00
aee7f1ce53
RESOLVED - issue SPR-5596: Test @Autowired @Configuration class constructors
2009-03-27 05:36:29 +00:00
1697932c57
consolidated context.annotation.support -> context.annotation
2009-03-27 04:57:13 +00:00
2c0c523d70
don't assert that CGLIB must be present unless there is at least one @Configuration class found
2009-03-27 03:10:41 +00:00
af058e599d
fixing tests in .test package that were failing due to missing CGLIB dependency
2009-03-27 02:10:41 +00:00
6698ed8420
IN PROGRESS - issue SPR-5599: Hook @Configuration class processing into <context:component-scan/> and <context:annotation-config/> through AnnotationConfigUtils#registerAnnotationConfigProcessors
2009-03-26 19:52:50 +00:00
77b2c4e199
SPR-5615 - Improved error message: s/is no interface/is not an interface
2009-03-26 13:56:14 +00:00
40b06b5f19
fixed broken "setManagedInterfaces" interface assertion (SPR-5615)
2009-03-26 13:49:21 +00:00
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.
2009-03-25 06:01:17 +00:00
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)
2009-03-25 03:14:35 +00:00
6ca253e3e6
RmiServiceExporter and RmiRegistryFactoryBean synchronize registry lookup/creation
2009-03-24 00:05:21 +00:00
dab23a71f9
polishing
2009-03-23 14:39:25 +00:00
df99929e21
added TaskScheduler interface and Trigger abstraction; added ConcurrentTaskScheduler and ThreadPoolTaskScheduler; added CommonJ TimerManagerTaskScheduler; added CronTrigger implementation for cron expression support
2009-03-23 14:38:55 +00:00
26f0671250
TimerTaskExecutor creates non-daemon Timer and uses bean name as default Timer name
2009-03-23 14:35:16 +00:00
d42e24a752
polishing
2009-03-23 14:15:47 +00:00
4344832a47
qualifier annotations and @Value can be used at method level as well (applying to all parameters);
...
fixed EL evaluation of prepared constructor arguments for repeated prototype creation
2009-03-23 14:13:41 +00:00
147709fa9e
Tweaks to package-info.java files
2009-03-23 07:36:44 +00:00
22b25e0d7b
Consolidated Util and MutableAnnotationUtils classes into existing AsmUtils
2009-03-23 07:01:01 +00:00
7f96f57375
polishing
2009-03-23 06:23:01 +00:00
1284bd585f
+ JavaDoc updates
...
+ added objectweb.asm back to .classpath to satisfy transitive need from groovy tests
+ package.html -> package-info.java
2009-03-23 05:28:58 +00:00
cd50e45645
+ Moving .config.java module -> .context
2009-03-23 04:48:04 +00:00
3ae3de19a9
+ Updated all projects to use the re-introduced org.springframework.asm instead of org.objectweb.asm (.java, template.mf, ivy.xml, and .classpath files have been updated)
...
+ Finished support for @Import, including detection of circular imports
2009-03-21 19:00:57 +00:00
13dfa11def
Add support for @ScopedProxy for factory beans using the @FactoryBean annotation within a @Component
...
Add missing unit tests
2009-03-13 18:14:40 +00:00
fc9c3009fe
Initial cut of feature to create factory beans using the @FactoryBean annotation within a @Component
2009-03-07 07:42:25 +00:00
faffd98621
Javadoc polish & pruning dead code
2009-03-07 05:49:12 +00:00
Juergen Hoeller