Hi there!
I am currently working on it too and I am wondering the same question.
Acutally, I manage to create (partially, I will explain why...) a new article in Liferay using this method. Here is the call :
(sorry for french comments...)
Here is some parts of the xml I use to generate the content String :
I have many other fields but it's exactly the same
Whith all these arguments in the addArticle() method, I manage to create my article, and make it appeared in the web content list.
However, I am facing a big issue, maybe a bug of Liferay :
The "text-area" fields remain empty, but "text" fields are well display.
If I click on the action "View" (to view it using the velocity template), the text-area is shown normally whith the right content.
This is the first issue.
The second issue :
As soon as I modified a fields (whatever which one), all my content disapears, all my fields are empty except the mandatory articleTitle (not part of my structure). The article view with the velocity template doesn't work anymore and show me my vm variables ($myField.getData()).
So I suppose my content is lost. I can fill in my fields from the edit page, and work normally with my article.
From here, Where can the problem come from ? Answer: I think, from the attribute instance-id in the XML.
As it is a generated value by Liferay, I didn't put this dynamic-content attribute in my xml used to generate the content String. And in fact, when I download the article (with the download button in the edit view), all my fields in the downloaded xml has a 'null' instance-id.
After editing and saving the desappeared fields, the newly downloaded xml includes now an instance-id, generated.
Now the relevant question is : How to tell Liferay to generate those instance-id from the beginning and avoid this loss of data?
Thnaks for reading.
I am currently working on it too and I am wondering the same question.
Acutally, I manage to create (partially, I will explain why...) a new article in Liferay using this method. Here is the call :
(sorry for french comments...)
try {
Document doc = SAXReaderUtil.read(loadXmlContentTemplate());
// Remplissage des champs du Document à l'aide d'une hashMap (data) contenant
// les attributs "name" du "dynamic-element" en KEY et les valeurs associés.
for (String key : data.keySet()) {
Node node = doc.selectSingleNode("/root/dynamic-element[@name='" + key + "']/dynamic-content");
node.setText("" + data.get(key) + "");
}
// Génération de la chaine Content à envoyer à Liferay --> lorsque traité par asXML(), les chevrons du CDATA sont transformé en code Html
String createdContentXml = StringEscapeUtils.unescapeXml(doc.asXML());
// titleMap reprend les différents language, obligatoire
Map<locale, string> titleMap = new HashMap<locale, string>();
titleMap.put(Locale.FRANCE,
data.get("id") +
" - " +
data.get("titre");
// Pour les champs INT obligatoires (displayDate)
GregorianCalendar date = (GregorianCalendar) GregorianCalendar.getInstance(TimeZone.getTimeZone("Europe/Paris"), Locale.FRANCE);
// Le serviceContext est obligatoire, ces différents champs sont optionnels SAUF groupId
ServiceContext serviceContext = new ServiceContext();
serviceContext.setScopeGroupId(Long.parseLong(PortletProps.get("groupId")));
JournalArticle addedTrip = JournalArticleLocalServiceUtil.addArticle(
Long.parseLong(PortletProps.get("userId")),
Long.parseLong(PortletProps.get("groupId")),
0L, //classNameId
0L, //classPK
"", // articleId -> ne peut pas être null
true, //autoArticleId
1D, //version
titleMap, // hashmap titre défini au dessus
null, //descriptionMap
createdContentXml, // content en xml généré plus haut
PortletProps.get("articleType"), // type, ne peut pas être null ou vide
PortletProps.get("structureId"), // structure de l'article, je ne sais pas si peut être null ou vide...
PortletProps.get("templateId"), // template de l'article, je ne sais pas si peut être null ou vide...
null, // layoutUuid
date.get(Calendar.MONTH), // |
date.get(Calendar.DAY_OF_MONTH), // |
date.get(Calendar.YEAR), // | --> displayDate
date.get(Calendar.HOUR), // |
date.get(Calendar.MINUTE), // |
0, // |
0, // |
0, // |--> expireDate, peut être null, vide ou 0 si neverExpire = true, sinon Attention aux contraintes!
0, // |
0, // |
true, // neverExpire
0, // |
0, // |
0, // |--> ReviewDate, peut être null, vide ou 0 si neverReview = true, sinon Attention aux contraintes!
0, // |
0, // |
true, // neverReview
true, // indexable
false, // smallImage
null, // null |
null, // null | ==> arguments concernant les images.
null, // null |
null, // null |
serviceContext //serviceContexte obligatoire, avec au moins scopeGroupId (= groupId de l'article)
);
// Exceptions pouvant être levées :
// DocumentException / NumerFormatException / PortalException / SystemException
} catch( Exception e) {
e.printStackTrace();
}
</locale,></locale,>Here is some parts of the xml I use to generate the content String :
I have many other fields but it's exactly the same
<root available-locales="fr_FR" default-locale="fr_FR">
<dynamic-element name="titre1" type="text" index-type="">
<dynamic-content></dynamic-content>
</dynamic-element>
<dynamic-element name="description-longue" type="text_area" index-type="">
<dynamic-content></dynamic-content>
</dynamic-element>
</root>Whith all these arguments in the addArticle() method, I manage to create my article, and make it appeared in the web content list.
However, I am facing a big issue, maybe a bug of Liferay :
The "text-area" fields remain empty, but "text" fields are well display.
If I click on the action "View" (to view it using the velocity template), the text-area is shown normally whith the right content.
This is the first issue.
The second issue :
As soon as I modified a fields (whatever which one), all my content disapears, all my fields are empty except the mandatory articleTitle (not part of my structure). The article view with the velocity template doesn't work anymore and show me my vm variables ($myField.getData()).
So I suppose my content is lost. I can fill in my fields from the edit page, and work normally with my article.
From here, Where can the problem come from ? Answer: I think, from the attribute instance-id in the XML.
As it is a generated value by Liferay, I didn't put this dynamic-content attribute in my xml used to generate the content String. And in fact, when I download the article (with the download button in the edit view), all my fields in the downloaded xml has a 'null' instance-id.
After editing and saving the desappeared fields, the newly downloaded xml includes now an instance-id, generated.
Now the relevant question is : How to tell Liferay to generate those instance-id from the beginning and avoid this loss of data?
Thnaks for reading.
