title: hazelcast vs hazelcast-client configuration
body: <p>Have been using Hazelcast 3.4.3 with the following, basic <code>hazelcast.xml</code> for testing:</p>
  
  <pre><code>&lt;hazelcast-client 
    xsi:schemaLocation="http://www.hazelcast.com/schema/client-config hazelcast-client-config-3.3.xsd"
    xmlns="http://www.hazelcast.com/schema/client-config"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  &gt;
  
    &lt;group&gt;...&lt;/group&gt;
  
    &lt;properties&gt;...&lt;/properties&gt;
  
    &lt;network&gt;
      &lt;port auto-increment="true"&gt;5701&lt;/port&gt;
      &lt;join&gt;...&lt;/join&gt;
    &lt;/network&gt;
  
    &lt;executor-pool-size&gt;10&lt;/executor-pool-size&gt;
  
    &lt;security&gt;
      &lt;credentials&gt;com.hazelcast.security.UsernamePasswordCredentials&lt;/credentials&gt;
    &lt;/security&gt;
  
    &lt;load-balancer type="random"/&gt;
  
  &lt;/hazelcast-client&gt;
  </code></pre>
  
  <p>After bumping the version of the dependency to 3.6 (or even just 3.5.5), Hazelcast fails to initialize with "Your xsd schema couldn't be load" (sic).</p>
  
  <p>If I add an additional dependency on the <code>hazelcast-client</code> artifact (which contains the missing schema file), I get this error instead: "Invalid content was found starting with element 'port'".</p>
  
  <p>Looks like Hazelcast now requires a separate server and client config? What's strange is that I can't find any mention of such a change in the release notes...</p>