org.forgerock / org.forgerock.openidm

19 Nov, 2012

1 commit

15 Nov, 2012

1 commit

  • f5fe64ad   UI branch changes, r1480-1529 ... Browse Dir » 
    http://sources.forgerock.org/cru/CR-891

This also includes global rename of _query-id to _queryId and _query-expression to _queryExpression.

Note for documenters: there are several changes expected to be made soon; review the code review (linked above) and note Andi's comments

git-svn-id: https://svn.forgerock.org/openidm/trunk@1531 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     

12 Nov, 2012

1 commit

  • 60d0d9cf   Merging UI branch, r1455-1477 ... Browse Dir » 
    Updates for UI: Corrected policy, max security answer attempts, task/workflow updates.
http://sources.forgerock.org/cru/CR-862

git-svn-id: https://svn.forgerock.org/openidm/trunk@1485 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     

08 Nov, 2012

1 commit

05 Nov, 2012

1 commit

  • 014cce17   OPENIDM-749 / CR-805 - OpenIDM started with new Launcher ... Browse Dir » 
    Assign directories to different location:
bin => install-location
bundle => install-location
conf => project-location
connectors => install-location
db => work-location
logs => work-location
script => project-location
security => install-location
workflow => install-location


git-svn-id: https://svn.forgerock.org/openidm/trunk@1426 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    Laszlo
     

02 Nov, 2012

1 commit

  • 90127ab2   CR-824 ... Browse Dir » 
    Merging in changes from UI branch to trunk

git-svn-id: https://svn.forgerock.org/openidm/trunk@1412 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     

18 Oct, 2012

1 commit

  • 5bfe13c6   OPENIDM-767 Return ISO8601 compatible dates in workflow response ... Browse Dir » 
    OPENIDM-768 Remove processDefinitionId and/or key from workflow process variables when starting a workflow 
OPENIDM-771 Change HTTP 400 return code to 403 where there is no operation implemented on the requested resource in workflow API 
OPENIDM-773 Add some missing attributes to the GET /workflow/processdefinition response object 
OPENIDM-774 Add superProcessInstanceId to the /workflow/processinstance/{id} response object
OPENIDM-775 Return HTTP 404 when the requested workflow resource is not found 
OPENIDM-776 Add some missing attributes to the GET /workflow/taskinstance response object
CR-771

git-svn-id: https://svn.forgerock.org/openidm/trunk@1314 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    omebold
     

11 Oct, 2012

1 commit

25 Sep, 2012

1 commit

20 Sep, 2012

1 commit

07 Sep, 2012

1 commit

05 Sep, 2012

1 commit

13 Aug, 2012

1 commit

07 Aug, 2012

1 commit

03 Aug, 2012

1 commit

26 Jul, 2012

1 commit

06 Jul, 2012

1 commit

05 Jun, 2012

1 commit

25 May, 2012

1 commit

10 Apr, 2012

1 commit

22 Feb, 2012

1 commit

09 Feb, 2012

2 commits

08 Feb, 2012

1 commit

15 Dec, 2011

1 commit

14 Dec, 2011

2 commits

12 Dec, 2011

1 commit

06 Dec, 2011

1 commit

05 Dec, 2011

8 commits

02 Dec, 2011

2 commits

01 Dec, 2011

1 commit

  • 745881bd   Introduce line unfolding and refolding in <screen> output for HTML ... Browse Dir » 
    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
    mark