my customer.xsd выглядит так. /> 1) не удалось найти документ; < /p>
2) документ не может быть прочитал; < /p>
3) Корневой элемент документа не является < /code>. < /p>
Я использую Maven для преобразования xsd в клазы Java. < /p>
Elements of this type are import-only and will never be exported.
Furthermore, elements of this type will be handled only if included in
a customer import file (customer.xsd) but are ignored if included in a
customer list import (customerlist2.xsd).
The reason for this discrepancy is that customer groups are site-specific,
and customer import is always done in the context of a site whereas customer
list import is not.
This element will never appear in a customer list export file (customerlist2.xsd)
but may be included in a customer export (customer.xsd). This element will also
be ignored if specified in a customer list import but will be processed in
a customer import.
The reason for this discrepancy is that customer groups are site-specific,
and customer export is always done in the context of a
site where as customer list export is not.
If a customer is managed externally (i.e. provider-id and external-id are specified)
then the password is always optional. Otherwise, a password is required for any of
the following scenarios:
* creation of a new customer
* importing a customer in REPLACE mode
* changing the login of a customer
The element 'provider-id' has been deprecated. Use external-profiles to manage provider-id/external-id pairs.
The element 'external-id' has been deprecated. Use external-profiles to manage provider-id/external-id pairs.
Support for the md5 encryption algorithm has changed. Passwords imported in md5 will be stored as an scrypt'd value.
Represents an encrypted or plain value and contains information on how to deal with it during import.
Import: If the attribute 'encrypted' is set to false, the content of this tag will be encrypted
using the new scrypt algorithm. 'encryptionScheme' should be 'null' in this case.
If the attribute 'encrypted' is set to true, it is assumed that the given password was encrypted
with the algorithm in 'encryptionScheme' (md5, scrypt, or the internal implementation s0001).
The password will be imported 'as is'.
Export: The attribute 'encrypted' will always be set to true. The attribute 'encryptionScheme'
will reflect the encryption scheme of the password in the database (md5 (deprecated), scrypt, or the internal implementation s0001).
The encrypted password will not be transformed during export.
Represents the assignment of a customer to a customer group.
When a <group-assignment> element is imported, the customer with the specified
customer-no is assigned to the customer group with the specified group-id. If an assignment
already exists, no change is made.
When an element is imported with attribute mode="delete", the assignment of the customer
with the specified customer-no to the customer group with the specified group-id is removed.
If the customer is not assigned to the group, no change is made.
When mode="delete", either the customer-no or group-id attribute can be omitted to remove
multiple assignments of customers to customer groups. If only customer-no is present, any
existing assignments of the specified customer to groups are removed. If only group-id is
present, any existing assignments of customers to the specified group are removed.
Assignments can only be created or removed for static customer groups. A warning message
is logged if a specified customer group is dynamic.
Allowed string values are the 'int' values defined for the Customer.gender attribute, and additionally the values 'male' and 'female' for backward compatibility.
The allowed character set for the login element is
limited to [A-Z a-z 0-9 .@_-].
Подробнее здесь: https://stackoverflow.com/questions/547 ... va-classes
