[
https://issues.apache.org/jira/browse/DIRSERVER-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531402
]
Ole Ersoy commented on DIRSERVER-1079:
--------------------------------------
I'm just commenting here (I've mentioned this in different contexts, but
figured I'd mention it again just as a backdrop). I first have to assume the
following with respect to the task though:
ASSUMPTION
There's a model instance that's created when server.xml is parsed. When this
model (Class files are added, mutated, or deleted) is updated, server.xml must
also be upated manually and the parsing of server.xml must then be tested to
verify that the xml representation of the model still "Fits" the model.
So that's the assumption. The IDEAL section below will be most useful if the
assumption is right :-).
IDEAL
Use XML Schema to generate the model. Then use something like Tuscany or EMF
or even Maven modello to generate the corresponding components (Java Beans) to
house the model instances. This way server.xml is always up to date and the
only concern for the developer is whether the model has configuration needed by
server services.
> Add module under apachds to test that the server.xml is up to date
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1079
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1079
> Project: Directory ApacheDS
> Issue Type: Sub-task
> Affects Versions: bigbang
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: bigbang
>
>
> As we make changes we need to remember to update the server.xml default file.
> However since this is overlooked quit often it's a good idea to just add a
> module to test that this server.xml file is working.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
