There is either some structural discrepancy between YAML configuration
file, and structure of Configuration type you are using, or bug in Jackson
YAML dataformat module. Unfortunately the way configuration is read in
loses location information (I think), otherwise it would be easier to see
exactly which token in YAML is at odds with expected state.

Exception basically states that within sequence of tokens, there should be
a field name, but what is seen is a start of map (in JSON that'd be "{", in
YAML multiple ways to indicate).

I don't think this would be related to Hibernate usage, unless you use YAML
configuration there too.

-+ Tatu +-


On Wed, May 18, 2016 at 7:11 AM, Matt Weaver <[email protected]> wrote:

> I'd add that I'm trying to use my JSON serializable objects as the same
> that I store in the database via Hibernate.  I've tried removing a good bit
> of code and that is the only thing that comes to mind as being an issue.
>
>
> On Wednesday, May 18, 2016 at 8:01:12 AM UTC-6, Matt Weaver wrote:
>>
>> Migrating my backend to use the Hibernate connector, but getting this:
>>
>> Exception in thread "main" com.fasterxml.jackson.core.JsonParseException:
>> Expected a field name (Scalar value in YAML), got this instead:
>> <com.fasterxml.jackson.dataformat.yaml.snakeyaml.events.MappingStartEvent(anchor=null,
>> tag=null, implicit=true)>
>>
>> I don't see any errors in my YAML, has anyone seen anything like this
>> before?  I've not fully exhausted all debugging options, but thought I'd
>> ask anyway (you know, saving time and all that).
>>
> --
> You received this message because you are subscribed to the Google Groups
> "dropwizard-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"dropwizard-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to