|
|
|
Re: Problem with ExtendedMetaData [message #1015125 is a reply to message #1015107] |
Wed, 27 February 2013 14:25 |
Ed Merks Messages: 33141 Registered: July 2009 |
Senior Member |
|
|
Patrik,
You're sure this resource factory getting used? You could set a
breakpoint in
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeature(EClass, String,
String, boolean) to see why it's failing. You can make the breakpoint
conditional on name being the name of the feature in question...
On 27/02/2013 2:30 PM, Patrik Nandorf wrote:
> yes, it seems
>
>
> /**
> * Creates an instance of the resource.
> * <!-- begin-user-doc -->
> * <!-- end-user-doc -->
> * @generated
> */
> @Override
> public Resource createResource(URI uri) {
> XMLResource result = new AResourceImpl(uri);
> result.getDefaultSaveOptions().put(XMLResource.OPTION_EXTENDED_META_DATA,
> extendedMetaData);
> result.getDefaultLoadOptions().put(XMLResource.OPTION_EXTENDED_META_DATA,
> extendedMetaData);
>
> result.getDefaultSaveOptions().put(XMLResource.OPTION_SCHEMA_LOCATION,
> Boolean.TRUE);
>
> result.getDefaultLoadOptions().put(XMLResource.OPTION_USE_ENCODED_ATTRIBUTE_STYLE,
> Boolean.TRUE);
> result.getDefaultSaveOptions().put(XMLResource.OPTION_USE_ENCODED_ATTRIBUTE_STYLE,
> Boolean.TRUE);
>
> result.getDefaultLoadOptions().put(XMLResource.OPTION_USE_LEXICAL_HANDLER,
> Boolean.TRUE);
> return result;
> }
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03852 seconds