I have been facing a issue related to upgrading a opensource application from jackson 1.9 to jackson 2.3.
The problem is coming in the method objectmapper.readvalue.
The version i was using initially was objectmapper.readvalue(jsonnode,typereference) with a jsondeserializer registered along with simplemodule.
now this method is deprecated in jackson2.3 and for this i planned to use
objectmapper.readvalue(jsonparser,typereference) getting jsonparser through jsonnode.traverse().
But jsonparser passed through this way resulted in giving out a null objectmapper through jsonparser.getCodec(), which is a standard way of getting a result.
This code was totally working with jackson 1.9..
I am not very well versed with jackson and not been able to find ample document on net for migration to new jackson.
Looking forward for any pointer/help in this regard...
Thanks in advance
Related
I am migrating from jdk8 to jdk11 and hence trying to use chronicle-queue v5.
In ChroincleQueue version 3 we had dedicated methods for creating SourceQueue and SinkQueue.
But I am finding it little difficult to implement the same with ChronicleQueue v5.
I am trying to follow this. In the doc they have mentioned use of ReplicatedQueue and ReplicatedQueueCfg classes. I looked into different classes of all the other packages of Chronicle but didn't find any of these classes.
How can I implement replication using ChronicleQueue5 ?
This annotation is documented here but not marked deprecated, however in the migration guide there's no mention of why it was removed, and what should be used instead.
I am totally new to Ktor, and I am supposed to port a 1.6 project to 2 while learning Ktor from scratch. Some leads in this direction will be much appreciated. Thanks
Multiple DSL markers were unified so you can use the KtorDsl annotation instead.
I need to use both quartz-1.8.6 and quartz-2.x.x dependencies in the same maven 3 project.
The reason for keeping 1.8.6 is that it's used by a large amount of code and new features are considered to written in spring, and in this case quartz-2.x come into play.
So the question is: how can I keep both these dependencies in the same project ? Maybe add some exclusions?
do you really need to use both of them at the same time
generally the classes may be deprecated. but usage will still be allowed.
You see whole idea of using maven is to avoid multiple jar of same API.
I will suggest code changes and completely using quartz 2.x API.
I was getting similar issue when I used lucene and was switching from 2.2 to 2.8/3, there were not just deprecated methods but many lucene classes were removed i the 2.8 API. I still ended in upgrading the API than using duplicate dependent jars
here's an idea i have been playing with for a while.
is it possible to mix CDI and Struts 1.3 ?
E.g. via a CDI Portable Extension..?
As for 'why', there are still a few projects 'out there' which are stuck on an old stack and don't have the option to switch to struts 2..
Just throwing it out there, i'm interested in your ideas =)
greetings from germany
I just committed my library to github, called struts-cdi. You should check it out.
https://github.com/reegnz/struts-cdi
It only works with Struts Actions for now, and not with ActionForms. If the need arises, I will also try to do container managed ActionForms. :^)
Stripes Injection Enricher satisfies injection points specified declaratively using standard Java EE annotations (#EJB, #Inject and #Resource).
I'm migrating the data layer of our application to NH version 2.1.0 (from 2.0.1) and noticed the use of LinFu. I discovered that framework and want to use it in other pieces of the application, especially I want to use the LinFu.Reflection.dll, which requires a reference to LinFu.DynamicProxy and here comes the trouble, the 1.0 final version of LinFu that I can find on google.code is not the same version used by NHibernate itself. Do I need to rebuild NHibernate.ByteCode.LinFu.dll changing the reference to the available version? If not, what else?
I have faced the same problem a few days ago. There's a tool named ILMERGE that merges .NET DLL-files, and that way you should be able to have several versions of the same DLL in your application.
Unfortunately I haven't tested the tool yet, I didn't get around to it, but I'll test in the next week.
But Rhino Mocks for example, has a binary with all dependencies included: http://ayende.com/projects/rhino-mocks/downloads.aspx, so it seems doable.