Hi Martin,
I'm not sure what you're asking here - without further information I
suspect you won't get any help as it's not clear what you want.
Jonathan
On 22 October 2013 14:32, Chamberland, Martin <[email protected]
> wrote:
> Did you have time to take a look at our problem ?****
>
> ** **
>
> Thank’s!****
>
> ** **
>
> Martin C.****
>
> ** **
>
> *De :* Jonathan Moules [mailto:[email protected]]
> *Envoyé :* 21 octobre 2013 08:40
> *À :* Chamberland, Martin
> *Cc :* [email protected]
> *Objet :* Re: [Geoserver-users] date BUG 2.4 Geoserver****
>
> ** **
>
> Hi Martin,****
>
> That's the ISO standard for date formatting.
> https://en.wikipedia.org/wiki/ISO_8601****
>
> ** **
>
> Could you be clearer what the problem is for you?****
>
> ** **
>
> Jonathan****
>
> ** **
>
> ** **
>
> On 17 October 2013 19:38, Chamberland, Martin <
> [email protected]> wrote:****
>
> Hi there,****
>
> ****
>
> We just install the new version Geoserver 2.4 and from now we seem to
> receive some strange date format in our request.****
>
> ****
>
> All date output create by our trigger look like this: 1969-12-31.****
>
> ****
>
> Is there maybe a bug in the 2.4 version ?****
>
> ****
>
> Martin C.****
>
> ****
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users****
>
> ** **
>
>
> This transmission is intended for the named addressee(s) only and may
> contain sensitive or protectively marked material up to RESTRICTED and
> should be handled accordingly. Unless you are the named addressee (or
> authorised to receive it for the addressee) you may not copy or use it, or
> disclose it to anyone else. If you have received this transmission in error
> please notify the sender immediately. All email traffic sent to or from us,
> including without limitation all GCSX traffic, may be subject to recording
> and/or monitoring in accordance with relevant legislation.****
>
--
This transmission is intended for the named addressee(s) only and may
contain sensitive or protectively marked material up to RESTRICTED and
should be handled accordingly. Unless you are the named addressee (or
authorised to receive it for the addressee) you may not copy or use it, or
disclose it to anyone else. If you have received this transmission in error
please notify the sender immediately. All email traffic sent to or from us,
including without limitation all GCSX traffic, may be subject to recording
and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
