from:"Karl Wright \(JIRA\)"

[jira] [Assigned] (CONNECTORS-55) Bundle database server with ManifoldCF packaged product

2011-08-12 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright reassigned CONNECTORS-55:
-

Assignee: Karl Wright

 Bundle database server with ManifoldCF packaged product
 ---

 Key: CONNECTORS-55
 URL: https://issues.apache.org/jira/browse/CONNECTORS-55
 Project: ManifoldCF
  Issue Type: Sub-task
  Components: Installers
Reporter: Jack Krupansky
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3


 The current requirement that the user install and deploy a PostgreSQL server 
 complicates the installation and deployment of LCF for the user. Installation 
 and deployment of LCF should be as simple as Solr itself. QuickStart is great 
 for the low-end and basic evaluation, but a comparable level of simplified 
 installation and deployment is still needed for full-blown, high-end 
 environments that need the full performance of a ProstgreSQL-class database 
 server. So, PostgreSQL should be bundled with the packaged release of LCF so 
 that installation and deployment of LCF will automatically install and deploy 
 a subset of the full PostgreSQL distribution that is sufficient for the needs 
 of LCF. Starting LCF, with or without the LCF UI, should automatically start 
 the database server. Shutting down LCF should also shutdown the database 
 server process.
 A typical use case would be for a non-developer who is comfortable with Solr 
 and simply wants to crawl documents from, for example, a SharePoint 
 repository and feed them into Solr. QuickStart should work well for the low 
 end or in the early stages of evaluation, but the user would prefer to 
 evaluate the real thing with something resembling a production crawl of 
 thousands of documents. Such a user might not be a hard-core developer or be 
 comfortable fiddling with a lot of software components simply to do one 
 conceptually simple operation.
 It should still be possible for the user to supply database server settings 
 to override the defaults, but the LCF package should have all of the 
 best-practice settings deemed appropriate for use with LCF.
 One downside is that installation and deployment will be platform-specific 
 since there are multiple processes and PostgreSQL itself requires a 
 platform-specific installation.
 This proposal presumes that PostgreSQL is the best option for the foreseeable 
 future, but nothing here is intended to preclude support for other database 
 servers in futures releases.
 This proposal should not have any impact on QuickStart packaging or 
 deployment.
 Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-60) Agent process should be started automatically

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Wright resolved CONNECTORS-60.
---

Resolution: Fixed
Fix Version/s: ManifoldCF 0.1
ManifoldCF 0.2
ManifoldCF 0.3

Agent process should be started automatically
-

Key: CONNECTORS-60
URL: https://issues.apache.org/jira/browse/CONNECTORS-60
Project: ManifoldCF
Issue Type: Sub-task
Components: Documentation
Reporter: Jack Krupansky
Assignee: Karl Wright
Priority: Minor
Fix For: ManifoldCF 0.3, ManifoldCF 0.2, ManifoldCF 0.1

LCF as it exists today is a bit too complex to run for an average user,
especially with a separate agent process for crawling. LCF should be as easy
to run as Solr is today. QuickStart is a good move in this direction, but the
same user-visible simplicity is needed for full LCF. The separate agent
process is a reasonable design for execution, but a little too cumbersome for
the average user to manage.
Unfortunately, it is expected that starting up a multi-process application
will require platform-specific scripting.
Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue.
KDW - this functionality is already present; however the documentation is not
adequate to help people figure out how to do it. So I'm moving this to
Documentation and treating it as a doc bug.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CONNECTORS-60) Agent process should be started automatically

2011-08-12 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright reassigned CONNECTORS-60:
-

Assignee: Karl Wright

 Agent process should be started automatically
 -

 Key: CONNECTORS-60
 URL: https://issues.apache.org/jira/browse/CONNECTORS-60
 Project: ManifoldCF
  Issue Type: Sub-task
  Components: Documentation
Reporter: Jack Krupansky
Assignee: Karl Wright
Priority: Minor
 Fix For: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3


 LCF as it exists today is a bit too complex to run for an average user, 
 especially with a separate agent process for crawling. LCF should be as easy 
 to run as Solr is today. QuickStart is a good move in this direction, but the 
 same user-visible simplicity is needed for full LCF. The separate agent 
 process is a reasonable design for execution, but a little too cumbersome for 
 the average user to manage.
 Unfortunately, it is expected that starting up a multi-process application 
 will require platform-specific scripting.
 Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue.
 KDW - this functionality is already present; however the documentation is not 
 adequate to help people figure out how to do it.  So I'm moving this to 
 Documentation and treating it as a doc bug.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-60) Agent process should be started automatically

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084067#comment-13084067
]

Karl Wright commented on CONNECTORS-60:
---

The Quick Start definitely meets the requirements listed for this task, so I'm
closing it.

Agent process should be started automatically
-

Key: CONNECTORS-60
URL: https://issues.apache.org/jira/browse/CONNECTORS-60
Project: ManifoldCF
Issue Type: Sub-task
Components: Documentation
Reporter: Jack Krupansky
Priority: Minor
Fix For: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-58) ManifoldCF scripting language, executed via the API, plus example jobs for file system and web crawl

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Wright updated CONNECTORS-58:
--

Component/s: Scripting client

Adding a new ticket category for scripting client.

ManifoldCF scripting language, executed via the API, plus example jobs for
file system and web crawl
---

Key: CONNECTORS-58
URL: https://issues.apache.org/jira/browse/CONNECTORS-58
Project: ManifoldCF
Issue Type: Sub-task
Components: Examples, Scripting client
Reporter: Jack Krupansky
Priority: Minor

Creating a basic connection setup to do a relatively simple crawl for a file
system or web can be a daunting task for someone new to LCF. So, it would be
nice to have a scripting file that supports an abbreviated API (subset of the
full API discussed in CONNECTORS-56) sufficient to create a default set of
connections and example jobs that the new user can choose from.
Beyond this initial need, this script format might be a useful form to dump
all of the connections and jobs in the LCF database in a form that can be
used to recreate an LCF configuration. Kind of a dump and reload
capability. That in fact might be how the initial example script gets created.
Those are two distinct use cases, but could utilize the same feature.
The example script could have example jobs to crawl a subdirectory of LCF,
crawl the LCF wiki, etc.
There could be more than one script. There might be example scripts for each
form of connector.
This capability should be available for both QuickStart and the general
release of LCF.
As just one possibility, the script format might be a sequence of JSON
expressions, each with an initial string analogous to a servlet path to
specify the operation to be performed, followed by the JSON form of the
connection or job or other LCF object. Or, some other format might be more
suitable.
Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-61) Support bundling of LCF with an app

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084074#comment-13084074
]

Karl Wright commented on CONNECTORS-61:
---

The current status of this ticket is that it is stalled. What is needed, in my
view, to complete it is the following:

(1) Make the jetty-runner class include specific methods for programmatically
starting and stopping the ManifoldCF quick start from within an enclosing
process, and
(2) Document those methods in how to build and deploy.

Support bundling of LCF with an app
---

Key: CONNECTORS-61
URL: https://issues.apache.org/jira/browse/CONNECTORS-61
Project: ManifoldCF
Issue Type: Sub-task
Components: Documentation, Framework crawler agent
Affects Versions: ManifoldCF 0.3
Reporter: Jack Krupansky
Priority: Minor

It should be possible for an application developer to bundle LCF with an
application to facilitate installation and deployment of the application in
conjunction with LCF. This may (or may not) be as simple as providing
appropriate jar files and documentation for how to use them, but there may be
other components or scripts needed.
There are two options: 1) include the LCF UI along with the other LCF
processes, and 2) exclude the LCF UI and include only the other processes
that can be controlled via the full API.
The database server would be included.
The web app server would be optional since the application may have its own
choice of web app server.
One use case is bundling LCF with Solr or a Solr-based application.
Note: This issue is part of Phase 2 of the CONNECTORS-50 umbrella issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-12 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084101#comment-13084101
 ] 

Karl Wright commented on CONNECTORS-224:


checkMimeTypeIndexable and checkFileIndexable will only be called from certain 
connectors, which are in a position to prefilter content.  Other connectors 
will not be able to use these.

For example, the Web connector calls checkMimeTypeIndexable and the JCIFS 
connector calls checkFileIndexable.  Hope this helps.



 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, 
 oss-mfc-beta.patch, oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-61) Support bundling of LCF with an app

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084112#comment-13084112
]

Karl Wright commented on CONNECTORS-61:
---

r1157095 for the jetty-runner changes.

Support bundling of LCF with an app
---

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-12 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084116#comment-13084116
 ] 

Karl Wright commented on CONNECTORS-224:


Checked in the latest patch, and I'll try to evaluate it at first available 
opportunity.


 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, 
 oss-mfc-beta.patch, oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-61) Support bundling of LCF with an app

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Wright resolved CONNECTORS-61.
---

Resolution: Fixed
Fix Version/s: ManifoldCF next

Support bundling of LCF with an app
---

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-50) Proposal for initial two releases of LCF, including packaged product and full API

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Wright resolved CONNECTORS-50.
---

Resolution: Fixed
Fix Version/s: ManifoldCF 0.3
Assignee: Karl Wright

Resolved, leaving scripting language request open as a separate ticket.

Proposal for initial two releases of LCF, including packaged product and full
API
-

Key: CONNECTORS-50
URL: https://issues.apache.org/jira/browse/CONNECTORS-50
Project: ManifoldCF
Issue Type: New Feature
Reporter: Jack Krupansky
Assignee: Karl Wright
Fix For: ManifoldCF 0.3

