Hi, Rushabh:

The Java API client calls the REST API to perform a document insert on the 
server.  Whether
the document insert invokes the trigger depends on how the server is 
configured, not on how
the Java is written.

In particular, take a look at how the domain qualifies documents.  You could 
test a document
insert with XQuery within QueryConsole to see if you can isolate why the 
pipeline isn't firing.


Hoping that helps,


Erik Hennum

________________________________
From: [email protected] 
[[email protected]] on behalf of Rushabh M 
[[email protected]]
Sent: Friday, January 04, 2013 2:13 AM
To: [email protected]
Subject: [MarkLogic Dev General] Java API Ingestion issue

Hello,

I would like your advise on an issue I have been facing while ingesting data 
through Java API wrapper in ML 6.0.
When Ingesting data through Java API into a MarkLogic database the Pipelines 
connected to that database are not triggered. But when
Below are further details and the API code.

I have custom pipeline which convets meta data to xml elements and is attached 
to this domain. When I am ingesting data into database through App builder flow 
or Bulk load the documents are creating ie as is document and a xhtml. But when 
inserting through Java API only the document is getting created
I am ingesting through JAVA API into HTTP Port(8010) created on the Database. 
No XDBC server involved.

DatabaseClient client = DatabaseClientFactory.newClient("localhost", 8010, 
"rest-writer", "x", Authentication.DIGEST);


FileInputStream docStream = new 
FileInputStream("/home/482251/Desktop/Test/Resume/482251_Resume.doc");

XMLDocumentManager docMgr = client.newXMLDocumentManager();

// create a handle on the content
InputStreamHandle handle = new InputStreamHandle(docStream);

// write the document content
docMgr.write("/home/482251/Testt/resume.doc", handle);


=====-----=====-----=====

_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to