[
https://issues.apache.org/jira/browse/DBUTILS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692013#comment-17692013
]
Miguel Costa edited comment on DBUTILS-150 at 2/22/23 8:20 AM:
---------------------------------------------------------------
Sorry Indeed I could provide a an example of what cause this.
So this classes are generated of a proto that looks like this (basically any
map or repeated "Message" will cause this):
{code:java}
syntax = "proto3";
package com.xyz.test;
message Test {
map<string, SInt64Value> fldMap = 1;
repeated SInt64Value anotherList = 2;
}
message SInt64Value {
sint64 intVal = 1;
}
{code}
It is stored as a BLOB in the DB.
I'll copy/update the ticket with the generated class from protobuf in a little
bit
was (Author: miguel_costa):
Sorry Indeed I could provide a an example of what cause this.
So this classes are generated of a proto that looks like this (basically any
map or repeated "Message" will cause this):
{code:java}
syntax = "proto3";
package com.xyz.test;
message Test {
map<string, StringValue> fldMap = 1;
repeated SInt64Value anotherList = 2;
}
message SInt64Value {
sint64 intVal = 1;
}
{code}
It is stored as a BLOB in the DB.
I'll copy/update the ticket with the generated class from protobuf in a little
bit
> BeanProcessor populateBean does not work when PropertyDescriptor is of type
> ----------------------------------------------------------------------------
>
> Key: DBUTILS-150
> URL: https://issues.apache.org/jira/browse/DBUTILS-150
> Project: Commons DbUtils
> Issue Type: Improvement
> Affects Versions: 1.7
> Reporter: Miguel Costa
> Assignee: Carl Franklin Hall
> Priority: Major
> Fix For: 1.8
>
> Attachments: 2023-02-14 10_14_48-Window.png, 2023-02-14
> 10_17_28-Window.png
>
>
> I've been using DB utils for a while to help me handle some custom beans
> (Protobufs)
> Anyway while debugging an issue I'm facing I noticed that the function
> BeanProcessor.populateBean is not able to handle
> PropertyDescriptor when their class is IndexedPropertyDescriptor instead of a
> normal PropertyDescriptor.
> IndexedPropertyDescriptor extends PropertyDescriptor so I would expect this
> to work without any issue, but currently it does not
>
> I can provide a PR for review with my best approach for it
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
