Integration of latest 'Gecko EMF Utilties' version#8
Integration of latest 'Gecko EMF Utilties' version#8ideas-into-software wants to merge 5 commits into
Conversation
- Fix for issue with Swagger Jakarta dependencies' OSGi metadata - included rebuilt Swagger Jakarta dependencies in local repository until released - Updated relevant bnd/bndrun files - Minor encoding-related fix Signed-off-by: Michael H. Siemaszko <mhs@into.software>
Signed-off-by: Michael H. Siemaszko <mhs@into.software>
Signed-off-by: Michael H. Siemaszko <mhs@into.software>
- Fixes for issues after dependencies' metadata updates Signed-off-by: Michael H. Siemaszko <mhs@into.software>
|
I applied fixes for issues reported earlier after dependencies' metadata updates you mentioned. Following endpoints were tested and work, i.e. return results:
The only remaining issues, which however seem to have no effect on the endpoints tested, are:
Considering this part was meant as integration of latest 'Gecko EMF Utilties' version, and that is what is done now, is there anything else you'd like me to take care of with this or can we proceed to releasing that latest Gecko EMF Utils, as per item #5 in geckoprojects-org/org.gecko.emf.utils#25 (comment) |
|
Can you do one last thing, before we merge this: Please add the dependencies for your exporters and check if you can get the expected results for e.g. http://localhost:8085/mdo/rest/trees/CityTree if you use the respective ContenTypes as MimeTypes with your requests? As an alternative to the request header, you can also use the QueryParameter For now I just want to see that it works in general. We will decide on the necessary export options that might be useful later. Please create issues for the two open issues you have mentioned. |
Signed-off-by: Michael H. Siemaszko <mhs@into.software>
Format-specific annotations ( In addition, the following issues and comments to existing issues / PRs were added: |
2 participants
@juergen-albert
PR is in draft mode due to issues which still appear - pending their resolution.
Current state and issues which still appear are:
application launched via
/de.jena.mdo.runtime/de.jena.mdo.runtime_local.bndrunautomatically shuts down after several seconds; see screencast attached; therefore, it is not possible to diagnose errors via console (gogo shell nor Felix webconsole), neither check if endpoints listed in/readme.mdare working, until this is resolved;this is after having added
de.jena.mdo.jdbc.exampletorunrequiresof/de.jena.mdo.runtime/de.jena.mdo.runtime_base.bndrunand resolved successfully; reason for adding this isjava.sql.SQLException: Database 'mdo' not found.error (full stack trace below), which I got when running via/de.jena.mdo.runtime/de.jena.mdo.runtime_local.bndrun, so I compared against/de.jena.mdo.jdbc.example/launch-derby.bndrunand this was the only bundle missing;other issues which were visible at that time were similar to those mentioned in our email / Slack exchange earlier, i.e.
Failed activation for 2 out of 3
MDODataImporterreferences - i.e. onlyMDODataImporter~trafficToAssetwas ACTIVE, the other two,MDODataImporter~treeToTreesandMDODataImporter~treeToAsset, failed activation;Failed activation also in (new one)
TrafficConfigurator;Unsatisfied references in
PiveauAdapterandPiveauRestConnector, as well as (new one)de.jena.mdo.jdbc.example.TrafficComponent;Until issue with automatic shutdown of app is resolved, it is not possible to diagnose issues which still appear, neither to verify endpoints are working.
Unfortunately, no logs indicating any error as cause for this shutdown are visible in console - the last entries before shutdown, which appear repeatedly (i.e. with each subsequent launch) are:
The
java.sql.SQLException: Database 'mdo' not founderror mentioned earlier.Screencast.from.11-15-2023.01.46.18.AM.webm