需要获取已发布的组件版本的 XML [英] Need to get the XML of a component's that version which is published
问题描述
我们正在迭代 Tridion 2011 文件夹中的组件，并根据组件的发布状态创建我们的自定义 XML 以用于 CDS.我给出下面的例子让你理解这个问题.
We are iterating the components in a folder in Tridion 2011 and creating our custom XML to be used on CDS on the basis of the publishing status of component. I am giving below example to make you understand the problem.
- 假设我们在一个文件夹中有 10 个组件，这些组件都已发布，并且我们发布了 XML，然后会为 10 个项目生成 XML.
- 现在我们对其中一个组件进行更改，但不发布它.
- 组件修改后，我们再次发布XML.然后 XML 也会为修改后的组件更新.因此，它创建了该组件的已发布版本与我们的 XML 中的版本之间的差异.
所以我想以这样一种方式发布自定义 XML，它应该只包含与已发布的组件版本同步的数据.
So I want to publish the custom XML in such a way that it should only contain that data which is in sync with published version of component.
推荐答案
如果我仓促下结论，请原谅我，但我强烈觉得这个问题是由于对 Tridion 缺乏了解而产生的.在 Tridion 中发布不仅仅是举一个标志来表明该项目已发布"，换句话说，准备好向外界展示.我知道这就是一些(许多)内容管理系统的运作方式(这可能解释了您问这个问题的原因).然而，在 Tridion 中，发布意味着项目实际上——物理地——从内容管理环境转移到内容交付环境.此环境始终包含您的内容版本，这些版本代表项目上次发布时的状态 - 仅仅是因为创建它们的正是发布行为.
Please forgive me if I jump to conclusions, but I strongly feel this question has arisen from a lack of understanding of Tridion. Publishing in Tridion does more than just raise a flag to indicate the item is 'published', in other words ready to be shown to the outside world. I know this is how some (many) content management systems operate (which may explain why you are asking this question). In Tridion, however, publishing means that the item is actually - physically - transferred from the content management environment to the content delivery environment. This environment always contains versions of your content that represent the state when the item was last published - simply because it was the very act of publishing that created them.
在我看来，您真正要问的是如何重建此发布功能.这从来都不是一个好主意.相反，您应该认真对待 Bart 的评论并查看 Tridion 提供的内容交付 API 之一(代理 API 或 OData Web 服务).您可以选择查看 DD4T，它构建在代理之上并公开完整的 Tridion 数据模型.
In my opinion, what you are really asking is how to rebuild this publishing functionality. This is never a good idea. Instead, you should take Bart's comment seriously and look at one of the content delivery APIs that Tridion has on offer (the broker API or the OData web service). Optionally you might want to look into DD4T, which is built on top of the broker and exposes the full Tridion data model.
这篇关于需要获取已发布的组件版本的 XML的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
