Mined Opinions For API: spring-framework-issues

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • It's fixed in Spring 3.1 - use @RequestMapping(method RequestMethod.GET, value "foo/bar", produces "application/json"), see [SPR-7353]( URL_https://jira.springsource.org/browse/SPR-7353) .. details
  • Ok, I've opened a Spring Source JIRA request for this one, perhaps it is a much needed improvement: URL_https://jira.springsource.org/browse/SPR-10552 [ URL_https://jira.springsource.org/browse/SPR-10552 ] Or else, it is a case of leveraging the Jackson conversion capabilities in clever ways which sounds like a lot of plumbing.. details
  • You'll need to change your pom.xml if you're migrating from 1.x (Step 1: Update Maven / JAR dependencies from URL_http://www.cowtowncoder.com/blog/archives/2012/04/entry_469.html is all you need for the builtin support to latch on).. details
  • Support for Jackson 2 has been added in Spring 3.2, and has also backported to Spring 3.1.2 ( URL_https://jira.springsource.org/browse/SPR-9507 [SPR-9507] ) .. details
  • See URL_http://blog.springsource.org/2011/02/21/spring-3-1-m1-mvc-namespace- enhancements-and-configuration/ [Spring-3.1-MVC-Namespace-Improvements] See URL_https://jira.springsource.org/browse/SPR-7504?focusedCommentId=62730&p age=com.atlassian.jira.plugin.system.issuetabpanels%3acomment-tabpanel [SPR-7504] Make it easier to add new Message Converters to AnnotationMethodHandlerAdapter Exemple: CODESNIPPET_JAVA1 .. details
  • Here is the link, please vote up : URL_https://jira.springsource.org/browse/SPR-7344 .. details
  • Thanks.. details
  • Seems like nobody wants it.. details
  • URL_https://jira.springsource.org/browse/SPR-7543 Automatically expose @PathVariables in the Model causes all methods that have {@PathVariable} parameters to include the {@PathVariable}'s in the model, so the model always contains more than 1 item, so {extractValueFromSingleKeyModel} doesn't work.. details
  • This is adapted from a bug report for Jackson here: URL_https://jira.springsource.org/browse/SPR-10552 [ URL_https://jira.springsource.org/browse/SPR-10552 ] CODESNIPPET_JAVA1 .. details
  • I think URL_https://jira.springsource.org/browse/SPR-7517 [this] Spring bug/feature request is similar, but I'm not sure how to fit all the pieces together.. details
Summaries the opinions about spring-framework-issues using topic modeling.
  • 0. spr jira jackson add plugin namespace system age enhancements 3acomment: 8
    • It's fixed in Spring 3.1 - use @RequestMapping(method RequestMethod.GET, value "foo/bar", produces "application/json"), see [SPR-7353]( .. details
    • Ok, I've opened a Spring Source JIRA request for this one, perhaps it is a much needed improvement: Or else, it is a case of leveraging the Jackson conversion capabilities in clever ways which sounds like a lot of plumbing.. details
    • You'll need to change your pom.xml if you're migrating from 1.x (Step 1: Update Maven / JAR dependencies from is all you need for the builtin support to latch on).. details
    • Support for Jackson 2 has been added in Spring 3.2, and has also backported to Spring 3.1.2 ( SPR-9507 ) .. details
    • See enhancements-and-configuration/ [Spring-3.1-MVC-Namespace-Improvements] See age=com.atlassian.jira.plugin.system.issuetabpanels%3acomment-tabpanel [SPR-7504] Make it easier to add new Message Converters to AnnotationMethodHandlerAdapter Exemple: CODESNIPPET .. details
    • Here is the link, please vote up : .. details
    • Thanks.. details
    • Seems like nobody wants it.. details
  • 0. model pathvariable automatically request piece adapt jackson report pathvariables item: 3
    • Automatically expose @PathVariables in the Model causes all methods that have {@PathVariable} parameters to include the {@PathVariable}'s in the model, so the model always contains more than 1 item, so {extractValueFromSingleKeyModel} doesn't work.. details
    • This is adapted from a bug report for Jackson here: CODESNIPPET .. details
    • I think this Spring bug/feature request is similar, but I'm not sure how to fit all the pieces together.. details
Summaries of the opinions about spring-framework-issues using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
  • Here is the link, please vote up : .
  • Support for Jackson 2 has been added in Spring 3 2, and has also backported to Spring 3 1 2 ( SPR 9507 ) .
  • You'll need to change your pom xml if you're migrating from 1 x (Step 1: Update Maven JAR dependencies from is all you need for the builtin support to latch on) .
  • Ok, I've opened a Spring Source JIRA request for this one, perhaps it is a much needed improvement: Or else, it is a case of leveraging the Jackson conversion capabilities in clever ways which sounds like a lot of plumbing .
  • Thanks .
  • Seems like nobody wants it .
  • It's fixed in Spring 3 1 use @RequestMapping(method RequestMethod GET, value "foo bar", produces "application json"), see SPR 7353]( .
  • See enhancements and configuration Spring 3 1 MVC Namespace Improvements See age=com atlassian jira plugin system issuetabpanels%3acomment tabpanel SPR 7504 Make it easier to add new Message Converters to AnnotationMethodHandlerAdapter Exemple: CODESNIPPET JAVA1 .
  • Here is the link, please vote up : .
  • Support for Jackson 2 has been added in Spring 3 2, and has also backported to Spring 3 1 2 ( SPR 9507 ) .
  • You'll need to change your pom xml if you're migrating from 1 x (Step 1: Update Maven JAR dependencies from is all you need for the builtin support to latch on) .
  • Ok, I've opened a Spring Source JIRA request for this one, perhaps it is a much needed improvement: Or else, it is a case of leveraging the Jackson conversion capabilities in clever ways which sounds like a lot of plumbing .
  • Thanks .
  • Seems like nobody wants it .
  • It's fixed in Spring 3 1 use @RequestMapping(method RequestMethod GET, value "foo bar", produces "application json"), see SPR 7353]( .
  • See enhancements and configuration Spring 3 1 MVC Namespace Improvements See age=com atlassian jira plugin system issuetabpanels%3acomment tabpanel SPR 7504 Make it easier to add new Message Converters to AnnotationMethodHandlerAdapter Exemple: CODESNIPPET JAVA1 .
  • Here is the link, please vote up : .
  • Support for Jackson 2 has been added in Spring 3 2, and has also backported to Spring 3 1 2 ( SPR 9507 ) .
  • You'll need to change your pom xml if you're migrating from 1 x (Step 1: Update Maven JAR dependencies from is all you need for the builtin support to latch on) .
  • Ok, I've opened a Spring Source JIRA request for this one, perhaps it is a much needed improvement: Or else, it is a case of leveraging the Jackson conversion capabilities in clever ways which sounds like a lot of plumbing .
  • Thanks .
  • Seems like nobody wants it .
  • It's fixed in Spring 3 1 use @RequestMapping(method RequestMethod GET, value "foo bar", produces "application json"), see SPR 7353]( .
  • See enhancements and configuration Spring 3 1 MVC Namespace Improvements See age=com atlassian jira plugin system issuetabpanels%3acomment tabpanel SPR 7504 Make it easier to add new Message Converters to AnnotationMethodHandlerAdapter Exemple: CODESNIPPET JAVA1 .
  • I think this Spring bug feature request is similar, but I'm not sure how to fit all the pieces together .
  • This is adapted from a bug report for Jackson here: CODESNIPPET JAVA1 .
  • Automatically expose @PathVariables in the Model causes all methods that have {@PathVariable} parameters to include the {@PathVariable}'s in the model, so the model always contains more than 1 item, so {extractValueFromSingleKeyModel} doesn't work .
  • I think this Spring bug feature request is similar, but I'm not sure how to fit all the pieces together .
  • This is adapted from a bug report for Jackson here: CODESNIPPET JAVA1 .
  • Automatically expose @PathVariables in the Model causes all methods that have {@PathVariable} parameters to include the {@PathVariable}'s in the model, so the model always contains more than 1 item, so {extractValueFromSingleKeyModel} doesn't work .
  • I think this Spring bug feature request is similar, but I'm not sure how to fit all the pieces together .
  • This is adapted from a bug report for Jackson here: CODESNIPPET JAVA1 .
  • Automatically expose @PathVariables in the Model causes all methods that have {@PathVariable} parameters to include the {@PathVariable}'s in the model, so the model always contains more than 1 item, so {extractValueFromSingleKeyModel} doesn't work .
Summaries of the opinions about spring-framework-issues using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about spring-framework-issues using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Onlysentiment:
  • Thanks.
  • N/A
Usability:
  • It's fixed in Spring 3.1 - use @RequestMapping(method RequestMethod.GET, value "foo/bar", produces "application/json"), see [SPR-7353]( URL_https://jira.springsource.org/browse/SPR-7353) .
  • URL_https://jira.springsource.org/browse/SPR-7543 Automatically expose @PathVariables in the Model causes all methods that have {@PathVariable} parameters to include the {@PathVariable}'s in the model, so the model always contains more than 1 item, so {extractValueFromSingleKeyModel} doesn't work.
Features:
  • Here is the link, please vote up : URL_https://jira.springsource.org/browse/SPR-7344 .
  • N/A
Bug:
  • N/A
  • This is adapted from a bug report for Jackson here: URL_https://jira.springsource.org/browse/SPR-10552 [ URL_https://jira.springsource.org/browse/SPR-10552 ] CODESNIPPET_JAVA1 .
  • Onlysentiment: 1
    1. general: 1
  • Features: 1
    1. general: 1
      • Here is the link, please vote up : URL_https://jira.springsource.org/browse/SPR-7344 .. details
  • Usability: 6
    1. general: 6
      • It's fixed in Spring 3.1 - use @RequestMapping(method RequestMethod.GET, value "foo/bar", produces "application/json"), see [SPR-7353]( URL_https://jira.springsource.org/browse/SPR-7353) .. details
      • Ok, I've opened a Spring Source JIRA request for this one, perhaps it is a much needed improvement: URL_https://jira.springsource.org/browse/SPR-10552 [ URL_https://jira.springsource.org/browse/SPR-10552 ] Or else, it is a case of leveraging the Jackson conversion capabilities in clever ways which sounds like a lot of plumbing.. details
      • You'll need to change your pom.xml if you're migrating from 1.x (Step 1: Update Maven / JAR dependencies from URL_http://www.cowtowncoder.com/blog/archives/2012/04/entry_469.html is all you need for the builtin support to latch on).. details
      • Support for Jackson 2 has been added in Spring 3.2, and has also backported to Spring 3.1.2 ( URL_https://jira.springsource.org/browse/SPR-9507 [SPR-9507] ) .. details
      • See URL_http://blog.springsource.org/2011/02/21/spring-3-1-m1-mvc-namespace- enhancements-and-configuration/ [Spring-3.1-MVC-Namespace-Improvements] See URL_https://jira.springsource.org/browse/SPR-7504?focusedCommentId=62730&p age=com.atlassian.jira.plugin.system.issuetabpanels%3acomment-tabpanel [SPR-7504] Make it easier to add new Message Converters to AnnotationMethodHandlerAdapter Exemple: CODESNIPPET_JAVA1 .. details
      • Seems like nobody wants it.. details
  • Bug: 2
    1. general: 2
      • This is adapted from a bug report for Jackson here: URL_https://jira.springsource.org/browse/SPR-10552 [ URL_https://jira.springsource.org/browse/SPR-10552 ] CODESNIPPET_JAVA1 .. details
      • I think URL_https://jira.springsource.org/browse/SPR-7517 [this] Spring bug/feature request is similar, but I'm not sure how to fit all the pieces together.. details
  • Usability: 1
    1. general: 1
      • URL_https://jira.springsource.org/browse/SPR-7543 Automatically expose @PathVariables in the Model causes all methods that have {@PathVariable} parameters to include the {@PathVariable}'s in the model, so the model always contains more than 1 item, so {extractValueFromSingleKeyModel} doesn't work.. details