Answering myself:
To solve this problem, simply set the appropriate format when you construct
the SimpleDateFormat inside CalendarSerializer.java.
The present CalendarSerializer defaults to 'yyyy-MM-dd'.
--
David S. Kenzik
[EMAIL PROTECTED] - http://kenzik.com
Original Music - http://kenzik.com/music
David Kenzik said...
> I've exposed a test method that dumps my passed GregorianCalendar object as
> a string:
>
> ...
> public void test(GregorianCalendar c)
> {
> System.out.println(c.toString());
> }
> ...
>
> The client side is doing the following:
>
> ...
> call.setMethodName("test");
> // Also tried:
> // Calendar testCal=new GregorianCalendar();
> GregorianCalendar testCal=new GregorianCalendar();
> System.out.println(testCal.toString());
> params.addElement(new Parameter("c",GregorianCalendar.class,testCal,null));
> call.setParams(params)
> response=call.invoke(url,"");
> ...
>
> I'm finding that some information is lost over the wire.
>
> The client side shows, as the javadocs suggest, that the testCal is indeed
> set to the current date/time. However, the server side loses all the time
> settings: HOUR, HOUR_OF_DAY, MINUTE, SECOND, MILLISECOND; and the 'time' key
> is off by the aforementioned time settings.
>
> According to the Apache-SOAP docs, GregorianCalendar is a predefined type
> mapping.
>
> Is this a known issue? Is this a new bug? Am I doing something wrong?
>
> Any input wuld be appreciated.
>
> --
> David S. Kenzik
> [EMAIL PROTECTED] - http://kenzik.com
> Original Music - http://kenzik.com/music
