Mined Opinions For API: org.apache.ibatis

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • This is mapped to person table in mysql database.I am querying the database like: CODESNIPPET_JAVA3 .. details
  • But this is pretty bad approach and client would not like it.. details
  • I am not able to get any result from database.It does not select any row even though value exists.I have checked that none of other validation checks are failing.. details
  • Since I am more familiar with Jackson, here are some aspects where I think Jackson has more complete support than Gson (apologies if I miss a Gson feature): Extensive annotation support; including full inheritance, and advanced "mix-in" annotations (associate annotations with a class for cases where you can not directly add them) Streaming (incremental) reading, writing, for ultra-high performance (or memory-limited) use cases; can mix with data binding (bind sub-trees) -- EDIT latest versions of Gson also include streaming reader Tree model (DOM-like access); can convert between various models (tree <-> java object <-> stream) Can use any constructors (or static factory methods), not just default constructor Field and getter/setter access (earlier gson versions only used fields, this may have changed) Out-of-box JAX-RS support Interoperability: can also use JAXB annotations, has support/work-arounds for common packages (joda, ibatis, cglib), JVM languages (groovy, clojure, scala) Ability to force static (declared) type handling for output Support for deserializing polymorphic types (Jackson 1.5) -- can serialize AND deserialize things like List correctly (with additional type information) Integrated support for binary content (base64 to/from JSON Strings) .. details
  • Since I am more familiar with Jackson, here are some aspects where I think Jackson has more complete support than Gson (apologies if I miss a Gson feature): Extensive annotation support; including full inheritance, and advanced "mix-in" annotations (associate annotations with a class for cases where you can not directly add them) Streaming (incremental) reading, writing, for ultra-high performance (or memory-limited) use cases; can mix with data binding (bind sub-trees) -- EDIT latest versions of Gson also include streaming reader Tree model (DOM-like access); can convert between various models (tree <-> java object <-> stream) Can use any constructors (or static factory methods), not just default constructor Field and getter/setter access (earlier gson versions only used fields, this may have changed) Out-of-box JAX-RS support Interoperability: can also use JAXB annotations, has support/work-arounds for common packages (joda, ibatis, cglib), JVM languages (groovy, clojure, scala) Ability to force static (declared) type handling for output Support for deserializing polymorphic types (Jackson 1.5) -- can serialize AND deserialize things like List correctly (with additional type information) Integrated support for binary content (base64 to/from JSON Strings) .. details
Summaries the opinions about org.apache.ibatis using topic modeling.
  • 0. database person query table mysql approach: 2
    • This is mapped to person table in mysql database.I am querying the database like: CODESNIPPET .. details
    • But this is pretty bad approach and client would not like it.. details
  • 0. gson jackson stream include mix constructor model case trees getter: 2
    • I am not able to get any result from database.It does not select any row even though value exists.I have checked that none of other validation checks are failing.. details
    • Since I am more familiar with Jackson, here are some aspects where I think Jackson has more complete support than Gson (apologies if I miss a Gson feature): Extensive annotation support; including full inheritance, and advanced "mix-in" annotations (associate annotations with a class for cases where you can not directly add them) Streaming (incremental) reading, writing, for ultra-high performance (or memory-limited) use cases; can mix with data binding (bind sub-trees) -- EDIT latest versions of Gson also include streaming reader Tree model (DOM-like access); can convert between various models (tree <-> java object <-> stream) Can use any constructors (or static factory methods), not just default constructor Field and getter/setter access (earlier gson versions only used fields, this may have changed) Out-of-box JAX-RS support Interoperability: can also use JAXB annotations, has support/work-arounds for common packages (joda, ibatis, cglib), JVM languages (groovy, clojure, scala) Ability to force static (declared) type handling for output Support for deserializing polymorphic types (Jackson 1.5) -- can serialize AND deserialize things like List correctly (with additional type information) Integrated support for binary content (base64 to/from JSON Strings) .. details
