hi marvin, thanks that is great !
unfortunately I dont know how to handle properties from the super class, as the compiler does not let me add them in the xmlsummary list ? though I added also a class paramter in the super class itself, the whole super class properties are in the xml export ... what I did not try yet is overloading the super class properties just for use them in the xmlsummary, I hope that there are other possibilities - are there ? if I had to do a transformation for a property I would have to use a calculated property I think, or I can use the "proxy class" as mentioned by Peter Cooper in the other reply to my question ? what was also a little pit fall is that there must not be blanks in the list. brg werner "Marvin Tener" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] > Some useful features in this direction in Cache 5.0.5. Documentation hasn't > caught up yet. > > In the referenced class add the class parameter: > Parameter XMLSUMMARY = "field1,field2,field3"; > to define the properties that represent a summary of this class. This > summary will be used by default whenever this class is referenced from > within another class. If you need a reference that is the entire class add > to the referecing property: > Property refprop As cls (XMLREFERENCE="complete"); > XMLREFERENCE="summary" is the default, but normally you can't tell the > difference since the default for XMLSUMMARY parameter is all properties in > the class. > > Another option is XMLREFERENCE="id" which outputs only the id of the > referenced class for a property. > > Marvin > > "Dipl.-Ing. Werner Riegler" <[EMAIL PROTECTED]> wrote in > message news:[EMAIL PROTECTED] > > Hi, > > > > there is an very interesting feature in cache I need very urgent - the xml > > projection > > > > but as I have some complex classes which have many relations to other > > classes (at least properties of complex types) > > > > I need to "cut off" the xml projection at a certain depth ... > > > > example to explain: > > > > class root ... > > { > > property A as classA; > > > > property B as classB; > > > > property C as classC; > > > > ... > > } > > > > class classA ... > > { > > property S as %String; > > ... > > > > property D as classD; > > > > > > } > > > > I even have same nested relations ... ( like a net ) ! > > > > It is very interesting - and a strong feature I think - that every XML > > enabled class is resolved by the xml write... > > But for Import / Export and Report use this is a little too much. > > > > So I would like to over write the XML representation of properties ... > > > > I found the possibilities to switch them off - XMLPROJECTION = NONE > > and to choose between Attribute and Element (which results to a compiler > > error in case of a Class), > > but I think I need the behaviour that e.g. only the Property called Name > for > > a related Class should be shown ... > > > > <root> > > <A S="xxx"> > > <D ...> > > </A> > > <B /> > > </root> > > > > should be instead of the whole <A> stuff like this: > > > > <root> > > <A S="xxx" D="yyy" > > > <B /> > > </root> > > > > any possibilities for this ? > > > > I think it is no goog idea to set the XML projection of property D in > Class > > A to none > > and also not to set Properties within Class D to none - because they > should > > only in case of > > the relation from class A become supressed for xml projection ... > > > > brg > > werner > > > > > >
