You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@manifoldcf.apache.org by Frank Brendel <fr...@eurolog.com> on 2015/03/11 10:25:46 UTC
SharePoint Path Mapping not working
Hello,
I cannot add a path mapping to the SharePoint connector.
In the jobs metadata tab I've configured a metadata rule:
Path match: /*
Action: include
All metadata: true
Now I want a new attribute 'url' that contains the complete URL to the
SharePoint source and not only the path.
Therefore I set the attribute name to 'url' and try to add a path mapping
Match regexp: (.*)
Replace string: http:\/\/host:port$(1)
But nothing happens. Why?
Thank you
Frank
Re: SharePoint Path Mapping not working
Posted by Frank Brendel <fr...@eurolog.com>.
Ok, I had to workaround some things:
1. Missing directories
mkdir framework/dist/example-proprietary
mkdir framework/dist/example
2. Wrong download locations:
connectors/alfresco/build.xml
87c87
< <get
src="https://artifacts.alfresco.com/nexus/service/local/repositories/releases/content/org/alfresco/alfresco-web-service-client/${alfresco-client.version}/alfresco-web-service-client-${alfresco-client.version}.jar"
dest="lib-proprietary"/>
---
> <get
src="https://artifacts.alfresco.com/nexus/service/local/repositories/releases/content/org/alfresco/alfresco-web-service-client/${alfresco-client.version}/alfresco-web-service-client-${alfresco-client.version}.jar"
dest="lib-proprietary/alfresco-web-service-client-${alfresco-client.version}.jar"/>
site/build.xml
266c266
< <get
src="http://downloads.sourceforge.net/project/dejavu/dejavu/2.33/dejavu-fonts-ttf-2.33.zip?r=&ts=1327734867&use_mirror=cdnetworks-us-2"
dest="fonts"/>
---
> <get
src="http://downloads.sourceforge.net/project/dejavu/dejavu/2.33/dejavu-fonts-ttf-2.33.zip?r=&ts=1327734867&use_mirror=cdnetworks-us-2"
dest="fonts/dejavu-fonts-ttf-2.33.zip"/>
279c279
< <get
src="http://jaist.dl.sourceforge.jp/ipafonts/51867/IPAGTTC00303.zip"
dest="fonts"/>
---
> <get
src="http://jaist.dl.sourceforge.jp/ipafonts/51867/IPAGTTC00303.zip"
dest="fonts/IPAGTTC00303.zip"/>
I need little time to configure and test the new version.
Frank
Am 11.03.2015 um 13:05 schrieb Frank Brendel:
> Hi Karl,
>
> I am trying to build ManifoldCF from trunk but it doesn't work when I
> make 'ant make-deps'.
>
> BUILD FAILED
> /eurolog/software/mcf-trunk/build.xml:173: The following error
> occurred while executing this line:
> /eurolog/software/mcf-trunk/framework/build.xml:1586: Could not create
> almost empty JAR archive
> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar (No such
> file or directory))
>
> Sorry if this is a dumb mistake but I am totally new in building java
> applications from source.
> Btw. the same error occurs with release-2.0.2.
>
>
> Frank
>
>
>
>
> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>> Hi Frank,
>>
>> See CONNECTORS-1171.
>>
>> Karl
>>
>>
>> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel
>> <frank.brendel@eurolog.com <ma...@eurolog.com>> wrote:
>>
>> Hi Karl,
>>
>> unfortunately SharePoint doesn't provide a field 'url'.
>> And the problem persists even if I change the attribute name to,
>> lets say 'myurl'.
>>
>>
>> Frank
>>
>>
>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>> Ah, ok, so basically you are saying that the UI is broken. That
>>> should be easy to confirm.
>>>
>>> FWIW, there is already a metadata field from SharePoint called
>>> "url". You can manipulate it by adding a Metadata Adjuster to
>>> your job pipeline. So that might be a better way to do this.
>>>
>>> Karl
>>>
>>>
>>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
>>> <frank.brendel@eurolog.com <ma...@eurolog.com>>
>>> wrote:
>>>
>>> Hi Karl,
>>>
>>> after clicking on "Add Path Mapping" I'd expect either the
>>> accepted mapping or an error message.
>>> But I see only "No mappings specified".
>>> I've set org.apache.manifoldcf.connectors to DEBUG and I see
>>> lots of "SharePoint: List" but no "SharePoint: Path..."
>>> entries as mentioned below.
>>>
>>>
>>> Thanks
>>> Frank
>>>
>>>
>>>
>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>> Hi Frank,
>>>>
>>>> I am not sure what you mean by "nothing happens", but if
>>>> you turn on connector debugging, you will be able to see
>>>> what happens in the ManifoldCF log.
>>>>
>>>> >>>>>>
>>>> // Add the path metadata item into the mix, if enabled
>>>> String pathAttributeName = sDesc.getPathAttributeName();
>>>> if (pathAttributeName != null &&
>>>> pathAttributeName.length() > 0)
>>>> {
>>>> if (Logging.connectors.isDebugEnabled())
>>>> Logging.connectors.debug("SharePoint: Path attribute name
>>>> is '"+pathAttributeName+"'");
>>>> String pathString =
>>>> sDesc.getPathAttributeValue(documentIdentifier);
>>>> if (Logging.connectors.isDebugEnabled())
>>>> Logging.connectors.debug("SharePoint: Path attribute value
>>>> is '"+pathString+"'");
>>>> data.addField(pathAttributeName,pathString);
>>>> }
>>>> else
>>>> Logging.connectors.debug("SharePoint: Path attribute name
>>>> is null");
>>>>
>>>> <<<<<<
>>>>
>>>> Thanks,
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel
>>>> <frank.brendel@eurolog.com
>>>> <ma...@eurolog.com>> wrote:
>>>>
>>>> Hello,
>>>>
>>>> I cannot add a path mapping to the SharePoint connector.
>>>>
>>>> In the jobs metadata tab I've configured a metadata rule:
>>>>
>>>> Path match: /*
>>>> Action: include
>>>> All metadata: true
>>>>
>>>> Now I want a new attribute 'url' that contains the
>>>> complete URL to the SharePoint source and not only the
>>>> path.
>>>> Therefore I set the attribute name to 'url' and try to
>>>> add a path mapping
>>>>
>>>> Match regexp: (.*)
>>>> Replace string: http:\/\/host:port$(1)
>>>> <http:%5C/%5C/host:port$%281%29>
>>>>
>>>> But nothing happens. Why?
>>>>
>>>>
>>>> Thank you
>>>> Frank
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
Re: SharePoint Path Mapping not working
Posted by Frank Brendel <fr...@eurolog.com>.
To workaround this I removed the path mapping and renamed the path
attribute name to 'myurl'.
Then in metadata expressions tab (from metadata adjuster connection) I
added an expression for 'url' = http://host:port${myurl}.
Thanks,
Frank
Am 11.03.2015 um 14:56 schrieb Frank Brendel:
> Ok, adding a path mapping works now.
>
> But the mapping itself doesn't work as expected.
>
> If I configure
> Match regexp: (.*) ==>Replace string: http//host:port$(1)
>
> I get
> http//host:port/Site/SubSite/Documents/Document.dochttp//host:port
>
> The string before the $(1) is appended.
>
>
> Frank
>
>
>
> Am 11.03.2015 um 14:16 schrieb Frank Brendel:
>> Ok, this was a trick question ;-)
>> I cannot use a lib distribution when I build from trunk.
>>
>>
>>
>> Am 11.03.2015 um 14:06 schrieb Frank Brendel:
>>> Hi Karl,
>>>
>>> I followed the documentation here
>>> https://manifoldcf.apache.org/release/release-2.0.2/en_US/how-to-build-and-deploy.html#Building+the+framework+and+the+connectors+using+Apache+Ant
>>> There is no notice to download a lib distribution as in the README.
>>>
>>> Can I use the 2.0.2 version for that?
>>>
>>>
>>> # cat /etc/redhat-release; java -version; ant -version
>>> CentOS release 6.6 (Final)
>>> java version "1.8.0_40"
>>> Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
>>> Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
>>> Apache Ant version 1.7.1 compiled on August 24 2010
>>>
>>>
>>> Frank
>>>
>>> Am 11.03.2015 um 13:43 schrieb Karl Wright:
>>>> I am seeing none of these problems here.
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 8:42 AM, Karl Wright <daddywri@gmail.com
>>>> <ma...@gmail.com>> wrote:
>>>>
>>>> What version of ant are you using? Because it doesn't seem to be
>>>> the right one.
>>>>
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 8:41 AM, Karl Wright <daddywri@gmail.com
>>>> <ma...@gmail.com>> wrote:
>>>>
>>>> Did you run "ant make-core-deps" first? Or download the lib
>>>> distribution and unpack according to the instructions in the
>>>> README?
>>>>
>>>> Karl
>>>>
>>>> On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel
>>>> <frank.brendel@eurolog.com
>>>> <ma...@eurolog.com>> wrote:
>>>>
>>>> Hi Karl,
>>>>
>>>> I am trying to build ManifoldCF from trunk but it
>>>> doesn't work when I make 'ant make-deps'.
>>>>
>>>> BUILD FAILED
>>>> /eurolog/software/mcf-trunk/build.xml:173: The following
>>>> error occurred while executing this line:
>>>> /eurolog/software/mcf-trunk/framework/build.xml:1586:
>>>> Could not create almost empty JAR archive
>>>> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar
>>>> (No such file or directory))
>>>>
>>>> Sorry if this is a dumb mistake but I am totally new in
>>>> building java applications from source.
>>>> Btw. the same error occurs with release-2.0.2.
>>>>
>>>>
>>>> Frank
>>>>
>>>>
>>>>
>>>>
>>>> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>>>>> Hi Frank,
>>>>>
>>>>> See CONNECTORS-1171.
>>>>>
>>>>> Karl
>>>>>
>>>>>
>>>>> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel
>>>>> <frank.brendel@eurolog.com
>>>>> <ma...@eurolog.com>> wrote:
>>>>>
>>>>> Hi Karl,
>>>>>
>>>>> unfortunately SharePoint doesn't provide a field
>>>>> 'url'.
>>>>> And the problem persists even if I change the
>>>>> attribute name to, lets say 'myurl'.
>>>>>
>>>>>
>>>>> Frank
>>>>>
>>>>>
>>>>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>>>>> Ah, ok, so basically you are saying that the UI is
>>>>>> broken. That should be easy to confirm.
>>>>>>
>>>>>> FWIW, there is already a metadata field from
>>>>>> SharePoint called "url". You can manipulate it by
>>>>>> adding a Metadata Adjuster to your job pipeline.
>>>>>> So that might be a better way to do this.
>>>>>>
>>>>>> Karl
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
>>>>>> <frank.brendel@eurolog.com
>>>>>> <ma...@eurolog.com>> wrote:
>>>>>>
>>>>>> Hi Karl,
>>>>>>
>>>>>> after clicking on "Add Path Mapping" I'd
>>>>>> expect either the accepted mapping or an error
>>>>>> message.
>>>>>> But I see only "No mappings specified".
>>>>>> I've set org.apache.manifoldcf.connectors to
>>>>>> DEBUG and I see lots of "SharePoint: List" but
>>>>>> no "SharePoint: Path..." entries as mentioned
>>>>>> below.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>> Frank
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>>>>> Hi Frank,
>>>>>>>
>>>>>>> I am not sure what you mean by "nothing
>>>>>>> happens", but if you turn on connector
>>>>>>> debugging, you will be able to see what
>>>>>>> happens in the ManifoldCF log.
>>>>>>>
>>>>>>> >>>>>>
>>>>>>> // Add the path metadata item into the
>>>>>>> mix, if enabled
>>>>>>> String pathAttributeName =
>>>>>>> sDesc.getPathAttributeName();
>>>>>>> if (pathAttributeName != null &&
>>>>>>> pathAttributeName.length() > 0)
>>>>>>> {
>>>>>>> if (Logging.connectors.isDebugEnabled())
>>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>>> attribute name is '"+pathAttributeName+"'");
>>>>>>> String pathString =
>>>>>>> sDesc.getPathAttributeValue(documentIdentifier);
>>>>>>> if (Logging.connectors.isDebugEnabled())
>>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>>> attribute value is '"+pathString+"'");
>>>>>>> data.addField(pathAttributeName,pathString);
>>>>>>> }
>>>>>>> else
>>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>>> attribute name is null");
>>>>>>>
>>>>>>> <<<<<<
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Karl
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank
>>>>>>> Brendel <frank.brendel@eurolog.com
>>>>>>> <ma...@eurolog.com>> wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I cannot add a path mapping to the
>>>>>>> SharePoint connector.
>>>>>>>
>>>>>>> In the jobs metadata tab I've configured
>>>>>>> a metadata rule:
>>>>>>>
>>>>>>> Path match: /*
>>>>>>> Action: include
>>>>>>> All metadata: true
>>>>>>>
>>>>>>> Now I want a new attribute 'url' that
>>>>>>> contains the complete URL to the
>>>>>>> SharePoint source and not only the path.
>>>>>>> Therefore I set the attribute name to
>>>>>>> 'url' and try to add a path mapping
>>>>>>>
>>>>>>> Match regexp: (.*)
>>>>>>> Replace string: http:\/\/host:port$(1)
>>>>>>> <http:%5C/%5C/host:port$%281%29>
>>>>>>>
>>>>>>> But nothing happens. Why?
>>>>>>>
>>>>>>>
>>>>>>> Thank you
>>>>>>> Frank
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: SharePoint Path Mapping not working
Posted by Karl Wright <da...@gmail.com>.
The rule is fired, and substitution takes place, until it no longer matches
anything in the string. That sounds silly but is the legacy behavior.
Karl
On Wed, Mar 11, 2015 at 10:37 AM, Frank Brendel <fr...@eurolog.com>
wrote:
> Hi Karl,
>
> I am using now
>
> Match regexp: ^/(.*)$ ==>Replace string: http//host:port/$(1)
>
> and it works :-)
>
> You say that each match rule is applied repeatedly but I have only one
> rule.
> Why is it applied twice?
>
>
> Thank you
> Frank
>
>
>
> Am 11.03.2015 um 15:26 schrieb Karl Wright:
>
> Hi Frank,
>
> Each match rule is applied repeatedly, which is why you are seeing it
> add the prefix repeatedly. This is legacy behavior we can't really change
> at this point. What you will need to do is make your regular expression be
> more specific, so that it can only apply once. For instance, only apply
> the rule if the first character is a "/".
>
> Karl
>
>
>
>
> On Wed, Mar 11, 2015 at 9:56 AM, Frank Brendel <fr...@eurolog.com>
> wrote:
>
>> Ok, adding a path mapping works now.
>>
>> But the mapping itself doesn't work as expected.
>>
>> If I configure
>> Match regexp: (.*) ==>Replace string: http//host:port$(1)
>>
>> I get
>> http//host:port/Site/SubSite/Documents/Document.dochttp//host:port
>>
>> The string before the $(1) is appended.
>>
>>
>> Frank
>>
>>
>>
>> Am 11.03.2015 um 14:16 schrieb Frank Brendel:
>>
>>> Ok, this was a trick question ;-)
>>> I cannot use a lib distribution when I build from trunk.
>>>
>>>
>>>
>>> Am 11.03.2015 um 14:06 schrieb Frank Brendel:
>>>
>>>> Hi Karl,
>>>>
>>>> I followed the documentation here
>>>> https://manifoldcf.apache.org/release/release-2.0.2/en_US/how-to-build-and-deploy.html#Building+the+framework+and+the+connectors+using+Apache+Ant
>>>> There is no notice to download a lib distribution as in the README.
>>>>
>>>> Can I use the 2.0.2 version for that?
>>>>
>>>>
>>>> # cat /etc/redhat-release; java -version; ant -version
>>>> CentOS release 6.6 (Final)
>>>> java version "1.8.0_40"
>>>> Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
>>>> Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
>>>> Apache Ant version 1.7.1 compiled on August 24 2010
>>>>
>>>>
>>>> Frank
>>>>
>>>> Am 11.03.2015 um 13:43 schrieb Karl Wright:
>>>>
>>>>> I am seeing none of these problems here.
>>>>> Karl
>>>>>
>>>>>
>>>>> On Wed, Mar 11, 2015 at 8:42 AM, Karl Wright <daddywri@gmail.com
>>>>> <ma...@gmail.com>> wrote:
>>>>>
>>>>> What version of ant are you using? Because it doesn't seem to be
>>>>> the right one.
>>>>>
>>>>> Karl
>>>>>
>>>>>
>>>>> On Wed, Mar 11, 2015 at 8:41 AM, Karl Wright <daddywri@gmail.com
>>>>> <ma...@gmail.com>> wrote:
>>>>>
>>>>> Did you run "ant make-core-deps" first? Or download the lib
>>>>> distribution and unpack according to the instructions in the
>>>>> README?
>>>>>
>>>>> Karl
>>>>>
>>>>> On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel
>>>>> <frank.brendel@eurolog.com
>>>>> <ma...@eurolog.com>> wrote:
>>>>>
>>>>> Hi Karl,
>>>>>
>>>>> I am trying to build ManifoldCF from trunk but it
>>>>> doesn't work when I make 'ant make-deps'.
>>>>>
>>>>> BUILD FAILED
>>>>> /eurolog/software/mcf-trunk/build.xml:173: The following
>>>>> error occurred while executing this line:
>>>>> /eurolog/software/mcf-trunk/framework/build.xml:1586:
>>>>> Could not create almost empty JAR archive
>>>>>
>>>>> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar
>>>>> (No such file or directory))
>>>>>
>>>>> Sorry if this is a dumb mistake but I am totally new in
>>>>> building java applications from source.
>>>>> Btw. the same error occurs with release-2.0.2.
>>>>>
>>>>>
>>>>> Frank
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>>>>>
>>>>>> Hi Frank,
>>>>>>
>>>>>> See CONNECTORS-1171.
>>>>>>
>>>>>> Karl
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel
>>>>>> <frank.brendel@eurolog.com
>>>>>> <ma...@eurolog.com>> wrote:
>>>>>>
>>>>>> Hi Karl,
>>>>>>
>>>>>> unfortunately SharePoint doesn't provide a field
>>>>>> 'url'.
>>>>>> And the problem persists even if I change the
>>>>>> attribute name to, lets say 'myurl'.
>>>>>>
>>>>>>
>>>>>> Frank
>>>>>>
>>>>>>
>>>>>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>>>>>
>>>>>>> Ah, ok, so basically you are saying that the UI is
>>>>>>> broken. That should be easy to confirm.
>>>>>>>
>>>>>>> FWIW, there is already a metadata field from
>>>>>>> SharePoint called "url". You can manipulate it by
>>>>>>> adding a Metadata Adjuster to your job pipeline.
>>>>>>> So that might be a better way to do this.
>>>>>>>
>>>>>>> Karl
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
>>>>>>> <frank.brendel@eurolog.com
>>>>>>> <ma...@eurolog.com>> wrote:
>>>>>>>
>>>>>>> Hi Karl,
>>>>>>>
>>>>>>> after clicking on "Add Path Mapping" I'd
>>>>>>> expect either the accepted mapping or an error
>>>>>>> message.
>>>>>>> But I see only "No mappings specified".
>>>>>>> I've set org.apache.manifoldcf.connectors to
>>>>>>> DEBUG and I see lots of "SharePoint: List" but
>>>>>>> no "SharePoint: Path..." entries as mentioned
>>>>>>> below.
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>> Frank
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>>>>>
>>>>>>>> Hi Frank,
>>>>>>>>
>>>>>>>> I am not sure what you mean by "nothing
>>>>>>>> happens", but if you turn on connector
>>>>>>>> debugging, you will be able to see what
>>>>>>>> happens in the ManifoldCF log.
>>>>>>>>
>>>>>>>> >>>>>>
>>>>>>>> // Add the path metadata item into the
>>>>>>>> mix, if enabled
>>>>>>>> String pathAttributeName =
>>>>>>>> sDesc.getPathAttributeName();
>>>>>>>> if (pathAttributeName != null &&
>>>>>>>> pathAttributeName.length() > 0)
>>>>>>>> {
>>>>>>>> if (Logging.connectors.isDebugEnabled())
>>>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>>>> attribute name is '"+pathAttributeName+"'");
>>>>>>>> String pathString =
>>>>>>>> sDesc.getPathAttributeValue(documentIdentifier);
>>>>>>>> if (Logging.connectors.isDebugEnabled())
>>>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>>>> attribute value is '"+pathString+"'");
>>>>>>>> data.addField(pathAttributeName,pathString);
>>>>>>>> }
>>>>>>>> else
>>>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>>>> attribute name is null");
>>>>>>>>
>>>>>>>> <<<<<<
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Karl
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank
>>>>>>>> Brendel <frank.brendel@eurolog.com
>>>>>>>> <ma...@eurolog.com>> wrote:
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I cannot add a path mapping to the
>>>>>>>> SharePoint connector.
>>>>>>>>
>>>>>>>> In the jobs metadata tab I've configured
>>>>>>>> a metadata rule:
>>>>>>>>
>>>>>>>> Path match: /*
>>>>>>>> Action: include
>>>>>>>> All metadata: true
>>>>>>>>
>>>>>>>> Now I want a new attribute 'url' that
>>>>>>>> contains the complete URL to the
>>>>>>>> SharePoint source and not only the path.
>>>>>>>> Therefore I set the attribute name to
>>>>>>>> 'url' and try to add a path mapping
>>>>>>>>
>>>>>>>> Match regexp: (.*)
>>>>>>>> Replace string: http:\/\/host:port$(1)
>>>>>>>> <http:%5C/%5C/host:port$%281%29>
>>>>>>>> <http:%5C/%5C/host:port$%281%29>
>>>>>>>>
>>>>>>>> But nothing happens. Why?
>>>>>>>>
>>>>>>>>
>>>>>>>> Thank you
>>>>>>>> Frank
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
Re: SharePoint Path Mapping not working
Posted by Frank Brendel <fr...@eurolog.com>.
Hi Karl,
I am using now
Match regexp: ^/(.*)$ ==>Replace string: http//host:port/$(1)
and it works :-)
You say that each match rule is applied repeatedly but I have only one rule.
Why is it applied twice?
Thank you
Frank
Am 11.03.2015 um 15:26 schrieb Karl Wright:
> Hi Frank,
>
> Each match rule is applied repeatedly, which is why you are seeing it
> add the prefix repeatedly. This is legacy behavior we can't really
> change at this point. What you will need to do is make your regular
> expression be more specific, so that it can only apply once. For
> instance, only apply the rule if the first character is a "/".
>
> Karl
>
>
>
>
> On Wed, Mar 11, 2015 at 9:56 AM, Frank Brendel
> <frank.brendel@eurolog.com <ma...@eurolog.com>> wrote:
>
> Ok, adding a path mapping works now.
>
> But the mapping itself doesn't work as expected.
>
> If I configure
> Match regexp: (.*) ==>Replace string: http//host:port$(1)
>
> I get
> http//host:port/Site/SubSite/Documents/Document.dochttp//host:port
>
> The string before the $(1) is appended.
>
>
> Frank
>
>
>
> Am 11.03.2015 um 14:16 schrieb Frank Brendel:
>
> Ok, this was a trick question ;-)
> I cannot use a lib distribution when I build from trunk.
>
>
>
> Am 11.03.2015 um 14:06 schrieb Frank Brendel:
>
> Hi Karl,
>
> I followed the documentation here
> https://manifoldcf.apache.org/release/release-2.0.2/en_US/how-to-build-and-deploy.html#Building+the+framework+and+the+connectors+using+Apache+Ant
> There is no notice to download a lib distribution as in
> the README.
>
> Can I use the 2.0.2 version for that?
>
>
> # cat /etc/redhat-release; java -version; ant -version
> CentOS release 6.6 (Final)
> java version "1.8.0_40"
> Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
> Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed
> mode)
> Apache Ant version 1.7.1 compiled on August 24 2010
>
>
> Frank
>
> Am 11.03.2015 um 13:43 schrieb Karl Wright:
>
> I am seeing none of these problems here.
> Karl
>
>
> On Wed, Mar 11, 2015 at 8:42 AM, Karl Wright
> <daddywri@gmail.com <ma...@gmail.com>
> <mailto:daddywri@gmail.com
> <ma...@gmail.com>>> wrote:
>
> What version of ant are you using? Because it
> doesn't seem to be
> the right one.
>
> Karl
>
>
> On Wed, Mar 11, 2015 at 8:41 AM, Karl Wright
> <daddywri@gmail.com <ma...@gmail.com>
> <mailto:daddywri@gmail.com
> <ma...@gmail.com>>> wrote:
>
> Did you run "ant make-core-deps" first? Or
> download the lib
> distribution and unpack according to the
> instructions in the
> README?
>
> Karl
>
> On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel
> <frank.brendel@eurolog.com
> <ma...@eurolog.com>
> <mailto:frank.brendel@eurolog.com
> <ma...@eurolog.com>>> wrote:
>
> Hi Karl,
>
> I am trying to build ManifoldCF from trunk
> but it
> doesn't work when I make 'ant make-deps'.
>
> BUILD FAILED
> /eurolog/software/mcf-trunk/build.xml:173:
> The following
> error occurred while executing this line:
>
> /eurolog/software/mcf-trunk/framework/build.xml:1586:
> Could not create almost empty JAR archive
>
> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar
> (No such file or directory))
>
> Sorry if this is a dumb mistake but I am
> totally new in
> building java applications from source.
> Btw. the same error occurs with release-2.0.2.
>
>
> Frank
>
>
>
>
> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>
> Hi Frank,
>
> See CONNECTORS-1171.
>
> Karl
>
>
> On Wed, Mar 11, 2015 at 7:29 AM, Frank
> Brendel
> <frank.brendel@eurolog.com
> <ma...@eurolog.com>
> <mailto:frank.brendel@eurolog.com
> <ma...@eurolog.com>>> wrote:
>
> Hi Karl,
>
> unfortunately SharePoint doesn't
> provide a field 'url'.
> And the problem persists even if I
> change the
> attribute name to, lets say 'myurl'.
>
>
> Frank
>
>
> Am 11.03.2015 um 12:15 schrieb
> Karl Wright:
>
> Ah, ok, so basically you are
> saying that the UI is
> broken. That should be easy
> to confirm.
>
> FWIW, there is already a
> metadata field from
> SharePoint called "url". You
> can manipulate it by
> adding a Metadata Adjuster to
> your job pipeline. So that
> might be a better way to do this.
>
> Karl
>
>
> On Wed, Mar 11, 2015 at 6:49
> AM, Frank Brendel
> <frank.brendel@eurolog.com
> <ma...@eurolog.com>
>
> <mailto:frank.brendel@eurolog.com
> <ma...@eurolog.com>>> wrote:
>
> Hi Karl,
>
> after clicking on "Add
> Path Mapping" I'd
> expect either the accepted
> mapping or an error
> message.
> But I see only "No
> mappings specified".
> I've set
> org.apache.manifoldcf.connectors to
> DEBUG and I see lots of
> "SharePoint: List" but
> no "SharePoint: Path..."
> entries as mentioned
> below.
>
>
> Thanks
> Frank
>
>
>
> Am 11.03.2015 um 11:09
> schrieb Karl Wright:
>
> Hi Frank,
>
> I am not sure what you
> mean by "nothing
> happens", but if you
> turn on connector
> debugging, you will be
> able to see what
> happens in the
> ManifoldCF log.
>
> >>>>>>
> // Add the path
> metadata item into the
> mix, if enabled
> String pathAttributeName =
> sDesc.getPathAttributeName();
> if
> (pathAttributeName != null &&
> pathAttributeName.length() > 0)
> {
> if
> (Logging.connectors.isDebugEnabled())
> Logging.connectors.debug("SharePoint: Path
> attribute name is
> '"+pathAttributeName+"'");
> String pathString =
> sDesc.getPathAttributeValue(documentIdentifier);
> if
> (Logging.connectors.isDebugEnabled())
> Logging.connectors.debug("SharePoint: Path
> attribute value is
> '"+pathString+"'");
>
> data.addField(pathAttributeName,pathString);
> }
> else
> Logging.connectors.debug("SharePoint: Path
> attribute name is null");
>
> <<<<<<
>
> Thanks,
> Karl
>
>
> On Wed, Mar 11, 2015
> at 5:25 AM, Frank
> Brendel
> <frank.brendel@eurolog.com
> <ma...@eurolog.com>
>
> <mailto:frank.brendel@eurolog.com
> <ma...@eurolog.com>>> wrote:
>
> Hello,
>
> I cannot add a
> path mapping to the
> SharePoint connector.
>
> In the jobs
> metadata tab I've configured
> a metadata rule:
>
> Path match: /*
> Action: include
> All metadata: true
>
> Now I want a new
> attribute 'url' that
> contains the
> complete URL to the
> SharePoint source
> and not only the path.
> Therefore I set
> the attribute name to
> 'url' and try to
> add a path mapping
>
> Match regexp: (.*)
> Replace string:
> http:\/\/host:port$(1)
> <http:%5C/%5C/host:port$%281%29>
>
> But nothing
> happens. Why?
>
>
> Thank you
> Frank
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Re: SharePoint Path Mapping not working
Posted by Karl Wright <da...@gmail.com>.
Hi Frank,
Each match rule is applied repeatedly, which is why you are seeing it add
the prefix repeatedly. This is legacy behavior we can't really change at
this point. What you will need to do is make your regular expression be
more specific, so that it can only apply once. For instance, only apply
the rule if the first character is a "/".
Karl
On Wed, Mar 11, 2015 at 9:56 AM, Frank Brendel <fr...@eurolog.com>
wrote:
> Ok, adding a path mapping works now.
>
> But the mapping itself doesn't work as expected.
>
> If I configure
> Match regexp: (.*) ==>Replace string: http//host:port$(1)
>
> I get
> http//host:port/Site/SubSite/Documents/Document.dochttp//host:port
>
> The string before the $(1) is appended.
>
>
> Frank
>
>
>
> Am 11.03.2015 um 14:16 schrieb Frank Brendel:
>
>> Ok, this was a trick question ;-)
>> I cannot use a lib distribution when I build from trunk.
>>
>>
>>
>> Am 11.03.2015 um 14:06 schrieb Frank Brendel:
>>
>>> Hi Karl,
>>>
>>> I followed the documentation here https://manifoldcf.apache.org/
>>> release/release-2.0.2/en_US/how-to-build-and-deploy.html#
>>> Building+the+framework+and+the+connectors+using+Apache+Ant
>>> There is no notice to download a lib distribution as in the README.
>>>
>>> Can I use the 2.0.2 version for that?
>>>
>>>
>>> # cat /etc/redhat-release; java -version; ant -version
>>> CentOS release 6.6 (Final)
>>> java version "1.8.0_40"
>>> Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
>>> Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
>>> Apache Ant version 1.7.1 compiled on August 24 2010
>>>
>>>
>>> Frank
>>>
>>> Am 11.03.2015 um 13:43 schrieb Karl Wright:
>>>
>>>> I am seeing none of these problems here.
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 8:42 AM, Karl Wright <daddywri@gmail.com
>>>> <ma...@gmail.com>> wrote:
>>>>
>>>> What version of ant are you using? Because it doesn't seem to be
>>>> the right one.
>>>>
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 8:41 AM, Karl Wright <daddywri@gmail.com
>>>> <ma...@gmail.com>> wrote:
>>>>
>>>> Did you run "ant make-core-deps" first? Or download the lib
>>>> distribution and unpack according to the instructions in the
>>>> README?
>>>>
>>>> Karl
>>>>
>>>> On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel
>>>> <frank.brendel@eurolog.com
>>>> <ma...@eurolog.com>> wrote:
>>>>
>>>> Hi Karl,
>>>>
>>>> I am trying to build ManifoldCF from trunk but it
>>>> doesn't work when I make 'ant make-deps'.
>>>>
>>>> BUILD FAILED
>>>> /eurolog/software/mcf-trunk/build.xml:173: The following
>>>> error occurred while executing this line:
>>>> /eurolog/software/mcf-trunk/framework/build.xml:1586:
>>>> Could not create almost empty JAR archive
>>>> (/eurolog/software/mcf-trunk/framework/dist/example/start.
>>>> jar
>>>> (No such file or directory))
>>>>
>>>> Sorry if this is a dumb mistake but I am totally new in
>>>> building java applications from source.
>>>> Btw. the same error occurs with release-2.0.2.
>>>>
>>>>
>>>> Frank
>>>>
>>>>
>>>>
>>>>
>>>> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>>>>
>>>>> Hi Frank,
>>>>>
>>>>> See CONNECTORS-1171.
>>>>>
>>>>> Karl
>>>>>
>>>>>
>>>>> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel
>>>>> <frank.brendel@eurolog.com
>>>>> <ma...@eurolog.com>> wrote:
>>>>>
>>>>> Hi Karl,
>>>>>
>>>>> unfortunately SharePoint doesn't provide a field 'url'.
>>>>> And the problem persists even if I change the
>>>>> attribute name to, lets say 'myurl'.
>>>>>
>>>>>
>>>>> Frank
>>>>>
>>>>>
>>>>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>>>>
>>>>>> Ah, ok, so basically you are saying that the UI is
>>>>>> broken. That should be easy to confirm.
>>>>>>
>>>>>> FWIW, there is already a metadata field from
>>>>>> SharePoint called "url". You can manipulate it by
>>>>>> adding a Metadata Adjuster to your job pipeline.
>>>>>> So that might be a better way to do this.
>>>>>>
>>>>>> Karl
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
>>>>>> <frank.brendel@eurolog.com
>>>>>> <ma...@eurolog.com>> wrote:
>>>>>>
>>>>>> Hi Karl,
>>>>>>
>>>>>> after clicking on "Add Path Mapping" I'd
>>>>>> expect either the accepted mapping or an error
>>>>>> message.
>>>>>> But I see only "No mappings specified".
>>>>>> I've set org.apache.manifoldcf.connectors to
>>>>>> DEBUG and I see lots of "SharePoint: List" but
>>>>>> no "SharePoint: Path..." entries as mentioned
>>>>>> below.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>> Frank
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>>>>
>>>>>>> Hi Frank,
>>>>>>>
>>>>>>> I am not sure what you mean by "nothing
>>>>>>> happens", but if you turn on connector
>>>>>>> debugging, you will be able to see what
>>>>>>> happens in the ManifoldCF log.
>>>>>>>
>>>>>>> >>>>>>
>>>>>>> // Add the path metadata item into the
>>>>>>> mix, if enabled
>>>>>>> String pathAttributeName =
>>>>>>> sDesc.getPathAttributeName();
>>>>>>> if (pathAttributeName != null &&
>>>>>>> pathAttributeName.length() > 0)
>>>>>>> {
>>>>>>> if (Logging.connectors.isDebugEnabled())
>>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>>> attribute name is '"+pathAttributeName+"'");
>>>>>>> String pathString =
>>>>>>> sDesc.getPathAttributeValue(documentIdentifier);
>>>>>>> if (Logging.connectors.isDebugEnabled())
>>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>>> attribute value is '"+pathString+"'");
>>>>>>> data.addField(pathAttributeName,pathString);
>>>>>>> }
>>>>>>> else
>>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>>> attribute name is null");
>>>>>>>
>>>>>>> <<<<<<
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Karl
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank
>>>>>>> Brendel <frank.brendel@eurolog.com
>>>>>>> <ma...@eurolog.com>> wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I cannot add a path mapping to the
>>>>>>> SharePoint connector.
>>>>>>>
>>>>>>> In the jobs metadata tab I've configured
>>>>>>> a metadata rule:
>>>>>>>
>>>>>>> Path match: /*
>>>>>>> Action: include
>>>>>>> All metadata: true
>>>>>>>
>>>>>>> Now I want a new attribute 'url' that
>>>>>>> contains the complete URL to the
>>>>>>> SharePoint source and not only the path.
>>>>>>> Therefore I set the attribute name to
>>>>>>> 'url' and try to add a path mapping
>>>>>>>
>>>>>>> Match regexp: (.*)
>>>>>>> Replace string: http:\/\/host:port$(1)
>>>>>>> <http:%5C/%5C/host:port$%281%29>
>>>>>>>
>>>>>>> But nothing happens. Why?
>>>>>>>
>>>>>>>
>>>>>>> Thank you
>>>>>>> Frank
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: SharePoint Path Mapping not working
Posted by Frank Brendel <fr...@eurolog.com>.
Ok, adding a path mapping works now.
But the mapping itself doesn't work as expected.
If I configure
Match regexp: (.*) ==>Replace string: http//host:port$(1)
I get
http//host:port/Site/SubSite/Documents/Document.dochttp//host:port
The string before the $(1) is appended.
Frank
Am 11.03.2015 um 14:16 schrieb Frank Brendel:
> Ok, this was a trick question ;-)
> I cannot use a lib distribution when I build from trunk.
>
>
>
> Am 11.03.2015 um 14:06 schrieb Frank Brendel:
>> Hi Karl,
>>
>> I followed the documentation here
>> https://manifoldcf.apache.org/release/release-2.0.2/en_US/how-to-build-and-deploy.html#Building+the+framework+and+the+connectors+using+Apache+Ant
>> There is no notice to download a lib distribution as in the README.
>>
>> Can I use the 2.0.2 version for that?
>>
>>
>> # cat /etc/redhat-release; java -version; ant -version
>> CentOS release 6.6 (Final)
>> java version "1.8.0_40"
>> Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
>> Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
>> Apache Ant version 1.7.1 compiled on August 24 2010
>>
>>
>> Frank
>>
>> Am 11.03.2015 um 13:43 schrieb Karl Wright:
>>> I am seeing none of these problems here.
>>> Karl
>>>
>>>
>>> On Wed, Mar 11, 2015 at 8:42 AM, Karl Wright <daddywri@gmail.com
>>> <ma...@gmail.com>> wrote:
>>>
>>> What version of ant are you using? Because it doesn't seem to be
>>> the right one.
>>>
>>> Karl
>>>
>>>
>>> On Wed, Mar 11, 2015 at 8:41 AM, Karl Wright <daddywri@gmail.com
>>> <ma...@gmail.com>> wrote:
>>>
>>> Did you run "ant make-core-deps" first? Or download the lib
>>> distribution and unpack according to the instructions in the
>>> README?
>>>
>>> Karl
>>>
>>> On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel
>>> <frank.brendel@eurolog.com
>>> <ma...@eurolog.com>> wrote:
>>>
>>> Hi Karl,
>>>
>>> I am trying to build ManifoldCF from trunk but it
>>> doesn't work when I make 'ant make-deps'.
>>>
>>> BUILD FAILED
>>> /eurolog/software/mcf-trunk/build.xml:173: The following
>>> error occurred while executing this line:
>>> /eurolog/software/mcf-trunk/framework/build.xml:1586:
>>> Could not create almost empty JAR archive
>>> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar
>>> (No such file or directory))
>>>
>>> Sorry if this is a dumb mistake but I am totally new in
>>> building java applications from source.
>>> Btw. the same error occurs with release-2.0.2.
>>>
>>>
>>> Frank
>>>
>>>
>>>
>>>
>>> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>>>> Hi Frank,
>>>>
>>>> See CONNECTORS-1171.
>>>>
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel
>>>> <frank.brendel@eurolog.com
>>>> <ma...@eurolog.com>> wrote:
>>>>
>>>> Hi Karl,
>>>>
>>>> unfortunately SharePoint doesn't provide a field 'url'.
>>>> And the problem persists even if I change the
>>>> attribute name to, lets say 'myurl'.
>>>>
>>>>
>>>> Frank
>>>>
>>>>
>>>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>>>> Ah, ok, so basically you are saying that the UI is
>>>>> broken. That should be easy to confirm.
>>>>>
>>>>> FWIW, there is already a metadata field from
>>>>> SharePoint called "url". You can manipulate it by
>>>>> adding a Metadata Adjuster to your job pipeline.
>>>>> So that might be a better way to do this.
>>>>>
>>>>> Karl
>>>>>
>>>>>
>>>>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
>>>>> <frank.brendel@eurolog.com
>>>>> <ma...@eurolog.com>> wrote:
>>>>>
>>>>> Hi Karl,
>>>>>
>>>>> after clicking on "Add Path Mapping" I'd
>>>>> expect either the accepted mapping or an error
>>>>> message.
>>>>> But I see only "No mappings specified".
>>>>> I've set org.apache.manifoldcf.connectors to
>>>>> DEBUG and I see lots of "SharePoint: List" but
>>>>> no "SharePoint: Path..." entries as mentioned
>>>>> below.
>>>>>
>>>>>
>>>>> Thanks
>>>>> Frank
>>>>>
>>>>>
>>>>>
>>>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>>>> Hi Frank,
>>>>>>
>>>>>> I am not sure what you mean by "nothing
>>>>>> happens", but if you turn on connector
>>>>>> debugging, you will be able to see what
>>>>>> happens in the ManifoldCF log.
>>>>>>
>>>>>> >>>>>>
>>>>>> // Add the path metadata item into the
>>>>>> mix, if enabled
>>>>>> String pathAttributeName =
>>>>>> sDesc.getPathAttributeName();
>>>>>> if (pathAttributeName != null &&
>>>>>> pathAttributeName.length() > 0)
>>>>>> {
>>>>>> if (Logging.connectors.isDebugEnabled())
>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>> attribute name is '"+pathAttributeName+"'");
>>>>>> String pathString =
>>>>>> sDesc.getPathAttributeValue(documentIdentifier);
>>>>>> if (Logging.connectors.isDebugEnabled())
>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>> attribute value is '"+pathString+"'");
>>>>>> data.addField(pathAttributeName,pathString);
>>>>>> }
>>>>>> else
>>>>>> Logging.connectors.debug("SharePoint: Path
>>>>>> attribute name is null");
>>>>>>
>>>>>> <<<<<<
>>>>>>
>>>>>> Thanks,
>>>>>> Karl
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank
>>>>>> Brendel <frank.brendel@eurolog.com
>>>>>> <ma...@eurolog.com>> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I cannot add a path mapping to the
>>>>>> SharePoint connector.
>>>>>>
>>>>>> In the jobs metadata tab I've configured
>>>>>> a metadata rule:
>>>>>>
>>>>>> Path match: /*
>>>>>> Action: include
>>>>>> All metadata: true
>>>>>>
>>>>>> Now I want a new attribute 'url' that
>>>>>> contains the complete URL to the
>>>>>> SharePoint source and not only the path.
>>>>>> Therefore I set the attribute name to
>>>>>> 'url' and try to add a path mapping
>>>>>>
>>>>>> Match regexp: (.*)
>>>>>> Replace string: http:\/\/host:port$(1)
>>>>>> <http:%5C/%5C/host:port$%281%29>
>>>>>>
>>>>>> But nothing happens. Why?
>>>>>>
>>>>>>
>>>>>> Thank you
>>>>>> Frank
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
Re: SharePoint Path Mapping not working
Posted by Frank Brendel <fr...@eurolog.com>.
Ok, this was a trick question ;-)
I cannot use a lib distribution when I build from trunk.
Am 11.03.2015 um 14:06 schrieb Frank Brendel:
> Hi Karl,
>
> I followed the documentation here
> https://manifoldcf.apache.org/release/release-2.0.2/en_US/how-to-build-and-deploy.html#Building+the+framework+and+the+connectors+using+Apache+Ant
> There is no notice to download a lib distribution as in the README.
>
> Can I use the 2.0.2 version for that?
>
>
> # cat /etc/redhat-release; java -version; ant -version
> CentOS release 6.6 (Final)
> java version "1.8.0_40"
> Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
> Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
> Apache Ant version 1.7.1 compiled on August 24 2010
>
>
> Frank
>
> Am 11.03.2015 um 13:43 schrieb Karl Wright:
>> I am seeing none of these problems here.
>> Karl
>>
>>
>> On Wed, Mar 11, 2015 at 8:42 AM, Karl Wright <daddywri@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>> What version of ant are you using? Because it doesn't seem to be
>> the right one.
>>
>> Karl
>>
>>
>> On Wed, Mar 11, 2015 at 8:41 AM, Karl Wright <daddywri@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>> Did you run "ant make-core-deps" first? Or download the lib
>> distribution and unpack according to the instructions in the
>> README?
>>
>> Karl
>>
>> On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel
>> <frank.brendel@eurolog.com
>> <ma...@eurolog.com>> wrote:
>>
>> Hi Karl,
>>
>> I am trying to build ManifoldCF from trunk but it doesn't
>> work when I make 'ant make-deps'.
>>
>> BUILD FAILED
>> /eurolog/software/mcf-trunk/build.xml:173: The following
>> error occurred while executing this line:
>> /eurolog/software/mcf-trunk/framework/build.xml:1586:
>> Could not create almost empty JAR archive
>> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar
>> (No such file or directory))
>>
>> Sorry if this is a dumb mistake but I am totally new in
>> building java applications from source.
>> Btw. the same error occurs with release-2.0.2.
>>
>>
>> Frank
>>
>>
>>
>>
>> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>>> Hi Frank,
>>>
>>> See CONNECTORS-1171.
>>>
>>> Karl
>>>
>>>
>>> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel
>>> <frank.brendel@eurolog.com
>>> <ma...@eurolog.com>> wrote:
>>>
>>> Hi Karl,
>>>
>>> unfortunately SharePoint doesn't provide a field 'url'.
>>> And the problem persists even if I change the
>>> attribute name to, lets say 'myurl'.
>>>
>>>
>>> Frank
>>>
>>>
>>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>>> Ah, ok, so basically you are saying that the UI is
>>>> broken. That should be easy to confirm.
>>>>
>>>> FWIW, there is already a metadata field from
>>>> SharePoint called "url". You can manipulate it by
>>>> adding a Metadata Adjuster to your job pipeline.
>>>> So that might be a better way to do this.
>>>>
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
>>>> <frank.brendel@eurolog.com
>>>> <ma...@eurolog.com>> wrote:
>>>>
>>>> Hi Karl,
>>>>
>>>> after clicking on "Add Path Mapping" I'd expect
>>>> either the accepted mapping or an error message.
>>>> But I see only "No mappings specified".
>>>> I've set org.apache.manifoldcf.connectors to
>>>> DEBUG and I see lots of "SharePoint: List" but
>>>> no "SharePoint: Path..." entries as mentioned
>>>> below.
>>>>
>>>>
>>>> Thanks
>>>> Frank
>>>>
>>>>
>>>>
>>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>>> Hi Frank,
>>>>>
>>>>> I am not sure what you mean by "nothing
>>>>> happens", but if you turn on connector
>>>>> debugging, you will be able to see what
>>>>> happens in the ManifoldCF log.
>>>>>
>>>>> >>>>>>
>>>>> // Add the path metadata item into the
>>>>> mix, if enabled
>>>>> String pathAttributeName =
>>>>> sDesc.getPathAttributeName();
>>>>> if (pathAttributeName != null &&
>>>>> pathAttributeName.length() > 0)
>>>>> {
>>>>> if (Logging.connectors.isDebugEnabled())
>>>>> Logging.connectors.debug("SharePoint: Path
>>>>> attribute name is '"+pathAttributeName+"'");
>>>>> String pathString =
>>>>> sDesc.getPathAttributeValue(documentIdentifier);
>>>>> if (Logging.connectors.isDebugEnabled())
>>>>> Logging.connectors.debug("SharePoint: Path
>>>>> attribute value is '"+pathString+"'");
>>>>> data.addField(pathAttributeName,pathString);
>>>>> }
>>>>> else
>>>>> Logging.connectors.debug("SharePoint: Path
>>>>> attribute name is null");
>>>>>
>>>>> <<<<<<
>>>>>
>>>>> Thanks,
>>>>> Karl
>>>>>
>>>>>
>>>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel
>>>>> <frank.brendel@eurolog.com
>>>>> <ma...@eurolog.com>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I cannot add a path mapping to the
>>>>> SharePoint connector.
>>>>>
>>>>> In the jobs metadata tab I've configured a
>>>>> metadata rule:
>>>>>
>>>>> Path match: /*
>>>>> Action: include
>>>>> All metadata: true
>>>>>
>>>>> Now I want a new attribute 'url' that
>>>>> contains the complete URL to the
>>>>> SharePoint source and not only the path.
>>>>> Therefore I set the attribute name to
>>>>> 'url' and try to add a path mapping
>>>>>
>>>>> Match regexp: (.*)
>>>>> Replace string: http:\/\/host:port$(1)
>>>>> <http:%5C/%5C/host:port$%281%29>
>>>>>
>>>>> But nothing happens. Why?
>>>>>
>>>>>
>>>>> Thank you
>>>>> Frank
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
Re: SharePoint Path Mapping not working
Posted by Frank Brendel <fr...@eurolog.com>.
Hi Karl,
I followed the documentation here
https://manifoldcf.apache.org/release/release-2.0.2/en_US/how-to-build-and-deploy.html#Building+the+framework+and+the+connectors+using+Apache+Ant
There is no notice to download a lib distribution as in the README.
Can I use the 2.0.2 version for that?
# cat /etc/redhat-release; java -version; ant -version
CentOS release 6.6 (Final)
java version "1.8.0_40"
Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
Apache Ant version 1.7.1 compiled on August 24 2010
Frank
Am 11.03.2015 um 13:43 schrieb Karl Wright:
> I am seeing none of these problems here.
> Karl
>
>
> On Wed, Mar 11, 2015 at 8:42 AM, Karl Wright <daddywri@gmail.com
> <ma...@gmail.com>> wrote:
>
> What version of ant are you using? Because it doesn't seem to be
> the right one.
>
> Karl
>
>
> On Wed, Mar 11, 2015 at 8:41 AM, Karl Wright <daddywri@gmail.com
> <ma...@gmail.com>> wrote:
>
> Did you run "ant make-core-deps" first? Or download the lib
> distribution and unpack according to the instructions in the
> README?
>
> Karl
>
> On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel
> <frank.brendel@eurolog.com <ma...@eurolog.com>>
> wrote:
>
> Hi Karl,
>
> I am trying to build ManifoldCF from trunk but it doesn't
> work when I make 'ant make-deps'.
>
> BUILD FAILED
> /eurolog/software/mcf-trunk/build.xml:173: The following
> error occurred while executing this line:
> /eurolog/software/mcf-trunk/framework/build.xml:1586:
> Could not create almost empty JAR archive
> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar
> (No such file or directory))
>
> Sorry if this is a dumb mistake but I am totally new in
> building java applications from source.
> Btw. the same error occurs with release-2.0.2.
>
>
> Frank
>
>
>
>
> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>> Hi Frank,
>>
>> See CONNECTORS-1171.
>>
>> Karl
>>
>>
>> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel
>> <frank.brendel@eurolog.com
>> <ma...@eurolog.com>> wrote:
>>
>> Hi Karl,
>>
>> unfortunately SharePoint doesn't provide a field 'url'.
>> And the problem persists even if I change the
>> attribute name to, lets say 'myurl'.
>>
>>
>> Frank
>>
>>
>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>> Ah, ok, so basically you are saying that the UI is
>>> broken. That should be easy to confirm.
>>>
>>> FWIW, there is already a metadata field from
>>> SharePoint called "url". You can manipulate it by
>>> adding a Metadata Adjuster to your job pipeline. So
>>> that might be a better way to do this.
>>>
>>> Karl
>>>
>>>
>>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
>>> <frank.brendel@eurolog.com
>>> <ma...@eurolog.com>> wrote:
>>>
>>> Hi Karl,
>>>
>>> after clicking on "Add Path Mapping" I'd expect
>>> either the accepted mapping or an error message.
>>> But I see only "No mappings specified".
>>> I've set org.apache.manifoldcf.connectors to
>>> DEBUG and I see lots of "SharePoint: List" but
>>> no "SharePoint: Path..." entries as mentioned below.
>>>
>>>
>>> Thanks
>>> Frank
>>>
>>>
>>>
>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>> Hi Frank,
>>>>
>>>> I am not sure what you mean by "nothing
>>>> happens", but if you turn on connector
>>>> debugging, you will be able to see what happens
>>>> in the ManifoldCF log.
>>>>
>>>> >>>>>>
>>>> // Add the path metadata item into the mix,
>>>> if enabled
>>>> String pathAttributeName =
>>>> sDesc.getPathAttributeName();
>>>> if (pathAttributeName != null &&
>>>> pathAttributeName.length() > 0)
>>>> {
>>>> if (Logging.connectors.isDebugEnabled())
>>>> Logging.connectors.debug("SharePoint: Path
>>>> attribute name is '"+pathAttributeName+"'");
>>>> String pathString =
>>>> sDesc.getPathAttributeValue(documentIdentifier);
>>>> if (Logging.connectors.isDebugEnabled())
>>>> Logging.connectors.debug("SharePoint: Path
>>>> attribute value is '"+pathString+"'");
>>>> data.addField(pathAttributeName,pathString);
>>>> }
>>>> else
>>>> Logging.connectors.debug("SharePoint: Path
>>>> attribute name is null");
>>>>
>>>> <<<<<<
>>>>
>>>> Thanks,
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel
>>>> <frank.brendel@eurolog.com
>>>> <ma...@eurolog.com>> wrote:
>>>>
>>>> Hello,
>>>>
>>>> I cannot add a path mapping to the
>>>> SharePoint connector.
>>>>
>>>> In the jobs metadata tab I've configured a
>>>> metadata rule:
>>>>
>>>> Path match: /*
>>>> Action: include
>>>> All metadata: true
>>>>
>>>> Now I want a new attribute 'url' that
>>>> contains the complete URL to the SharePoint
>>>> source and not only the path.
>>>> Therefore I set the attribute name to 'url'
>>>> and try to add a path mapping
>>>>
>>>> Match regexp: (.*)
>>>> Replace string: http:\/\/host:port$(1)
>>>> <http:%5C/%5C/host:port$%281%29>
>>>>
>>>> But nothing happens. Why?
>>>>
>>>>
>>>> Thank you
>>>> Frank
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>
>
Re: SharePoint Path Mapping not working
Posted by Karl Wright <da...@gmail.com>.
I am seeing none of these problems here.
Karl
On Wed, Mar 11, 2015 at 8:42 AM, Karl Wright <da...@gmail.com> wrote:
> What version of ant are you using? Because it doesn't seem to be the
> right one.
>
> Karl
>
>
> On Wed, Mar 11, 2015 at 8:41 AM, Karl Wright <da...@gmail.com> wrote:
>
>> Did you run "ant make-core-deps" first? Or download the lib distribution
>> and unpack according to the instructions in the README?
>>
>> Karl
>>
>> On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel <frank.brendel@eurolog.com
>> > wrote:
>>
>>> Hi Karl,
>>>
>>> I am trying to build ManifoldCF from trunk but it doesn't work when I
>>> make 'ant make-deps'.
>>>
>>> BUILD FAILED
>>> /eurolog/software/mcf-trunk/build.xml:173: The following error occurred
>>> while executing this line:
>>> /eurolog/software/mcf-trunk/framework/build.xml:1586: Could not create
>>> almost empty JAR archive
>>> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar (No such file
>>> or directory))
>>>
>>> Sorry if this is a dumb mistake but I am totally new in building java
>>> applications from source.
>>> Btw. the same error occurs with release-2.0.2.
>>>
>>>
>>> Frank
>>>
>>>
>>>
>>>
>>> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>>>
>>> Hi Frank,
>>>
>>> See CONNECTORS-1171.
>>>
>>> Karl
>>>
>>>
>>> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel <
>>> frank.brendel@eurolog.com> wrote:
>>>
>>>> Hi Karl,
>>>>
>>>> unfortunately SharePoint doesn't provide a field 'url'.
>>>> And the problem persists even if I change the attribute name to, lets
>>>> say 'myurl'.
>>>>
>>>>
>>>> Frank
>>>>
>>>>
>>>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>>>
>>>> Ah, ok, so basically you are saying that the UI is broken. That should
>>>> be easy to confirm.
>>>>
>>>> FWIW, there is already a metadata field from SharePoint called
>>>> "url". You can manipulate it by adding a Metadata Adjuster to your job
>>>> pipeline. So that might be a better way to do this.
>>>>
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel <
>>>> frank.brendel@eurolog.com> wrote:
>>>>
>>>>> Hi Karl,
>>>>>
>>>>> after clicking on "Add Path Mapping" I'd expect either the accepted
>>>>> mapping or an error message.
>>>>> But I see only "No mappings specified".
>>>>> I've set org.apache.manifoldcf.connectors to DEBUG and I see lots of
>>>>> "SharePoint: List" but no "SharePoint: Path..." entries as mentioned below.
>>>>>
>>>>>
>>>>> Thanks
>>>>> Frank
>>>>>
>>>>>
>>>>>
>>>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>>>
>>>>> Hi Frank,
>>>>>
>>>>> I am not sure what you mean by "nothing happens", but if you turn on
>>>>> connector debugging, you will be able to see what happens in the ManifoldCF
>>>>> log.
>>>>>
>>>>> >>>>>>
>>>>> // Add the path metadata item into the mix, if enabled
>>>>> String pathAttributeName = sDesc.getPathAttributeName();
>>>>> if (pathAttributeName != null && pathAttributeName.length() > 0)
>>>>> {
>>>>> if (Logging.connectors.isDebugEnabled())
>>>>> Logging.connectors.debug("SharePoint: Path attribute name is
>>>>> '"+pathAttributeName+"'");
>>>>> String pathString =
>>>>> sDesc.getPathAttributeValue(documentIdentifier);
>>>>> if (Logging.connectors.isDebugEnabled())
>>>>> Logging.connectors.debug("SharePoint: Path attribute value is
>>>>> '"+pathString+"'");
>>>>> data.addField(pathAttributeName,pathString);
>>>>> }
>>>>> else
>>>>> Logging.connectors.debug("SharePoint: Path attribute name is
>>>>> null");
>>>>>
>>>>> <<<<<<
>>>>>
>>>>> Thanks,
>>>>> Karl
>>>>>
>>>>>
>>>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel <
>>>>> frank.brendel@eurolog.com> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I cannot add a path mapping to the SharePoint connector.
>>>>>>
>>>>>> In the jobs metadata tab I've configured a metadata rule:
>>>>>>
>>>>>> Path match: /*
>>>>>> Action: include
>>>>>> All metadata: true
>>>>>>
>>>>>> Now I want a new attribute 'url' that contains the complete URL to
>>>>>> the SharePoint source and not only the path.
>>>>>> Therefore I set the attribute name to 'url' and try to add a path
>>>>>> mapping
>>>>>>
>>>>>> Match regexp: (.*)
>>>>>> Replace string: http:\/\/host:port$(1)
>>>>>>
>>>>>> But nothing happens. Why?
>>>>>>
>>>>>>
>>>>>> Thank you
>>>>>> Frank
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>
Re: SharePoint Path Mapping not working
Posted by Karl Wright <da...@gmail.com>.
What version of ant are you using? Because it doesn't seem to be the right
one.
Karl
On Wed, Mar 11, 2015 at 8:41 AM, Karl Wright <da...@gmail.com> wrote:
> Did you run "ant make-core-deps" first? Or download the lib distribution
> and unpack according to the instructions in the README?
>
> Karl
>
> On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel <fr...@eurolog.com>
> wrote:
>
>> Hi Karl,
>>
>> I am trying to build ManifoldCF from trunk but it doesn't work when I
>> make 'ant make-deps'.
>>
>> BUILD FAILED
>> /eurolog/software/mcf-trunk/build.xml:173: The following error occurred
>> while executing this line:
>> /eurolog/software/mcf-trunk/framework/build.xml:1586: Could not create
>> almost empty JAR archive
>> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar (No such file
>> or directory))
>>
>> Sorry if this is a dumb mistake but I am totally new in building java
>> applications from source.
>> Btw. the same error occurs with release-2.0.2.
>>
>>
>> Frank
>>
>>
>>
>>
>> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>>
>> Hi Frank,
>>
>> See CONNECTORS-1171.
>>
>> Karl
>>
>>
>> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel <frank.brendel@eurolog.com
>> > wrote:
>>
>>> Hi Karl,
>>>
>>> unfortunately SharePoint doesn't provide a field 'url'.
>>> And the problem persists even if I change the attribute name to, lets
>>> say 'myurl'.
>>>
>>>
>>> Frank
>>>
>>>
>>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>>
>>> Ah, ok, so basically you are saying that the UI is broken. That should
>>> be easy to confirm.
>>>
>>> FWIW, there is already a metadata field from SharePoint called "url".
>>> You can manipulate it by adding a Metadata Adjuster to your job pipeline.
>>> So that might be a better way to do this.
>>>
>>> Karl
>>>
>>>
>>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel <
>>> frank.brendel@eurolog.com> wrote:
>>>
>>>> Hi Karl,
>>>>
>>>> after clicking on "Add Path Mapping" I'd expect either the accepted
>>>> mapping or an error message.
>>>> But I see only "No mappings specified".
>>>> I've set org.apache.manifoldcf.connectors to DEBUG and I see lots of
>>>> "SharePoint: List" but no "SharePoint: Path..." entries as mentioned below.
>>>>
>>>>
>>>> Thanks
>>>> Frank
>>>>
>>>>
>>>>
>>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>>
>>>> Hi Frank,
>>>>
>>>> I am not sure what you mean by "nothing happens", but if you turn on
>>>> connector debugging, you will be able to see what happens in the ManifoldCF
>>>> log.
>>>>
>>>> >>>>>>
>>>> // Add the path metadata item into the mix, if enabled
>>>> String pathAttributeName = sDesc.getPathAttributeName();
>>>> if (pathAttributeName != null && pathAttributeName.length() > 0)
>>>> {
>>>> if (Logging.connectors.isDebugEnabled())
>>>> Logging.connectors.debug("SharePoint: Path attribute name is
>>>> '"+pathAttributeName+"'");
>>>> String pathString =
>>>> sDesc.getPathAttributeValue(documentIdentifier);
>>>> if (Logging.connectors.isDebugEnabled())
>>>> Logging.connectors.debug("SharePoint: Path attribute value is
>>>> '"+pathString+"'");
>>>> data.addField(pathAttributeName,pathString);
>>>> }
>>>> else
>>>> Logging.connectors.debug("SharePoint: Path attribute name is
>>>> null");
>>>>
>>>> <<<<<<
>>>>
>>>> Thanks,
>>>> Karl
>>>>
>>>>
>>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel <
>>>> frank.brendel@eurolog.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I cannot add a path mapping to the SharePoint connector.
>>>>>
>>>>> In the jobs metadata tab I've configured a metadata rule:
>>>>>
>>>>> Path match: /*
>>>>> Action: include
>>>>> All metadata: true
>>>>>
>>>>> Now I want a new attribute 'url' that contains the complete URL to the
>>>>> SharePoint source and not only the path.
>>>>> Therefore I set the attribute name to 'url' and try to add a path
>>>>> mapping
>>>>>
>>>>> Match regexp: (.*)
>>>>> Replace string: http:\/\/host:port$(1)
>>>>>
>>>>> But nothing happens. Why?
>>>>>
>>>>>
>>>>> Thank you
>>>>> Frank
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
Re: SharePoint Path Mapping not working
Posted by Karl Wright <da...@gmail.com>.
Did you run "ant make-core-deps" first? Or download the lib distribution
and unpack according to the instructions in the README?
Karl
On Wed, Mar 11, 2015 at 8:05 AM, Frank Brendel <fr...@eurolog.com>
wrote:
> Hi Karl,
>
> I am trying to build ManifoldCF from trunk but it doesn't work when I make
> 'ant make-deps'.
>
> BUILD FAILED
> /eurolog/software/mcf-trunk/build.xml:173: The following error occurred
> while executing this line:
> /eurolog/software/mcf-trunk/framework/build.xml:1586: Could not create
> almost empty JAR archive
> (/eurolog/software/mcf-trunk/framework/dist/example/start.jar (No such file
> or directory))
>
> Sorry if this is a dumb mistake but I am totally new in building java
> applications from source.
> Btw. the same error occurs with release-2.0.2.
>
>
> Frank
>
>
>
>
> Am 11.03.2015 um 12:36 schrieb Karl Wright:
>
> Hi Frank,
>
> See CONNECTORS-1171.
>
> Karl
>
>
> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel <fr...@eurolog.com>
> wrote:
>
>> Hi Karl,
>>
>> unfortunately SharePoint doesn't provide a field 'url'.
>> And the problem persists even if I change the attribute name to, lets say
>> 'myurl'.
>>
>>
>> Frank
>>
>>
>> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>>
>> Ah, ok, so basically you are saying that the UI is broken. That should
>> be easy to confirm.
>>
>> FWIW, there is already a metadata field from SharePoint called "url".
>> You can manipulate it by adding a Metadata Adjuster to your job pipeline.
>> So that might be a better way to do this.
>>
>> Karl
>>
>>
>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel <frank.brendel@eurolog.com
>> > wrote:
>>
>>> Hi Karl,
>>>
>>> after clicking on "Add Path Mapping" I'd expect either the accepted
>>> mapping or an error message.
>>> But I see only "No mappings specified".
>>> I've set org.apache.manifoldcf.connectors to DEBUG and I see lots of
>>> "SharePoint: List" but no "SharePoint: Path..." entries as mentioned below.
>>>
>>>
>>> Thanks
>>> Frank
>>>
>>>
>>>
>>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>>
>>> Hi Frank,
>>>
>>> I am not sure what you mean by "nothing happens", but if you turn on
>>> connector debugging, you will be able to see what happens in the ManifoldCF
>>> log.
>>>
>>> >>>>>>
>>> // Add the path metadata item into the mix, if enabled
>>> String pathAttributeName = sDesc.getPathAttributeName();
>>> if (pathAttributeName != null && pathAttributeName.length() > 0)
>>> {
>>> if (Logging.connectors.isDebugEnabled())
>>> Logging.connectors.debug("SharePoint: Path attribute name is
>>> '"+pathAttributeName+"'");
>>> String pathString =
>>> sDesc.getPathAttributeValue(documentIdentifier);
>>> if (Logging.connectors.isDebugEnabled())
>>> Logging.connectors.debug("SharePoint: Path attribute value is
>>> '"+pathString+"'");
>>> data.addField(pathAttributeName,pathString);
>>> }
>>> else
>>> Logging.connectors.debug("SharePoint: Path attribute name is
>>> null");
>>>
>>> <<<<<<
>>>
>>> Thanks,
>>> Karl
>>>
>>>
>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel <
>>> frank.brendel@eurolog.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I cannot add a path mapping to the SharePoint connector.
>>>>
>>>> In the jobs metadata tab I've configured a metadata rule:
>>>>
>>>> Path match: /*
>>>> Action: include
>>>> All metadata: true
>>>>
>>>> Now I want a new attribute 'url' that contains the complete URL to the
>>>> SharePoint source and not only the path.
>>>> Therefore I set the attribute name to 'url' and try to add a path
>>>> mapping
>>>>
>>>> Match regexp: (.*)
>>>> Replace string: http:\/\/host:port$(1)
>>>>
>>>> But nothing happens. Why?
>>>>
>>>>
>>>> Thank you
>>>> Frank
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
Re: SharePoint Path Mapping not working
Posted by Frank Brendel <fr...@eurolog.com>.
Hi Karl,
I am trying to build ManifoldCF from trunk but it doesn't work when I
make 'ant make-deps'.
BUILD FAILED
/eurolog/software/mcf-trunk/build.xml:173: The following error occurred
while executing this line:
/eurolog/software/mcf-trunk/framework/build.xml:1586: Could not create
almost empty JAR archive
(/eurolog/software/mcf-trunk/framework/dist/example/start.jar (No such
file or directory))
Sorry if this is a dumb mistake but I am totally new in building java
applications from source.
Btw. the same error occurs with release-2.0.2.
Frank
Am 11.03.2015 um 12:36 schrieb Karl Wright:
> Hi Frank,
>
> See CONNECTORS-1171.
>
> Karl
>
>
> On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel
> <frank.brendel@eurolog.com <ma...@eurolog.com>> wrote:
>
> Hi Karl,
>
> unfortunately SharePoint doesn't provide a field 'url'.
> And the problem persists even if I change the attribute name to,
> lets say 'myurl'.
>
>
> Frank
>
>
> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>> Ah, ok, so basically you are saying that the UI is broken. That
>> should be easy to confirm.
>>
>> FWIW, there is already a metadata field from SharePoint called
>> "url". You can manipulate it by adding a Metadata Adjuster to
>> your job pipeline. So that might be a better way to do this.
>>
>> Karl
>>
>>
>> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
>> <frank.brendel@eurolog.com <ma...@eurolog.com>> wrote:
>>
>> Hi Karl,
>>
>> after clicking on "Add Path Mapping" I'd expect either the
>> accepted mapping or an error message.
>> But I see only "No mappings specified".
>> I've set org.apache.manifoldcf.connectors to DEBUG and I see
>> lots of "SharePoint: List" but no "SharePoint: Path..."
>> entries as mentioned below.
>>
>>
>> Thanks
>> Frank
>>
>>
>>
>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>> Hi Frank,
>>>
>>> I am not sure what you mean by "nothing happens", but if you
>>> turn on connector debugging, you will be able to see what
>>> happens in the ManifoldCF log.
>>>
>>> >>>>>>
>>> // Add the path metadata item into the mix, if enabled
>>> String pathAttributeName = sDesc.getPathAttributeName();
>>> if (pathAttributeName != null &&
>>> pathAttributeName.length() > 0)
>>> {
>>> if (Logging.connectors.isDebugEnabled())
>>> Logging.connectors.debug("SharePoint: Path attribute name is
>>> '"+pathAttributeName+"'");
>>> String pathString =
>>> sDesc.getPathAttributeValue(documentIdentifier);
>>> if (Logging.connectors.isDebugEnabled())
>>> Logging.connectors.debug("SharePoint: Path attribute value
>>> is '"+pathString+"'");
>>> data.addField(pathAttributeName,pathString);
>>> }
>>> else
>>> Logging.connectors.debug("SharePoint: Path attribute name is
>>> null");
>>>
>>> <<<<<<
>>>
>>> Thanks,
>>> Karl
>>>
>>>
>>> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel
>>> <frank.brendel@eurolog.com
>>> <ma...@eurolog.com>> wrote:
>>>
>>> Hello,
>>>
>>> I cannot add a path mapping to the SharePoint connector.
>>>
>>> In the jobs metadata tab I've configured a metadata rule:
>>>
>>> Path match: /*
>>> Action: include
>>> All metadata: true
>>>
>>> Now I want a new attribute 'url' that contains the
>>> complete URL to the SharePoint source and not only the path.
>>> Therefore I set the attribute name to 'url' and try to
>>> add a path mapping
>>>
>>> Match regexp: (.*)
>>> Replace string: http:\/\/host:port$(1)
>>> <http:%5C/%5C/host:port$%281%29>
>>>
>>> But nothing happens. Why?
>>>
>>>
>>> Thank you
>>> Frank
>>>
>>>
>>
>>
>>
>
>
>
Re: SharePoint Path Mapping not working
Posted by Karl Wright <da...@gmail.com>.
Hi Frank,
See CONNECTORS-1171.
Karl
On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel <fr...@eurolog.com>
wrote:
> Hi Karl,
>
> unfortunately SharePoint doesn't provide a field 'url'.
> And the problem persists even if I change the attribute name to, lets say
> 'myurl'.
>
>
> Frank
>
>
> Am 11.03.2015 um 12:15 schrieb Karl Wright:
>
> Ah, ok, so basically you are saying that the UI is broken. That should be
> easy to confirm.
>
> FWIW, there is already a metadata field from SharePoint called "url".
> You can manipulate it by adding a Metadata Adjuster to your job pipeline.
> So that might be a better way to do this.
>
> Karl
>
>
> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel <fr...@eurolog.com>
> wrote:
>
>> Hi Karl,
>>
>> after clicking on "Add Path Mapping" I'd expect either the accepted
>> mapping or an error message.
>> But I see only "No mappings specified".
>> I've set org.apache.manifoldcf.connectors to DEBUG and I see lots of
>> "SharePoint: List" but no "SharePoint: Path..." entries as mentioned below.
>>
>>
>> Thanks
>> Frank
>>
>>
>>
>> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>>
>> Hi Frank,
>>
>> I am not sure what you mean by "nothing happens", but if you turn on
>> connector debugging, you will be able to see what happens in the ManifoldCF
>> log.
>>
>> >>>>>>
>> // Add the path metadata item into the mix, if enabled
>> String pathAttributeName = sDesc.getPathAttributeName();
>> if (pathAttributeName != null && pathAttributeName.length() > 0)
>> {
>> if (Logging.connectors.isDebugEnabled())
>> Logging.connectors.debug("SharePoint: Path attribute name is
>> '"+pathAttributeName+"'");
>> String pathString = sDesc.getPathAttributeValue(documentIdentifier);
>> if (Logging.connectors.isDebugEnabled())
>> Logging.connectors.debug("SharePoint: Path attribute value is
>> '"+pathString+"'");
>> data.addField(pathAttributeName,pathString);
>> }
>> else
>> Logging.connectors.debug("SharePoint: Path attribute name is null");
>>
>> <<<<<<
>>
>> Thanks,
>> Karl
>>
>>
>> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel <frank.brendel@eurolog.com
>> > wrote:
>>
>>> Hello,
>>>
>>> I cannot add a path mapping to the SharePoint connector.
>>>
>>> In the jobs metadata tab I've configured a metadata rule:
>>>
>>> Path match: /*
>>> Action: include
>>> All metadata: true
>>>
>>> Now I want a new attribute 'url' that contains the complete URL to the
>>> SharePoint source and not only the path.
>>> Therefore I set the attribute name to 'url' and try to add a path mapping
>>>
>>> Match regexp: (.*)
>>> Replace string: http:\/\/host:port$(1)
>>>
>>> But nothing happens. Why?
>>>
>>>
>>> Thank you
>>> Frank
>>>
>>
>>
>>
>>
>
>
>
Re: SharePoint Path Mapping not working
Posted by Frank Brendel <fr...@eurolog.com>.
Hi Karl,
unfortunately SharePoint doesn't provide a field 'url'.
And the problem persists even if I change the attribute name to, lets
say 'myurl'.
Frank
Am 11.03.2015 um 12:15 schrieb Karl Wright:
> Ah, ok, so basically you are saying that the UI is broken. That
> should be easy to confirm.
>
> FWIW, there is already a metadata field from SharePoint called "url".
> You can manipulate it by adding a Metadata Adjuster to your job
> pipeline. So that might be a better way to do this.
>
> Karl
>
>
> On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
> <frank.brendel@eurolog.com <ma...@eurolog.com>> wrote:
>
> Hi Karl,
>
> after clicking on "Add Path Mapping" I'd expect either the
> accepted mapping or an error message.
> But I see only "No mappings specified".
> I've set org.apache.manifoldcf.connectors to DEBUG and I see lots
> of "SharePoint: List" but no "SharePoint: Path..." entries as
> mentioned below.
>
>
> Thanks
> Frank
>
>
>
> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>> Hi Frank,
>>
>> I am not sure what you mean by "nothing happens", but if you turn
>> on connector debugging, you will be able to see what happens in
>> the ManifoldCF log.
>>
>> >>>>>>
>> // Add the path metadata item into the mix, if enabled
>> String pathAttributeName = sDesc.getPathAttributeName();
>> if (pathAttributeName != null && pathAttributeName.length() > 0)
>> {
>> if (Logging.connectors.isDebugEnabled())
>> Logging.connectors.debug("SharePoint: Path attribute name is
>> '"+pathAttributeName+"'");
>> String pathString =
>> sDesc.getPathAttributeValue(documentIdentifier);
>> if (Logging.connectors.isDebugEnabled())
>> Logging.connectors.debug("SharePoint: Path attribute value is
>> '"+pathString+"'");
>> data.addField(pathAttributeName,pathString);
>> }
>> else
>> Logging.connectors.debug("SharePoint: Path attribute name
>> is null");
>>
>> <<<<<<
>>
>> Thanks,
>> Karl
>>
>>
>> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel
>> <frank.brendel@eurolog.com <ma...@eurolog.com>> wrote:
>>
>> Hello,
>>
>> I cannot add a path mapping to the SharePoint connector.
>>
>> In the jobs metadata tab I've configured a metadata rule:
>>
>> Path match: /*
>> Action: include
>> All metadata: true
>>
>> Now I want a new attribute 'url' that contains the complete
>> URL to the SharePoint source and not only the path.
>> Therefore I set the attribute name to 'url' and try to add a
>> path mapping
>>
>> Match regexp: (.*)
>> Replace string: http:\/\/host:port$(1)
>> <http:%5C/%5C/host:port$%281%29>
>>
>> But nothing happens. Why?
>>
>>
>> Thank you
>> Frank
>>
>>
>
>
>
Re: SharePoint Path Mapping not working
Posted by Karl Wright <da...@gmail.com>.
Ah, ok, so basically you are saying that the UI is broken. That should be
easy to confirm.
FWIW, there is already a metadata field from SharePoint called "url". You
can manipulate it by adding a Metadata Adjuster to your job pipeline. So
that might be a better way to do this.
Karl
On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel <fr...@eurolog.com>
wrote:
> Hi Karl,
>
> after clicking on "Add Path Mapping" I'd expect either the accepted
> mapping or an error message.
> But I see only "No mappings specified".
> I've set org.apache.manifoldcf.connectors to DEBUG and I see lots of
> "SharePoint: List" but no "SharePoint: Path..." entries as mentioned below.
>
>
> Thanks
> Frank
>
>
>
> Am 11.03.2015 um 11:09 schrieb Karl Wright:
>
> Hi Frank,
>
> I am not sure what you mean by "nothing happens", but if you turn on
> connector debugging, you will be able to see what happens in the ManifoldCF
> log.
>
> >>>>>>
> // Add the path metadata item into the mix, if enabled
> String pathAttributeName = sDesc.getPathAttributeName();
> if (pathAttributeName != null && pathAttributeName.length() > 0)
> {
> if (Logging.connectors.isDebugEnabled())
> Logging.connectors.debug("SharePoint: Path attribute name is
> '"+pathAttributeName+"'");
> String pathString = sDesc.getPathAttributeValue(documentIdentifier);
> if (Logging.connectors.isDebugEnabled())
> Logging.connectors.debug("SharePoint: Path attribute value is
> '"+pathString+"'");
> data.addField(pathAttributeName,pathString);
> }
> else
> Logging.connectors.debug("SharePoint: Path attribute name is null");
>
> <<<<<<
>
> Thanks,
> Karl
>
>
> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel <fr...@eurolog.com>
> wrote:
>
>> Hello,
>>
>> I cannot add a path mapping to the SharePoint connector.
>>
>> In the jobs metadata tab I've configured a metadata rule:
>>
>> Path match: /*
>> Action: include
>> All metadata: true
>>
>> Now I want a new attribute 'url' that contains the complete URL to the
>> SharePoint source and not only the path.
>> Therefore I set the attribute name to 'url' and try to add a path mapping
>>
>> Match regexp: (.*)
>> Replace string: http:\/\/host:port$(1)
>>
>> But nothing happens. Why?
>>
>>
>> Thank you
>> Frank
>>
>
>
>
>
Re: SharePoint Path Mapping not working
Posted by Frank Brendel <fr...@eurolog.com>.
Hi Karl,
after clicking on "Add Path Mapping" I'd expect either the accepted
mapping or an error message.
But I see only "No mappings specified".
I've set org.apache.manifoldcf.connectors to DEBUG and I see lots of
"SharePoint: List" but no "SharePoint: Path..." entries as mentioned below.
Thanks
Frank
Am 11.03.2015 um 11:09 schrieb Karl Wright:
> Hi Frank,
>
> I am not sure what you mean by "nothing happens", but if you turn on
> connector debugging, you will be able to see what happens in the
> ManifoldCF log.
>
> >>>>>>
> // Add the path metadata item into the mix, if enabled
> String pathAttributeName = sDesc.getPathAttributeName();
> if (pathAttributeName != null && pathAttributeName.length() > 0)
> {
> if (Logging.connectors.isDebugEnabled())
> Logging.connectors.debug("SharePoint: Path attribute name is
> '"+pathAttributeName+"'");
> String pathString = sDesc.getPathAttributeValue(documentIdentifier);
> if (Logging.connectors.isDebugEnabled())
> Logging.connectors.debug("SharePoint: Path attribute value is
> '"+pathString+"'");
> data.addField(pathAttributeName,pathString);
> }
> else
> Logging.connectors.debug("SharePoint: Path attribute name is null");
>
> <<<<<<
>
> Thanks,
> Karl
>
>
> On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel
> <frank.brendel@eurolog.com <ma...@eurolog.com>> wrote:
>
> Hello,
>
> I cannot add a path mapping to the SharePoint connector.
>
> In the jobs metadata tab I've configured a metadata rule:
>
> Path match: /*
> Action: include
> All metadata: true
>
> Now I want a new attribute 'url' that contains the complete URL to
> the SharePoint source and not only the path.
> Therefore I set the attribute name to 'url' and try to add a path
> mapping
>
> Match regexp: (.*)
> Replace string: http:\/\/host:port$(1)
>
> But nothing happens. Why?
>
>
> Thank you
> Frank
>
>
Re: SharePoint Path Mapping not working
Posted by Karl Wright <da...@gmail.com>.
Hi Frank,
I am not sure what you mean by "nothing happens", but if you turn on
connector debugging, you will be able to see what happens in the ManifoldCF
log.
>>>>>>
// Add the path metadata item into the mix, if enabled
String pathAttributeName = sDesc.getPathAttributeName();
if (pathAttributeName != null && pathAttributeName.length() > 0)
{
if (Logging.connectors.isDebugEnabled())
Logging.connectors.debug("SharePoint: Path attribute name is
'"+pathAttributeName+"'");
String pathString = sDesc.getPathAttributeValue(documentIdentifier);
if (Logging.connectors.isDebugEnabled())
Logging.connectors.debug("SharePoint: Path attribute value is
'"+pathString+"'");
data.addField(pathAttributeName,pathString);
}
else
Logging.connectors.debug("SharePoint: Path attribute name is null");
<<<<<<
Thanks,
Karl
On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel <fr...@eurolog.com>
wrote:
> Hello,
>
> I cannot add a path mapping to the SharePoint connector.
>
> In the jobs metadata tab I've configured a metadata rule:
>
> Path match: /*
> Action: include
> All metadata: true
>
> Now I want a new attribute 'url' that contains the complete URL to the
> SharePoint source and not only the path.
> Therefore I set the attribute name to 'url' and try to add a path mapping
>
> Match regexp: (.*)
> Replace string: http:\/\/host:port$(1)
>
> But nothing happens. Why?
>
>
> Thank you
> Frank
>