Yes, I had to re-write the importer to handle nulls and empty spaces when getting products from Magento. There are nulls and empty spaces because in Magento there are parent products that do not have values filled in for all of the necessary attributes. The code in the importer will do a hard fail if it encounters this, throwing this above exception. Changing the code to handle the nulls or empty spaces will allow the importer to continue on and import the parents and their children.
Also, there were a few key gotchas that were not documented anywhere.
1.) The connection string to the importer is: <sever_name>/index.php
- it will create the path to the Magento product catalog on its own through the service. Trying to add the full path to the catalog or <sever_name>/index.php/admin does not allow the identity provider to authenticate against the Magento instance and throws a poorly handled exception.
2.) Make sure that the Magento identity provider in your OSGI configs is just the server name, no other paths are needed.
3.) To get the images to be in the dam you will have to get SSH access to the actual images on the Magento server, down them locally, and use the acs-commons tool to do a bulk asset importer into AEM.
- the importer will run giving you a valid path to the dam on the product to the image but the image to the products will not be there as the importer will not port over the actual image.