com.bowstreet.builders.webapp.methods
Class ServiceCallMethodsDataArg
java.lang.Object
com.bowstreet.builders.webapp.methods.ServiceCallMethodsDataArg
public class ServiceCallMethodsDataArg
- extends java.lang.Object
This class encapsulates the request data required by a ServiceCall
invoke method. Why bother? Why not use setters? It's 'cos the
ServiceCallMethods class is going to get used as an LJO that is
shared by all users with the same profile - there is an LJO instance
for the session, not per user. So we cannot keep data that is built
at regen time in the LJO. It needs to be in a variable. And rather than
use lots of variables or an IXml structure, it's easier and faster
to use a real object. In the LJO we just store the name of the
Variable - the variable name can be the same for every user, but the
variable content can obviously be different.
-
Constructor Summary |
ServiceCallMethodsDataArg(java.lang.String name,
java.lang.String namespace,
java.lang.String classname,
java.lang.String value)
|
Methods inherited from class java.lang.Object |
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
ServiceCallMethodsDataArg
public ServiceCallMethodsDataArg(java.lang.String name,
java.lang.String namespace,
java.lang.String classname,
java.lang.String value)
getArrayItemName
public java.lang.String getArrayItemName()
getArrayItemNS
public java.lang.String getArrayItemNS()
getClassname
public java.lang.String getClassname()
getName
public java.lang.String getName()
getNamespace
public java.lang.String getNamespace()
getSchemaType
public java.lang.String getSchemaType()
getValue
public java.lang.String getValue()
setArrayItemName
public void setArrayItemName(java.lang.String arrayItemName)
setArrayItemNS
public void setArrayItemNS(java.lang.String arrayItemNS)
setSchemaType
public void setSchemaType(java.lang.String type)
Copyright © 2009 IBM. All Rights Reserved.