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

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven