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 <[email protected]
<mailto:[email protected]>> 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 <[email protected]
<mailto:[email protected]>> 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
<[email protected]
<mailto:[email protected]>> 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
<[email protected]
<mailto:[email protected]>> 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
<[email protected]
<mailto:[email protected]>> 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 <[email protected]
<mailto:[email protected]>> 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
