Open dstenger opened 9 years ago
The required classes are still there ([1] and [2]).
[1] org.deegree.console.datastore.feature.MappingWizardSQL [2] src/main/webapp/console/datastore/feature/sql/wizard.xhtml
Workaround needs to be described in user handbook and further technical information shall be provided how to solve this issue.
I would like to offer my help with fixing this issue. Together with the other outstanding console 3.4 issues, I would expect this to be an effort of about 5 days.
Current work-arounds are:
org.deegree.feature.persistence.sql.mapper.AppSchemaMapper
manually
The CLI tool has been integrated into deegree
Hi, I know this is old issue but I`m little bit confused what is output. I read manual where wizard is mentioned and also I can see screenshots in manual how to use it. I tried several version but I was not able to find wizard. Is it wizard in version 3.4.16 or not ? If not why is still mentioned in documentation ? @tfr42 mentioned it was removed from 3.4. Is it preferred way to use CLI tool ?
@siplo The wizard was never fully migrated into the deegree admin console in version 3.4.x. The last version with a working schema wizard was deegree webservices version 3.3.21. For deegree 3.4, and 3.5 the recommended workaround is to use the deegree GML tools CLI to generate SQL DDL scripts and SQLFeatureStore configuration files. And yes, the documentation should reflect the current status, and the screenshots with the wizard need to be removed. Volunteers are welcome .
In deegree-3.3.13 the console included an wizard being able to create a SQL FeatureStore configuration and database scripts from an GML application schema.
This wizard should be migrated to the console of deegree-3.4.
For more details see: http://download.deegree.org/documentation/3.3.13/html/featurestores.html#auto-generating-a-mapping-configuration-and-tables