Unsolved

This post is more than 5 years old

2 Intern

 • 

212 Posts

1967

November 16th, 2009 16:00

metadata values

Binding: Java

Atmos onLine

I looked for guidelines around this in the Programmers guide but if I missed these apologize -

1. When uploading a file using UploadHelper to an objectpath, if the filename has spaces, a signature mismatch error is thrown. Does this mean that all filenames must be stripped off spaces.

2. Can objectpath names (directory names) contain spaces? I am getting errors when trying to create one.

3. The binding allows a user to set a metadata value with a ampersand (&) in it. But trying to access the metadata results in a XML parsing error -

com.emc.esu.api.EsuException: Error parsing response      at com.emc.esu.api.rest.EsuRestApi.parseObjectListWithMetadata(EsuRestApi.java:2098)      at com.emc.esu.api.rest.EsuRestApi.listObjectsWithMetadata(EsuRestApi.java:877)      at com.emc.esu.api.rest.EsuRestApi.listObjectsWithMetadata(EsuRestApi.java:822)      at com.emc.edn.atmosbrowser.jobs.LoadTaggedObjectsJob.run(LoadTaggedObjectsJob.java:47)      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.jdom.input.JDOMParseException: Error on line 128: The entity name must immediately follow the '&' in the entity reference.      at org.jdom.input.SAXBuilder.build(SAXBuilder.java:504)      at org.jdom.input.SAXBuilder.build(SAXBuilder.java:807)      at com.emc.esu.api.rest.EsuRestApi.parseObjectListWithMetadata(EsuRestApi.java:2050)      ... 4 more Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.      at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)      at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)      at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)      at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1411)      at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1836)      at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3017)      at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:645)      at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)      at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:508)      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)      at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)      at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)      at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)      at org.jdom.input.SAXBuilder.build(SAXBuilder.java:489)      ... 6 more

281 Posts

November 17th, 2009 08:00

Hi Aashish,

I'll check on #1 and #2; it may be signature generation problems.

For #3, it sounds like the server is not properly escaping & to & in the XML.  You should open a ticket for this one.  Please also check < and >, they should be escaped to < and >

No Events found!

Top