Re: Adding HelperContext as a parm for (URI, Name) methods

2007-03-20 Thread Frank Budinsky
Brian, There is already spec discussion about possibly deprecating the DataGraph interface entirely. Even if that doesn't happen, I think that the (URI, name) methods should be deprecated. Frank. "Brian Murray" <[EMAIL PROTECTED]> wrote on 03/20/2007 10:28:29 AM: > Thanks Kelvin. > > That i

Re: Adding HelperContext as a parm for (URI, Name) methods

2007-03-20 Thread Brian Murray
Thanks Kelvin. That is a workaround for the example I provided. However, the absence of HelperContext as a parm does seem to render createRootObject(URI, Name) and DataGraph.getType(URI, name) of very limited use. The DataGraph methods are different from the following: DataObject.createDataObje

Re: Adding HelperContext as a parm for (URI, Name) methods

2007-03-20 Thread kelvin goodson
Brian, this would be an issue for the SDO spec, but I don't think it's necessary, since you can use Type type =helperContext1.getTypeHelper().getType(uri, name); and then use dataGraph.createRootObject(type); the root object will then provide the type scope context for subsequent updates to th

Adding HelperContext as a parm for (URI, Name) methods

2007-03-19 Thread Brian Murray
Has there already been discussion about adding a HelperContext parm for methods which take URI and name as input? It seems necessary to me. For example, if you've created a Type with helperContext1.getXSDHelper().define() or helperContext1.getTypeHelper().define(), then DataGraph.createRootObjec