blob: 2bf88fd70ee88d0a1d12572be2c3c09335a14b9f [file] [log] [blame]
<!--
/***************************************************************************************************************************
* Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the
* specific language governing permissions and limitations under the License.
***************************************************************************************************************************/
-->
Serializing
<p>
The following methods are used for serializing <code>Config</code> objects back into INI files:
</p>
<ul class='doctree'>
<li class='jc'>{@link oaj.config.Config}
<ul>
<li class='jm'>{@link oaj.config.Config#writeTo(Writer) writeTo(Writer)}
<li class='jm'>{@link oaj.config.Config#toString() toString()}
</ul>
</ul>
<p>
Both methods are thread safe.
</p>
<p>
The <code>Config</code> class implements the {@link oaj.Writable} which means it can be
returned as-is by REST methods to be serialized as INI text.
</p>