Currently, LCF has a relatively high-bar for evaluation and use, requiring
developer expertise. Also, although LCF has a comprehensive UI, it is not
currently packaged for use as a crawling engine for advanced applications.
A small set of individual feature requests are needed to address these
issues. They are summarized briefly to show how they fit together for two
initial releases of LCF, but will be broken out into individual LCF Jira
issues.
Goals:
1. LCF as a standalone, downloadable, usable-out-of-the-box product (much as
Solr is today)
2. LCF as a toolkit for developers needing customized crawling and repository
access
3. An API-based crawling engine that can be integrated with applications (as
Aperture is today)
Larger goals:
1. Make it very easy for users to evaluate LCF.
2. Make it very easy for developers to customize LCF.
3. Make it very easy for appplications to fully manage and control LCF in
operation.
Two phases:
1) Standalone, packaged app that is super-easy to evaluate and deploy. Call
it LCF 0.5.
2) API-based crawling engine for applications for which the UI might not be
appropriate. Call it LCF 1.0.
Phase 1
---
LCF 0.5 right out of the box would interface loosely with Solr 1.4 or later.
It would contain roughly the features that are currently in place or
currently underway, plus a little more.
Specifically, LCF 0.5 would contain these additional capabilities:
1. Plug-in architecture for connectors (CONNECTORS-40 - DONE)
2. Packaged app ready to run with embedded Jetty app server (CONNECTORS-59)
3. Bundled with database - PostgreSQL or derby - ready to run without
additional manual setup (CONNECTORS-55)
4. Mini-API to initially configure default connections and example jobs for
file system and web crawl (CONNECTORS-58)
5. Agent process started automatically (CONNECTORS-60)
6. Solr output connector option to commit at end of job, by default
(CONNECTORS-57)
Installation and basic evaluation of LCF would be essentially as simple as
Solr is today. The example
connections and jobs would permit the user to initiate example crawls of a
file system example
directory and an example web on the LCF web site with just a couple of clicks
(as opposed to the
detailed manual setup required today to create repository and output
connections and jobs.
It is worth considering whether the SharePoint connector could also be
included as part of the default package.
Users could then add additional connectors and repositories and jobs as
desired.
Timeframe for release? Level of effort?
Phase 2
---
The essence of Phase 2 is that LCF would be split to allow direct, full API
access to LCF as a
crawling engine, in additional to the full LCF UI. Call this LCF 1.0.
Specifically, LCF 1.0 would contain these additional capabilities:
1. Full API for LCF as a crawling engine (CONNECTORS-56)
2. LCF can be bundled within an app (CONNECTORS-61)
3. LCF event and activity notification for full control by an application
(CONNECTORS-41)
Overall, LCF will offer roughly the same crawling capabilities as with LCF
0.5, plus whatever bug
fixes and minor enhancements might also be added.
Timeframe for release? Level of effort?
-
Issues:
- Can we package PostgreSQL with LCF so LCF can set it up?
- Or do we need Derby for that purpose?
- Managing multiple processes (UI, database, agent, app processes)
- What exactly would the API look like? (URL, XML, JSON, YAML?)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-50) Proposal for initial two releases of LCF, including packaged product and full API

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084131#comment-13084131
]

Karl Wright commented on CONNECTORS-50:
---

I'm going to resolve this ticket, since the planning part is now meaningless,
and the only thing that remains is a scripting language, for which there is a
separate ticket.

Proposal for initial two releases of LCF, including packaged product and full
API
-

Key: CONNECTORS-50
URL: https://issues.apache.org/jira/browse/CONNECTORS-50
Project: ManifoldCF
Issue Type: New Feature
Reporter: Jack Krupansky
Fix For: ManifoldCF 0.3

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-34) eRoom authority and connector

2011-08-12 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright updated CONNECTORS-34:
--

Component/s: eRoom connector

 eRoom authority and connector
 -

 Key: CONNECTORS-34
 URL: https://issues.apache.org/jira/browse/CONNECTORS-34
 Project: ManifoldCF
  Issue Type: New Feature
  Components: eRoom connector
Reporter: Karl Wright

 eRoom has a SOAP API which looks like it has enough power to perhaps 
 implement a connector and an authority.  The eRoom API url is here (and yes, 
 it is a chinese url, but is legit):
 https://eroom.abraxas.ch/eroomHelp/en/API_Help/Api.htm#home_api.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-54) A Filesystem output connector would be useful and would allow more complete unit tests

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084140#comment-13084140
]

Karl Wright commented on CONNECTORS-54:
---

ManifoldCF in Action required a simple file-based repository to be written, and
an output connector to that repository also. It's not so simple because the
metadata and acl information also needs to go into the file system for this to
be useful. I'm therefore going to close this ticket since I can't think of any
realistic use for the proposed connector other than testing.

A Filesystem output connector would be useful and would allow more complete
unit tests
---

Key: CONNECTORS-54
URL: https://issues.apache.org/jira/browse/CONNECTORS-54
Project: ManifoldCF
Issue Type: Improvement
Reporter: Karl Wright
Fix For: ManifoldCF 0.3

Right now, the unit tests are limited because there is no way to check that
the indexed files actually do get indexed. The addition of a filesystem
output connector would allow more complete tests to be constructed. In
addition, such a connector might well be useful in its own right.
The connector would need to convert URI's into relative file paths, but other
than that there's really nothing very tricky about it. Configuration
information is minimal; just the root path of the output is all that's needed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-54) A Filesystem output connector would be useful and would allow more complete unit tests

2011-08-12 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-54.
---

   Resolution: Won't Fix
Fix Version/s: ManifoldCF 0.3

 A Filesystem output connector would be useful and would allow more complete 
 unit  tests
 ---

 Key: CONNECTORS-54
 URL: https://issues.apache.org/jira/browse/CONNECTORS-54
 Project: ManifoldCF
  Issue Type: Improvement
Reporter: Karl Wright
 Fix For: ManifoldCF 0.3


 Right now, the unit tests are limited because there is no way to check that 
 the indexed files actually do get indexed.  The addition of a filesystem 
 output connector would allow more complete tests to be constructed.  In 
 addition, such a connector might well be useful in its own right.
 The connector would need to convert URI's into relative file paths, but other 
 than that there's really nothing very tricky about it.  Configuration 
 information is minimal; just the root path of the output is all that's needed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-94) fix common localization traps

2011-08-12 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright updated CONNECTORS-94:
--

Component/s: Framework core

 fix common localization traps
 -

 Key: CONNECTORS-94
 URL: https://issues.apache.org/jira/browse/CONNECTORS-94
 Project: ManifoldCF
  Issue Type: Task
  Components: Framework core
Reporter: Robert Muir

 Searching thru the LCF code, i found several uses of the following that 
 appear to be potentially dangerous:
 * getBytes() with no encoding: this is dangerous as the encoding is 
 completely unspecified. In most places this should likely mean UTF-8
 * getBytes(utf-8): this is mostly a nitpick, but this alias is not 
 guaranteed to exist (see Charset docs). I suggest changing these all to 
 UTF-8
   
 * String.toLowerCase()/String.toUpperCase() with no specified Locale, where 
 it appears the text is not used solely for display, but instead for 'caseless 
 matching'. I suggest changing these to use either the root Locale: new 
 Locale() or even easier, Locale.ENGLISH. This way ACF does not have 
 surprising behavior on say a Turkish computer.
 I can contribute a patch to address these.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-94) fix common localization traps

2011-08-12 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084142#comment-13084142
 ] 

Karl Wright commented on CONNECTORS-94:
---

Has there been any update to this ticket?


 fix common localization traps
 -

 Key: CONNECTORS-94
 URL: https://issues.apache.org/jira/browse/CONNECTORS-94
 Project: ManifoldCF
  Issue Type: Task
  Components: Framework core
Reporter: Robert Muir

 Searching thru the LCF code, i found several uses of the following that 
 appear to be potentially dangerous:
 * getBytes() with no encoding: this is dangerous as the encoding is 
 completely unspecified. In most places this should likely mean UTF-8
 * getBytes(utf-8): this is mostly a nitpick, but this alias is not 
 guaranteed to exist (see Charset docs). I suggest changing these all to 
 UTF-8
   
 * String.toLowerCase()/String.toUpperCase() with no specified Locale, where 
 it appears the text is not used solely for display, but instead for 'caseless 
 matching'. I suggest changing these to use either the root Locale: new 
 Locale() or even easier, Locale.ENGLISH. This way ACF does not have 
 surprising behavior on say a Turkish computer.
 I can contribute a patch to address these.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CONNECTORS-94) fix common localization traps

2011-08-12 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright reassigned CONNECTORS-94:
-

Assignee: Robert Muir

 fix common localization traps
 -

 Key: CONNECTORS-94
 URL: https://issues.apache.org/jira/browse/CONNECTORS-94
 Project: ManifoldCF
  Issue Type: Task
  Components: Framework core
Reporter: Robert Muir
Assignee: Robert Muir

 Searching thru the LCF code, i found several uses of the following that 
 appear to be potentially dangerous:
 * getBytes() with no encoding: this is dangerous as the encoding is 
 completely unspecified. In most places this should likely mean UTF-8
 * getBytes(utf-8): this is mostly a nitpick, but this alias is not 
 guaranteed to exist (see Charset docs). I suggest changing these all to 
 UTF-8
   
 * String.toLowerCase()/String.toUpperCase() with no specified Locale, where 
 it appears the text is not used solely for display, but instead for 'caseless 
 matching'. I suggest changing these to use either the root Locale: new 
 Locale() or even easier, Locale.ENGLISH. This way ACF does not have 
 surprising behavior on say a Turkish computer.
 I can contribute a patch to address these.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-92) Move from ant to maven or other build system with decent library management

2011-08-12 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-92.
---

   Resolution: Fixed
Fix Version/s: ManifoldCF 0.3

 Move from ant to maven or other build system with decent library management
 ---

 Key: CONNECTORS-92
 URL: https://issues.apache.org/jira/browse/CONNECTORS-92
 Project: ManifoldCF
  Issue Type: Wish
  Components: Build
Reporter: Jettro Coenradie
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: Screen shot 2010-08-23 at 16.31.07.png, 
 maven-poms-including-start-jar.patch, 
 maven-poms-problem-starting-jetty-and-derby.patch, maven-start-jar.patch, 
 move-to-maven-acf-framework.patch, patch-connectors.zip


 I am looking at the current project structure. If we want to make another 
 build tool available I think we need to change the directory structure. I 
 tried to place a suggestion in an image. Can you please have a look at it. If 
 we agree that this is a good way to go, than I will continue to work on a 
 patch. Which might be a bit hard with all these changing directories, but 
 I'll do my best to at least get an idea whether it would be working.
 So I have three questions:
 - Do you want to move to maven or put maven next to ant?
 - Do you prefer another build mechanism [ant with ivy, gradle, maven3]
 - Do you have an idea about the amount of scripts that need to be changed if 
 we change the project structure
 The image of a possible project layout (that is based on the maven standards) 
 is attached to the issue

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-92) Move from ant to maven or other build system with decent library management

