Examples of NamespaceResolver

client.net.sf.saxon.ce.om.NamespaceResolver
Abstract class that supports lookup of a lexical QName to get the expanded QName.
net.sf.saxon.om.NamespaceResolver
Abstract class that supports lookup of a lexical QName to get the expanded QName.
org.apache.commons.jxpath.ri.NamespaceResolver
Namespace resolver for {@link JXPathContextReferenceImpl}. @author Dmitri Plotnikov @version $Revision: 668329 $ $Date: 2008-06-16 16:59:48 -0500 (Mon, 16 Jun 2008) $
org.apache.jackrabbit.name.NamespaceResolver
Interface for resolving namespace URIs and prefixes. Unlike the JCR {@link javax.jcr.NamespaceRegistry} interface, this interface containsno functionality other than the basic namespace URI and prefix resolution methods. This interface is therefore used internally in many places where the full namespace registry is either not available or some other mechanism is used for resolving namespaces.
org.apache.jackrabbit.spi.commons.namespace.NamespaceResolver
Interface for resolving namespace URIs and prefixes. Unlike the JCR {@link javax.jcr.NamespaceRegistry} interface, this interface containsno functionality other than the basic namespace URI and prefix resolution methods. This interface is therefore used internally in many places where the full namespace registry is either not available or some other mechanism is used for resolving namespaces.
org.eclipse.persistence.internal.oxm.NamespaceResolver

It is common for an XML document to include one or more namespaces. TopLink supports this using its NamespaceResolver. The namespace resolver maintains pairs of namespace prefixes and URIs. TopLink uses these prefixes in conjunction with the XPath statements you specify on EIS mappings to XML records and XML mappings.
Although TopLink captures namespace prefixes in the XPath statements for mappings (if applicable), the input document is not required to use the same namespace prefixes. TopLink will use the namespace prefixes specified in the mapping when creating new documents.
Code Sample
NamespaceResolver resolver = new NamespaceResolver(); resolver.put( "ns", "urn:namespace-example"); XMLDescriptor descriptor = new XMLDescriptor(); descriptor.setJavaClass(Customer.class); descriptor.setDefaultRootElement("ns:customer"); descriptor.setNamespaceResolver(resolver); XMLDirectMapping mapping = new XMLDirectMapping(); mapping.setAttributeName("id"); mapping.setXPath("ns:id/text()"); descriptor.addMapping(mapping); @see org.eclipse.persistence.oxm.XMLDescriptor @see org.eclipse.persistence.eis.EISDescriptor
org.eclipse.persistence.oxm.NamespaceResolver

It is common for an XML document to include one or more namespaces. TopLink supports this using its NamespaceResolver. The namespace resolver maintains pairs of namespace prefixes and URIs. TopLink uses these prefixes in conjunction with the XPath statements you specify on EIS mappings to XML records and XML mappings.
Although TopLink captures namespace prefixes in the XPath statements for mappings (if applicable), the input document is not required to use the same namespace prefixes. TopLink will use the namespace prefixes specified in the mapping when creating new documents.
Code Sample
NamespaceResolver resolver = new NamespaceResolver(); resolver.put( "ns", "urn:namespace-example"); XMLDescriptor descriptor = new XMLDescriptor(); descriptor.setJavaClass(Customer.class); descriptor.setDefaultRootElement("ns:customer"); descriptor.setNamespaceResolver(resolver); XMLDirectMapping mapping = new XMLDirectMapping(); mapping.setAttributeName("id"); mapping.setXPath("ns:id/text()"); descriptor.addMapping(mapping); @see org.eclipse.persistence.oxm.XMLDescriptor @see org.eclipse.persistence.eis.EISDescriptor
org.pdf4j.saxon.om.NamespaceResolver
Abstract class that supports lookup of a lexical QName to get the expanded QName.

Examples of org.eclipse.persistence.oxm.NamespaceResolver

    private boolean xmlDeclaration;
    private NamespaceResolver namespaceResolver;


    public SDOXMLDocument() {
        xmlDeclaration = true;
        namespaceResolver = new NamespaceResolver();
    }

View Full Code Here

Examples of org.eclipse.persistence.oxm.NamespaceResolver

        addDescriptor(buildInstantiationCopyPolicyDescriptor());
        
        addDescriptor(buildPropertyDescriptor());


        // Set the name spaces on all descriptors.
        NamespaceResolver namespaceResolver = new NamespaceResolver();
        namespaceResolver.put("xsi", "http://www.w3.org/2001/XMLSchema-instance");
        //namespaceResolver.put("xsd", "http://www.w3.org/2001/XMLSchema");
        namespaceResolver.put("orm", ormNamespace);


        for (XMLDescriptor descriptor : (Collection<XMLDescriptor>) getDescriptors().values()) {
            descriptor.setNamespaceResolver(namespaceResolver);
        }

View Full Code Here

Examples of org.pdf4j.saxon.om.NamespaceResolver

        if (p == null) {
            prefix = "";
        } else {
            prefix = p.getStringValue();
        }
        NamespaceResolver resolver = new InscopeNamespaceResolver(element);
        String uri = resolver.getURIForPrefix(prefix, true);
        if (uri == null) {
            return null;
        }
        return new AnyURIValue(uri);
    }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.