For sure, software security should be part of every developer’s requirements: they should be explained and detailed before development. Unfortunately, it happens in real life that this is not always the case.
I’ve been thinking about a way to sanitize the output of a large-scale legacy Spring MVC application in a reliable way (i.e. not go on each page to fix issues).
Shortly after you start building docker containers you will realize that you need some place to publish your images. You could push to the central docker registry. However, the central registry is public. Not a great idea if you are working on a private project.
Looking at all the projects I've worked on over the years, big or small, there's been one nasty constant. A mistake that creeps up on you at least once a project and puts an indelible mark on all future work. And it has everything to do with not sticking to the optimal workflow.
As of Lucene 4.10 there will be a new proximity query to further generalize on MultiPhraseQuery and the span queries: it allows you to directly build an arbitrary automaton expressing how the terms must occur in sequence, including any transitions to handle slop.
Your DBA just wants to help. And when you're working with large sets of data - or any sets of data, really - sometimes that's the help you need, because small mistakes can quickly balloon into large ones.
The moment I had this credit card sized thing on my palm, I was so excited to get started with it. But then, wait! Do you need a HDMI TV or display monitor, USB keyboard and a USB mouse to connect to it? Oh really!? I was not interested to invest any further. Here is what I did.
This week we're talking to Andreea Borcea, developer of patient-empowering solutions for the healthcare industry, co-host of Farstuff: The IoT Podcast, and featured author in DZone's 2014 Guide to Internet of Things.
We use a logging layer over log4j to encourage our developers to log at any point in the code where they thought some extra context would help resolve runtime errors. The layer had to have a familiar API, be effortless to code, and cheap to call. This posting is mostly about the cost to call the logger and a little about enhancing the presentation of logged values.
If you missed anything on DZone this week, now's your chance to catch up! This week's best include the ultimate guide to Java 8 features, a beginner's guide to JPA/Hibernate entity state transitions, when to dump Scrum for Kanban, and more.