2011-08-12 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084146#comment-13084146
 ] 

Karl Wright commented on CONNECTORS-92:
---

We now have a maven build system, in addition to ant, that was contributed 
elsewhere, so I'm closing this ticket.


 Move from ant to maven or other build system with decent library management
 ---

 Key: CONNECTORS-92
 URL: https://issues.apache.org/jira/browse/CONNECTORS-92
 Project: ManifoldCF
  Issue Type: Wish
  Components: Build
Reporter: Jettro Coenradie
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: Screen shot 2010-08-23 at 16.31.07.png, 
 maven-poms-including-start-jar.patch, 
 maven-poms-problem-starting-jetty-and-derby.patch, maven-start-jar.patch, 
 move-to-maven-acf-framework.patch, patch-connectors.zip


 I am looking at the current project structure. If we want to make another 
 build tool available I think we need to change the directory structure. I 
 tried to place a suggestion in an image. Can you please have a look at it. If 
 we agree that this is a good way to go, than I will continue to work on a 
 patch. Which might be a bit hard with all these changing directories, but 
 I'll do my best to at least get an idea whether it would be working.
 So I have three questions:
 - Do you want to move to maven or put maven next to ant?
 - Do you prefer another build mechanism [ant with ivy, gradle, maven3]
 - Do you have an idea about the amount of scripts that need to be changed if 
 we change the project structure
 The image of a possible project layout (that is based on the maven standards) 
 is attached to the issue

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-100) DB lock timeout, and/or indefinite or excessive database activity

2011-08-12 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084147#comment-13084147
 ] 

Karl Wright commented on CONNECTORS-100:


I haven't heard anything back from the Derby folks. I'm therefore going to 
leave this ticket open.  HSQLDB works better for the hopcount queries, although 
it does not work well for the report queries.  So I guess you can pick your 
poison at the moment.


 DB lock timeout, and/or indefinite or excessive database activity
 -

 Key: CONNECTORS-100
 URL: https://issues.apache.org/jira/browse/CONNECTORS-100
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework core
 Environment: Running unmodified dist/example from trunk/ using the 
 default configuration.
Reporter: Andrzej Bialecki 
Assignee: Karl Wright

 When a job is started and running (via crawler-ui) occasionally it's not 
 possible to display a list of running jobs. The problem persists even after 
 restarting ACF. The following exception is thrown in the console:
 {code}
 org.apache.acf.core.interfaces.ACFException: Database exception: Exception 
 doing query: A lock could not be obtained within the time requested
 at 
 org.apache.acf.core.database.Database.executeViaThread(Database.java:421)
 at 
 org.apache.acf.core.database.Database.executeUncachedQuery(Database.java:465)
 at 
 org.apache.acf.core.database.Database$QueryCacheExecutor.create(Database.java:1072)
 at 
 org.apache.acf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:144)
 at 
 org.apache.acf.core.database.Database.executeQuery(Database.java:167)
 at 
 org.apache.acf.core.database.DBInterfaceDerby.performQuery(DBInterfaceDerby.java:727)
 at 
 org.apache.acf.crawler.jobs.JobManager.makeJobStatus(JobManager.java:5611)
 at 
 org.apache.acf.crawler.jobs.JobManager.getAllStatus(JobManager.java:5549)
 at 
 org.apache.jsp.showjobstatus_jsp._jspService(showjobstatus_jsp.java:316)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at 
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
 at 
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at 
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
 at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
 at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
 at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
 at 
 org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
 at 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
 at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.Server.handle(Server.java:326)
 at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
 at 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
 at 
 org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
 at 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 Caused by: java.sql.SQLTransactionRollbackException: A lock could not be 
 obtained within the time requested
 at 
 org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown 
 Source)
 at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown 
 Source)
 at 
 org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown 
 Source)
 at 
 org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown 
 Source)
 at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown 
 Source)
 at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown 
 Source)
 at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown 
 Source)
 at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
 at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown

[jira] [Commented] (CONNECTORS-31) For the Solr LCF security filter plugin, establish a concept of session to improve performance

2011-08-12 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084151#comment-13084151
 ] 

Karl Wright commented on CONNECTORS-31:
---

We fixed this another way - by using caching within individual authorities.  
This improvement is therefore likely unneeded, so I'm going to close this 
ticket for now.


 For the Solr LCF security filter plugin, establish a concept of session to 
 improve performance
 --

 Key: CONNECTORS-31
 URL: https://issues.apache.org/jira/browse/CONNECTORS-31
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Solr Security Filter
Reporter: Karl Wright
 Fix For: ManifoldCF 0.3


 Instead of only allowing an authenticated user name to be passed to the 
 LCFSecurityFilter SearchComponent, improve this to return a security token 
 and optionally receive the security token as well.  Then it will be possible 
 for it to make the access tokens sticky, reducing load on the authority 
 service on situations where multiple searches occur in each session.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-31) For the Solr LCF security filter plugin, establish a concept of session to improve performance

2011-08-12 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-31.
---

   Resolution: Won't Fix
Fix Version/s: ManifoldCF 0.3

 For the Solr LCF security filter plugin, establish a concept of session to 
 improve performance
 --

 Key: CONNECTORS-31
 URL: https://issues.apache.org/jira/browse/CONNECTORS-31
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Solr Security Filter
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3


 Instead of only allowing an authenticated user name to be passed to the 
 LCFSecurityFilter SearchComponent, improve this to return a security token 
 and optionally receive the security token as well.  Then it will be possible 
 for it to make the access tokens sticky, reducing load on the authority 
 service on situations where multiple searches occur in each session.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-12 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084220#comment-13084220
 ] 

Karl Wright commented on CONNECTORS-224:


It doesn't build on 1.5 still:

compile-connector:
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\build.xml:10:
warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last;
 set to false for repeatable builds
[javac] Compiling 9 source files to C:\wip\mcf\CONNECTORS-224\connectors\ope
nsearchserver\build\connector\classes
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:59: cannot find symbol
[javac] symbol  : constructor IOException(org.apache.manifoldcf.core.interfa
ces.ManifoldCFException)
[javac] location: class java.io.IOException
[javac] throw new IOException(e);
[javac]   ^
[javac] 1 error

This is easily corrected; I'll check in a fix.



 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, 
 oss-mfc-beta.patch, oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-12 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084224#comment-13084224
 ] 

Karl Wright commented on CONNECTORS-224:


Another problem that occurs in this connector with no real connection is that 
notification never completes.  Tons of exceptions:

ERROR 2011-08-12 12:15:00,637 (Job notification thread) - 
java.net.ConnectException: Connection refused: connect
org.apache.manifoldcf.core.interfaces.ManifoldCFException: 
java.net.ConnectException: Connection refused: connect
at 
org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerConnection.call(OpenSearchServerConnection.java:102)
at 
org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerAction.init(OpenSearchServerAction.java:19)
at 
org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerConnector.noteJobComplete(OpenSearchServerConnector.java:328)
at 
org.apache.manifoldcf.crawler.system.JobNotificationThread.run(JobNotificationThread.java:115)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.init(Socket.java:375)
at java.net.Socket.init(Socket.java:249)
at 
org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(Unknown
 Source)
at 
org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(Unknown
 Source)
at org.apache.commons.httpclient.HttpConnection.open(Unknown Source)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Unknown 
Source)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(Unknown Source)
at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown 
Source)
at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown 
Source)
at 
org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerConnection.call(OpenSearchServerConnection.java:93)
... 3 more

This is actually a framework problem, I believe; the job is aborted but 
notification is attempted anyhow.  But it is supposed to give up not try 
indefinitely.

I'll create a new ticket for that issue.


 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, 
 oss-mfc-beta.patch, oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-238) Exception on end notification is not handled properly

2011-08-12 Thread Karl Wright (JIRA)

Exception on end notification is not handled properly
-

 Key: CONNECTORS-238
 URL: https://issues.apache.org/jira/browse/CONNECTORS-238
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework agents process
Reporter: Karl Wright


When an exception occurs during end notification, handling should permit the 
job to stop.  Notification is a nicety, not a requirement, and the notification 
method is called even when the job is aborted.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-238) Exception on end notification is not handled properly

2011-08-12 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-238.


   Resolution: Fixed
Fix Version/s: ManifoldCF 0.3
 Assignee: Karl Wright

r1157178


 Exception on end notification is not handled properly
 -

 Key: CONNECTORS-238
 URL: https://issues.apache.org/jira/browse/CONNECTORS-238
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework agents process
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3


 When an exception occurs during end notification, handling should permit the 
 job to stop.  Notification is a nicety, not a requirement, and the 
 notification method is called even when the job is aborted.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-12 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084252#comment-13084252
]

Karl Wright commented on CONNECTORS-224:

Ok, I've tested some more.

This is a lot better than before. The issues previously described seem to have
been fixed. Now we have a new set of issues to consider. I'm listing these
below.

(1) In addOrReplaceDocument(), the following code is present:

OpenSearchServerConfig config = getConfigParameters(null);
Integer count = addInstance(config);
synchronized (count) {

Can you explain what the purpose of this synchronizer is? It looks to me like
you might be effectively managing your own connection pool here, which is both
redundant and would prevent ManifoldCF end users from controlling the size of
that pool. Am I correct?

(2) In addOrReplaceDocument(), you close the input stream. You should not do
that. The caller closes the stream.

(3) Formatting. Apache guidelines set indenting to 2 spaces, with no tabs.
ManifoldCF adheres to this convention. It would be great if you could reformat
accordingly.

Thanks again!

OpenSearchServer connector
--

Key: CONNECTORS-224
URL: https://issues.apache.org/jira/browse/CONNECTORS-224
Project: ManifoldCF
Issue Type: New Feature
Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
Labels: OpenSearchServer, connector, outputconnector
Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch,
oss-mfc-beta.patch, oss-mfc-dev.patch

Original Estimate: 336h
Remaining Estimate: 336h

Provide an output connector for
[OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-09 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082021#comment-13082021
 ] 

Karl Wright commented on CONNECTORS-224:


I checked in and tested Maven build files in the branch.

 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, 
 oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-09 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082027#comment-13082027
 ] 

