com.sun.syndication.io.impl
クラス BaseWireFeedGenerator
java.lang.Object
com.sun.syndication.io.impl.BaseWireFeedGenerator
- すべての実装されたインタフェース:
- WireFeedGenerator
- 直系の既知のサブクラス:
- Atom03Generator, Atom10Generator, RSS090Generator
public abstract class BaseWireFeedGenerator
- extends java.lang.Object
- implements WireFeedGenerator
| クラス java.lang.Object から継承されたメソッド |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
BaseWireFeedGenerator
protected BaseWireFeedGenerator(java.lang.String type)
getType
public java.lang.String getType()
- インタフェース
WireFeedGenerator の記述:
- Returns the type of feed the generator creates.
- 定義:
- インタフェース
WireFeedGenerator 内の getType
- 戻り値:
- the type of feed the generator creates.
- 関連項目:
for details on the format of this string.
generateModuleNamespaceDefs
protected void generateModuleNamespaceDefs(Element root)
generateFeedModules
protected void generateFeedModules(java.util.List modules,
Element feed)
generateItemModules
public void generateItemModules(java.util.List modules,
Element item)
generateForeignMarkup
protected void generateForeignMarkup(Element e,
java.util.List foreignMarkup)
purgeUnusedNamespaceDeclarations
protected static void purgeUnusedNamespaceDeclarations(Element root)
- Purging unused declarations is less optimal, performance-wise, than never adding them in the first place. So, we
should still ask the ROME guys to fix their code (not adding dozens of unnecessary module declarations). Having
said that: purging them here, before XML generation, is more efficient than parsing and re-molding the XML after
ROME generates it.
Note that the calling app could still add declarations/modules to the Feed tree after this. Which is fine. But
those modules are then responsible for crawling to the root of the tree, at generate() time, to make sure their
namespace declarations are present.