Re: [infinispan-dev] XML config validation not happening?
Ok, I managed to handle this case with use of xml adapters for
clustering type. It is fairly simple. The end result being that xml
schema does not constrain mode attribute of clustering element. Only
first character of clustering mode is looked at along with presence of
<sync> or <async> in order to set appropriate cache mode. Therefore, we
are handling this exactly as before except we are not tightly
constraining mode string in schema. If needed, this can be done by hand.
Good enough?
On 11/08/09 5:00 PM, Galder Zamarreno wrote:
As a side note, I liked the way cache mode was previously configured
via
this combo:
- cache mode: invalidation, replication or distribution
- and<sync>/<async> elements to indicate whether it's sync or not sync.
If cache mode now incorporates sync/async works on the name itself, that
means that when switching between sync to async and viceversa, you have
to change two things, the cache mode name, plus the<sync>/<async> XML
elements. This duplicity of efforts could lead to confusion and wrong
doing by the users.