|
|
Displaying issues 1 to 8 of 8 matching issues.
 |
PETALSESBCONT-250
|
The topology service uses the WSAPI
|
Christophe DENEUX
|
Christophe DENEUX
|
|
Resolved
|
Fixed
|
2013-04-03
|
2016-02-02
|
12 years, 31 weeks, 5 days ago
|
| |
PETALSESBCONT-234
|
The topology service must throw its own exceptions
|
Christophe DENEUX
|
Christophe DENEUX
|
|
Resolved
|
Fixed
|
2013-03-12
|
2013-03-14
|
12 years, 35 weeks, 1 day ago
|
 |
PETALSESBCONT-223
|
The topology configuration resource should be read by the launcher instead of the kernel
|
Christophe DENEUX
|
Christophe DENEUX
|
|
Resolved
|
Fixed
|
2013-02-13
|
2013-03-12
|
12 years, 39 weeks ago
|
| |
PETALSESBCONT-222
|
Remove support of the domain mode "autodiscover"
|
Christophe DENEUX
|
Christophe DENEUX
|
|
Resolved
|
Fixed
|
2013-02-12
|
2013-02-12
|
12 years, 39 weeks, 1 day ago
|
| |
PETALSESBCONT-220
|
Remove support of the domain mode "standalone"
|
Christophe DENEUX
|
Christophe DENEUX
|
|
Resolved
|
Fixed
|
2013-02-12
|
2013-02-12
|
12 years, 39 weeks, 1 day ago
|
| |
PETALSESBCONT-218
|
The default value of the property 'petals.topology.url' must be changed to be relative to the local configuration resource
|
Christophe DENEUX
|
Christophe DENEUX
|
|
Resolved
|
Fixed
|
2013-02-08
|
2013-03-12
|
12 years, 39 weeks ago
|
| |
PETALSESBCONT-53
|
Add an API to parse a topology configuration from an InputStream
|
Christophe DENEUX
|
Christophe DENEUX
|
|
Resolved
|
Fixed
|
2010-09-10
|
2013-02-06
|
12 years, 40 weeks ago
|
| |
PETALSESBCONT-51
|
The topology configuration should be read by the petals launchers and not by the kernel itself
|
Christophe DENEUX
|
Christophe DENEUX
|
|
Resolved
|
Duplicate
|
2010-09-10
|
2013-03-12
|
15 years, 9 weeks, 5 days ago
|
|
|
