Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > MSMQT failed to publish the message coming into the queue
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 7th June 14:26
galeforce
External User
 
Posts: 1
Default MSMQT failed to publish the message coming into the queue



Hi, I'm just starting to learn BTS2004, and had some decent experience with
2002. Having a problem getting 2004 to map anything. All I get is:

"MSMQT failed to publish the message coming into the queue
DIRECT=OS:rd-v1304\Private$\CRMPublish, because no consumer was waiting for
it."

I have configured send/receive ports, and just using the built in xml
pipeline. The doc instance validates against the spec, and the map is very
simple. Looking in HAT, it seems to think the doc is the wrong type,
despite the fact it only validates against the correct schema. The doc even
has the namespace in it, so no reason I can see that it shouldn't recognize
it.

Any ideas where to start?

Thanks!
Mike
  Reply With Quote


  sponsored links


2 7th June 14:26
galeforce
External User
 
Posts: 1
Default MSMQT failed to publish the message coming into the queue



More info:

If I remove the namespace from the do***ent instance, I get:

"There was a failure executing the receive pipeline:
"Microsoft.BizTalk.DefaultPipelines.XMLReceive " Source: "XML disassembler"
Receive Location: "CRMPublish" Reason: The disassembler cannot retrieve the
do***ent specification by using this type: "message". Either the schema is
not deployed correctly, or more than one schema is deployed for the same
message type."

and:

"The MSMQT subservice failed to process incoming message, error code "COM
object that has been separated from its underlying RCW can not be used." ."

There is only one do***ent specification with a "message" element, so I
really don't understand what the problem is in identifiying this do***ent
correctly!

Mike
  Reply With Quote
3 7th June 14:26
galeforce
External User
 
Posts: 1
Default More info...


And if I remove the target namespace from the do***ent definition, it seems
to identify the do***ent, but it still won't map:

"The Messaging Engine failed while executing the inbound map for the message
coming from source URL:"CRMPublish" with the Message Type "message".
Details:"The root element is missing."

I'm basically using the same doc specs and map that worked on BTS 2002. How
would you debug these errors on 2004?

Thanks,
Mike
  Reply With Quote
4 7th June 14:26
larryfr
External User
 
Posts: 1
Default More info...


Hi Mike, can you post a zip of the project you are using that is having
this problem?
Also, as to using maps/do***ents from 2002, did you import these using a
BizTalk migration project?

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
--------------------
| From: "GaleForce" <nospan_mmcguinness@galeforcesolutions.com>
| References: <elOg6U8VEHA.2908@TK2MSFTNGP10.phx.gbl>
<ONInol8VEHA.1128@TK2MSFTNGP10.phx.gbl>
| Subject: More info...
| Date: Mon, 21 Jun 2004 13:04:47 -0700
| Lines: 72
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132
| Message-ID: <OqZ9Bs8VEHA.212@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.biztalk.server
| NNTP-Posting-Host: h209-139-213-230.gtconnect.net 209.139.213.230
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!cpmsftn gxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9695
| X-Tomcat-NG: microsoft.public.biztalk.server
|
| And if I remove the target namespace from the do***ent definition, it
seems
| to identify the do***ent, but it still won't map:
|
| "The Messaging Engine failed while executing the inbound map for the
message
| coming from source URL:"CRMPublish" with the Message Type "message".
| Details:"The root element is missing."
|
| I'm basically using the same doc specs and map that worked on BTS 2002.
How
| would you debug these errors on 2004?
|
| Thanks,
| Mike
|
|


| > More info:
| >
| > If I remove the namespace from the do***ent instance, I get:
| >
| > "There was a failure executing the receive pipeline:
| > "Microsoft.BizTalk.DefaultPipelines.XMLReceive " Source: "XML disassembler"
| > Receive Location: "CRMPublish" Reason: The disassembler cannot retrieve | the
| > do***ent specification by using this type: "message". Either the schema is
| > not deployed correctly, or more than one schema is deployed for the same
| > message type."
| >
| > and:
| >
| > "The MSMQT subservice failed to process incoming message, error code "COM
| > object that has been separated from its underlying RCW can not be used." | ."
| >
| > There is only one do***ent specification with a "message" element, so I
| > really don't understand what the problem is in identifiying this do***ent
| > correctly!
| >
| > Mike
| >
| >
| > "GaleForce" <nospan_mmcguinness@galeforcesolutions.com> wrote in message
| > news:elOg6U8VEHA.2908@TK2MSFTNGP10.phx.gbl...
| > > Hi, I'm just starting to learn BTS2004, and had some decent experience
| > with
| > > 2002. Having a problem getting 2004 to map anything. All I get is:
| > >
| > > "MSMQT failed to publish the message coming into the queue
| > > DIRECT=OS:rd-v1304\Private$\CRMPublish, because no consumer was waiting
| > for
| > > it."
| > >
| > > I have configured send/receive ports, and just using the built in xml
| > > pipeline. The doc instance validates against the spec, and the map is
| > very
| > > simple. Looking in HAT, it seems to think the doc is the wrong type,
| > > despite the fact it only validates against the correct schema. The doc
| > even
| > > has the namespace in it, so no reason I can see that it shouldn't
| > recognize
| > > it.
| > >
| > > Any ideas where to start?
| > >
| > > Thanks!
| > > Mike
| > >
| > >
| >
| >
|
|
|
  Reply With Quote
