20 Sep, 2012
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@1230 d98387aa-ee2c-4292-a9e6-504d2a719fd3
03 Aug, 2012
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@1132 d98387aa-ee2c-4292-a9e6-504d2a719fd3
26 Jul, 2012
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@1110 d98387aa-ee2c-4292-a9e6-504d2a719fd3
25 May, 2012
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@1077 d98387aa-ee2c-4292-a9e6-504d2a719fd3
06 Dec, 2011
1 commit
-
…able via GET http://localhost:8080/openidm/workflow/activiti git-svn-id: https://svn.forgerock.org/openidm/trunk@571 d98387aa-ee2c-4292-a9e6-504d2a719fd3
02 Dec, 2011
1 commit
-
…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
25 May, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@211 d98387aa-ee2c-4292-a9e6-504d2a719fd3