Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 31

Thread: HTTP 403 on Schemas?

  1. #11

    Default

    Hi everyone,
    We are also facing the same problem with the bean schema. Can anybody provide an alternative solution to these schema URLs? Any guidance will be appreciable. Thanks.

  2. #12
    Join Date
    May 2012
    Posts
    4

    Default

    Here too. Panic setting in.

    This is a problem in development and in production. Dont restart your apps, they wont start ! Call ops fast, stop all automated restarts and new deployments until this is fixed !

    Anyone from Spring care to comment - an ETA on this would be good, or instructions on how to resolve ?

  3. #13
    Join Date
    May 2012
    Posts
    3

    Default

    We have found that the problem in our application was that we specified the spring util schema location as www.springsource.org and changing it to www.springframework.org works.

    It appears that in the Spring 3 spring.schemas files, only www.springframework.org has a mapping. Our app was written using Spring 2 originally, and recently has been upgraded to Spring 3, however we probably should have updated our xsd locations in our config files too.

    So far, it appears that this might be our fix, but we haven't tested it well yet.

    I haven't got the code in front of me, so can't post our exact changes.

    Pete

  4. #14
    Join Date
    May 2007
    Posts
    10

    Default

    This is a serious problem - when is it going to be fixed?

    We are talking about production systems here!!!
    George

  5. #15
    Join Date
    Jun 2005
    Posts
    4

    Default Production systems will not start

    Quote Originally Posted by georgea View Post
    This is a serious problem - when is it going to be fixed?

    We are talking about production systems here!!!
    Ditto. This is a MAJOR issue. Any fixes anyone? HELP!

  6. #16
    Join Date
    May 2007
    Posts
    10

    Default

    The only fix (just tried it and works) I can recommend is to place all the needed spring schemas in the same folder as your applicationContext and in your applicationContext.xml specify the location of the XSDs using the classpath protocol:

    <beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="http://www.springframework.org/schema/p"
    xmlns:context="http://www.springframework.org/schema/context"
    xmlns="http://www.springframework.org/schema/beans"
    xsi:schemaLocation="
    http://www.springframework.org/schema/context
    classpath:spring-context-3.0.xsd
    http://www.springframework.org/schema/beans
    classpath:spring-beans-3.0.xsd">
    George

  7. #17
    Join Date
    Jun 2009
    Posts
    2

    Default

    Quote Originally Posted by georgea View Post
    The only fix (just tried it and works) I can recommend is to place all the needed spring schemas in the same folder as your applicationContext and in your applicationContext.xml specify the location of the XSDs using the classpath protocol:
    I did the same fix this morning on all our production webservers, as it's easiest to make.

  8. #18

    Smile Finally a solution for HTTP 403 error

    Hi all,
    This is the solution we've found so far.
    What we did was to add a file in "WebContent/META-INF/spring.schemas" with the content :
    Code:
    http\://www.springframework.org/schema/beans/spring-beans-3.0.xsd=org/springframework/beans/factory/xml/spring-beans-3.0.xsd
    http\://www.springframework.org/schema/tool/spring-tool-3.0.xsd=org/springframework/beans/factory/xml/spring-tool-3.0.xsd
    http\://www.springframework.org/schema/util/spring-util-3.0.xsd=org/springframework/beans/factory/xml/spring-util-3.0.xsd
    http\://www.springframework.org/schema/aop/spring-aop-3.0.xsd=org/springframework/aop/config/spring-aop-3.0.xsd
    http\://www.springframework.org/schema/jdbc/spring-jdbc-3.0.xsd=org/springframework/jdbc/config/spring-jdbc-3.0.xsd
    http\://www.springframework.org/schema/context/spring-context-3.0.xsd=org/springframework/context/config/spring-context-3.0.xsd
    http\://www.springframework.org/schema/jee/spring-jee-3.0.xsd=org/springframework/ejb/config/spring-jee-3.0.xsd
    http\://www.springframework.org/schema/lang/spring-lang-3.0.xsd=org/springframework/scripting/config/spring-lang-3.0.xsd
    http\://www.springframework.org/schema/task/spring-task-3.0.xsd=org/springframework/scheduling/config/spring-task-3.0.xsd
    http\://www.springframework.org/schema/tx/spring-tx-3.0.xsd=org/springframework/transaction/config/spring-tx-3.0.xsd
    What we basically did was to tell Spring to look for the required files in the project's libraries itself. For example, for the beans entry which all of us were having errors :
    "http\://www.springframework.org/schema/beans/spring-beans-3.0.xsd",
    We found the particular in the Project's libraries folder with this location "org/springframework/beans/factory/xml/spring-tool-3.0.xsd".

    For your project, the address might be different, you can find the particular xsd file in Maven dependencies section. Also, you might not need all the mappings that I've put above. You can map whatever you want in the schemas file.

    Hope this helps!

  9. #19
    Join Date
    Jun 2005
    Posts
    4

    Default Fix

    Quote Originally Posted by trulija View Post
    I did the same fix this morning on all our production webservers, as it's easiest to make.
    I have fixed our production servers now, I believe in the correct way, which is to place a spring.schemas in META-INF to map the URLs to the classpath files manually.

    https://gist.github.com/2761901

  10. #20
    Join Date
    Jun 2005
    Posts
    4

    Default

    Great minds think alike

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •