06-26-04 03:51 PM
Two things:
- what about the SQLAdapter? (Or are you using another database?)
- the XMLAssembler pipeline component has an option that lets you specify wh
ether to keep the processing instruction or not
- the mapper has an option called "Omit XML Declaration" - set this to "no"
I don't know how you call your component, but that's probably from within yo
ur orchestration so the XMLAssembler won't help you a lot. Are you using th
e mapper?
Best regards,
Christof
"Johan Nedin" <radioboring@hotmail.com> wrote in message news:2bb8ab8f.0406230030.8bf6be0@po
sting.google.com...
> Hello Christof!
>
> Thanx for your advice.
> I followed your advice and after some additional banging of my head
> against the wall I managed to get my component up and running (only to
> discover a different error...
>
> Here is how I solved the problem:
> 1. I removed everything from the GAC.
> 2. Removed all dll's from the bin directories.
> 3. Recompiled all my projects.
> 4. Used the BizTalk deployment wizard to deploy my BizTalk assembly.
> 5. Tested my orchestration...
> 6. No luck...
> 7. Dragged and dropped my components from the bin\deployment to the
> GAC.
> 8. Tested my orchestration...
> 9. Felt lucky...
> 10. Partial success...
>
> My Orchestration is performing database insert using SQLXml (via a
> database component, now happily functioning with my orchestration),
> and for some reason the orchestration removes the XML-declaration.
> (<?xml version="1.0 encoding="ISO-8859-1" ?> )
>
> My next question... Is this by design? Or is there a property that
> disables this "feature" when you are getting your xml-message from
> file... SQLXml doesn't seem to work very well without the
> xml-declaration, which means that I have to put the xml-declaration
> back in my database component (the one called from the orchestration),
> which ofcourse is a small matter, but irritating.
>
> Thanx
>
> / Johan
[ Post a follow-up to this message ]
|