First question:
SOJO support XML-RPC, as special case for XML.
The problem by XML is, which tags/structure (Elementes and/or Attributes) are supported?
For example:
<root class="a.b.c.MyClass" id="123">
<myprop>...</myprop>
...
</root>
Is this example a good decision for a XML output?
Where will you define your own tags and how?
Second question:
What do you mean with "work with hibernate lazy fetching"?
Circular references are not a problem. SOJO dissolve circles.
Regards,
Mario
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Their default lazy fetching adds at runtime an addtional field that contains the jdbcresultset object. So trying to graph that will lead to a major error when you try to getCursorName - you can turn lazy fetching off for mapped objects or just ignore that getlazy field I can email the exact 'getlazy..' field name added to the hibernate pojos at runtime.
Then add a hibernate user flag option
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
First question:
SOJO support XML-RPC, as special case for XML.
The problem by XML is, which tags/structure (Elementes and/or Attributes) are supported?
For example:
<root class="a.b.c.MyClass" id="123">
<myprop>...</myprop>
...
</root>
Is this example a good decision for a XML output?
Where will you define your own tags and how?
Second question:
What do you mean with "work with hibernate lazy fetching"?
Circular references are not a problem. SOJO dissolve circles.
Regards,
Mario
Logged In: NO
Hi, please email me mglazer8 AT yahoo DOT com to discuss more.
can you make the 'class' and 'uniqueid' fields optional on output? My json list maps values and others dont need that
xml should look like json, simple, no attributes.
<object.class.getSimplename()>
<field.name>field.value</field.name>
<object.class.getSimplename()>
<field.name>field.value</field.name>
</object.class.getSimplename()>
</object.class.getSimplename()>
Hibernate is tricky
Their default lazy fetching adds at runtime an addtional field that contains the jdbcresultset object. So trying to graph that will lead to a major error when you try to getCursorName - you can turn lazy fetching off for mapped objects or just ignore that getlazy field I can email the exact 'getlazy..' field name added to the hibernate pojos at runtime.
Then add a hibernate user flag option