5 7th June 14:27
larryfr
External User
 
Posts: 1
Default More info...


Mike, I've compiled the project you provided, published it to my BizTalk
2004 machine, created a file receive location which specifies the map in
the project (so we pickup the file and map it,) and I also created a send
location that has a filter for bts.receiveportname=the inbound port name.

I pass in the sample do***ent you provided and it passes through the system
with no problems.

From looking back over your mail thread it seems you've ran into a few
problems, I'm not certain which one is the current issue with this schema.
What is the current error you are receiving? Also, how are you receiving
the do***ents and sending them? Can you try what I mention above with a
simple file receive and send port?

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
--------------------
| X-Tomcat-ID: 568366245
| References: <elOg6U8VEHA.2908@TK2MSFTNGP10.phx.gbl>
<ONInol8VEHA.1128@TK2MSFTNGP10.phx.gbl>
<OqZ9Bs8VEHA.212@TK2MSFTNGP12.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: larryfr@online.microsoft.com ("larry franks")
| Organization: Microsoft
| Date: Mon, 21 Jun 2004 20:42:49 GMT
| Subject: RE: More info...
| X-Tomcat-NG: microsoft.public.biztalk.server
| Message-ID: <CfQ4OB9VEHA.3788@cpmsftngxa10.phx.gbl>
| Newsgroups: microsoft.public.biztalk.server
| Lines: 94
| Path: cpmsftngxa10.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9696
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Hi Mike, can you post a zip of the project you are using that is having
| this problem?
| Also, as to using maps/do***ents from 2002, did you import these using a
| BizTalk migration project?
|
| Larry Franks
|
| This posting is provided "AS IS" with no warranties,and confers no
rights.
| Subscribe at
|
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
| &SD=msdn
| --------------------
| | From: "GaleForce" <nospan_mmcguinness@galeforcesolutions.com>
| | References: <elOg6U8VEHA.2908@TK2MSFTNGP10.phx.gbl>
| <ONInol8VEHA.1128@TK2MSFTNGP10.phx.gbl>
| | Subject: More info...
| | Date: Mon, 21 Jun 2004 13:04:47 -0700
| | Lines: 72
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132
| | Message-ID: <OqZ9Bs8VEHA.212@TK2MSFTNGP12.phx.gbl>
| | Newsgroups: microsoft.public.biztalk.server
| | NNTP-Posting-Host: h209-139-213-230.gtconnect.net 209.139.213.230
| | Path:
|
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!cpmsftn gxa06.phx.gbl!TK2MSFTNGP08
| .phx.gbl!TK2MSFTNGP12.phx.gbl
| | Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9695
| | X-Tomcat-NG: microsoft.public.biztalk.server
| |
| | And if I remove the target namespace from the do***ent definition, it
| seems
| | to identify the do***ent, but it still won't map:
| |
| | "The Messaging Engine failed while executing the inbound map for the
| message
| | coming from source URL:"CRMPublish" with the Message Type "message".
| | Details:"The root element is missing."
| |
| | I'm basically using the same doc specs and map that worked on BTS 2002.

| How
| | would you debug these errors on 2004?
| |
| | Thanks,
| | Mike
| |
| |


