This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

First, strongly consider using Spring 3.0 and its AnnotationConfigApplicationContext. It replaces the JavaConfig project and its JavaConfigApplicationContext.

Second, this will probably be a hard limitation of the way that things work right now. ASM is assuming that the class is loadable as a classpath resource. If you're fetching it via a URL, that violates the assumption.

Add an issue for this in JIRA if you like. It's conceivable that we could accommodate this, because at the end of the day ASM really just needs an input stream.