Interestingly, if I exclude this module in my pom, then the problem goes
away... I don't even need this code apparently!
<dependency>
<groupId>io.dropwizard</groupId>
<artifactId>dropwizard-core</artifactId>
<exclusions>
<exclusion>
<groupId>com.fasterxml.jackson.module</groupId>
<artifactId>jackson-module-jaxb-annotations</artifactId>
</exclusion>
</exclusions>
</dependency>
On Wednesday, October 5, 2016 at 3:17:06 PM UTC-7, Vasuki Seshadri wrote:
>
> What about the micro-patch you suggested, 2.7.8.1? Is that something you
> can put into Maven central repo so I can unblock myself? Not sure I want to
> use a SNAPSHOT dependency...
>
> On Wednesday, October 5, 2016 at 3:08:51 PM UTC-7, Tatu Saloranta wrote:
>>
>> I don't know if downgrade is possible; you'd have to go down to 2.6. Not
>> sure if DW core relies on 2.7 functionality or not; if not, downgrade to
>> 2.6.7 would be a work-around.
>>
>> But yes, when new version arrives you would override DW default version;
>> if you can deploy local build, you could 2.8.4-SNAPSHOT or 2.7.9-SNAPSHOT.
>>
>> -+ Tatu +-
>>
>>
>> On Wed, Oct 5, 2016 at 2:17 PM, Vasuki Seshadri <[email protected]>
>> wrote:
>>
>>> Thanks for the information. Are you suggesting overriding the Jackson
>>> version in DropWizard with a custom one in my pom.xml? Or should I revert
>>> my DropWizard version to an older one until this is fixed?
>>>
>>> On Wednesday, October 5, 2016 at 12:39:26 PM UTC-7, Tatu Saloranta wrote:
>>>>
>>>> This was just recently reported, and fixed:
>>>>
>>>> https://github.com/FasterXML/jackson-module-jaxb-annotations/issues/63
>>>>
>>>> and it was related to JAXB annotations module.
>>>> Unfortunately there's no release with the fix yet; it will be in 2.7.9
>>>> (will take a while) and 2.8.4 (should be out sooner).
>>>> Locally it is possible to just sub-class JaxbAnnotationIntrospector.
>>>> I could also release micro-patch, 2.7.8.1 just for JAXB module if that
>>>> would help.
>>>>
>>>> -+ Tatu +-
>>>>
>>>>
>>>> On Wed, Oct 5, 2016 at 10:56 AM, Vasuki Seshadri <[email protected]>
>>>> wrote:
>>>>
>>>>> Everything was working fine with my simple DropWizard 0.9.3 app, but
>>>>> when I upgrade to 1.0.2, I get this cryptic error:
>>>>>
>>>>> config-file.yml has an error:
>>>>> * Failed to parse configuration; Must call method with a container
>>>>> type (got [reference type, class
>>>>> java.util.Optional<java.lang.String<[simple type, class
>>>>> java.lang.String]>])
>>>>> at [Source: N/A; line: -1, column: -1]
>>>>>
>>>>> How do I go about debugging this? I have narrowed it down to the usage
>>>>> of a DataSourceFactory (for JDBI) in my Configuration class. If I remove
>>>>> this object, I get past this error, but of course, I need it to work.
>>>>>
>>>>> Thanks,
>>>>> Vasuki.
>>>>>
>>>>> --
>>>>> 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.
>>>
>>
>>
--
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.
