You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Seelmann (JIRA)" <ji...@apache.org> on 2007/08/02 00:01:53 UTC
[jira] Created: (DIRSTUDIO-160) Support for ADS 1.5.1 configuration
Support for ADS 1.5.1 configuration
-----------------------------------
Key: DIRSTUDIO-160
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-160
Project: Directory Studio
Issue Type: New Feature
Components: studio-apacheds-configuration
Affects Versions: 0.8.1, 0.8.0
Reporter: Stefan Seelmann
The current version of ADS configuraton plugin is only usable for ADS 1.5.0. We should also support the 1.5.1 server.xml layout.
Perhaps the following approach would work:
- When loading an existing config file we could add some kind of auto-detection. If the file is invalid to the 1.5.0 XML-Schema/DTD then try the other.
- When creating a new file the version could be selected in the wizard.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSTUDIO-160) Support for ADS 1.5.1 configuration
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot closed DIRSTUDIO-160.
--------------------------------------------
Resolution: Duplicate
Assignee: Pierre-Arnaud Marcelot
Duplicate of DIRSTUDIO-236.
Sorry Stefan, I did not see you had created this one...
> Support for ADS 1.5.1 configuration
> -----------------------------------
>
> Key: DIRSTUDIO-160
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-160
> Project: Directory Studio
> Issue Type: New Feature
> Components: studio-apacheds-configuration
> Affects Versions: 0.8.0, 0.8.1
> Reporter: Stefan Seelmann
> Assignee: Pierre-Arnaud Marcelot
>
> The current version of ADS configuraton plugin is only usable for ADS 1.5.0. We should also support the 1.5.1 server.xml layout.
> Perhaps the following approach would work:
> - When loading an existing config file we could add some kind of auto-detection. If the file is invalid to the 1.5.0 XML-Schema/DTD then try the other.
> - When creating a new file the version could be selected in the wizard.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.