Karl Wright commented on CONNECTORS-224:


I just discovered that this connector won't build under jdk 1.5, which is a 
problem since ManifoldCF has not yet moved to a minimum Java version of 1.6.  
These are the errors I get:


compile-connector:
[mkdir] Created dir: C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\b
uild\connector\classes
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\build.xml:10:
warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last;
 set to false for repeatable builds
[javac] Compiling 6 source files to C:\wip\mcf\CONNECTORS-224\connectors\ope
nsearchserver\build\connector\classes
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:8: package javax.xml.stream does not exist
[javac] import javax.xml.stream.XMLOutputFactory;
[javac] ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:9: package javax.xml.stream does not exist
[javac] import javax.xml.stream.XMLStreamException;
[javac] ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:10: package javax.xml.stream does not exist
[javac] import javax.xml.stream.XMLStreamWriter;
[javac] ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:42: cannot find symbol
[javac] symbol  : class XMLStreamException
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] throws XMLStreamException, IOException {
[javac]^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:34: cannot find symbol
[javac] symbol  : class XMLStreamException
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] } catch (XMLStreamException e) {
[javac]  ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:44: cannot find symbol
[javac] symbol  : class XMLOutputFactory
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] XMLOutputFactory factory = XMLOutputFactory.newInstance(
);
[javac] ^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:44: cannot find symbol
[javac] symbol  : variable XMLOutputFactory
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] XMLOutputFactory factory = XMLOutputFactory.newInstance(
);
[javac]^
[javac] C:\wip\mcf\CONNECTORS-224\connectors\opensearchserver\connector\src\
main\java\org\apache\manifoldcf\agents\output\opensearchserver\OpenSearchServerI
ndex.java:46: cannot find symbol
[javac] symbol  : class XMLStreamWriter
[javac] location: class org.apache.manifoldcf.agents.output.opensearchserver
.OpenSearchServerIndex
[javac] XMLStreamWriter writer = factory.createXMLStreamWriter(s
w);
[javac] ^
[javac] 8 errors

BUILD FAILED


The XML parser that is used currently throughout ManifoldCF, and is thus 
available, is a modified version of xerces - you will see it under the lib 
directory.

This does NOT affect maven, because maven is at minimum a 1.6 build already.  
It will affect the ability, however, to include the opensearchserver connector 
in the shipping packages.  So it seems to me that you have three choices here: 
(1) wait until we officially adopt Java 1.6 as the minimum standard java 
version before merging this into trunk; (2) modify your code so that it does 
not use the 1.6 features; or (3) change the conditional compilation in the ant 
build so that it won't even try to compile the connector under JDK 1.5.  Please 
let me know what you prefer to do.


 OpenSearchServer connector
 --

 Key:

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-09 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082029#comment-13082029
 ] 

Karl Wright commented on CONNECTORS-224:


Trying out the connector, it appears that the connection check() method is not 
doing anything, as I get back Connection working even with completely bogus 
parameters:

View Output Connection Status
Name:   testDescription:
Connection type:OpenSearchServerMax connections:10
Server Location (URL):  http://localhost:8080/
Index name: index
User name:  foo
API Key:bar
Connection status:  Connection working

This should be fixed, obviously.


 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, 
 oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-09 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082030#comment-13082030
 ] 

Karl Wright commented on CONNECTORS-224:


The Parameters tab also appears to have no Javascript correctness checking 
whatsoever.  I can specify a blank URL and a blank index name and it still 
allows me to save it.  This too should be addressed.

 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, 
 oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-09 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082034#comment-13082034
 ] 

Karl Wright commented on CONNECTORS-224:


When I try to crawl using the server and the connection is bogus, the crawl 
proceeds a while and does not seem to notice that there is no output server.  
Very shortly thereafter, the whole system runs out of memory:


agents process ran out of memory - shutting down
java.lang.OutOfMemoryError: Java heap space
at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:133)
at java.lang.StringCoding.decode(StringCoding.java:173)
at java.lang.StringCoding.decode(StringCoding.java:185)
at java.lang.String.init(String.java:570)
at java.lang.String.init(String.java:593)
at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer
Index.getXML(OpenSearchServerIndex.java:58)
at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer
Index.init(OpenSearchServerIndex.java:28)
at org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServer
Connector.addOrReplaceDocument(OpenSearchServerConnector.java:153)
at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.ad
dOrReplaceDocument(IncrementalIngester.java:1499)
at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.pe
rformIngestion(IncrementalIngester.java:469)
at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.do
cumentIngest(IncrementalIngester.java:364)
at org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ing
estDocument(WorkerThread.java:1587)
at org.apache.manifoldcf.crawler.connectors.filesystem.FileConnector.pro
cessDocuments(FileConnector.java:283)
at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.proc
essDocuments(BaseRepositoryConnector.java:423)
at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja
va:564)


I haven't looked at the code, but clearly the connector is trying to queue up 
documents in memory for some reason.  If that's what's going on, that's never 
going to fly because there cannot possibly be proper feedback of error 
conditions etc.

 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, 
 oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-08 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13080861#comment-13080861
 ] 

Karl Wright commented on CONNECTORS-224:


I've created a branch for further development of this connector until it is 
ready to commit to trunk.  The url for the branch is:

https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-224.

For subsequent patches, please submit diffs against this branch.  Thanks!


 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Issue Comment Edited] (CONNECTORS-224) OpenSearchServer connector

2011-08-08 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13080867#comment-13080867
 ] 

Karl Wright edited comment on CONNECTORS-224 at 8/8/11 9:47 AM:


As far as the use of html files, the real question is how resources interact 
with class loaders in Java.  ManifoldCF originally had its HTML code generated 
by JSP files, but had to change this architecture.  The reason ManifoldCF 
pulled its HTML code out of JSP files was because JSPs don't work well with 
class loaders.  Connectors must be self-contained in that loading the connector 
class from whatever library directory is specified in the properties.xml file 
is adequate to locate all resources for the connector.  Can you clarify whether 
or not you think this will work for your html resource files?


  was (Author: kwri...@metacarta.com):
As far as the use of html files, the real question is how resources 
interact with class loaders in Java.  The reason ManifoldCF pulled its HTML 
code out of JSP files was because JSPs don't work well with class loaders.  
Connectors must be self-contained in that loading the connector class from 
whatever library directory is specified in the properties.xml file is adequate 
to locate all resources for the connector.  Can you clarify whether or not you 
think this will work for your html resource files?

  
 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-08 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13080867#comment-13080867
 ] 

Karl Wright commented on CONNECTORS-224:


As far as the use of html files, the real question is how resources interact 
with class loaders in Java.  The reason ManifoldCF pulled its HTML code out of 
JSP files was because JSPs don't work well with class loaders.  Connectors must 
be self-contained in that loading the connector class from whatever library 
directory is specified in the properties.xml file is adequate to locate all 
resources for the connector.  Can you clarify whether or not you think this 
will work for your html resource files?


 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-08 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13081000#comment-13081000
 ] 

Karl Wright commented on CONNECTORS-224:


When I build using ant build, this is what I get:

compile-connector:
[mkdir] Created dir: 
/data/mcf/CONNECTORS-224/connectors/opensearchserver/build/connector/classes
[javac] Compiling 5 source files to 
/data/mcf/CONNECTORS-224/connectors/opensearchserver/build/connector/classes
[javac] 
/data/mcf/CONNECTORS-224/connectors/opensearchserver/connector/src/main/java/org/apache/manifoldcf/agents/output/opensearchserver/OpenSearchServerConnector.java:17:
 package 
org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerAction 
does not exist
[javac] import 
org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerAction.CommandEnum;
[javac] 
  ^
[javac] 
/data/mcf/CONNECTORS-224/connectors/opensearchserver/connector/src/main/java/org/apache/manifoldcf/agents/output/opensearchserver/OpenSearchServerConnector.java:181:
 cannot find symbol
[javac] symbol  : class OpenSearchServerAction
[javac] location: class 
org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerConnector
[javac] OpenSearchServerAction oo = new OpenSearchServerAction(
[javac] ^
[javac] 
/data/mcf/CONNECTORS-224/connectors/opensearchserver/connector/src/main/java/org/apache/manifoldcf/agents/output/opensearchserver/OpenSearchServerConnector.java:181:
 cannot find symbol
[javac] symbol  : class OpenSearchServerAction
[javac] location: class 
org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerConnector
[javac] OpenSearchServerAction oo = new OpenSearchServerAction(
[javac] ^
[javac] 
/data/mcf/CONNECTORS-224/connectors/opensearchserver/connector/src/main/java/org/apache/manifoldcf/agents/output/opensearchserver/OpenSearchServerConnector.java:182:
 cannot find symbol
[javac] symbol  : variable CommandEnum
[javac] location: class 
org.apache.manifoldcf.agents.output.opensearchserver.OpenSearchServerConnector
[javac] CommandEnum.optimize, 
getParameters(null));
[javac] ^
[javac] 4 errors

BUILD FAILED


 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-224) OpenSearchServer connector

2011-08-08 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13081010#comment-13081010
 ] 

Karl Wright commented on CONNECTORS-224:


Great - patch 3 committed (and now it builds).


 OpenSearchServer connector
 --

 Key: CONNECTORS-224
 URL: https://issues.apache.org/jira/browse/CONNECTORS-224
 Project: ManifoldCF
  Issue Type: New Feature
  Components: OpenSearchServer connector
Affects Versions: ManifoldCF 0.3
Reporter: Emmanuel Keller
Assignee: Karl Wright
  Labels: OpenSearchServer, connector, outputconnector
 Attachments: oss-mfc-alpha.patch, oss-mfc-alpha2.patch, 
 oss-mfc-dev.patch

   Original Estimate: 336h
  Remaining Estimate: 336h

 Provide an output connector for 
 [OpenSearchServer|http://www.open-search-server.com].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-07 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright updated CONNECTORS-236:
---

   Resolution: Fixed
Fix Version/s: ManifoldCF 0.3
 Assignee: Karl Wright
   Status: Resolved  (was: Patch Available)

r1154789.

 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt, 
 patch2.txt, patch3.txt, patch4.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-05 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079950#comment-13079950
 ] 

