Hello Angela,

Saving the serialized output from the jx generator to a file like John did, is 
just serializing the pipeline to xml serializer, then save the xml in the 
browser to disk. He described that when using this saved xml, the problem was 
solved.

Now, a little confusing perhaps, but saving the xml output in your browser can 
be quite different then the SAX events in your pipeline (yesterday I was 
flabeergasted having two "href" attributes in my SAX, where an xsl would use 
the first one, and the serializer the latter....)

Anyway, the problem John had, was that when generating your own xml/SAX, you 
have to be aware to use the correct namespaces. Saving the xml like John, is 
just saving the xml output in your browser (there is a source writing 
transformer, i know, but i don't think you want this)

Regards Ard

Hi Ard

I'm having the same problem as well.
How do you save the serialized xml output from the jx generator as a file??

Is there anything in the documentation that I can read to guide me??

many thanks


 
On 4/10/07, Ard Schrijvers <[EMAIL PROTECTED]> wrote: 

>
> I'm trying to use a custom generator and the jx transformer to
> generate a form  from flowscript using form.showForm(....).
>
> When I use my custom generator to generate the template and the jx
> transformer as the next step, the continuation id is replaced but
> none of the ft: entries are replaced by the fi: equivalents. The 
> <jx:import> tag remains after the transformation as well.
>
> When I take the serialized xml output from my generator, save
> it as a
> file and use that file and the default generator to start the 
> pipeline, everything works fine. What am I missing?

You probably (i am quite sure) are missing namespaces in the SAX events 
generated by your generator. You should see this when:

1) you do a logtransformer after your generator 
2) you do a logtransformer after your generation of (xml saved from the 
generator)

I know, it is confusing, but your generated saved xml might have different SAX 
events because of namespaces. Probably (quite sure again), you are setting a 
namespace in your generator on some parent element, and you forget to set them 
on child nodes 

Regards Ard

>
>
> Regards
> John Hewett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

--------------------------------------------------------------------- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED] 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to