Hi Geert, Thanks for your reply. Yeah plugin is configurable. You need to provide host and port from the alfresco channel. Plugin will not require any change. Only you have to modify the REST url's so that it can fit to your need.
Thanks Abhinav kumar mishra On 8 May 2014 17:27, <[email protected]> wrote: > Send General mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://developer.marklogic.com/mailman/listinfo/general > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of General digest..." > > > Today's Topics: > > 1. Re: YAML support (Geert Josten) > 2. Re: Testing for invalid URI before fn:doc() gets to it > (Michael Sokolov) > 3. Re: Marklogic and Alfresco Integration & Challenges (Geert > Josten) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 8 May 2014 13:33:13 +0200 > From: "Geert Josten" <[email protected]> > Subject: Re: [MarkLogic Dev General] YAML support > To: "'MarkLogic Developer Discussion'" > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > Hi Mohamad, > > > > If you have an XSLT that can convert a single YAML text document into its > YAXML representation, than it should be trivial to hook that XSLT into an > MLCP ingest to have it applied while importing documents. That XSLT > shouldn't be much more difficult than the one going the other way, though > it might help make an EBNF for YAML and feed that into a parser generator, > for example bottlecap.de/rex.. > > > > Kind regards, > > Geert > > > > Van: [email protected] [mailto: > [email protected]] Namens David Ennis > Verzonden: dinsdag 6 mei 2014 20:43 > Aan: MarkLogic Developer Discussion > Onderwerp: Re: [MarkLogic Dev General] YAML support > > > > HI. > > > > This might be a starting point for you: > > > > It is a draft guideline of an XML representation of YAML - called YAXML. > > > > http://yaml.org/xml.html > > The sample shows the other way around - XML ->xslt -> yaml, but it does > outline how the various parts of a YAML file are represented in XML. So, > if you already have a parser for your YAML files, perhaps they could be > used to pre-process them to YAXML format before ingestion. The sample > stylesheet on the website should be a starting point of being able to > transform back to YAML on the way out of MarkLogic. > > > > > > Looking forward: MarkLogic 8 promises to deliver server-side javascript > support.. Considering that there are already great Javascript YAML > libraries, it would seem that in the future, you could harness one of these > to convert YAML to YAXML on ingestion.... > > > > Kind Regards, > > David > > > > On 6 May 2014 15:56, Mohamad Thahir <[email protected] <mailto: > [email protected]> > wrote: > > Does MarkLogic support YAML for ingestion? Can someone recommend best way > to ingest YAML docs > > Sent from my iPhone > _______________________________________________ > General mailing list > [email protected] <mailto:[email protected]> > http://developer.marklogic.com/mailman/listinfo/general > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://developer.marklogic.com/pipermail/general/attachments/20140508/8f65846e/attachment-0001.html > > ------------------------------ > > Message: 2 > Date: Thu, 08 May 2014 07:56:45 -0400 > From: Michael Sokolov <[email protected]> > Subject: Re: [MarkLogic Dev General] Testing for invalid URI before > fn:doc() gets to it > To: MarkLogic Developer Discussion <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I'm pretty sure doc (' ') (i.e. doc (' ')) throws an invalid uri > exception on every version, if you need a test case. > > -Mike > > On 4/30/2014 12:09 PM, Michael Blakeley wrote: > > With 7.0-2.3 I'm having a hard time finding anything that fails: > doc('tug%x') and doc('some.php?module=/path/with/badURI') and > doc('!@#$%^&*()') and even doc('{') all work for me. It makes sense for > fn:doc to be very permissive. > > > > Anyway I would just use try-catch. Performance should not be a problem, > if you are worried about that. Any database lookup should be more expensive > than a try-catch, and some simple tests confirm that. > > > > doc('a'), xdmp:elapsed-time() > > => PT0.000045S > > > > try { doc('a') } > > catch ($ex) { $ex }, > > xdmp:elapsed-time() > > => PT0.000045S > > > > Profiling shows that the second expression is dominated by the call to > fn:doc, which is what I'd expect. > > > > -- Mike > > > > On 30 Apr 2014, at 07:32 , David Sewell <[email protected]> wrote: > > > >> A rare 500 error showed up in our logfile recently that was the evident > result > >> of someone trying to mount an injection attack via URIs meant to pass > code to > >> PHP. We have pretty solid handling of server-side errors so there's no > real > >> security problem, but I'm a bit stumped as to how to tighten our calls > to > >> fn:doc() to prevent them handling invalid URIs. > >> > >> Basically, the ErrorLog.txt error was similar to > >> > >> XDMP-URI: (err:FODC0005) fn:doc("some.php?module=/path/with/badURI") -- > Invalid > >> URI format: "some.php?module=/path/with/badURI" > >> > >> where the argument to fn:doc() contained the attempted injection string. > >> > >> The specs for fn:doc($uri as xs:string?) say "if $uri is not a valid > URI, an > >> error may be raised [err:FODC0005]." Clear enough, and I could just put > a > >> try/catch around the call to fn:doc(). But what I'd rather do is to > test for URI > >> validity before passing the string to fn:doc() in the first place. > >> > >> I thought that testing along the lines of > >> > >> if ($string castable as xs:anyURI) then .... > >> > >> would do it, but that appears to return true no matter what string it > receives. > >> For example, > >> > >> "tug%x" castable as xs:anyURI > >> > >> returns true. (Saxon and BaseX return false--should MarkLogic?) > >> > >> Is there any alternative to try/catch here? > >> > >> > >> > >> -- > >> David Sewell, Editorial and Technical Manager > >> ROTUNDA, The University of Virginia Press > >> PO Box 400314, Charlottesville, VA 22904-4314 USA > >> Email: [email protected] Tel: +1 434 924 9973 > >> Web: http://rotunda.upress.virginia.edu/ > >> _______________________________________________ > >> General mailing list > >> [email protected] > >> http://developer.marklogic.com/mailman/listinfo/general > >> > > _______________________________________________ > > General mailing list > > [email protected] > > http://developer.marklogic.com/mailman/listinfo/general > > > > ------------------------------ > > Message: 3 > Date: Thu, 8 May 2014 13:56:55 +0200 > From: "Geert Josten" <[email protected]> > Subject: Re: [MarkLogic Dev General] Marklogic and Alfresco > Integration & Challenges > To: "'MarkLogic Developer Discussion'" > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > Hi Abhinav, > > > > I'd expect you don't need to change java code to point to a specific > host/port. It looks like there is configuration code, probably to make it > configurable from within Alfresco. Zaizi at zaizi.com or @zaizi can > likely give more accurate pointers.. > > > > Cheers, > > Geert > > > > Van: [email protected] [mailto: > [email protected]] Namens abhinav mishra > Verzonden: woensdag 7 mei 2014 19:57 > Aan: [email protected] > Onderwerp: Re: [MarkLogic Dev General] Marklogic and Alfresco Integration > & Challenges > > > > Thanks Mike for the reply. > > > > I happy to inform that i am able to integrate the Alfresco with Marklogic > after doing some extensive research. > > Sharing the steps, hope it may help others. Because i was helpless when > started with it. > > > > Steps: > > 1- Create the jar file with the help of Alfresco add-on provided on " < > https://github.com/zaizi/marklogic-alfresco-integration> > https://github.com/zaizi/marklogic-alfresco-integration"; > > > > 2- Place the jar file inside alfresco classpath. > > > > 3- Place the config files to "\tomcat\shared\classes\alfresco" > > > > 4- Create a REST interface on ML server, and modify the URL inside the > MarkLogicPublishingHelper.java as per your rest interface. > > > > 5- Restart the alfresco. > > > > Start publishing your content from Alfresco to ML through MarkLogic > channel. > > > > > > > > > Regards, > Abhinav Kumar Mishra > > > > > > On Mon, Apr 28, 2014 at 9:55 PM, abhinav mishra > <[email protected]<mailto: > [email protected]> > wrote: > > > > I want to integrate Alfresco and Marklogic, means Alfresco as a front-end > and Marklogic as data storage. Alfresco as ECM has very good user > interface and Marklogic has Content management capablities. So the > combination of the both can build a very rich app. > > > > What are challenges and dependencies for Integrating MarkLogic and > Alfresco ? > > > > I have downloaded the Add-On from Alfresco website (github link mentioned > below), but i am not able to integrate it. > > > > "https://github.com/zaizi/marklogic-alfresco-integration"; > > > > > > Is there any other adapter to achieve the integration ? > > > > Please help. > > > > > > Regards, > Abhinav Kumar Mishra > > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://developer.marklogic.com/pipermail/general/attachments/20140508/66731102/attachment.html > > ------------------------------ > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > > > End of General Digest, Vol 119, Issue 13 > **************************************** >
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