Summaries of the opinions about org.apache.ibatis 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.
  • This is mapped to person table in mysql database I am querying the database like: CODESNIPPET JAVA3 .
  • But this is pretty bad approach and client would not like it .
  • This is mapped to person table in mysql database I am querying the database like: CODESNIPPET JAVA3 .
  • But this is pretty bad approach and client would not like it .
  • This is mapped to person table in mysql database I am querying the database like: CODESNIPPET JAVA3 .
  • But this is pretty bad approach and client would not like it .
  • Since I am more familiar with Jackson, here are some aspects where I think Jackson has more complete support than Gson (apologies if I miss a Gson feature): Extensive annotation support; including full inheritance, and advanced "mix in" annotations (associate annotations with a class for cases where you can not directly add them) Streaming (incremental) reading, writing, for ultra high performance (or memory limited) use cases; can mix with data binding (bind sub trees) EDIT latest versions of Gson also include streaming reader Tree model (DOM like access); can convert between various models (tree < > java object < > stream) Can use any constructors (or static factory methods), not just default constructor Field and getter setter access (earlier gson versions only used fields, this may have changed) Out of box JAX RS support Interoperability: can also use JAXB annotations, has support work arounds for common packages (joda, ibatis, cglib), JVM languages (groovy, clojure, scala) Ability to force static (declared) type handling for output Support for deserializing polymorphic types (Jackson 1 5) can serialize AND deserialize things like List correctly (with additional type information) Integrated support for binary content (base64 to from JSON Strings) .
  • I am not able to get any result from database It does not select any row even though value exists I have checked that none of other validation checks are failing .
  • Since I am more familiar with Jackson, here are some aspects where I think Jackson has more complete support than Gson (apologies if I miss a Gson feature): Extensive annotation support; including full inheritance, and advanced "mix in" annotations (associate annotations with a class for cases where you can not directly add them) Streaming (incremental) reading, writing, for ultra high performance (or memory limited) use cases; can mix with data binding (bind sub trees) EDIT latest versions of Gson also include streaming reader Tree model (DOM like access); can convert between various models (tree < > java object < > stream) Can use any constructors (or static factory methods), not just default constructor Field and getter setter access (earlier gson versions only used fields, this may have changed) Out of box JAX RS support Interoperability: can also use JAXB annotations, has support work arounds for common packages (joda, ibatis, cglib), JVM languages (groovy, clojure, scala) Ability to force static (declared) type handling for output Support for deserializing polymorphic types (Jackson 1 5) can serialize AND deserialize things like List correctly (with additional type information) Integrated support for binary content (base64 to from JSON Strings) .
  • I am not able to get any result from database It does not select any row even though value exists I have checked that none of other validation checks are failing .
  • Since I am more familiar with Jackson, here are some aspects where I think Jackson has more complete support than Gson (apologies if I miss a Gson feature): Extensive annotation support; including full inheritance, and advanced "mix in" annotations (associate annotations with a class for cases where you can not directly add them) Streaming (incremental) reading, writing, for ultra high performance (or memory limited) use cases; can mix with data binding (bind sub trees) EDIT latest versions of Gson also include streaming reader Tree model (DOM like access); can convert between various models (tree < > java object < > stream) Can use any constructors (or static factory methods), not just default constructor Field and getter setter access (earlier gson versions only used fields, this may have changed) Out of box JAX RS support Interoperability: can also use JAXB annotations, has support work arounds for common packages (joda, ibatis, cglib), JVM languages (groovy, clojure, scala) Ability to force static (declared) type handling for output Support for deserializing polymorphic types (Jackson 1 5) can serialize AND deserialize things like List correctly (with additional type information) Integrated support for binary content (base64 to from JSON Strings) .
  • I am not able to get any result from database It does not select any row even though value exists I have checked that none of other validation checks are failing .
