Oh, but you might glean something from the Chapter 9 example, with is
still under development but may have enough stuff in it to be
interesting.
Once the 0.2-incubating release goes out the door, I'd like to propose
that the next release be considered a ManifoldCF in Action book
release. Basically this will mean that we need a release that is
consistent with the examples and explanations in the book, before the
book actually is done.
If you have an eclipse settings file or documentation, please consider
contributing it! I know other people like and use eclipse, even
though I don't. ;-)
Karl
On Fri, Apr 29, 2011 at 8:12 PM, daddy...@gmail.com daddy...@gmail.com wrote:
I am not sure but it is likely related to postgresql
Yes, I plan on contributing my work. I have successfully setup the war
files and the agent code from within eclipse where I can break through
any of the code!!! I need to sit down and write down the steps and
capture a clean project structure, it took literally a week to figure it
out. Once
So I just learnt that you can not reuse a stream. In my code I create
a hash from the file content, and the
So I just learnt that you can not reuse a stream. In my code I create
a hash from the file content, and then I want to sent it via http to the
archive server. You guessed it the InputStream is not valid anymore.
The best solution I've figured out was to read the content into a
temporary
Using a temporary file is the right approach.
Karl
On Mon, May 2, 2011 at 12:30 PM, ho...@farzad.net wrote:
So I just learnt that you can not reuse a stream. In my code I create a
hash from the file content, and then I want to sent it via http to the
archive server. You guessed it the
I'm creating the temp file in the addOrReplaceDocument method
(BaseOuputConnector Interface), if the temp file creation fails, what
would be the right return code. Right now I'm choosing between
DOCUMENTSTATUS_ACCEPTED or DOCUMENTSTATUS_REJECTED, what is the right
way of communicating an
If you fail to create the temporary file, I'd just throw a ManifoldCFException.
Karl
On Mon, May 2, 2011 at 1:36 PM, ho...@farzad.net wrote:
I'm creating the temp file in the addOrReplaceDocument method
(BaseOuputConnector Interface), if the temp file creation fails, what would
be the right
Active directory authority doesn't handle unknown user case properly
Key: CONNECTORS-195
URL: https://issues.apache.org/jira/browse/CONNECTORS-195
Project: ManifoldCF
[
https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-195:
---
Attachment: CONNECTORS-195.patch
Patch which may work to resolve the issue
Active
Is there a place where the sequence of interface calls between Manifold
Engine and the Output Connector is listed. I'm interested in what is
called when the user is doing:
1) Add new output connection
2) Create a new job with that output connection
3) Start the job
4) Pause the job
5) Abort
The book explains all of this in great detail, as well as logging
conventions. This all begins in Chapter 5, which is the next chapter
to be released via MEAP.
Logging for an output connector should use the
org.apache.manifoldcf.agents.system.Logging.ingest logger. You enable
that logger with
Last time I was working hard at this, it seems that I added the ability
to store data in the threadContext object. See code below. Can't
remember if this is the correct way, or I figured a work around? : ) If
it is correct, it would be right vehicle for the session id too.
Thanks!
Thread contexts should not be linked cross-thread. For managing
sessions, it seems to me that there are two possible models, as
described below:
(1) For any given configuration, there's ONE session ID shared among
all connector class instances which share that configuration.
OR
(2) Each
15 matches
Mail list logo
