Announcement Announcement Module
No announcement yet.
Best practise on spring bugs Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Best practise on spring bugs

    There is a known bug in spring 2.5.5
    which directly affects our application as thrown errors during controller execution are passed back completely to the client.
    Our controllers heavily use annotations for both, the class annotation, the method mappings as well as the method parameters.

    We build and deploy roundabout 12 bundles using spring 2.5.5 for compilation. Moving back to spring 2.5.4 would not be a problem at this point but useless.

    Unlike in normal, legacy webapps where i would simply switch back to spring 2.5.4 to get rid of this bug, the usage of this release would mean that the core bundles of the s2ap would have to be replaced by an older release.

    What is the best practise way to face this problem in order to be able to deploy our application without using spring 2.5.5 ??

    Are there any known issues on using older spring releases for s2ap ??



  • #2
    Best practise on spring bugs


    The issue of 'pinning' to a particular version of Spring is a known and quite unfortunate side-effect of OSGi versioning. We are working on a solution to allow applications to use a version of Spring that is separate to the one the Platform itself runs on, but this won't make the 1.0 final release.

    Moving back to 2.5.4 *might* work, but 2.5.5 contains fixes that the Platform needs. We'll be releasing a build of the Platform that contains 2.5.6 as soon as 2.5.6 is available.