Forbidden: http://www.springframework.org/schema/aop/spring-aop-3.1.xsd

[wensington]

When I try to access http://www.springframework.org/schem...ng-aop-3.1.xsd, it says forbidden. Please help. I couldn't find another copy anywhere. Thanks!

[cmontemu]

Just tried with 3.0 and 2.5 version and reached the same problem. Indeed it's happening not only for AOP, but also for other schemas (beans, context, etc.).

Here is one copy of spring-aop-3.1.xsd (you may also find there any other schema/version):
http://grepcode.com/file/repository....ng-aop-3.1.xsd

Hope it helps you.
Carlos.

[robsonke]

Same issue here. It's occuring since 20 hours or so.

[ingvar]

Same here as well... causing all kinds of problems, but I guess it's as bad time as any to stop depending on these remote files.

[rramchander]

Is there any way to get SpringSource to open up access to these XSDs? At least temporarily until we can fix our Spring definitions?

[spaceriker]

Is there any way to get SpringSource to open up access to these XSDs? At least temporarily until we can fix our Spring definitions?

I just figured that static.springframework.com is working. So for eg. http://www.springframework.org/schema/beans has changed to http://static.springframework.org/schema/beans - and so on. Try it, at the very least you can get the xsds downloaded.

[Andrei Stefan]

http://forum.springsource.org/showth...403-on-Schemas

[robsonke]

For what it's worth, they fixed it:
https://jira.springsource.org/browse/SPR-9427

[paikerabbas]

When I try to access http://www.springframework.org/schem...ng-aop-3.1.xsd, it says forbidden. Please help. I couldn't find another copy anywhere. Thanks!

Yesterday we also strugglet and production was also affected because of the below xsd was not available.
http://www.springframework.org/schem...-beans-3.0.xsd

When we were trying to open this in ie/firefox we were getting the forbidden but once the problem is resolved this was available or vice versa.

Is this the intermittent issue of springsource ??

[ingvar]

I recommend reading the latest comment from Chris Beam here.
https://jira.springsource.org/browse...#comment-79125

The problem in our case was that we were refering to spring-tx-3.1.xsd in our application context file but had an older version of spring-tx in the webapp. It was just a missing dependency for spring-tx in our Maven pom file. After fixing the pom.xml we got the correct jar and the webapp got the xsd file from classpath instead of trying to download it from springframework.org.