topic Re: Interceptor not matche with 4.1.7 migration in Alfresco Archive

Interceptor not matche with 4.1.7 migration

titiabackup — Thu, 18 Dec 2014 16:51:06 GMT

Hi,I have a problems that i don't understand.I have an interceptor from the 3.0.0 version which have ok but since the 4.1.7 migrationit's not call and i don't understand why.THe interceptor is in a module which is correctly include in alfresco, because the log describe a call to the default construc

Re: Interceptor not matche with 4.1.7 migration

mrogers — Thu, 18 Dec 2014 18:20:40 GMT

Can't see anything wrong with what you have posted. But I suggest you double check the bean names since the spring configuration may have changed, since 3.0.0. (You may be intercepting the wrong bean now. And I note that you are intercepting "contentService" rather than "ContentService".)

Also please note that index control is now provided by alfresco 4.X so your module may no longer be necessary.

Re: Interceptor not matche with 4.1.7 migration

mrogers — Thu, 18 Dec 2014 18:20:52 GMT

Re: Interceptor not matche with 4.1.7 migration

titiabackup — Fri, 19 Dec 2014 09:14:09 GMT

THanks a lot, the bean intercept exists but i'm not sure that what the same use for indexing now.

Do you know the bean used for read the content to index it ?

Otherwise, i find this configuration which wil be used to not index the content.


<type name="cm:content">
        <title>Content</title>
        <parent>cm:cmobject</parent>
        <properties>
           <property name="cm:content">
              <type>d:content</type>
              <mandatory>false</mandatory>
              <index enabled="false">
              </index>
           </property>
        </properties>
     </type>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍

THe documentation link is : <a>http://docs.alfresco.com/4.1/concepts/search-fts-config.html</a>

But when i had this code to the share-config-custom.xml, the content indexed and it's not that i want.

what method is used to not indexe content of a document ?

Re: Interceptor not matche with 4.1.7 migration

titiabackup — Fri, 19 Dec 2014 13:13:58 GMT

Hi,

i finally set the property cm:isContentIndexed to false when i had the document by java code:
<java>
contentProps.put(ContentModel.PROP_IS_CONTENT_INDEXED, false);
</java>

and it's work fine.

The interceptor problems came from the fact that contentService wasn't the service call by the indexing .

The interceptor deprecated in my code.

Thanks for all.

titia