ad back in correctly. I'm not posting any schema
or xml here because I see the same problems regardless of what I'm
(de)serializing (always wsdl2java objects defined as complexType).
Any suggestions would be welcome,
Thanks
--
*Michael Thome*
BBN Technologies 10 Moulton St, Cambridge
I'll do it if I
need to)
Thanks,
Michael
--
*Michael Thome*
BBN Technologies 10 Moulton St, Cambridge MA 02138 USA
phone: +1 617 873 1853
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
round 100x faster than the approaches
I tried before.
At any rate, using either the above code or my original code leaves me
deserializing a bit more than 1000x faster than yesterday. Can't
complain too much about that... ;-)
Thanks,
-Michael
Michael Thome wrote:
Thanks for the examples.
Thanks for the examples. I've got a few followups, if you don't mind...
Peter Molettiere wrote:
Chances are you're doing it right. My experience is that axis is
pretty slow, especially if you have large object graphs to read and
write.
I sure hope I'm not doing it right, though so far your solu
Here's a stupid question - gotta be a faq, but darned if I can find the
right keywords...
I'd like to be able to deserialize/serialize data in the form of
wsdl2java-generated structures from/to arbitrary streams. For instance,
if I serialize such an object to a file, I would like to end up wit
(B
(B
(B
(BDown the rat hole we go...
(B
(BAt first glance, the below looked like it was going to work, but the
(Bserialization/deserialization code emitted by wsdl2java with this
(Bapproach incorrectly turns the groups into named elements! This
(Bleaves us in a state where the deserial
(B
(B
(B
(BOK - I *think* I have a solution. The following seems to allow me to
(B(a) avoid changing the document syntax, (b) validation/parsing works
(Bproperly, and (c) wsdl2java seems to generate sane code. The cost is
(Bsome minimal extra complexity in the schema and an extra generate
(B
(B
(B
(BAck - you are correct. I only looked at the generated code (which
(Blooks fine) and tried validating against an example that turned out to
(Bbe too simple.
(B
(BNow I don't know... Any workaround would be extremely welcome, as I
(Bneed this to work, also.
(B
(BI really don't
(B
(B
(B
(BHaving just gone through a similar exercise:
(B1. I think the correct approach ought to be to attach the min/max
(Battributes to the choice rather than to the sequence - e.g. you want a
(Bsingle sequence of any number of a choice of {and,or,not} elements, not
(Bany number of seq
