Home » Archived » XML Schema Definition (XSD) » handle import of other documents
|
| Re: handle import of other documents [message #72657 is a reply to message #72643] |
Thu, 28 June 2007 13:50   |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
The support for <xsd:include> and <xsd:import> is already implemented.
Perhaps I misunderstand? In order for imports and include to resolve
it's important for the XSDSchema instance to be contained by a resource
that's contained by a resource set, since the additional schemas that
must be loaded need to be loaded into that resource set. Have a look at
XSDMainExample for how to set things up properly. Note that if the
schemaLocations are relative URIs, it's also important to specify an
absolute URI for loading the initial schema since relative URIs within
the schema are interpreted relative of the absolute URI of the
containing document.
urs zeidler wrote:
> In a given schema i have an include element, with the semantic of
> importing an other document, so that the elements are resolved locally.
>
> How should i implementing this import element.
|
|
| |
| Re: handle import of other documents [message #72685 is a reply to message #72670] |
Thu, 28 June 2007 15:55 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------060108000900000600000803
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
I see. This isn't related directly related to XSD then. Normally EMF
would let you refer to things in other documents directly, without need
for a specific attribute to define which resource is being "imported".
I demoed a bit of that in the Webinar Rich and I gave yesterday:
http://live.eclipse.org/node/278
If you wanted to process such an "import" directly, you'd get the
containing resource's URI, (eObject.eResource().getURI()), call
URI.resolve with the "resource" attribute value converted to a URI to
get an absolute URI, and then use ResourceSet.getResource(<resolvedURI>,
true) to demand load that resource. You could use the
XMLResource.OPTION_RESOURCE_HANDLER to do such post processing right
after load automatically.
urs zeidler wrote:
> Perhaps i have ask the wrong way.
> It's not about the import of an other schema,
> it's about importing another document of the same schema.
> The import element is define in this schema like this :
>
>
> <xsd:element name="import">
> <xsd:annotation>
> <xsd:documentation
> source="java:org.springframework.core.io.Resource">
> Specifies an XML bean definition resource to import.
> </xsd:documentation>
> </xsd:annotation>
> <xsd:complexType>
> <xsd:complexContent>
> <xsd:restriction base="xsd:anyType">
> <xsd:attribute name="resource" type="xsd:string"
> use="required">
> <xsd:annotation>
> <xsd:documentation>
> The relative resource location of the XML (bean definition) file
> to import,
> for example "myImport.xml" or "includes/myImport.xml" or
> "../myImport.xml".
> </xsd:documentation>
> </xsd:annotation>
> </xsd:attribute>
> </xsd:restriction>
> </xsd:complexContent>
> </xsd:complexType>
> </xsd:element>
>
> so the xsd2emf importer creates this :
>
> <eClassifiers xsi:type="ecore:EClass" name="ImportType">
> <eAnnotations
> source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
> <details key="name" value="import_._type"/>
> <details key="kind" value="empty"/>
> </eAnnotations>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="resource"
> unique="false"
> lowerBound="1" eType="ecore:EDataType
> http://www.eclipse.org/emf/2003/XMLType#//String">
> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel">
> <details key="documentation" value="
	The
> relative resource location of the XML (bean definition) file to
> import,
	for example "myImport.xml" or
> "includes/myImport.xml" or
> "../myImport.xml".
&# x9;						 "/>
>
> </eAnnotations>
> <eAnnotations
> source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
> <details key="kind" value="attribute"/>
> <details key="name" value="resource"/>
> </eAnnotations>
> </eStructuralFeatures>
> </eClassifiers>
>
> Witch lead to this interface :
> /**
> * <copyright>
> * </copyright>
> *
> * $Id: ImportType.java,v 1.1 2007/03/15 14:29:11 urs Exp $
> */
> package org.springframework.schema.beans;
>
> import org.eclipse.emf.ecore.EObject;
>
> /**
> * <!-- begin-user-doc -->
> * A representation of the model object '<em><b>Import Type</b></em>'.
> * <!-- end-user-doc -->
> *
> * <p>
> * The following features are supported:
> * <ul>
> * <li>{@link
> org.springframework.schema.beans.ImportType#getResource
> <em>Resource</em>}</li>
> * </ul>
> * </p>
> *
> * @see org.springframework.schema.beans.BeansPackage#getImportType( )
> * @model extendedMetaData="name='import_._type' kind='empty'"
> * @generated
> */
> public interface ImportType extends EObject {
> /**
> * Returns the value of the '<em><b>Resource</b></em>' attribute.
> * <!-- begin-user-doc -->
> * <!-- end-user-doc -->
> * <!-- begin-model-doc -->
> *
> * The relative resource location of the XML (bean definition)
> file to import,
> * for example "myImport.xml" or "includes/myImport.xml" or
> "../myImport.xml".
> *
> * <!-- end-model-doc -->
> * @return the value of the '<em>Resource</em>' attribute.
> * @see #setResource(String)
> * @see
> org.springframework.schema.beans.BeansPackage#getImportType_ Resource()
> * @model unique="false"
> dataType="org.eclipse.emf.ecore.xml.type.String" required="true"
> * extendedMetaData="kind='attribute' name='resource'"
> * @generated
> */
> String getResource();
>
> /**
> * Sets the value of the '{@link
> org.springframework.schema.beans.ImportType#getResource
> <em>Resource</em>}' attribute.
> * <!-- begin-user-doc -->
> * <!-- end-user-doc -->
> * @param value the new value of the '<em>Resource</em>' attribute.
> * @see #getResource()
> * @generated
> */
> void setResource(String value);
>
> } // ImportType
>
>
> I think I need to load the resource, and add them somehow to the
> ResourceSet, that EMF can resolve the elements defined in the imported
> documents.
> And this is the main question for me. (perhaps that's an EMF question)
>
> greetings urs.
--------------060108000900000600000803
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I see. This isn't related directly related to XSD then.
|
|
|
| Re: handle import of other documents [message #72698 is a reply to message #72685] |
Thu, 28 June 2007 16:14 |
 urs zeidler
Messages: 91
Registered: July 2009 |
Member |
|
|
Ed Merks schrieb:
> I see. This isn't related directly related to XSD then. Normally EMF
> would let you refer to things in other documents directly, without need
> for a specific attribute to define which resource is being "imported".
> I demoed a bit of that in the Webinar Rich and I gave yesterday:
>
> http://live.eclipse.org/node/278
>
> If you wanted to process such an "import" directly, you'd get the
> containing resource's URI, (eObject.eResource().getURI()), call
> URI.resolve with the "resource" attribute value converted to a URI to
> get an absolute URI, and then use ResourceSet.getResource(<resolvedURI>,
> true) to demand load that resource. You could use the
> XMLResource.OPTION_RESOURCE_HANDLER to do such post processing right
> after load automatically.
>
I know that EMF can resolve other documents, but i need to stay with the
schema, because the documents are for an other application (the spring
container) and they need to be readable by it as unqualified XML.
Thanks, i will try your hints, when i have further questions i will take
the EMF group.
greetings urs.
|
|
|
| Re: handle import of other documents [message #602467 is a reply to message #72643] |
Thu, 28 June 2007 13:50 |
Ed Merks
Messages: 33133
Registered: July 2009 |
Senior Member |
|
|
The support for <xsd:include> and <xsd:import> is already implemented.
Perhaps I misunderstand? In order for imports and include to resolve
it's important for the XSDSchema instance to be contained by a resource
that's contained by a resource set, since the additional schemas that
must be loaded need to be loaded into that resource set. Have a look at
XSDMainExample for how to set things up properly. Note that if the
schemaLocations are relative URIs, it's also important to specify an
absolute URI for loading the initial schema since relative URIs within
the schema are interpreted relative of the absolute URI of the
containing document.
urs zeidler wrote:
> In a given schema i have an include element, with the semantic of
> importing an other document, so that the elements are resolved locally.
>
> How should i implementing this import element.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| |
| Re: handle import of other documents [message #602477 is a reply to message #72670] |
Thu, 28 June 2007 15:55 |
Ed Merks
Messages: 33133
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------060108000900000600000803
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
I see. This isn't related directly related to XSD then. Normally EMF
would let you refer to things in other documents directly, without need
for a specific attribute to define which resource is being "imported".
I demoed a bit of that in the Webinar Rich and I gave yesterday:
http://live.eclipse.org/node/278
If you wanted to process such an "import" directly, you'd get the
containing resource's URI, (eObject.eResource().getURI()), call
URI.resolve with the "resource" attribute value converted to a URI to
get an absolute URI, and then use ResourceSet.getResource(<resolvedURI>,
true) to demand load that resource. You could use the
XMLResource.OPTION_RESOURCE_HANDLER to do such post processing right
after load automatically.
urs zeidler wrote:
> Perhaps i have ask the wrong way.
> It's not about the import of an other schema,
> it's about importing another document of the same schema.
> The import element is define in this schema like this :
>
>
> <xsd:element name="import">
> <xsd:annotation>
> <xsd:documentation
> source="java:org.springframework.core.io.Resource">
> Specifies an XML bean definition resource to import.
> </xsd:documentation>
> </xsd:annotation>
> <xsd:complexType>
> <xsd:complexContent>
> <xsd:restriction base="xsd:anyType">
> <xsd:attribute name="resource" type="xsd:string"
> use="required">
> <xsd:annotation>
> <xsd:documentation>
> The relative resource location of the XML (bean definition) file
> to import,
> for example "myImport.xml" or "includes/myImport.xml" or
> "../myImport.xml".
> </xsd:documentation>
> </xsd:annotation>
> </xsd:attribute>
> </xsd:restriction>
> </xsd:complexContent>
> </xsd:complexType>
> </xsd:element>
>
> so the xsd2emf importer creates this :
>
> <eClassifiers xsi:type="ecore:EClass" name="ImportType">
> <eAnnotations
> source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
> <details key="name" value="import_._type"/>
> <details key="kind" value="empty"/>
> </eAnnotations>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="resource"
> unique="false"
> lowerBound="1" eType="ecore:EDataType
> http://www.eclipse.org/emf/2003/XMLType#//String">
> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel">
> <details key="documentation" value="
	The
> relative resource location of the XML (bean definition) file to
> import,
	for example "myImport.xml" or
> "includes/myImport.xml" or
> "../myImport.xml".
&# x9;						 "/>
>
> </eAnnotations>
> <eAnnotations
> source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
> <details key="kind" value="attribute"/>
> <details key="name" value="resource"/>
> </eAnnotations>
> </eStructuralFeatures>
> </eClassifiers>
>
> Witch lead to this interface :
> /**
> * <copyright>
> * </copyright>
> *
> * $Id: ImportType.java,v 1.1 2007/03/15 14:29:11 urs Exp $
> */
> package org.springframework.schema.beans;
>
> import org.eclipse.emf.ecore.EObject;
>
> /**
> * <!-- begin-user-doc -->
> * A representation of the model object '<em><b>Import Type</b></em>'.
> * <!-- end-user-doc -->
> *
> * <p>
> * The following features are supported:
> * <ul>
> * <li>{@link
> org.springframework.schema.beans.ImportType#getResource
> <em>Resource</em>}</li>
> * </ul>
> * </p>
> *
> * @see org.springframework.schema.beans.BeansPackage#getImportType( )
> * @model extendedMetaData="name='import_._type' kind='empty'"
> * @generated
> */
> public interface ImportType extends EObject {
> /**
> * Returns the value of the '<em><b>Resource</b></em>' attribute.
> * <!-- begin-user-doc -->
> * <!-- end-user-doc -->
> * <!-- begin-model-doc -->
> *
> * The relative resource location of the XML (bean definition)
> file to import,
> * for example "myImport.xml" or "includes/myImport.xml" or
> "../myImport.xml".
> *
> * <!-- end-model-doc -->
> * @return the value of the '<em>Resource</em>' attribute.
> * @see #setResource(String)
> * @see
> org.springframework.schema.beans.BeansPackage#getImportType_ Resource()
> * @model unique="false"
> dataType="org.eclipse.emf.ecore.xml.type.String" required="true"
> * extendedMetaData="kind='attribute' name='resource'"
> * @generated
> */
> String getResource();
>
> /**
> * Sets the value of the '{@link
> org.springframework.schema.beans.ImportType#getResource
> <em>Resource</em>}' attribute.
> * <!-- begin-user-doc -->
> * <!-- end-user-doc -->
> * @param value the new value of the '<em>Resource</em>' attribute.
> * @see #getResource()
> * @generated
> */
> void setResource(String value);
>
> } // ImportType
>
>
> I think I need to load the resource, and add them somehow to the
> ResourceSet, that EMF can resolve the elements defined in the imported
> documents.
> And this is the main question for me. (perhaps that's an EMF question)
>
> greetings urs.
--------------060108000900000600000803
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I see. This isn't related directly related to XSD then.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: handle import of other documents [message #602482 is a reply to message #72685] |
Thu, 28 June 2007 16:14 |
urs zeidler
Messages: 91
Registered: July 2009 |
Member |
|
|
Ed Merks schrieb:
> I see. This isn't related directly related to XSD then. Normally EMF
> would let you refer to things in other documents directly, without need
> for a specific attribute to define which resource is being "imported".
> I demoed a bit of that in the Webinar Rich and I gave yesterday:
>
> http://live.eclipse.org/node/278
>
> If you wanted to process such an "import" directly, you'd get the
> containing resource's URI, (eObject.eResource().getURI()), call
> URI.resolve with the "resource" attribute value converted to a URI to
> get an absolute URI, and then use ResourceSet.getResource(<resolvedURI>,
> true) to demand load that resource. You could use the
> XMLResource.OPTION_RESOURCE_HANDLER to do such post processing right
> after load automatically.
>
I know that EMF can resolve other documents, but i need to stay with the
schema, because the documents are for an other application (the spring
container) and they need to be readable by it as unqualified XML.
Thanks, i will try your hints, when i have further questions i will take
the EMF group.
greetings urs.
|
|
|
Goto Forum:
Current Time: Tue Apr 16 15:25:38 GMT 2024
Powered by FUDForum. Page generated in 0.19794 seconds |
] 
Search
Help
Register
Login
Home
