On Jun 8, 3:46 pm, Jan Eliasen <elia...@[EMAIL PROTECTED]
> wrote:
> >Can you also explain why adding "another level of indirection" works?
> >My initial schema just had a root node with some attributes. Your
> >solution has a root node and a child with the attributes. Why does one
> >work and the other doesn't?
>
> Baiscally, in your schema, you hadn't described in any way, how a
> record was terminated. You had set the default record delimiter on the
> root node, but you hadn't described any records that used that
> delimiter. I did that.
Right. So the only difference between a schema that will split the
records and a schema that will read in the whole message is that the
'record' node has a maxOccurs of 1 instead of unbounded. Is that
correct?
> >Another related question: Is it possible to split flat files into
> >grouped records?
> >I have this (other) file that has repeating identifiers in each line.
>
> >[ID] [DATA]
> >0001,Hello!
> >0001,How are you?
> >0002,Dear Sir,
> >0002,In response...
>
> >I would like to split this in two messages, one for each ID and each
> >message would have two records. Is that possible or am I looking at
> >writing my own disassembler component here...?
>
> Well, this one is (potentially) more difficult than the previous one.
>
> Are there ALWAYS exactly two lines? Or can there be some groups with
> one record, some groups with ten records, etc.?
There can be one or more records per ID. I'm currently working on a
solution where I split all the records of the incoming message and
then aggregate them back using a serial convoy orchestration and some
custom code.
Is there another solution using just the disassembler?
Thanx
--Marc Jacobi
|
