|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
cXML: Need to support an external DTD under XMLNSC |
« View previous topic :: View next topic » |
Author |
Message
|
ccrandall |
Posted: Thu Sep 02, 2010 12:08 pm Post subject: cXML: Need to support an external DTD under XMLNSC |
|
|
Acolyte
Joined: 23 Oct 2008 Posts: 52
|
As part of my MB v7 migration effort, I've run into a custom broker application that's sending a cXML message to a vendor. With cXML, there's an external DTD I need to include which under the XML parser looked like this:
SET OutputRoot.XML.(XML.DocTypeDecl).(XML.SystemId) = 'http://xml.cxml.org/schemas/cXML/1.1.010/cXML.dtd';
Now that we are moving to XMLNSC, I'm not quite sure how to translate this statement because there doesn't seem to be an equivalent for XML.SystemId and the documentation says the XMLNSC does not support external DTDs. I'm a bit confused by that last tidbit because DTDs are still part of the XML spec and I would think they should be supported. Perhaps I'm misunderstanding the documentation???
Thanks in advance,
Curt |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Sep 02, 2010 12:17 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
In certain cases where XMLNSC will not accomodate you use XMLNS.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
ccrandall |
Posted: Thu Sep 02, 2010 1:08 pm Post subject: |
|
|
Acolyte
Joined: 23 Oct 2008 Posts: 52
|
|
Back to top |
|
 |
kimbert |
Posted: Thu Sep 02, 2010 2:38 pm Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
I did consider this, but I'm concerned about using XMLNS b/c it too also states in the Info Center that external DTDs are not supported |
They are supported in the sense that the XMLNS parser will parser and write the <DTD> tag whether it contains an internal DTD or a reference to an external one. None of the message broker XML parsers will actually load and use an external DTD, though.
Quote: |
Another concern I had, though, with XMLNS was that one of our IBM reps mentioned that it too was basically deprecated and we were highly encouraged to do everything in XMLNSC. But I suppose when the day comes where that parser isn't supported, we'll cross that bridge when we get to it. |
Please tell that rep to use more careful language in future. The facts are:
- XMLNSC is usually the best choice of XML parser.
- XMLNS is usually the second-best choice of XML parser. In your case it's the best choice. It is not deprecated, and there is nothing in the InfoCenter to say otherwise.
- The XML domain is deprecated ( so please don't use it in new message flows ) but will not be removed from the product. Probably not ever. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|