Remove requirement of mapping element from cfg.xml

deployed with 0.8

schema changed

This is a simple patch to nhibernate-configuration-2.0.xsd (add MinOccurs='0' to the mapping element). I have created a simple application that uses a cfg.xml file with no mappings & adds mappings programatically and this works fine.

This feature is
in line with current hibernate cfg.xml files and with the following use case:

1) Need to use more then one database like in EI scenarios.
( so cant use app.config)
2) Want to keep connection info configurable( so: dont hardcode configuration but use cfg.xml)
3) Want to keep class-persist info either programmatically( no problem hardcoding there I think) or in its own class.hbm.xml files.

Regards,
R

It will need to be done anyway when a nhibernate config section is built and replaces the current <add key="" value="" /> handling there is now.