Karl Wright commented on CONNECTORS-236:


Patch 4 committed to the branch.


 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt, 
 patch2.txt, patch3.txt, patch4.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-05 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13080079#comment-13080079
 ] 

Karl Wright commented on CONNECTORS-236:


Merged the CONNECTORS-236 branch into trunk.  r1154315.


 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt, 
 patch2.txt, patch3.txt, patch4.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-234) Add the CMIS binding parameter for the CMIS Repository Connector

2011-08-05 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13080086#comment-13080086
 ] 

Karl Wright commented on CONNECTORS-234:


I merged branches/CONNECTORS-236 into trunk and applied the patch.  It built 
fine but the cmis end-to-end tests failed.  Here's the trace:

[junit] java.lang.Exception: Job reports error.
[junit] at 
org.apache.manifoldcf.cmis_tests.APISanityTest.waitJobInactive(APISanityTest.java:510)
[junit] at 
org.apache.manifoldcf.cmis_tests.APISanityTest.sanityCheck(APISanityTest.java:350)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[junit] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[junit] at java.lang.reflect.Method.invoke(Method.java:616)
[junit] at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
[junit] at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
[junit] at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
[junit] at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
[junit] at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)

I think the test may need to be updated to use the new code.


 Add the CMIS binding parameter for the CMIS Repository Connector
 

 Key: CONNECTORS-234
 URL: https://issues.apache.org/jira/browse/CONNECTORS-234
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: patch5.txt

   Original Estimate: 3h
  Remaining Estimate: 3h

 The CMIS Repository Connector must include a new configuration parameter to 
 set the CMIS binding protocol.
 This is an important parameter that allows to fit Manifold on each product 
 vendor, this because not all the vendors have implemented all the CMIS 
 bindings.
 This means that the configuration form should have the following 
 possibilities for this new binding parameter:
 - LOCAL (for the JVM local process binding)
 - AtomPub (the CMIS AtomPub protocol)
 - Web Services - SOAP (the CMIS WS-SOAP Protocol)
 This patch should involve only the configuration settings for the CMIS 
 session without changing any lines of code of the process of the CMIS 
 Repository Connector.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-234) Add the CMIS binding parameter for the CMIS Repository Connector

2011-08-05 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright updated CONNECTORS-234:
---

   Resolution: Fixed
Fix Version/s: ManifoldCF 0.3
   Status: Resolved  (was: Patch Available)

r1154329.

 Add the CMIS binding parameter for the CMIS Repository Connector
 

 Key: CONNECTORS-234
 URL: https://issues.apache.org/jira/browse/CONNECTORS-234
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: patch5.txt, patch6.txt

   Original Estimate: 3h
  Remaining Estimate: 3h

 The CMIS Repository Connector must include a new configuration parameter to 
 set the CMIS binding protocol.
 This is an important parameter that allows to fit Manifold on each product 
 vendor, this because not all the vendors have implemented all the CMIS 
 bindings.
 This means that the configuration form should have the following 
 possibilities for this new binding parameter:
 - LOCAL (for the JVM local process binding)
 - AtomPub (the CMIS AtomPub protocol)
 - Web Services - SOAP (the CMIS WS-SOAP Protocol)
 This patch should involve only the configuration settings for the CMIS 
 session without changing any lines of code of the process of the CMIS 
 Repository Connector.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-193) Not all output connectors adhere to the standard convention for naming of tabs, form elements, and javascript methods

2011-08-04 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079312#comment-13079312
 ] 

Karl Wright commented on CONNECTORS-193:


I changed the output connector tab names because users were having problems 
figuring out what tabs came from the output connectors.  r1153836.


 Not all output connectors adhere to the standard convention for naming of 
 tabs, form elements, and javascript methods
 -

 Key: CONNECTORS-193
 URL: https://issues.apache.org/jira/browse/CONNECTORS-193
 Project: ManifoldCF
  Issue Type: Bug
  Components: GTS connector, Lucene/SOLR connector
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Erlend Garåsen

 The convention for form elements and javascript methods is that all element 
 names and methods must begin with lowercase oc.  The convention for output 
 specification tabs is that the tab name should contain the name of the 
 target, e.g. GTS Parameters or Solr Metadata Mapping.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-04 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079438#comment-13079438
 ] 

Karl Wright commented on CONNECTORS-236:


Hi Piergiorgio,

I had a look at your Setup method, and what you do is create a second instance 
of Jetty that includes all the ManifoldCF web applications, as well as the CMIS 
server.  This should not be needed since the MCF web applications are already 
deployed on the other instance of Jetty.  You just need to use the right port 
number to talk with them, which I believe is 8346.

I'm not sure this is causing your difficulties or not but it certainly isn't 
good.


 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-04 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079441#comment-13079441
 ] 

Karl Wright commented on CONNECTORS-236:


Another change I'd like to see is to pull the snapshot war out of the maven 
repository.  The filesystem tests do it that way by allowing optional -D 
arguments, which maven provides, to point at the repository war.  Copying that 
would also make it possible to run the same tests under ant.


 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-04 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079445#comment-13079445
 ] 

Karl Wright commented on CONNECTORS-236:


Ok, never mind - the pair of jetty servers is indeed separate as you say.


 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-04 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079452#comment-13079452
 ] 

Karl Wright commented on CONNECTORS-236:


I checked this in with two changes.  First, the chemistry war I put into the 
lib directory.  I presume that the artifact under maven will be deployed from 
there, and that the ant build will refer to the war directly.  Second, I did 
not include the changes to jetty-runner, since they didn't make any sense to me.

The branch these changes are in is: 
https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-236.



 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-04 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079465#comment-13079465
 ] 

Karl Wright commented on CONNECTORS-236:


Added.


 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt, 
 patch2.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-04 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079494#comment-13079494
 ] 

Karl Wright commented on CONNECTORS-236:


I think we should do what we do for other artifacts that are not yet available: 
ask the user to install them into maven, by just adding to the procedure 
described here:

http://incubator.apache.org/connectors/how-to-build-and-deploy.html#Preparation



 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt, 
 patch2.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-04 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079498#comment-13079498
 ] 

Karl Wright commented on CONNECTORS-236:


I updated build.xml and Base.java to use relative paths to the wars.  Now I can 
run the test under ant, but it fails in just the manner you describe (timeout 
waiting for job to finish).  I was able to see manifoldcf.log when I exited; 
it's full of these:

Error tossed: org.apache.chemistry.opencmis.client.runtime.FolderImpl
java.lang.ClassCastException: org.apache.chemistry.opencmis.client.runtime.Folde
rImpl
at org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector
.getDocumentVersions(CmisRepositoryConnector.java:1026)
at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.getD
ocumentVersions(BaseRepositoryConnector.java:355)
at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.getD
ocumentVersions(BaseRepositoryConnector.java:336)
at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.getD
ocumentVersions(BaseRepositoryConnector.java:315)
at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.getD
ocumentVersions(BaseRepositoryConnector.java:292)
at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja
va:321)



 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt, 
 patch2.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-236) Tests and test server needed for CMIS connector

2011-08-04 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079506#comment-13079506
 ] 

Karl Wright commented on CONNECTORS-236:


I checked in the patch changes.


 Tests and test server needed for CMIS connector
 ---

 Key: CONNECTORS-236
 URL: https://issues.apache.org/jira/browse/CONNECTORS-236
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Reporter: Piergiorgio Lucidi
 Attachments: 
 chemistry-opencmis-server-inmemory-war-0.5.0-SNAPSHOT.war, patch.txt, 
 patch2.txt, patch3.txt


 The CMIS connector needs tests, and a CMIS test server to run against.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-237) RSS Connector proxy code doesn't seem to function correctly

2011-08-04 Thread Karl Wright (JIRA)

RSS Connector proxy code doesn't seem to function correctly
---

 Key: CONNECTORS-237
 URL: https://issues.apache.org/jira/browse/CONNECTORS-237
 Project: ManifoldCF
  Issue Type: Bug
  Components: RSS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright


Trying to crawl through a proxy fails.  No activity is recorded but all fetches 
fail (with timeout errors) and are requeued.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-03 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13078766#comment-13078766
]

Karl Wright commented on CONNECTORS-235:

Thanks for the info. The fix, as structured, should generally apply to
PostgreSQL too. Please let me know if it works for you. But I'll need to
research how this problem could have gotten past the tests regardless.

item description element not indexed

Key: CONNECTORS-235
URL: https://issues.apache.org/jira/browse/CONNECTORS-235
Project: ManifoldCF
Issue Type: Improvement
Components: RSS connector
Affects Versions: ManifoldCF 0.2
Reporter: Kate McGonigal
Assignee: Karl Wright
Fix For: ManifoldCF 0.3

The RSS feed's *item* description is not written to any field in the Solr
index.
I have a typical RSS feed with the general structure:
rss
channel
title/title
link/link
description/description
item
title/title
link/link
pubDate/pubDate
description *** the description I do want *** /description
author/author
category/category
/item
/channel
/rss
Example:
For the RSS feed:
http://www.onemansjazz.ca/component/option,com_rss/feed,RSS2.0/no_html,1/
the rss/channel/item/description field is not indexed into Solr.
Example notes:
- what does get written to the Solr description field is the description
metadata from the website, i.e. Jazz radio show from Winnipeg on CKUW 95.9
FM, hosted by Maurice Hogue. in this case.
- on the Dechromed Content tab of the job, No dechromed content is
selected. I'm not sure if that is relevant.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-03 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079097#comment-13079097
]

Karl Wright commented on CONNECTORS-235:

Hmm, I'm using the very same feed you are, with PostgreSQL, and seeing perfect
results.
Can you attach a screen shot of the View Job page of the job in question?
Also, the View Connection page for both the output connection and the
repository connection?

item description element not indexed

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-03 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079118#comment-13079118
]

Karl Wright commented on CONNECTORS-235:

One problem I found is that due to a rebuild I was not using PostgreSQL after
all, so here's another check-in to fix its handling of streamed carrydown info.
r1153702.

item description element not indexed

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-03 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079134#comment-13079134
]

Karl Wright commented on CONNECTORS-235:

