Hi (again) Mirto 
I'll try to help out on this one as well. You can leverage some of the aui input tag lib to help you out here. In your view (jsp?) you can use the aui input with an attribute that will render the flags for the languages that are available (configured) for you instance.
The post of the different values Liferay will actually handle for you which is great. On the back side you can use the ParamUtil to get the list of values. I am going from memory here but I think you get an array with <locale>=<value> like this --
I think at this stage you can convert it to a Map using the MapUtil class
... or something like that. Now that you have your map, you can call your service with the Map as a parameter and you should be good to go.
I'll try to help out on this one as well. You can leverage some of the aui input tag lib to help you out here. In your view (jsp?) you can use the aui input with an attribute that will render the flags for the languages that are available (configured) for you instance.
<aui:input name="sample" localized="<%= true %>" />The post of the different values Liferay will actually handle for you which is great. On the back side you can use the ParamUtil to get the list of values. I am going from memory here but I think you get an array with <locale>=<value> like this --
String[] sampleValues = ParamUtil.getStringValues(actionRequest, "sample", null);I think at this stage you can convert it to a Map using the MapUtil class
Map<locale, string> sampleMap = MapUtil.fromArray(sampleValues);</locale,>... or something like that. Now that you have your map, you can call your service with the Map as a parameter and you should be good to go.
Hi Andrew, thanks (again)
I'm trying your suggestions
First progress:
I discovered how multilingual content is stored.
Using a Basic Web Content (journalarticle) when you edit an article you have a button to create a new translation (here I'm using English and Italian)
After the action that creates an Italian translation the multilanguage fields content is transformed in XML (example for description field)
Instead in my test field (the field "name" in the guestbook demo application) there is only standard text.
I'm investigating about the create translation function.
I'm trying your suggestions
First progress:
I discovered how multilingual content is stored.
Using a Basic Web Content (journalarticle) when you edit an article you have a button to create a new translation (here I'm using English and Italian)
After the action that creates an Italian translation the multilanguage fields content is transformed in XML (example for description field)
<!--?xml version='1.0' encoding='UTF-8'?-->
<root available-locales="en_US,it_IT," default-locale="en_US">
<description language-id="it_IT">prova multilingua</description>
<description language-id="en_US">multilingual test</description>
</root>Instead in my test field (the field "name" in the guestbook demo application) there is only standard text.
I'm investigating about the create translation function.
Community
Company
Feedback