Jon,
Fair enough, although this does seem like an exceptional case to me.
I think you could probably achieve the same effect by breaking your
large payload schema into a set of smaller "atoms" suitable for
independent transmission. Each of these components could be validated
individually, in addition to validation of the "whole" when it is
assembled.
- Matt
-----Original Message-----
From: dev_at_samizdatdigital.org [mailto:dev_at_samizdatdigital.org]
Sent: Tuesday, June 29, 2004 4:28 PM
To: users_at_jaxb.dev.java.net
Subject: Re: Polymorphism problems
On Jun 29, 2004, at 10:36 AM, Matt Munz wrote:
> OK. Let's take a poll. Everyone who wants to use JAXB to generate
> invalid XML, raise your hand ;) Seriously, I'd like to know the use
> case for that...
i am designing applications which build complex objects in a
distributed fashion. as an object is being built, it is in an invalid
state, and this semi-finished xml gets sent from component to component
(not all of them are java, so i can't do java serialization or rmi) as
xml payloads. java handles the communication and dispatch, and looks at
the partially correct xml to figure out where it should go to become
more correct. the point is, i have a need to generate invalid (but
well-formed!) xml, and to only validate when i'm ready to. so, i vote
for marshalling invalid xml. +1
jon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net