ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » cXML: Need to support an external DTD under XMLNSC

Post new topic  Reply to topic
 cXML: Need to support an external DTD under XMLNSC « View previous topic :: View next topic » 
Author Message
ccrandall
PostPosted: Thu Sep 02, 2010 12:08 pm    Post subject: cXML: Need to support an external DTD under XMLNSC Reply with quote

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
View user's profile Send private message
fjb_saper
PostPosted: Thu Sep 02, 2010 12:17 pm    Post subject: Reply with quote

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
View user's profile Send private message Send e-mail
ccrandall
PostPosted: Thu Sep 02, 2010 1:08 pm    Post subject: Reply with quote

Acolyte

Joined: 23 Oct 2008
Posts: 52

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:

http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ad21060_.htm?resultof=%22%65%78%74%65%72%6e%61%6c%22%20%22%65%78%74%65%72%6e%22%20%22%44%54%44%22%20%22%64%74%64%22%20%22%73%75%70%70%6f%72%74%22%20

But I did notice in a couple other threads here that people were directed to use XMLNS for this very same thing and I didn't see anyone post back that it didn't work. So, I'll give it a try and see if it works.

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.

Thanks!
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Sep 02, 2010 2:38 pm    Post subject: Reply with quote

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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » cXML: Need to support an external DTD under XMLNSC
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.