15 Dec, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@625 d98387aa-ee2c-4292-a9e6-504d2a719fd3
14 Dec, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@619 d98387aa-ee2c-4292-a9e6-504d2a719fd3
13 Dec, 2011
5 commits
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@615 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@612 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
…he chapter that explains sync.json git-svn-id: https://svn.forgerock.org/openidm/trunk@611 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@610 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@609 d98387aa-ee2c-4292-a9e6-504d2a719fd3
12 Dec, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@605 d98387aa-ee2c-4292-a9e6-504d2a719fd3
09 Dec, 2011
12 commits
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@594 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@593 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@592 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@591 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@590 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@589 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@588 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@587 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@586 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@585 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@584 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@583 d98387aa-ee2c-4292-a9e6-504d2a719fd3
06 Dec, 2011
4 commits
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@575 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@574 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@573 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
I'd recommend <section> instead of <sect1> <sect2> <sect3> etc. as the stylesheets know how to handled nested <section> elements, and docs are easier to restructure when sections are not numbered. git-svn-id: https://svn.forgerock.org/openidm/trunk@572 d98387aa-ee2c-4292-a9e6-504d2a719fd3
05 Dec, 2011
7 commits
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@570 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@569 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@567 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@566 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@564 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@563 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@562 d98387aa-ee2c-4292-a9e6-504d2a719fd3
02 Dec, 2011
2 commits
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@557 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
…e works appears to have changed since the doc was last updated git-svn-id: https://svn.forgerock.org/openidm/trunk@556 d98387aa-ee2c-4292-a9e6-504d2a719fd3
01 Dec, 2011
1 commit
-
The idea is that when you break long lines in <screen> at a space character, the reader can double-click to collapse folded lines to a single line for easy copying into a terminal window, and then double-click again to refold the lines for easy reading. Line continuations with \ would allow folded lines to be used directly, at least on *n*x, and also be syntactically correct. Yet, its harder to edit a command that used \ to continue lines. The JavaScript expects line continuations where continued lines start with a space. Lines without initial spaces do not get collapsed. For example: <screen>$ curl --user admin:admin -X PUT -d '{ "name":"joe", "firstname":"joe", "lastname":"smith", "email":"joe@abc.com", "userPassword":"11111111"}' http://localhost:8080/openidm/managed/user/joe {"_rev":"0","_id":"joe"}</screen> Shows up as: $ curl --user admin:admin -X PUT -d '{ "name":"joe", "firstname":"joe", "lastname":"smith", "email":"joe@abc.com", "userPassword":"11111111"}' http://localhost:8080/openidm/managed/user/joe {"_rev":"0","_id":"joe"} And then when you double-click: $ curl --user admin:admin -X PUT -d '{ "name":"joe", "firstname":"joe", "lastname":"smith", "email":"joe@abc.com", "userPassword":"11111111"}' http://localhost:8080/openidm/managed/user/joe {"_rev":"0","_id":"joe"} And vice versa. There's no doubt cleanup to do in the core doc sources to take advantage of this. git-svn-id: https://svn.forgerock.org/openidm/trunk@551 d98387aa-ee2c-4292-a9e6-504d2a719fd3
30 Nov, 2011
2 commits
-
I did comment out the note about disabling the reconciliation sample, because the config file had "enabled":false when I looked after installing today. By the way, if you want external URLs to open in a new tab, you can use xlink:show="new" on the <link>. git-svn-id: https://svn.forgerock.org/openidm/trunk@549 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
Notice that you get syntax highlighting by adding a language attribute, such as language="javascript", to block elements that preserve whitespace like <programlisting> or <screen>. I'm not particularly proud of the colors defined in src/main/docbkx-stylesheets/html/coredoc.xsl. Perhaps someone less aesthetically challenged could fix that. git-svn-id: https://svn.forgerock.org/openidm/trunk@547 d98387aa-ee2c-4292-a9e6-504d2a719fd3
29 Nov, 2011
2 commits
-
…r to create or read managed user JSON. git-svn-id: https://svn.forgerock.org/openidm/trunk@543 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
This works around http://code.google.com/p/docbkx-tools/issues/detail?id=36 allowing links that work in the HTML, and look like this in the source: refer to the chapter on <link xlink:href="admin-guide#chap-troubleshooting" xlink:role="http://docbook.org/xlink/role/olink"><citetitle >Troubleshooting</citetitle></link> in the <citetitle>Administration Guide</citetitle>. As the olinkdb files are not currently built for other formats, the xlink:role="http://docbook.org/xlink/role/olink" links are ignored during output generation. git-svn-id: https://svn.forgerock.org/openidm/trunk@542 d98387aa-ee2c-4292-a9e6-504d2a719fd3
21 Nov, 2011
2 commits
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@520 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@519 d98387aa-ee2c-4292-a9e6-504d2a719fd3