Hi Sergey,
I wrote that email right before I went on vacation, hence the radio silence
on my end.
The better work-around on my end was to cut down the object in the service
layer prior to serialization. I bet I could also do this in an interceptor
if the return type is a collection of a certain type, then strip off some
parts of the object prior to passing it out to JAXB.
Ideally, what I¹d love to be able to do would be to take something like the
following:
<BatchFile id=900>
<FileName>SomeFile.txt</FileName>
<AuditObject id=37>
<Column index=²1²>
... Lots of sample data elements...
</Column>
<Column index=²2²>
... Lots of sample data elements...
</Column>
... Lots more columns ...
</AuditObject>
</BatchFile>
And then say that certain elements should be reduced to just ids (or xrefs
or something), so you¹d have something like the following:
<BatchFile id=900>
<FileName>SomeFile.txt</FileName>
<AuditObject id=37 />
</BatchFile>
That way the caller would have enough to request the additional info without
starting at the batch file at the top.
For now, cutting down the object by removing the AuditObject in the service
layer makes the app performant.
Thanks, as always, for the help.
Also I finished up the List<?> converter (by adding code on the client
side) that I wrote about previously should I post the code to the list?
Thanks,
Dan
-----
CONFIDENTIALITY NOTICE: The information contained in this message
may be privileged and confidential and protected from disclosure.
If the reader of this message is not the intended recipient, or
responsible for delivering it to the intended recipient, please
be advised that any distribution, dissemination, copying or other
transmission or use of the information contained in this message
or its enclosed attachments is strictly prohibited. Please
notify us immediately if you have received this message in error
by replying to the sender of the message and deleting it from
your computer. Thank you.
