I want to change the XML data of content in journal article table.
i know liferay recommend to do this using liferay API , but i have to do this.

No, you don't have to do this. That is an excuse being made by someone that will not just say "no, we can't do this".

Tampering with the liferay database, especially in a case such as this, will lead to database corruption, environment instability and likely inoperability.

Anyone who says "I just have to modify the database directly" doesn't understand this core principle and should not be trusted to make any modifications to Liferay.

The Liferay database is not yours. I've said this time and time again. Forget it is there. Pretend your DB tool is broken. Never ever point it at the Liferay database and look at the contents. It is not yours to play with, it is not yours to look at, and it is not yours to modify.

Let's say, for example, that you somehow were able to figure this out. What about the related tables, are you going to update those too? Oh, you don't know that there are related tables? How are you prepared to deal with the subsequent Liferay failures? Oh, and web content is certainly also replicated in both the search index and local node caches, neither of which are updated when a table is modified directly. In fact, if you knew better, you would know that for this kind of scenario most of the time the docs come from the index, not the database, so when you change the DB you won't see a corresponding change in the UI.

There are reasons we say "don't look at or modify the database". It is not documented. Especially in columns that store XML or JSON, they are definitely not documented. It is subject to unannounced and unreported change. Columns with one name might have been deprecated (or even worse) repurposed without adjusting the name. The DB is just one cog in Liferay's machinery to quickly render and serve content, it is just the persistent store but is not the only runtime source of data.

If you don't use the Liferay API, you are abdicating your responsibilities as a Liferay admin and/or developer. It demonstrates that you are missing a basic understanding of one of the core principles of using and working with Liferay.

All of this may sound harsh, but it is meant to. If I've left you or someone else with the impression that what you're doing is wrong, that is totally the intent. I have been called in time and time again trying to "fix" things that someone modifying the DB directly has broken.








Come meet me at the 2017 LSNA!

Can you cast your node to an Element?
Element element = (Element) node;

Then you could call getContent() and use setContent to store CDATA objects.

But instead of fetching the content directly you should use JournalArticleLocalService to fetch the articles you want to change and call getContent/setContent to modify them. That way they are reindexed when you save them. Otherwise, if you do it directly in the database you need to reindex all articles.