| | > More info:
| | >
| | > If I remove the namespace from the do***ent instance, I get:
| | >
| | > "There was a failure executing the receive pipeline:
| | > "Microsoft.BizTalk.DefaultPipelines.XMLReceive " Source: "XML | disassembler"
| | > Receive Location: "CRMPublish" Reason: The disassembler cannot retrieve | | the
| | > do***ent specification by using this type: "message". Either the schema | is
| | > not deployed correctly, or more than one schema is deployed for the same
| | > message type."
| | >
| | > and:
| | >
| | > "The MSMQT subservice failed to process incoming message, error code | "COM
| | > object that has been separated from its underlying RCW can not be used." | | ."
| | >
| | > There is only one do***ent specification with a "message" element, so I
| | > really don't understand what the problem is in identifiying this | do***ent
| | > correctly!
| | >
| | > Mike
| | >
| | >
| | > "GaleForce" <nospan_mmcguinness@galeforcesolutions.com> wrote in message
| | > news:elOg6U8VEHA.2908@TK2MSFTNGP10.phx.gbl...
| | > > Hi, I'm just starting to learn BTS2004, and had some decent experience
| | > with
| | > > 2002. Having a problem getting 2004 to map anything. All I get is:
| | > >
| | > > "MSMQT failed to publish the message coming into the queue
| | > > DIRECT=OS:rd-v1304\Private$\CRMPublish, because no consumer was | waiting
| | > for
| | > > it."
| | > >
| | > > I have configured send/receive ports, and just using the built in xml
| | > > pipeline. The doc instance validates against the spec, and the map is
| | > very
| | > > simple. Looking in HAT, it seems to think the doc is the wrong type,
| | > > despite the fact it only validates against the correct schema. The | doc
| | > even
| | > > has the namespace in it, so no reason I can see that it shouldn't
| | > recognize
| | > > it.
| | > >
| | > > Any ideas where to start?
| | > >
| | > > Thanks!
| | > > Mike
| | > >
| | > >
| | >
| | >
| |
| |
| |
|
|
  Reply With Quote
6 7th June 14:27
galeforce
External User
 
Posts: 1
Default More info...


Hi Larry, thanks for testing it.

I fixed a few problems, and got to the point yesterday where it just seems
to fail with the mapping (the last thread post I made). I've tried doing it
through MSMQ and the File Receive function. I can pump it straight through
using the pass through, but once I select the map on the receive port, I
get:

"The Messaging Engine failed while executing the inbound map for the message
coming from source URL:"CRMPublish" with the Message Type "message".
Details:"The root element is missing."

All I put for the send location filter is bts.receiveportname exists. It
seems to recognize the do***ent and where it's supposed to go, but something
seems to be going wrong in the mapping. This is a totally fresh install,
and there are no other projects, assemblies, ports, etc on the server.

Any ideas?

Thanks again,
Mike
  Reply With Quote
7 7th June 14:27
galeforce
External User
 
Posts: 1
Default Possibly do***entation bug?


Hi Larry, after starting the server up fresh this morning, it seemed to
process all queued do***ents correctly. I followed the deployment
directions in the help file, but it appears that you also have to stop and
restart the host for it to pick up deployed changes properly...otherwise it
seems to use a mix of old/new deployed components in different parts of the
BizTalk app (i.e. the explorer sees the new components, but the engine uses
the old config).

I tested this by making map changes, unassociating the map with the port,
undeploying the component, then rebuilding and deploying the component, and
reassociating the map with the port. When I tried to process a do***ent, it
passed it through rather than mapping it. Once I restarted the host, it
mapped it correctly. Or maybe I just need to unenlist and re-enlist the
ports? The help items for deploying and undeploying an assembly don't seem
to mention anything about this, although the deployment mentions enlisting
ports, but it doesn't really imply that you should have un-enlisted them
first.

Anyway, think I've got it figured out now...thanks for your help!

Mike
  Reply With Quote
8 7th June 14:27
larryfr
External User
 
Posts: 1
Default Possibly do***entation bug?


Hi Mike, yep, for a schema/map restarting the host should get the new
version in use. There is some caching going on and the new version should
eventually be loaded, but I do not have specific numbers on the cache
interval.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
--------------------
| From: "GaleForce" <nospan_mmcguinness@galeforcesolutions.com>
| References: <elOg6U8VEHA.2908@TK2MSFTNGP10.phx.gbl>
<ONInol8VEHA.1128@TK2MSFTNGP10.phx.gbl>
<OqZ9Bs8VEHA.212@TK2MSFTNGP12.phx.gbl>
<CfQ4OB9VEHA.3788@cpmsftngxa10.phx.gbl>
<nC81tOGWEHA.3440@cpmsftngxa10.phx.gbl>
<e1OiAZHWEHA.1152@TK2MSFTNGP09.phx.gbl>
| Subject: Possibly do***entation bug?
| Date: Tue, 22 Jun 2004 11:27:05 -0700
| Lines: 253
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132
| Message-ID: <uFe2FaIWEHA.3336@TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.biztalk.server
| NNTP-Posting-Host: h209-139-213-230.gtconnect.net 209.139.213.230
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP11
.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9704
| X-Tomcat-NG: microsoft.public.biztalk.server
|
| Hi Larry, after starting the server up fresh this morning, it seemed to
| process all queued do***ents correctly. I followed the deployment
| directions in the help file, but it appears that you also have to stop and
| restart the host for it to pick up deployed changes properly...otherwise
it
| seems to use a mix of old/new deployed components in different parts of
the
| BizTalk app (i.e. the explorer sees the new components, but the engine
uses
| the old config).
|
| I tested this by making map changes, unassociating the map with the port,
| undeploying the component, then rebuilding and deploying the component,
and
| reassociating the map with the port. When I tried to process a do***ent,
it
| passed it through rather than mapping it. Once I restarted the host, it
| mapped it correctly. Or maybe I just need to unenlist and re-enlist the
| ports? The help items for deploying and undeploying an assembly don't
seem
| to mention anything about this, although the deployment mentions enlisting
| ports, but it doesn't really imply that you should have un-enlisted them
| first.
|
| Anyway, think I've got it figured out now...thanks for your help!
|
| Mike
|
|