Ok, another mystery solved. The RSS chromed data mode of None was not
properly tried because of the inadvertant database switch, and I found that
recrawling vs. crawling fresh generated incorrect version information. I've
fixed that problem but I can't check it in because it causes the following
error against a plain-vanilla Solr installation:

ERROR: [http://www.onemansjazz.ca/content/view/330/50/] multiple values
encountered for non multiValued field description: [Jazz radio show from
Winnipeg on CKUW 95.9 FM, hosted by Maurice Hogue., I have created a Listener
Survey and if you have the time to complete it, that would be terrific. I#39;m
trying to do an evaluation of One Man#39;s Jazz as well as considering some
new options that have arisen. Your feedback would be most appreciate.This
survey is in two parts and is a total of twenty parts, most of them just
require a click of your mouse. Click here
(http://www.surveymonkey.com/s/C3DZ3JK) for Part One, and here
(http://www.surveymonkey.com/s/C38FVH8) for Part Two. Thanks again for your
input. ]

I'm not sure why Solr is interpreting this long field as multivalued, but
clearly it would be much better if I used a metadata name that wasn't
description, since Solr's example configuration has dibs on that. I'll
experiment and post further.

item description element not indexed

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-03 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079137#comment-13079137
]

Karl Wright commented on CONNECTORS-235:

I switched the name to summary. r1153705.

item description element not indexed

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-03 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079141#comment-13079141
]

Karl Wright commented on CONNECTORS-235:

Just to be clear, here's an example of the Solr log line for indexing one of
the documents from the above mentioned feed. You can, of course, configure the
job to map the field names to whatever you like. This is with no mapping
whatsoever.

INFO: [] webapp=/solr path=/update/extract
params={literal.source=http://www.onemansjazz.ca/component/option,com_rss/feed,RSS2.0/no_html,1/literal.category=Radio+-+Play+listsliteral.summary=I+had+a+lot+of+fun+putting+this+show+together+this+week.+Hope+you+enjoy+it,+too.literal.id=http://www.onemansjazz.ca/content/view/332/30/literal.title=July+23,+2011+Playlistliteral.pubdate=1311339967000}
status=0 QTime=13

I'm pretty certain you must have a metadata value set for description in your
job, because there is absolutely no mechanism (and never was one) for picking
up the channel description from the feed. So you will have to remove that in
order to get all this to work for you.

item description element not indexed

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-02 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13078502#comment-13078502
]

Karl Wright commented on CONNECTORS-235:

That's not good. I'll have a look into this as well.

item description element not indexed

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-02 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13078518#comment-13078518
]

Karl Wright commented on CONNECTORS-235:

I was able to reproduce this with Derby. I am certain that it doesn't happen
under postgresql. I'll check HSQLDB.

item description element not indexed

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-02 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13078521#comment-13078521
]

Karl Wright commented on CONNECTORS-235:

Same thing under HSQLDB. So the trick is going to be to fix these two
databases without breaking PostgreSQL.

item description element not indexed

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-235) item description element not indexed

2011-08-02 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13078536#comment-13078536
]

Karl Wright commented on CONNECTORS-235:

Fix for file-based carrydown data for HSQLDB and Derby. r1153314.

item description element not indexed

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-27 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-223.


Resolution: Fixed

r1151437


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-223.patch, CONNECTORS-223_forkMode.patch, 
 CONNECTORS-223_jetty-runner.patch, CONNECTORS-223_tests.patch, 
 test_reset.patch


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-230) CMIS connector needs to be documented in end-user-documentation

2011-07-27 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-230.


   Resolution: Fixed
Fix Version/s: ManifoldCF 0.3

r1151547.


 CMIS connector needs to be documented in end-user-documentation
 -

 Key: CONNECTORS-230
 URL: https://issues.apache.org/jira/browse/CONNECTORS-230
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Documentation
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3


 There needs to be a section on the CMIS connector and authority in the end 
 user documentation.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-226) Usage and meaning of ManifoldCFException type REPOSITORY_CONNECTION_ERROR needs to be reviewed and clarified

2011-07-26 Thread Karl Wright (JIRA)

Usage and meaning of ManifoldCFException type REPOSITORY_CONNECTION_ERROR needs 
to be reviewed and clarified


 Key: CONNECTORS-226
 URL: https://issues.apache.org/jira/browse/CONNECTORS-226
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework core, JCIFS connector, LiveLink connector
Affects Versions: ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.3
Reporter: Karl Wright


The ManifoldCFException type REPOSITORY_CONNECTION_ERROR seems to be treated by 
the framework somewhat inconsistently.  In some places it is treated as a 
permanent connection exception, and in others as a temporary connection 
exception (in lieu of a ServiceInterruption where ServiceInterruption is not 
possible).  Only two connectors use it (LiveLink and jCIFS), and the JCIFS case 
is not interesting.  So really this is currently here to support Livelink.

There are two ways forward.  The first way is to convert the Livelink 
connector's exception to a true ServiceInterruption, and revert 
REPOSITORY_CONNECTION_ERROR to its original meaning, which has now been 
deprecated as a result of the fact that connect() methods can no longer throw 
ManifoldCFExceptions at all.  The second is to continue the current 
Livelink-style usage, and make ALL usages consistent with that.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CONNECTORS-226) Usage and meaning of ManifoldCFException type REPOSITORY_CONNECTION_ERROR needs to be reviewed and clarified

2011-07-26 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright reassigned CONNECTORS-226:
--

Assignee: Karl Wright

 Usage and meaning of ManifoldCFException type REPOSITORY_CONNECTION_ERROR 
 needs to be reviewed and clarified
 

 Key: CONNECTORS-226
 URL: https://issues.apache.org/jira/browse/CONNECTORS-226
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework core, JCIFS connector, LiveLink connector
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright

 The ManifoldCFException type REPOSITORY_CONNECTION_ERROR seems to be treated 
 by the framework somewhat inconsistently.  In some places it is treated as a 
 permanent connection exception, and in others as a temporary connection 
 exception (in lieu of a ServiceInterruption where ServiceInterruption is not 
 possible).  Only two connectors use it (LiveLink and jCIFS), and the JCIFS 
 case is not interesting.  So really this is currently here to support 
 Livelink.
 There are two ways forward.  The first way is to convert the Livelink 
 connector's exception to a true ServiceInterruption, and revert 
 REPOSITORY_CONNECTION_ERROR to its original meaning, which has now been 
 deprecated as a result of the fact that connect() methods can no longer throw 
 ManifoldCFExceptions at all.  The second is to continue the current 
 Livelink-style usage, and make ALL usages consistent with that.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful

2011-07-26 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13071061#comment-13071061
 ] 

Karl Wright commented on CONNECTORS-221:


I tried to apply either patch 5 or patch 6 to the branch and they both failed 
to apply cleanly.  I've committed all patches up to patch 4.  Any hints?


 A CMIS connector would be helpful
 -

 Key: CONNECTORS-221
 URL: https://issues.apache.org/jira/browse/CONNECTORS-221
 Project: ManifoldCF
  Issue Type: New Feature
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
 Attachments: CONNECTORS-221-DEPENDENCIES.txt, 
 CONNECTORS-221-Java.txt, CONNECTORS-221-branch-build-patch-2.txt, 
 CONNECTORS-221-branch-build-patch-3.txt, 
 CONNECTORS-221-branch-java-patch-2.txt, 
 CONNECTORS-221-branch-java-patch-3.txt, 
 CONNECTORS-221-branch-java-patch-4.txt, 
 CONNECTORS-221-branch-java-patch-5.txt, 
 CONNECTORS-221-branch-java-patch-6.txt, CONNECTORS-221-branch-java-patch.txt, 
 CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, 
 CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, 
 screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, 
 screenshot-8.jpg


 Several people have asked if ManifoldCF supports CMIS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-221) A CMIS connector would be helpful

2011-07-26 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright updated CONNECTORS-221:
---

   Resolution: Fixed
Fix Version/s: ManifoldCF 0.3
 Assignee: Karl Wright
   Status: Resolved  (was: Patch Available)

r1151106, merging CONNECTORS-221 branch into trunk


 A CMIS connector would be helpful
 -

 Key: CONNECTORS-221
 URL: https://issues.apache.org/jira/browse/CONNECTORS-221
 Project: ManifoldCF
  Issue Type: New Feature
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-221-DEPENDENCIES.txt, 
 CONNECTORS-221-Java.txt, CONNECTORS-221-branch-build-patch-2.txt, 
 CONNECTORS-221-branch-build-patch-3.txt, 
 CONNECTORS-221-branch-java-patch-2.txt, 
 CONNECTORS-221-branch-java-patch-3.txt, 
 CONNECTORS-221-branch-java-patch-4.txt, 
 CONNECTORS-221-branch-java-patch-5.txt, 
 CONNECTORS-221-branch-java-patch-6.txt, CONNECTORS-221-branch-java-patch.txt, 
 CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, 
 CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, 
 screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, 
 screenshot-8.jpg


 Several people have asked if ManifoldCF supports CMIS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-227) CMIS connector does not report exception text for connection check method

2011-07-26 Thread Karl Wright (JIRA)

CMIS connector does not report exception text for connection check method
-

 Key: CONNECTORS-227
 URL: https://issues.apache.org/jira/browse/CONNECTORS-227
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
Priority: Minor


The CMIS connector does not include the exception text in its connection errors:

Connection failed: CMIS: Error during getting a new session

The convention is to include the exception text, as follows:

Connection failed: CMIS: Error during getting a new session: xxx

... where xxx is the text.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-228) Need maven support for CMIS connector build

2011-07-26 Thread Karl Wright (JIRA)

Need maven support for CMIS connector build
---

 Key: CONNECTORS-228
 URL: https://issues.apache.org/jira/browse/CONNECTORS-228
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright


The new CMIS connector needs to be built and included under the Maven build.  
This includes its dependencies.



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-227) CMIS connector does not report exception text for connection check method

2011-07-26 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright updated CONNECTORS-227:
---

   Resolution: Fixed
Fix Version/s: ManifoldCF 0.3
   Status: Resolved  (was: Patch Available)

