My test:

// create a connector server with a correct map parameter map1
connectorServer = new GenericConnectorServer(map1, mbs);

// create a connector with a correct map parameter map2
connector = new GenericConnector(map2);

// connect the connector with an erroneous map parameter map3
// expected IOException
try {
  connector.connect(map3);
}
catch (IOException e) {
  ref.println("(OK) Expected IOException raised");
}

// connect again without map parameter
connector.connect();

Here i expect the connector to use the default map passed
to it constructor.
Instead, it seems that the first connect call overrides the map parameter
definitively (and not only for the connect call).

It is not clear in the javadoc what is the expected behavior in this case.
But the JMXMP implementation (which redefines the connect method)
has the "expected", well, let's say the "more natural" behavior.

Also, note that my implementation does not redefine the connect method.

TCK test :
api/javax/management/remote/generic/GenericConnector/index.html#GenericConnectorTest
Test case : ConnectorConnect009

###@###.### 2003-10-07