Upgrade to OxygenXML and xsd-schema

[martinanton]

I've installed the new version of the editor and what once was green TEI-xml files is now full with red dots.

Basically a header like this:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://www.tei-c.org/ns/1.0 ../meta/asbwschema.xsd" xml:id="L02772"
   xml:base="https://id.xxxxx.at">

did not work anymore. first issue was to remove the tei-part of the schemaLocation, because the xsd calls TEI as well:

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns="http://www.tei-c.org/ns/1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
   xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tei="http://www.tei-c.org/ns/1.0"
   xmlns:vc="http://www.w3.org/2007/XMLSchema-versioning" elementFormDefault="qualified"
   targetNamespace="http://www.tei-c.org/ns/1.0" vc:minVersion="1.1">
   <xs:import namespace="http://www.w3.org/XML/1998/namespace"
      schemaLocation="http://www.w3.org/2001/xml.xsd"/>

then I've tried to uninstall the TEI-plugin TEI P5 Version 16 and in the preferences of Oxygen I un-checked the external document type (» Preferences->Document Type Association in oXygen and deactivated all the TEI frameworks that have "External" in the storage columns.«)

Nevertheless with or without the plugin I get errors:
Without:
Couldn't load custom extension from class: ro.sync.ecss.extensions.tei.TEIP5ExtensionsBundle because: Could not load class: ro.sync.ecss.extensions.tei.TEIP5ExtensionsBundle
With:
404 Not Found for: https://www.oxygenxml.com/InstData/Addo ... 6088575586

and it tries to access an old framework which was there years ago.

(On current MacOS, tried several new installations, replaced the app folder, deleted the folder in Library/Application Support)

What has changed between 24.1 and 25 that the xsd doesn't work as desired anymore?

[alex_jitianu]

Hello,
It's a good thing you've uninstalled the other plugins to eliminate them as a possible cause. Although TEI P5 Version 16 packs the same version of TEI Schema (4.4.0) as Oxygen 25.
This error signals a corrupt built-in framework. it's like the tei.jar is no longer present inside the {OxygenInstallDir}/frameworks/tei folder.

Couldn't load custom extension from class: ro.sync.ecss.extensions.tei.TEIP5ExtensionsBundle because: Could not load class: ro.sync.ecss.extensions.tei.TEIP5ExtensionsBundle

The extension of this update site should be XML.

404 Not Found for: https://www.oxygenxml.com/InstData/Addo ... 6088575586
and it tries to access an old framework which was there years ago.

If you go to Help->Manage Addons... do you see any TEI related frameworks? If you do, please uninstall them. You can also go and delete [user_home_directory]/Library/Preferences/com.oxygenxml/extensions/v25.0

By the way, what error did you initially receive?

Best regards,
Alex

[martinanton]

Thank you! I believe I've done everything you suggested:

• There are no more add-ons installed, no framework listed, obsolete or not
• In the extensions folder were two subfolders, one named 24.1 and one named 25. I've deleted the extensions folder. extensions/25 was newly built when I re-started oxygen
• In the {OxygenInstallDir}/frameworks/tei-folder there was tei.jar. So to make sure it's not corrupted I've deleted the oxygen folder in the application folder and re-downloaded Oxygen but I still get

  Couldn't load custom extension from class: ro.sync.ecss.extensions.tei.TEIP5ExtensionsBundle because: Could not load class: ro.sync.ecss.extensions.tei.TEIP5ExtensionsBundle

Initially it started complaining about the xml:id as being used twice. this was solved by removing the tei-part from schemaLocation

[martinanton]

I seem to have come closer to solving the issue. I went into preferences and typed "framework" and found several wrong entries listed. Now the schema still doesn't resolve everything it did before but there seems to be good reason.

[alex_jitianu]

Hello,

Perhaps you have some additional locations in the Document Type Association / Locations preference page and those frameworks are loaded from those locations. If they have catalogs, those catalogs might intercept and resolve the schemas.

Best regards,
Alex

[martinanton]

Yes, this solves it! Thank you!