unable to import-jdl for gateways with no sql
See original GitHub issueOverview of the issue
Since 4.0.3 it’s able to generate UAA based gateways without database. It’s still needed to add microservice entities using JDL. But this fails, as import-jdl assumes a app must have a database.
The error message is
The jdl is being parsed.
{ name: 'IllegalArgumentException',
message: 'The passed database type must either be \'sql\', \'mysql\', \'mariadb\', \'postgresql\', \'oracle\', \'mssql\', \'mongodb\', or \'cassandra\'',
prototype:
Error
at new buildException (/home/david/Projekte/microXchng/code/uaa-setup/gw403/node_modules/jhipster-core/lib/exceptions/exception_factory.js:43:25)
at Object.getIsType (/home/david/Projekte/microXchng/code/uaa-setup/gw403/node_modules/jhipster-core/lib/core/jhipster/field_types.js:148:11)
at init (/home/david/Projekte/microXchng/code/uaa-setup/gw403/node_modules/jhipster-core/lib/parser/jdl_parser.js:49:23)
at Object.parse [as convertToJDL] (/home/david/Projekte/microXchng/code/uaa-setup/gw403/node_modules/jhipster-core/lib/parser/jdl_parser.js:38:3)
at constructor.parseJDL (/home/david/Projekte/microXchng/code/uaa-setup/gw403/node_modules/generator-jhipster/generators/import-jdl/index.js:49:41)
at Object.<anonymous> (/home/david/Projekte/microXchng/code/uaa-setup/gw403/node_modules/yeoman-generator/lib/base.js:439:23)
at /home/david/Projekte/microXchng/code/uaa-setup/gw403/node_modules/yeoman-generator/node_modules/run-async/index.js:25:25
at /home/david/Projekte/microXchng/code/uaa-setup/gw403/node_modules/yeoman-generator/node_modules/run-async/index.js:24:19
at /home/david/Projekte/microXchng/code/uaa-setup/gw403/node_modules/yeoman-generator/lib/base.js:440:9
at runCallback (timers.js:649:20) }
Motivation for or Use Case
Need to generate frontend client for entities
Reproduce the error
Try to import a JDL file using yo jhipster:import-jdl
Related issues
allow uaa gateways to have no database configured
Suggest a Fix
I’m sure this has to be done on jhipster/jhipster-core. In particular we should assert the situation, that for gateways (with uaa) all entities must be mapped to a microservice.
JHipster Version(s)
4.0.3
JHipster configuration
UAA gateway with no Database configured
- Checking this box is mandatory (this is just to show you read everything)
Issue Analytics
- State:
- Created 7 years ago
- Comments:29 (29 by maintainers)
Top Results From Across the Web
Error while trying to import a jdl file to a jhipster project using ...
Save this question. Show activity on this post. I'm trying to import a jdl file, but I get the Error: Enumeration values must...
Read more >jhipster/generator-jhipster - Gitter
I was having some weirdness with my gateway app so I decided to start over from scratch. Getting The type 'ZonedDateTime' doesn't exist....
Read more >Creating an entity - JHipster
You can generate entities from a JDL file using the jdl sub-generator, by running jhipster jdl your-jdl-file.jh . If you do not want...
Read more >JHipster-minibook-aprilv-1556109659909 - Análise e Projeto de ...
You'll generate a gateway (powered by Netflix Zuul), a blog microservice (that talks to ... Run JHipster's import-jdl command to import this microservices ......
Read more >Relationships in JDL and NoSQL - Google Groups
However, both fail with the same error: ± yo jhipster:import-jdl store.jh. The jdl is being parsed. NoSQLModelingException: NoSQL entities don't have ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The front-end should only use the REST endpoints underneath, and not be tied to a specific database (this is not totally true: we don’t have the same pagination option for Cassandra). @MathieuAA I’m not sure which solution you find is the “best”, but I would just remove the validation.
@deepu105 Your solution is the best one. I’ll implement it and then add it to the documentation.