r1151170.


 CMIS connector does not report exception text for connection check method
 -

 Key: CONNECTORS-227
 URL: https://issues.apache.org/jira/browse/CONNECTORS-227
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
Priority: Minor
 Fix For: ManifoldCF 0.3

 Attachments: patch.txt


 The CMIS connector does not include the exception text in its connection 
 errors:
 Connection failed: CMIS: Error during getting a new session
 The convention is to include the exception text, as follows:
 Connection failed: CMIS: Error during getting a new session: xxx
 ... where xxx is the text.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CONNECTORS-231) Apache Commons IO dependency is missing in the pom.xml

2011-07-26 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright reassigned CONNECTORS-231:
--

Assignee: Karl Wright

 Apache Commons IO dependency is missing in the pom.xml
 --

 Key: CONNECTORS-231
 URL: https://issues.apache.org/jira/browse/CONNECTORS-231
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework core
Affects Versions: ManifoldCF 0.3
Reporter: Piergiorgio Lucidi
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: patch.txt

   Original Estimate: 1h
  Remaining Estimate: 1h

 Trying to use the Webapp deployed with Maven using Jetty and trying to add a 
 new repository connector the application return a NoClassDef exception for 
 the Apache Commons IO package.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-228) Need maven support for CMIS connector build

2011-07-26 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright updated CONNECTORS-228:
---

   Resolution: Fixed
Fix Version/s: ManifoldCF 0.3
   Status: Resolved  (was: Patch Available)

r1151180
r1151182


 Need maven support for CMIS connector build
 ---

 Key: CONNECTORS-228
 URL: https://issues.apache.org/jira/browse/CONNECTORS-228
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: patch.txt


 The new CMIS connector needs to be built and included under the Maven build.  
 This includes its dependencies.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful

2011-07-25 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070530#comment-13070530
 ] 

Karl Wright commented on CONNECTORS-221:


Hi Piergiorgio,

The authority connector now no longer throws an exception when the connection 
parameters are bogus, but the Repository connector does:

java.lang.ClassCastException: org.apache.chemistry.opencmis.commons.exceptions.C
misConnectionException cannot be cast to java.lang.Error
at org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector
.getSession(CmisRepositoryConnector.java:327)
at org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector
.checkConnection(CmisRepositoryConnector.java:407)
at org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector
.check(CmisRepositoryConnector.java:284)
at org.apache.jsp.viewconnection_jsp._jspService(viewconnection_jsp.java
:326)

Can you look at this?  The check() method should either throw a 
ManifoldCFException or return an appropriate string.



 A CMIS connector would be helpful
 -

 Key: CONNECTORS-221
 URL: https://issues.apache.org/jira/browse/CONNECTORS-221
 Project: ManifoldCF
  Issue Type: New Feature
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
 Attachments: CONNECTORS-221-DEPENDENCIES.txt, 
 CONNECTORS-221-Java.txt, CONNECTORS-221-branch-build-patch-2.txt, 
 CONNECTORS-221-branch-build-patch-3.txt, 
 CONNECTORS-221-branch-java-patch-2.txt, 
 CONNECTORS-221-branch-java-patch-3.txt, 
 CONNECTORS-221-branch-java-patch-4.txt, CONNECTORS-221-branch-java-patch.txt, 
 CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, 
 CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, 
 screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, 
 screenshot-8.jpg


 Several people have asked if ManifoldCF supports CMIS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CONNECTORS-225) When using Derby, ManifoldCF incremental indexer sometimes gets a deadlock exception

2011-07-24 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright reassigned CONNECTORS-225:
--

Assignee: Karl Wright

 When using Derby, ManifoldCF incremental indexer sometimes gets a deadlock 
 exception
 

 Key: CONNECTORS-225
 URL: https://issues.apache.org/jira/browse/CONNECTORS-225
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework agents process
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright

 When working with Derby and indexing documents rapidly, sometimes the 
 following deadlock stack trace is thrown:
 at 
 org.apache.manifoldcf.core.database.DBInterfaceDerby.reinterpretExcep
 tion(DBInterfaceDerby.java:803)
 at 
 org.apache.manifoldcf.core.database.DBInterfaceDerby.performQuery(DBI
 nterfaceDerby.java:961)
 at 
 org.apache.manifoldcf.core.database.BaseTable.performQuery(BaseTable.
 java:229)
 at 
 org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.no
 teDocumentIngest(IncrementalIngester.java:1372)
 at 
 org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.pe
 rformIngestion(IncrementalIngester.java:469)
 at 
 org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.do
 cumentIngest(IncrementalIngester.java:365)
 at 
 org.apache.manifoldcf.crawler.system.WorkerThread$ProcessActivity.ing
 estDocument(WorkerThread.java:1587)
 at 
 org.apache.manifoldcf.crawler.connectors.webcrawler.WebcrawlerConnect
 or.processDocuments(WebcrawlerConnector.java:1222)
 at 
 org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.proc
 essDocuments(BaseRepositoryConnector.java:423)
 at 
 org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful

2011-07-24 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070271#comment-13070271
 ] 

Karl Wright commented on CONNECTORS-221:


The pertinent response is:

Karl,

Axis 1.4 is known to work on application servers that come with a more recent 
version of the SAAJ API (which is basically the case for all Java EE 5 
compliant servers because the SAAJ API is a dependency of the JAX-WS API). 
Therefore, it should work in your case as well.

Andreas


So, I'm willing to merge this branch into trunk.  I'll look into doing that 
sometime this week.  In the meantime, please confirm that development is 
essentially complete for the moment.


 A CMIS connector would be helpful
 -

 Key: CONNECTORS-221
 URL: https://issues.apache.org/jira/browse/CONNECTORS-221
 Project: ManifoldCF
  Issue Type: New Feature
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
 Attachments: CONNECTORS-221-DEPENDENCIES.txt, 
 CONNECTORS-221-Java.txt, CONNECTORS-221-branch-build-patch-2.txt, 
 CONNECTORS-221-branch-build-patch-3.txt, 
 CONNECTORS-221-branch-java-patch-2.txt, 
 CONNECTORS-221-branch-java-patch-3.txt, CONNECTORS-221-branch-java-patch.txt, 
 CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, 
 CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, 
 screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, 
 screenshot-8.jpg


 Several people have asked if ManifoldCF supports CMIS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-20 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068263#comment-13068263
]

Karl Wright commented on CONNECTORS-223:

bq. Per default, maven also runs the tests in a separate process.

So does it start the process, run all the tests, and shut the process down? Or
does it start a process for each test?

bq. The execution procedure is sequential. Each tests runs to the whole
lifecycle, before an other test starts.

Ok, that's a relief.

Other than trying to run these tests myself under maven, I can't think of any
other way to proceed other than to ask you to figure out a way to get at the
manifoldcf.log output for the test that fails. The timeout is happening
because the crawl it sets up is never finishing. This could well be due to
some static objects hanging around from one cycle to the next, but I'm never
going to be able to tell without some work. I would have thought using ant
with fork=false would exercise the same path, but clearly Maven is doing
something different from that.

Maybe the best way forward is to give me detailed instructions on how to set
maven up in the way you have it, so I can debug at length.

Tests in project hierarchy do not adhere to maven conventions
-

Key: CONNECTORS-223
URL: https://issues.apache.org/jira/browse/CONNECTORS-223
Project: ManifoldCF
Issue Type: Bug
Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.3

Attachments: CONNECTORS-223.patch, test_reset.patch

Maven expects unit tests under .../src/test/java, and root-level project
tests under tests/xxx/src/test/java (or equivalent, along with their own
pom.xml at tests and tests/xxx). This is basically compatible with the ant
build except in location detail. The proposal is to move stuff around to
make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-20 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068326#comment-13068326
 ] 

Karl Wright commented on CONNECTORS-223:


I tried running mvn on the pom's currently checked in and I get this:

[ERROR] Failed to execute goal on project mcf-core: Could not resolve dependenci
es for project org.apache.manifoldcf:mcf-core:jar:0.3.0-SNAPSHOT: Could not find
 artifact com.bitmechanic:jdbcpool:jar:0.99 in central (http://repo1.maven.org/m
aven2) - [Help 1]
[ERROR]

Do you see this error too?


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-223.patch, test_reset.patch


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-20 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068334#comment-13068334
 ] 

Karl Wright commented on CONNECTORS-223:


r1148733.


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-223.patch, CONNECTORS-223_forkMode.patch, 
 test_reset.patch


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-20 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068363#comment-13068363
 ] 

Karl Wright commented on CONNECTORS-223:


With this and similar imports, I was able to get further.  Now I am stopped by 
the following error, which looks like something new:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:
2.1:copy (copy-war) on project mcf-jettyrunner: Unable to find artifact. Could n
ot find artifact org.apache.manifoldcf:mcf-api-service:war:0.3.0-SNAPSHOT
[ERROR]

Thoughts?  (I'm keeping all this information around in order to update the 
how-to-build-and-deploy page, FWIW.)

 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-223.patch, CONNECTORS-223_forkMode.patch, 
 test_reset.patch


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Issue Comment Edited] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-20 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068363#comment-13068363
 ] 

Karl Wright edited comment on CONNECTORS-223 at 7/20/11 1:24 PM:
-

With that import and a few other similar imports, I was able to get further.  
Now I am stopped by the following error, which looks like something new:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:
2.1:copy (copy-war) on project mcf-jettyrunner: Unable to find artifact. Could n
ot find artifact org.apache.manifoldcf:mcf-api-service:war:0.3.0-SNAPSHOT
[ERROR]

This is the result of mvn test.

Thoughts?  (I'm keeping all this information around in order to update the 
how-to-build-and-deploy page, FWIW.)

  was (Author: kwri...@metacarta.com):
With that import and a few other similar imports, I was able to get 
further.  Now I am stopped by the following error, which looks like something 
new:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:
2.1:copy (copy-war) on project mcf-jettyrunner: Unable to find artifact. Could n
ot find artifact org.apache.manifoldcf:mcf-api-service:war:0.3.0-SNAPSHOT
[ERROR]

Thoughts?  (I'm keeping all this information around in order to update the 
how-to-build-and-deploy page, FWIW.)
  
 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-223.patch, CONNECTORS-223_forkMode.patch, 
 test_reset.patch


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-20 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-223.


