Hmm,
I'm not sure what i'm doing wrong. Currently I'm unable to troubleshoot because everytime I visit the vco/api/workflows page I get a HTTP 401 ("full authentication required to access this resource"). Maybe I should note I'm using the vcac integrated vco (vcac 6.0.1).
so the link I'm trying to visit looks like this:
https://vcac.local:8281/vco/api/workflows/19c610ca5af84162bd955a955ab961d2/executions/ff808081457f00...
No basic auth popup (tried ie, firefox, chrome) nothing. Just 401. Also I tried submitting a basic auth header - no luck (not sure which credentials exacly are needed to visit this ...)
Well but let's get focused on the problem here:
I was able to resolve the issues using a different object from the solarsystem example (star instead of planet). I looked at the source code of the example, but i'm not sure what's different for the star / planet objects that could cause the star being provisioned and the planet not to be.
So I tried to build my own custom object using some aspect oriented programming. Source looks like this:
package com.testlab.o11n.plugin.TESTPLUG;
import java.io.Serializable;
public abstract class AbstractObject implements Serializable{
private static final long serialVersionUID = 1L;
private String id;
public AbstractObject() {
// Not exacly sure what this is used for in vco / vcac and how unique this should be
id = this.toString();
}
/* Serialize the object's content as Base64 encoded string.
*
* @return the the serialized content of the object as an UTF-8 string
*/
public String getId() {
return id;
}
}
//----------------------------------------------------------------------
package com.testlab.o11n.plugin.TESTPLUG;
import com.vmware.o11n.plugin.sdk.annotation.*;
@VsoObject(name = "TestObject", description="Some Test for the API browser here")
// What exacly is the "idAccessor" needed for?
@VsoFinder(name = "TestObject", idAccessor = "getId()", hidden = false, image = "images/item-16x16.png", description="Some Test for the API browser here")
public class TestObject extends AbstractObject{
private static final long serialVersionUID = 1L;
@VsoProperty(readOnly = false, description = "The name of the object.")
private String objName;
@VsoProperty(readOnly = false, description = "The owner of the object.")
private String objOwner;
@VsoConstructor(description="Creates a object.")
public TestObject(@VsoParam(description="The object name as a String")String objName, @VsoParam(description="The object owner as a String")String objOwner) {
// call parent constuctor
super();
this.objName = objName;
this.objOwner = objOwner;
}
public String getObjOwner() {
return objOwner;
}
public void setObjOwner(String objOwner) {
this.objOwner = objOwner;
}
public String getObjName() {
return objName;
}
public void setObjName(String objName) {
this.objName = objName;
}
@VsoMethod(description="A test method which dosn't do anything.")
public void objMethod()
{
}
}
Within vCO I just created a workflow which has a single scripting task which basiclly creates a new object as output parameter (of type TestObject) like this:
myObject = new TESTPLUGTestObject(objName,objOwner);
The workflow runs successfully, the object is created within the script task (checked by system.log printout accessing the object properties) but when the workflow finishs, the variables result set shows "Not Found" - "The linked element cannot be found" for the output parameter.
So far I'm not sure what is causing this.
Sooooo. The documentation is note quite clear what the ID of a custom object is used for. However, from the examples it seems like a unique id is needed for vCO to locate the object - which could be the reason why my workflow isn't working
I'm also not sure what the requirements for custom objects are - specially when using annotation based creation. And last but not least I don't know yet how and where custom created objects are stored in vCO and how they're retreived by vcac.
Do you have any information about that for me?
