- iOS/Objective-C 元类和类别
- objective-c - -1001 错误,当 NSURLSession 通过 httpproxy 和/etc/hosts
- java - 使用网络类获取 url 地址
- ios - 推送通知中不播放声音
我已经看到了一些关于这个主题的问题,但我无法将其应用到我的案例中,因为我尝试应用它们,但错误仍然存在。所以我来揭露我的情况。
我读了一些关于它的评论,并说如果我在 Entidade 类中更改我的列 idEntidade 的名称,我就可以成功。但是我不能改变数据库。
我试图将 scope= Distritos.class
放入我的 @JsonIdentityInfo(generator = ObjectIdGenerators.PropertyGenerator.class, property = "idDistrito")
但它不起作用.
我需要帮助。
我正在尝试使用带有 Angular 的 spring MVC 将数据保存在我的数据库中。当我点击保存数据时,我得到了这个错误
2017-09-29 13:28:02.126 WARN 2716 --- [nio-8080-exec-2] .w.s.m.s.DefaultHandlerExceptionResolver : Failed to read HTTP message: org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Already had POJO for id (java.lang.Long) [[ObjectId: key=1, type=com.fasterxml.jackson.databind.deser.impl.PropertyBasedObjectIdGenerator, scope=java.lang.Object]]; nested exception is com.fasterxml.jackson.databind.JsonMappingException: Already had POJO for id (java.lang.Long) [[ObjectId: key=1, type=com.fasterxml.jackson.databind.deser.impl.PropertyBasedObjectIdGenerator, scope=java.lang.Object]] (through reference chain: digifred.global.model.Distritos["idEntidade"]->digifred.global.model.Entidades["idEntidade"])
2017-09-29 13:28:02.126 WARN 2716 --- [nio-8080-exec-2] .w.s.m.s.DefaultHandlerExceptionResolver : Resolved exception caused by Handler execution: org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Already had POJO for id (java.lang.Long) [[ObjectId: key=1, type=com.fasterxml.jackson.databind.deser.impl.PropertyBasedObjectIdGenerator, scope=java.lang.Object]]; nested exception is com.fasterxml.jackson.databind.JsonMappingException: Already had POJO for id (java.lang.Long) [[ObjectId: key=1, type=com.fasterxml.jackson.databind.deser.impl.PropertyBasedObjectIdGenerator, scope=java.lang.Object]] (through reference chain: digifred.global.model.Distritos["idEntidade"]->digifred.global.model.Entidades["idEntidade"])
2017-09-29 13:46:14.096 INFO 2716 --- [ Thread-46] ationConfigEmbeddedWebApplicationContext : Closing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@53b2ae5: startup date [Fri Sep 29 13:23:36 BRT 2017]; root of context hierarchy
我有这些课
@Entity
@Table(name = "distritos", schema="glb")
@XmlRootElement
@NamedQueries({
@NamedQuery(name = "Distritos.findAll", query = "SELECT d FROM Distritos d"),
@NamedQuery(name = "Distritos.findByIdDistrito", query = "SELECT d FROM Distritos d WHERE d.idDistrito = :idDistrito"),
@NamedQuery(name = "Distritos.findByNome", query = "SELECT d FROM Distritos d WHERE d.nome = :nome"),
@NamedQuery(name = "Distritos.findByCodigoDne", query = "SELECT d FROM Distritos d WHERE d.codigoDne = :codigoDne"),
@NamedQuery(name = "Distritos.findByFlagAtivo", query = "SELECT d FROM Distritos d WHERE d.flagAtivo = :flagAtivo")})
@JsonIdentityInfo(generator = ObjectIdGenerators.PropertyGenerator.class, property = "idDistrito")
public class Distritos implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
@Basic(optional = false)
@Column(name = "id_distrito")
private Long idDistrito;
@Basic(optional = false)
@NotNull
@Size(min = 1, max = 70)
@Column(name = "nome")
private String nome;
@Size(max = 8)
@Column(name = "codigo_dne")
private String codigoDne;
@Column(name = "flag_ativo")
private Integer flagAtivo;
@JoinColumn()
@ManyToOne
private Entidades idEntidade;
@JoinColumn()
@ManyToOne(optional = false)
private Municipios idMunicipio;
@JoinColumn()
@ManyToOne(optional = false)
private Ufs idUf;
gets and sets ..
}
类(Class)斗争
@Entity
@Table(name = "entidades", schema="glb")
@XmlRootElement
@NamedQueries({
@NamedQuery(name = "Entidades.findAll", query = "SELECT e FROM Entidades e"),
@NamedQuery(name = "Entidades.findByIdEntidade", query = "SELECT e FROM Entidades e WHERE e.idEntidade = :idEntidade"),
@NamedQuery(name = "Entidades.findByBairro", query = "SELECT e FROM Entidades e WHERE e.bairro = :bairro"),
@NamedQuery(name = "Entidades.findByBrasao", query = "SELECT e FROM Entidades e WHERE e.brasao = :brasao"),
@NamedQuery(name = "Entidades.findByCnpj", query = "SELECT e FROM Entidades e WHERE e.cnpj = :cnpj"),
@NamedQuery(name = "Entidades.findByComplemento", query = "SELECT e FROM Entidades e WHERE e.complemento = :complemento"),
@NamedQuery(name = "Entidades.findByEmail", query = "SELECT e FROM Entidades e WHERE e.email = :email"),
@NamedQuery(name = "Entidades.findByLogradouro", query = "SELECT e FROM Entidades e WHERE e.logradouro = :logradouro"),
@NamedQuery(name = "Entidades.findByNome", query = "SELECT e FROM Entidades e WHERE e.nome = :nome"),
@NamedQuery(name = "Entidades.findByNumero", query = "SELECT e FROM Entidades e WHERE e.numero = :numero"),
@NamedQuery(name = "Entidades.findBySigla", query = "SELECT e FROM Entidades e WHERE e.sigla = :sigla"),
@NamedQuery(name = "Entidades.findByTelefone", query = "SELECT e FROM Entidades e WHERE e.telefone = :telefone")})
@JsonIdentityInfo(generator = ObjectIdGenerators.PropertyGenerator.class, property = "idEntidade")
public class Entidades implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
@Basic(optional = false)
private Long idEntidade;
@Size(max = 50)
private String bairro;
private BigInteger brasao;
@Basic(optional = false)
@NotNull
@Size(min = 1, max = 14)
private String cnpj;
@Size(max = 20)
private String complemento;
// @Pattern(regexp="[a-z0-9!#$%&'*+/=?^_`{|}~-]+(?:\\.[a-z0-9!#$%&'*+/=?^_`{|}~-]+)*@(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?", message="E-mail inválido")//if the field contains email address consider using this annotation to enforce field validation
@Size(max = 30)
private String email;
@Size(max = 50)
private String logradouro;
@Basic(optional = false)
@NotNull
@Size(min = 1, max = 70)
private String nome;
@Size(max = 20)
private String numero;
@Basic(optional = false)
@NotNull
@Size(min = 1, max = 4)
private String sigla;
@Size(max = 12)
private String telefone;
@OneToMany(cascade = CascadeType.ALL, mappedBy = "idEntidade")
private Collection<EntidadesAdministradores> entidadesAdministradoresCollection;
@OneToMany(cascade = CascadeType.ALL, mappedBy = "entidades")
private Collection<Bairros> bairrosCollection;
@OneToMany(cascade = CascadeType.ALL, mappedBy = "idEntidade")
private Collection<PessoasDeficiencias> pessoasDeficienciasCollection;
@OneToMany(cascade = CascadeType.ALL, mappedBy = "idEntidade")
private Collection<PessoasEnderecos> pessoasEnderecosCollection;
@OneToMany(cascade = CascadeType.ALL, mappedBy = "idEntidade")
private Collection<EntidadesLicencas> entidadesLicencasCollection;
@OneToMany(cascade = CascadeType.ALL, mappedBy = "idEntidade")
private Collection<PessoasContatos> pessoasContatosCollection;
@OneToMany(mappedBy = "idEntidade")
private Collection<Logradouros> logradourosCollection;
@OneToMany(cascade = CascadeType.ALL, mappedBy = "idEntidade")
private Collection<Pessoas> pessoasCollection;
@JoinColumn()
@ManyToOne(optional = false)
private Municipios idMunicipio;
@OneToMany(cascade = CascadeType.ALL, mappedBy = "idEntidade")
private Collection<PessoasCaracteristicas> pessoasCaracteristicasCollection;
public Entidades() {
}
.... gets and sets . .
}
类 DistritosController
@RestController
@RequestMapping(value="/user")
public class DistritosController {
@Autowired
DistritosService distritosService;
@RequestMapping(method = RequestMethod.POST, value = "/distritos", consumes = MediaType.APPLICATION_JSON_VALUE)
public ResponseEntity<Distritos> cadastrarDistritos(@RequestBody Distritos distritos) {
Distritos distritosCadastrado = distritosService.cadastrar(distritos);
return new ResponseEntity<Distritos>(distritosCadastrado, HttpStatus.CREATED);
}
@RequestMapping(method = RequestMethod.GET, value = "/distritos", produces = MediaType.APPLICATION_JSON_VALUE)
public ResponseEntity<Collection<Distritos>> buscarTodosDistritos() {
Collection<Distritos> distritosBuscados = distritosService.buscarTodos();
return new ResponseEntity<>(distritosBuscados, HttpStatus.OK);
}
@RequestMapping(method = RequestMethod.GET, value = "/distritos/{id}", produces = MediaType.APPLICATION_JSON_VALUE)
public ResponseEntity<Distritos> buscarDistritosPorId(@PathVariable int id) {
Distritos distritos = distritosService.buscaPorId(id);
return new ResponseEntity<>(distritos, HttpStatus.OK);
}
@RequestMapping(method = RequestMethod.DELETE, value = "/distritos/{id}")
public ResponseEntity<Distritos> excluirDistritos(@PathVariable int id) {
Distritos distritoEncontrado = distritosService.buscaPorId(id);
if (distritoEncontrado == null) {
return new ResponseEntity<>(HttpStatus.NOT_FOUND);
}
distritosService.excluir(distritoEncontrado);
return new ResponseEntity<>(HttpStatus.OK);
}
@RequestMapping(method = RequestMethod.PUT, value = "/distritos", consumes = MediaType.APPLICATION_JSON_VALUE)
public ResponseEntity<Distritos> alterarDistritos(@RequestBody Distritos distritos) {
Distritos distritoAlterado = distritosService.alterar(distritos);
return new ResponseEntity<Distritos>(distritoAlterado, HttpStatus.OK);
}
}
最佳答案
有两个问题:
两者都是 @JsonIdentityInfo
的应该是范围内的,因为你的两个类都有相同的生成器类型 - ObjectIdGenerators.PropertyGenerator.class
.
Scope is used to define applicability of an Object Id: all ids must be unique within their scope; where scope is defined as combination of this value and generator type. Comparison is simple equivalence, meaning that both type generator type and scope class must be the same. Scope is used for determining how many generators are needed; more than one scope is typically only needed if external Object Ids have overlapping value domains (i.e. are only unique within some limited scope)
对于 Distritos
:
@JsonIdentityInfo(scope = Distritos.class, generator = ObjectIdGenerators.PropertyGenerator.class, property = "idDistrito")
对于 Entidades
:
@JsonIdentityInfo(scope = Entidades.class, generator = ObjectIdGenerators.PropertyGenerator.class, property = "idEntidade")
@JoinColumn()
@ManyToOne
private Entidades idEntidade;
以某种方式干扰
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
@Basic(optional = false)
private Long idEntidade;
当您将完整的 Distritos
传递给 Jackson 反序列化器时对象(包含 Entidades
内部,如您的示例所示)。
我做了一些调试,发现 BeanDeserializer (按名称解析字段)无法反序列化属性字段,因为它与 id 字段同名,所以我更改了 idEntidade
至 entidade
在 Distritos
类。
在这些更改之后,我的示例项目工作正常(因为我已经从您的类中删除了一些字段 - Distritos.idMunicipio
、Distritos.idUf
以及来自 Entidades 的所有 Collection
)。您必须检查其他类(例如 Municipios
和 Ufs
)是否有相同的问题,并修复它们。
关于java - JSON 解析错误 : Already had POJO for id,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/46493841/
最近开始学习MongoDB。今天老师教了我们 mongoexport 命令。在练习时,我遇到了一个典型的问题,包括教练在内的其他同学都没有遇到过。我在我的 Windows 10 机器上使用 Mongo
我是 JSON Schema 的新手,读过什么是 JSON Schema 等等。但我不知道如何将 JSON Schema 链接到 JSON 以针对该 JSON Schema 进行验证。谁能解释一下?
在 xml 中,我可以在另一个 xml 文件中包含一个文件并使用它。如果您的软件从 xml 获取配置文件但没有任何方法来分离配置,如 apache/ngnix(nginx.conf - site-av
我有一个 JSON 对象,其中包含一个本身是 JSON 对象的字符串。我如何反序列化它? 我希望能够做类似的事情: #[derive(Deserialize)] struct B { c: S
考虑以下 JSON { "a": "{\"b\": 12, \"c\": \"test\"}" } 我想定义一个泛型读取 Reads[Outer[T]]对于这种序列化的 Json import
关闭。这个问题不满足Stack Overflow guidelines .它目前不接受答案。 想改善这个问题吗?更新问题,使其成为 on-topic对于堆栈溢出。 11 个月前关闭。 Improve
我的旧项目在 MySQL 中有 Standard JSON 格式的数据。 对于我在 JS (Node.js) 和 DynamoDB 中的全新项目,关于 Standard JSON格式: 是否建议将其转
JSON 值字符串、数字、true、false、null 是否是有效的 JSON? 即,是 true 一个有效的 JSON 文档?还是必须是数组/对象? 一些验证器接受这个(例如 http://jso
我有一个 JSON 字符串,其中一个字段是文本字段。这个文本字段可以包含用户在 UI 中输入的文本,如果他们输入的文本是 JSON 文本,也许是为了说明一些编码,我需要对他们的文本进行编码,以便它不会
我正在通过 IBM MQ 调用处理数据,当由 ColdFusion 10 (10,0,11,285437) 序列化时,0 将作为 +0.0 返回,它会导致无效的 JSON并且无法反序列化。 stPol
我正在从三个数组中生成一个散列,然后尝试构建一个 json。我通过 json object has array 成功了。 require 'json' A = [['A1', 'A2', 'A3'],
我从 API 接收 JSON,响应可以是 30 种类型之一。每种类型都有一组唯一的字段,但所有响应都有一个字段 type 说明它是哪种类型。 我的方法是使用serde .我为每种响应类型创建一个结构并
我正在下载一个 JSON 文件,我已将其检查为带有“https://jsonlint.com”的有效 JSON 到文档目录。然后我打开文件并再次检查,结果显示为无效的 JSON。这怎么可能????这是
我正在尝试根据从 API 接收到的数据动态创建一个 JSON 对象。 收到的示例数据:将数据解码到下面给出的 CiItems 结构中 { "class_name": "test", "
我想从字符串转换为对象。 来自 {"key1": "{\n \"key2\": \"value2\",\n \"key3\": {\n \"key4\": \"value4\"\n }\n
目前我正在使用以下代码将嵌套的 json 转换为扁平化的 json: import ( "fmt" "github.com/nytlabs/gojsonexplode" ) func
我有一个使用来自第三方 API 的数据的应用程序。我需要将 json 解码为一个结构,这需要该结构具有“传入”json 字段的 json 标签。传出的 json 字段具有不同的命名约定,因此我需要不同
我想使用 JSON 架构来验证某些值。我有两个对象,称它们为 trackedItems 和 trackedItemGroups。 trackedItemGroups 是组名称和 trackedItem
考虑以下案例类模式, case class Y (a: String, b: String) case class X (dummy: String, b: Y) 字段b是可选的,我的一些数据集没有字
我正在存储 cat ~/path/to/file/blah | 的输出jq tojson 在一个变量中,稍后在带有 JSON 内容的 curl POST 中使用。它运作良好,但它删除了所有换行符。我知
我是一名优秀的程序员,十分优秀!