topic Re: Content description saved value locale problem? in Alfresco Archive

Content description saved value locale problem?

nenad982 — Thu, 08 May 2014 10:43:57 GMT

Hi all,I am experiencing following problem. My clients are using German and English locales to work with Alfresco (they like Explorer and they don't want to use Share). If they add some value for node description on English locale and search for that description value in Advanced Search in German lo

Re: Content description saved value locale problem?

mrogers — Thu, 08 May 2014 11:55:46 GMT

Is there possibility to use Java API to save value for description for ALL LOCALES.

Yes. I'm thinking of a policy that sets the value for each language. Or the other approach is to remove or replace the MLText interceptor.

Re: Content description saved value locale problem?

nenad982 — Thu, 08 May 2014 12:43:44 GMT

Hi mrogers,

thank you for your answer. What is the name of that MLText interceptor? This part with policy is not clear to me, so could you give me point where to look for some example or something?

Thanks a lot

Re: Content description saved value locale problem?

kaynezhang — Fri, 09 May 2014 03:06:37 GMT

MLText interceptor is not a policy,it is an aop method interceptor

The MLPropertyInterceptor(org.alfresco.repo.node.MLPropertyInterceptor) is used to deal with the localized node properties .
1.It intercepts the node service methods: getProperty, getProperties to filter out multilingual text properties and return only current local
2.It intercepts the node service methods: setProperties, setProperty、createNode、addAspect to set the current local property value of a multilingual text.
You can override MLPropertyInterceptor's

public Object invoke(final MethodInvocation invocation) throws Throwable‍

method:
in your implematation version of intercepting the node service methods: setProperties, setProperty、createNode、addAspect,add all local valuse to MLText.

Re: Content description saved value locale problem?

nenad982 — Fri, 16 May 2014 09:38:04 GMT

Hi all,

overriding of MLPropertyInterceptor.java fixed my issue.

Thanks to all…