Summaries of the opinions about org.apache.ibatis using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about org.apache.ibatis 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).
Performance:
  • N/A
  • Since I am more familiar with Jackson, here are some aspects where I think Jackson has more complete support than Gson (apologies if I miss a Gson feature): Extensive annotation support; including full inheritance, and advanced "mix-in" annotations (associate annotations with a class for cases where you can not directly add them) Streaming (incremental) reading, writing, for ultra-high performance (or memory-limited) use cases; can mix with data binding (bind sub-trees) -- EDIT latest versions of Gson also include streaming reader Tree model (DOM-like access); can convert between various models (tree <-> java object <-> stream) Can use any constructors (or static factory methods), not just default constructor Field and getter/setter access (earlier gson versions only used fields, this may have changed) Out-of-box JAX-RS support Interoperability: can also use JAXB annotations, has support/work-arounds for common packages (joda, ibatis, cglib), JVM languages (groovy, clojure, scala) Ability to force static (declared) type handling for output Support for deserializing polymorphic types (Jackson 1.5) -- can serialize AND deserialize things like List correctly (with additional type information) Integrated support for binary content (base64 to/from JSON Strings) .
Usability:
  • This is mapped to person table in mysql database.I am querying the database like: CODESNIPPET_JAVA3 .
  • I am not able to get any result from database.It does not select any row even though value exists.I have checked that none of other validation checks are failing.
  • Usability: 2
    1. general: 2
      • This is mapped to person table in mysql database.I am querying the database like: CODESNIPPET_JAVA3 .. details
      • But this is pretty bad approach and client would not like it.. details
  • Performance: 1
    1. general: 1
      • Since I am more familiar with Jackson, here are some aspects where I think Jackson has more complete support than Gson (apologies if I miss a Gson feature): Extensive annotation support; including full inheritance, and advanced "mix-in" annotations (associate annotations with a class for cases where you can not directly add them) Streaming (incremental) reading, writing, for ultra-high performance (or memory-limited) use cases; can mix with data binding (bind sub-trees) -- EDIT latest versions of Gson also include streaming reader Tree model (DOM-like access); can convert between various models (tree <-> java object <-> stream) Can use any constructors (or static factory methods), not just default constructor Field and getter/setter access (earlier gson versions only used fields, this may have changed) Out-of-box JAX-RS support Interoperability: can also use JAXB annotations, has support/work-arounds for common packages (joda, ibatis, cglib), JVM languages (groovy, clojure, scala) Ability to force static (declared) type handling for output Support for deserializing polymorphic types (Jackson 1.5) -- can serialize AND deserialize things like List correctly (with additional type information) Integrated support for binary content (base64 to/from JSON Strings) .. details
  • Usability: 2
    1. general: 2
      • I am not able to get any result from database.It does not select any row even though value exists.I have checked that none of other validation checks are failing.. details
      • Since I am more familiar with Jackson, here are some aspects where I think Jackson has more complete support than Gson (apologies if I miss a Gson feature): Extensive annotation support; including full inheritance, and advanced "mix-in" annotations (associate annotations with a class for cases where you can not directly add them) Streaming (incremental) reading, writing, for ultra-high performance (or memory-limited) use cases; can mix with data binding (bind sub-trees) -- EDIT latest versions of Gson also include streaming reader Tree model (DOM-like access); can convert between various models (tree <-> java object <-> stream) Can use any constructors (or static factory methods), not just default constructor Field and getter/setter access (earlier gson versions only used fields, this may have changed) Out-of-box JAX-RS support Interoperability: can also use JAXB annotations, has support/work-arounds for common packages (joda, ibatis, cglib), JVM languages (groovy, clojure, scala) Ability to force static (declared) type handling for output Support for deserializing polymorphic types (Jackson 1.5) -- can serialize AND deserialize things like List correctly (with additional type information) Integrated support for binary content (base64 to/from JSON Strings) .. details