Resolution: Fixed

 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-223.patch, CONNECTORS-223_forkMode.patch, 
 CONNECTORS-223_jetty-runner.patch, test_reset.patch


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-19 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067802#comment-13067802
 ] 

Karl Wright commented on CONNECTORS-223:


r1148417.


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-223.patch, test_reset.patch


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-19 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067811#comment-13067811
 ] 

Karl Wright commented on CONNECTORS-223:


bq. Invoking more than one test ends up in a database not found error.

So let me be sure I understand the model.  These tests are all executing in one 
JVM, correct?  Can you attach a stack trace?  I suspect that the issue has to 
do with setup/teardown of the database; I believe that each test's cleanup 
method removes the database, so if the sequence looks like this, for tests A, 
B, and C:

setup (A)
setup (B)
setup (C)
(A)
(B)
(C)
cleanup (C)
cleanup (B)
cleanup (A)

... then this could happen.  But if the sequence is:

setup (A)
(A)
cleanup (A)
etc.

... then it is a complete mystery.  I should be able to tell what sequence it 
is from a trace though.


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-223.patch, test_reset.patch


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-19 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067837#comment-13067837
 ] 

Karl Wright commented on CONNECTORS-223:


I tried to simulate what maven does by changing the ant build's junit 
invocation from fork=true to fork=false.  When I do this without the 
patch, I get the same symptom as you see under Maven.  With the patch, however, 
it works fine.

I think perhaps there is a problem with your testing procedure?  I'm going to 
commit the patch changes now - could you synch up and try them again under 
maven?

r1148443.


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3

 Attachments: CONNECTORS-223.patch, test_reset.patch


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-18 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13066923#comment-13066923
 ] 

Karl Wright commented on CONNECTORS-223:


The only requirement I have for creation of the test databases and 
configuration files is that it must be possible to have multiple workareas 
checked out with on tests running on each so that the tests do not collide with 
one another.  Setting up paths that depend on resources may therefore not work.

Other than than, I'm open to any patch you want to propose.


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful

2011-07-18 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067324#comment-13067324
 ] 

Karl Wright commented on CONNECTORS-221:


Committed these changes to the branch.  r1148064.

 A CMIS connector would be helpful
 -

 Key: CONNECTORS-221
 URL: https://issues.apache.org/jira/browse/CONNECTORS-221
 Project: ManifoldCF
  Issue Type: New Feature
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
 Attachments: CONNECTORS-221-DEPENDENCIES.txt, 
 CONNECTORS-221-Java.txt, CONNECTORS-221-branch-build-patch-2.txt, 
 CONNECTORS-221-branch-build-patch-3.txt, 
 CONNECTORS-221-branch-java-patch-2.txt, 
 CONNECTORS-221-branch-java-patch-3.txt, CONNECTORS-221-branch-java-patch.txt, 
 CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, 
 CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, 
 screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, 
 screenshot-8.jpg


 Several people have asked if ManifoldCF supports CMIS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-15 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065748#comment-13065748
 ] 

Karl Wright commented on CONNECTORS-223:


Please go ahead, and attach the patch to this ticket; I'll commit it right away.



 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-15 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065780#comment-13065780
 ] 

Karl Wright commented on CONNECTORS-223:


Renaming the tests should not be hard.  But what about the test base classes?  
Since they begin with Test they will be executed independently, although they 
do not have any actual tests in them.  They do have expensive setup and 
teardown methods though.  Thus they should probably also be renamed to 
something that won't execute on its own.




 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-15 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065853#comment-13065853
 ] 

Karl Wright commented on CONNECTORS-223:


r1147086.  Let me know if there's anything further you need.


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful

2011-07-14 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065144#comment-13065144
]

Karl Wright commented on CONNECTORS-221:

You have to invoke the authority service to have the authority connector
invoked. This is an HTTP request. For example (if you have curl) curl
http://localhost:8345/mcf-authority-service/UserACLs?username=f...@bar.com;.

The Active Directory connector is not an exception at all. Other connectors
that have authorities are: Documentum, Livelink, and Meridio.

As for how to do this with CMIS, let's ask a few basic questions. First, does
CMIS have a notion of user groups? I see from your earlier comment that the
user id's might be something like johndoe or admin. Are there group ID's
too? Because all you really need to do at authority time is come up with the
list of user id's and group id's that correspond to a user, nothing having to
do with content.

A CMIS connector would be helpful
-

Key: CONNECTORS-221
URL: https://issues.apache.org/jira/browse/CONNECTORS-221
Project: ManifoldCF
Issue Type: New Feature
Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
Attachments: CONNECTORS-221-DEPENDENCIES.txt,
CONNECTORS-221-Java.txt, CONNECTORS-221-branch-build-patch-2.txt,
CONNECTORS-221-branch-java-patch-2.txt, CONNECTORS-221-branch-java-patch.txt,
CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt,
CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg,
screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg,
screenshot-8.jpg

Several people have asked if ManifoldCF supports CMIS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-14 Thread Karl Wright (JIRA)

Tests in project hierarchy do not adhere to maven conventions
-

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.3
Reporter: Karl Wright


Maven expects unit tests under .../src/test/java, and root-level project tests 
under tests/xxx/src/test/java (or equivalent, along with their own pom.xml at 
tests and tests/xxx).  This is basically compatible with the ant build except 
in location detail.  The proposal is to move stuff around to make the tests 
work with maven.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful

2011-07-14 Thread Karl Wright (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065219#comment-13065219
]

Karl Wright commented on CONNECTORS-221:

bq. Each CMIS repository could have different population, the username has
meaning only for a specific CMIS repository (it depends on the repositoryId
that could be added in the configuration).

So your pass-through authority connector would have to require you to specify
the repositoryId as part of its configuration information, even though it will
not use this value in any way. That will separate the user space and force the
MCF user to choose which user space they mean for the repository tokens.

bq. I'm not sure that I can implement this solution, but I can investigate.

The authority connector would not need to even communicate to the repository.
It would simply provide a MCF-user-specified regular-expression-based mapping
from the active directory user name to the user names used by that particular
repository, but would not involve the repository in this at all. It would
always return exactly one access token for a given user request.

Have a look at the null authority, which does almost what you need this to do.
You will need to add regular-expression-based mapping, that is all. See
ManifoldCF in Action chapter 8 for a description of how that can be done.

A CMIS connector would be helpful
-

Several people have asked if ManifoldCF supports CMIS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-14 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065257#comment-13065257
 ] 

Karl Wright commented on CONNECTORS-223:


I just ran into a potential issue.  The framework tests are organized as 
follows:

- the core test package consists of tests and a TestBase class
- the agents test package consists of tests and a TestBase class that extends 
the core TestBase class
- the pull-agent test package consists of tests and a TestBase class that 
extends the agents TestBase class

The question is, where should the TestBase classes live?  Will maven do the 
right thing if these are all moved, to core/src/test/java, 
agents/src/test/java, and pull-agent/src/test/java, respectively?  Or do we 
need specific mcf-core-test, mcf-agents-test, and mcf-pull-agent-test 
subprojects, for the test base classes?  How is this usually handled in Maven?


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright

 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-14 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065329#comment-13065329
 ] 

Karl Wright commented on CONNECTORS-223:


I've created a branch, 
https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-223, where 
I've started the rearrangement.  If you could have a look at the framework 
subproject in this branch to see if I have arranged things properly, that would 
be great.  If that all looks OK, I'm planning to tackle the connectors next, 
then the end-to-end tests.


 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright

 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-223) Tests in project hierarchy do not adhere to maven conventions

2011-07-14 Thread Karl Wright (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright resolved CONNECTORS-223.


   Resolution: Fixed
Fix Version/s: ManifoldCF 0.3
 Assignee: Karl Wright

 Tests in project hierarchy do not adhere to maven conventions
 -

 Key: CONNECTORS-223
 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.3


 Maven expects unit tests under .../src/test/java, and root-level project 
 tests under tests/xxx/src/test/java (or equivalent, along with their own 
 pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
 build except in location detail.  The proposal is to move stuff around to 
 make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-222) Would like support for building and running ManifoldCF under eclipse

2011-07-14 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065461#comment-13065461
 ] 

Karl Wright commented on CONNECTORS-222:


It might be worth considering using the maven Eclipse plug-in for this purpose. 
 As tobr dev says:

I also tried to import mcf into eclipse but it does not work in an easy way.
That's why I was looking for the maven integration.
It is really easy to import the modules using maven and the m2eclipse plugin
(Just import as maven project)...

The maven plugin is also able to depend on the current SNAPSHOT versions of
the project dependencies.

It may be worth looking into this approach.


 Would like support for building and running ManifoldCF under eclipse
 

 Key: CONNECTORS-222
 URL: https://issues.apache.org/jira/browse/CONNECTORS-222
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Framework agents process
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright

 Being able to build and run under Eclipse would allow people to develop 
 connectors and patches more readily.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-222) Would like support for building and running ManifoldCF under eclipse

2011-07-13 Thread Karl Wright (JIRA)

Would like support for building and running ManifoldCF under eclipse


 Key: CONNECTORS-222
 URL: https://issues.apache.org/jira/browse/CONNECTORS-222
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Framework agents process
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright


Being able to build and run under Eclipse would allow people to develop 
connectors and patches more readily.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful

2011-07-13 Thread Karl Wright (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065044#comment-13065044
 ] 

Karl Wright commented on CONNECTORS-221:


Any progress on an authority connector?


 A CMIS connector would be helpful
 -

 Key: CONNECTORS-221
 URL: https://issues.apache.org/jira/browse/CONNECTORS-221
 Project: ManifoldCF
  Issue Type: New Feature
  Components: CMIS connector
Affects Versions: ManifoldCF 0.3
Reporter: Karl Wright
 Attachments: CONNECTORS-221-DEPENDENCIES.txt, 
 CONNECTORS-221-Java.txt, CONNECTORS-221-branch-build-patch-2.txt, 
 CONNECTORS-221-branch-java-patch-2.txt, CONNECTORS-221-branch-java-patch.txt, 
 CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, 
 CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, 
 screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, 
 screenshot-8.jpg


 Several people have asked if ManifoldCF supports CMIS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

< 1 2 3 4 5 6 7 >

201 - 300 of 696 matches

Mail list logo