This isn't part of the SOAP framework to my knowledge. If you want to send a locale from the client to the server, you should include it as part of your specific protocol.
On Tue, Oct 13, 2009 at 3:23 PM, jp4 <[email protected]> wrote: > > Dan, > > Thanks for the reply. In my case, I may want to return Locale specific > error messages and currency formats. Is there a way to retrieve the Locale > from the client for the current request? I've read that Accept-Language > and > charset are alternatives. Is one approach preferred over the other? > > Thanks > > John > > > dkulp wrote: > > > > > > For CXF, there normally isn't much you have to do. By default, we use > > UTF-8 > > for all "on the wire" things so international strings and such "just > > work". > > You can override it by setting the Message.ENCODING setting in the > Message > > early in the interceptor chain, but it's rare to be needed. > > > > Dan > > > > > > > > On Tue October 6 2009 12:51:26 pm jp4 wrote: > >> I am working on a project to internationalize our CXF based web services > >> and I was hoping that someone could point me to some good > documentation. > >> I'm looking for information such as how is the Locale set by the client > >> (http headers?), how is the Locale accessed by the service, etc. Any > >> help > >> would be greatly appreciated. We are currently using WSDL to Java to > >> generate our web services if that is relevant. > >> > >> Thanks, > >> > >> John > >> > > > > -- > > Daniel Kulp > > [email protected] > > http://www.dankulp.com/blog > > > > > > -- > View this message in context: > http://www.nabble.com/CXF-Internationalization-tp25772509p25879137.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