| > Hi Larry, thanks for testing it.
| >
| > I fixed a few problems, and got to the point yesterday where it just seems
| > to fail with the mapping (the last thread post I made). I've tried doing | it
| > through MSMQ and the File Receive function. I can pump it straight | through
| > using the pass through, but once I select the map on the receive port, I
| > get:
| >
| > "The Messaging Engine failed while executing the inbound map for the | message
| > coming from source URL:"CRMPublish" with the Message Type "message".
| > Details:"The root element is missing."
| >
| > All I put for the send location filter is bts.receiveportname exists. It
| > seems to recognize the do***ent and where it's supposed to go, but | something
| > seems to be going wrong in the mapping. This is a totally fresh install,
| > and there are no other projects, assemblies, ports, etc on the server.
| >
| > Any ideas?
| >
| > Thanks again,
| > Mike
| >
| >
| > ""larry franks"" <larryfr@online.microsoft.com> wrote in message
| > news:nC81tOGWEHA.3440@cpmsftngxa10.phx.gbl...
| > > Mike, I've compiled the project you provided, published it to my BizTalk
| > > 2004 machine, created a file receive location which specifies the map in
| > > the project (so we pickup the file and map it,) and I also created a | send
| > > location that has a filter for bts.receiveportname=the inbound port | name.
| > >
| > > I pass in the sample do***ent you provided and it passes through the
| > system
| > > with no problems.
| > >
| > > From looking back over your mail thread it seems you've ran into a few
| > > problems, I'm not certain which one is the current issue with this | schema.
| > > What is the current error you are receiving? Also, how are you | receiving
| > > the do***ents and sending them? Can you try what I mention above with a
| > > simple file receive and send port?
| > >
| > > Larry Franks
| > >
| > > This posting is provided "AS IS" with no warranties,and confers no | rights.
| > > Subscribe at
| > >
| > | http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
| > > &SD=msdn
| > > --------------------
| > > | X-Tomcat-ID: 568366245
| > > | References: <elOg6U8VEHA.2908@TK2MSFTNGP10.phx.gbl>
| > > <ONInol8VEHA.1128@TK2MSFTNGP10.phx.gbl>
| > > <OqZ9Bs8VEHA.212@TK2MSFTNGP12.phx.gbl>
| > > | MIME-Version: 1.0
| > > | Content-Type: text/plain
| > > | Content-Transfer-Encoding: 7bit
| > > | From: larryfr@online.microsoft.com ("larry franks")
| > > | Organization: Microsoft
| > > | Date: Mon, 21 Jun 2004 20:42:49 GMT
| > > | Subject: RE: More info...
| > > | X-Tomcat-NG: microsoft.public.biztalk.server
| > > | Message-ID: <CfQ4OB9VEHA.3788@cpmsftngxa10.phx.gbl>
| > > | Newsgroups: microsoft.public.biztalk.server
| > > | Lines: 94
| > > | Path: cpmsftngxa10.phx.gbl
| > > | Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9696
| > > | NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
| > > |
| > > | Hi Mike, can you post a zip of the project you are using that is | having
| > > | this problem?
| > > | Also, as to using maps/do***ents from 2002, did you import these using | a
| > > | BizTalk migration project?
| > > |
| > > | Larry Franks
| > > |
| > > | This posting is provided "AS IS" with no warranties,and confers no
| > > rights.
| > > | Subscribe at
| > > |
| > >
| > | http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
| > > | &SD=msdn
| > > | --------------------
| > > | | From: "GaleForce" <nospan_mmcguinness@galeforcesolutions.com>
| > > | | References: <elOg6U8VEHA.2908@TK2MSFTNGP10.phx.gbl>
| > > | <ONInol8VEHA.1128@TK2MSFTNGP10.phx.gbl>
| > > | | Subject: More info...
| > > | | Date: Mon, 21 Jun 2004 13:04:47 -0700
| > > | | Lines: 72
| > > | | X-Priority: 3
| > > | | X-MSMail-Priority: Normal
| > > | | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| > > | | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132
| > > | | Message-ID: <OqZ9Bs8VEHA.212@TK2MSFTNGP12.phx.gbl>
| > > | | Newsgroups: microsoft.public.biztalk.server
| > > | | NNTP-Posting-Host: h209-139-213-230.gtconnect.net 209.139.213.230
| > > | | Path:
| > > |
| > >
| > | cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!cpmsftn gxa06.phx.gbl!TK2MSFTNGP08
| > > | .phx.gbl!TK2MSFTNGP12.phx.gbl
| > > | | Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9695
| > > | | X-Tomcat-NG: microsoft.public.biztalk.server
| > > | |
| > > | | And if I remove the target namespace from the do***ent definition, | it
| > > | seems
| > > | | to identify the do***ent, but it still won't map:
| > > | |
| > > | | "The Messaging Engine failed while executing the inbound map for the
| > > | message
| > > | | coming from source URL:"CRMPublish" with the Message Type "message".
| > > | | Details:"The root element is missing."
| > > | |
| > > | | I'm basically using the same doc specs and map that worked on BTS
| > 2002.
| > >
| > > | How
| > > | | would you debug these errors on 2004?
| > > | |
| > > | | Thanks,
| > > | | Mike
| > > | |
| > > | |
| > > | | "GaleForce" <nospan_mmcguinness@galeforcesolutions.com> wrote in
| > message
| > > | | news:ONInol8VEHA.1128@TK2MSFTNGP10.phx.gbl...
| > > | | > More info:
| > > | | >
| > > | | > If I remove the namespace from the do***ent instance, I get:
| > > | | >
| > > | | > "There was a failure executing the receive pipeline:
| > > | | > "Microsoft.BizTalk.DefaultPipelines.XMLReceive " Source: "XML
| > > | disassembler"
| > > | | > Receive Location: "CRMPublish" Reason: The disassembler cannot
| > > retrieve
| > > | | the
| > > | | > do***ent specification by using this type: "message". Either the
| > > schema
| > > | is
| > > | | > not deployed correctly, or more than one schema is deployed for | the
| > > same
| > > | | > message type."
| > > | | >
| > > | | > and:
| > > | | >
| > > | | > "The MSMQT subservice failed to process incoming message, error | code
| > > | "COM
| > > | | > object that has been separated from its underlying RCW can not be
| > > used."
| > > | | ."
| > > | | >
| > > | | > There is only one do***ent specification with a "message" element,
| > so
| > > I
| > > | | > really don't understand what the problem is in identifiying this
| > > | do***ent
| > > | | > correctly!
| > > | | >
| > > | | > Mike
| > > | | >
| > > | | >
| > > | | > "GaleForce" <nospan_mmcguinness@galeforcesolutions.com> wrote in
| > > message
| > > | | > news:elOg6U8VEHA.2908@TK2MSFTNGP10.phx.gbl...
| > > | | > > Hi, I'm just starting to learn BTS2004, and had some decent
| > > experience
| > > | | > with
| > > | | > > 2002. Having a problem getting 2004 to map anything. All I get
| > is:
| > > | | > >
| > > | | > > "MSMQT failed to publish the message coming into the queue
| > > | | > > DIRECT=OS:rd-v1304\Private$\CRMPublish, because no consumer was
| > > | waiting
| > > | | > for
| > > | | > > it."
| > > | | > >
| > > | | > > I have configured send/receive ports, and just using the built | in
| > > xml
| > > | | > > pipeline. The doc instance validates against the spec, and the
| > map
| > > is
| > > | | > very
| > > | | > > simple. Looking in HAT, it seems to think the doc is the
wrong
| > > type,
| > > | | > > despite the fact it only validates against the correct schema.
| > The
| > > | doc
| > > | | > even
| > > | | > > has the namespace in it, so no reason I can see that it
| shouldn't
| > > | | > recognize
| > > | | > > it.
| > > | | > >
| > > | | > > Any ideas where to start?
| > > | | > >
| > > | | > > Thanks!
| > > | | > > Mike
| > > | | > >
| > > | | > >
| > > | | >
| > > | | >
| > > | |
| > > | |
| > > | |
| > > |
| > > |
| > >
| >
| >
|
|
|
  Reply With Quote
Reply


Thread Tools
Display Modes




Copyright © 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666