Skip to main content

Java Core Service Trouble with DateTime Convertion to java.util.Date

In my previous post A Core Service Java Client, I was describing how to generate the proxy classes for the Java client. It turns out, however, that the custom bindings I was using for converting DateTime string representations to java.util.Date were not working properly. When I was running my client, all the dates were coming back 'null'.

The problem was the default Adapter code generated by wsimport. I saw the conversion too simplistically. The custom bindings that I was using

<jxb:bindings version="1.0" xmlns:jxb="http://java.sun.com/xml/ns/jaxb" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <jxb:globalBindings generateElementProperty="false">
    <jxb:javaType name="java.util.Date" xmlType="xs:dateTime"/>
  </jxb:globalBindings>
</jxb:bindings>

would generate the following adapter code:

public class Adapter1 extends XmlAdapter<String, Date> {
    public Date unmarshal(String value) {
        return new Date(value);
    }

    public String marshal(Date value) {
        if (value == null) {
            return null;
        }
        return value.toString();
    }
}

The dates trafficked between the webservice and client are in the format yyyy-MM-ddTHH:mm:ss and, for the adapter above, would yield an exception and a 'null' overall value.

Solution

The solution is to provide my own converter. I implemented the following two utility methods:

public static String parseDateToString(Date date) {
    SimpleDateFormat formatter = new SimpleDateFormat(DATE_PATTERN);
    return formatter.format(date);
}

public static Date parseStringToDate(String date) {
    try {
        SimpleDateFormat formatter = new SimpleDateFormat(DATE_PATTERN);
        return formatter.parse(date);
    } catch (ParseException e) {
        // big bubu
    }
    return null;
}

private static final String DATE_PATTERN = "yyyy-MM-dd'T'HH:mm:ss";

Note: SimpleDateFormat is not thread-safe, hence the new instance on every call.

The custom bindings needs to be changed to instruct wsimport to make use of the two methods (as per documentation):

<jxb:bindings version="1.0" xmlns:jxb="http://java.sun.com/xml/ns/jaxb" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <jxb:globalBindings generateElementProperty="false">
    <jxb:javaType name="java.util.Date" xmlType="xs:dateTime"
      parseMethod="mitza.coreservice.util.Utils.parseStringToDate"
      printMethod="mitza.coreservice.util.Utils.parseDateToString" />
  </jxb:globalBindings>
</jxb:bindings>

I had put the two converter methods inside class Utils, in package mitza.coreservice.util.

Finally, running wsimport again yields the following Adapter class:

public class Adapter1 extends XmlAdapter<String, Date> {
    public Date unmarshal(String value) {
        return (mitza.coreservice.util.Utils.parseStringToDate(value));
    }

    public String marshal(Date value) {
        return (mitza.coreservice.util.Utils.parseDateToString(value));
    }
}

This works very well...

The updated code is available in my Google Code project.


Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...