Index External

Using 4.5.3 of the MediaBin Web Service SDK with Java, I'm trying to insert Externally Indexed images. It looks like there should be a method called InsertAsset_IndexExternal, but it doesn't actually appear to be in the SDK JAR. Does the method have a different name?

Actually, I see in [thread=12357]this[/thread] much older post that the method is not exposed though the web service. Is that still true?

Find more posts tagged with

Comments

msnider

InsertAsset_IndexExternal became available in 4.5.2.

Maybe you have an outdated version of the java stub. Check your web service's WSDL (http://localhost/MediabinWebService/MediaBinServer.asmx?wsdl) to locate that the web service supports the method (it should).

You can they rebuild the Java stub using your current WSDL.

Mark

Migrateduser

Many thanks. Rebuilding the stub fixed that problem, but now when I attempt to use the method to insert an Externally Index asset I get back the following exception:

Exception Server was unable to process request. --> MBException: Unprintable or illegal character found in identifier. Illegal characters are / \ : * ? " < > | (0x80040446)

A search turns up [thread=20875]this[/thread] post which seems to be the same problem, but contains no solution. I presume it's the backslash which is causing the problem? Is there some special way to pass the UNC string so it can handle such characters?

lyman

Oops. Do not know how the previous post went unanswered. That was a slip-up on my part.

The error message applies to the filename and should be unaffected by the characters in the path. However, if the name is:

\\fscluster.corp.company.com\public\DAM\indexExternalTest\0002214333273.psd

(taken from previous post) for example, it is possible that the logic that splits off the extension is confused by the dots in the UNC path.

I will poke around and see if I can reproduce the problem outside WS.

Cheers,

Lyman Hurd

Migrateduser

Turns out my error was not coming from the UNC path, but from the asset name. I was trying to use the full UNC path as the asset name, which didn't seem to enjoy the back slashes. Removing the back slashes from the asset name seems to have fixed the problem.