Hi Luis, You have several options:
*1) Don't use the code generator.* Of course, this is the least preferrable option, because without code generation, you'll be missing out on quite a few nice features in jOOQ. But of course, jOOQ can totally be used without it, the API is exactly the same. Here's an example from the tutorial, making use of "plain SQL": https://www.jooq.org/doc/latest/manual/getting-started/use-cases/jooq-as-a-standalone-sql-builder And here's the chapter about plain SQL: https://www.jooq.org/doc/latest/manual/sql-building/plain-sql *2) Use an "offline" meta data source for the code generator.* We currently support the following 3 modes of generating code "offline", i.e. without an actual database connection: *From an XML file:* https://www.jooq.org/doc/latest/manual/code-generation/codegen-xml The XML file implements this schema: https://www.jooq.org/xsd/jooq-meta-3.10.0.xsd The advantage of this approach is that you can easily generate the XML file from some other meta data description, e.g. using XSLT. *From a DDL file:* https://www.jooq.org/doc/latest/manual/code-generation/codegen-ddl The jOOQ parser (introduced in 3.9) can parse almost all SQL that can be represented with the jOOQ API, so if you're not using any fancy, vendor-specific DDL extensions, then you could directly reuse your DDL scripts to generate jOOQ code. Behind the scenes, the DDL is translated to the H2 dialect and imported into an in-memory H2 database prior to reverse engineering that. If you run into issues with this approach, please do let us know. We're always happy to extend parser functionality. *From JPA annotated entities:* https://www.jooq.org/doc/latest/manual/code-generation/codegen-jpa If you already work with JPA along with jOOQ, you can re-use the meta information defined in your entities and reverse engineer those. Behind the scenes, jOOQ uses Hibernate to generate an in-memory H2 database, and reverse engineers that afterwards. *3. Write your own meta data implementation* The meta data implementations defined in jooq-meta or jooq-meta-extensions can be extended easily for you to define your own meta data specification. Let me know if you need more help with that. Cheers, Lukas 2018-01-04 0:21 GMT+01:00 Luis Diego Arce <lda.l...@gmail.com>: > Hi everybody!! > > I'm exploring the benefits and advantages of using AWS CI/CD tools and in > the middle of this process I'm using a specific project developed in Maven, > but I'm facing several issues when attempting to generate the WAR file. > Basically, I'm getting common communication issues between AWS services > (cloud) and my database server (internal network). It could be easily fixed > by creating a secure communication channel (VPN, open some ports thru my > router, etc.) between my network and AWS, but it's not what I expect to do > at this point, even more, when I do really want to automate the build > process using AWS CodePipeline. > > Honestly, I'm not an expert Java programmer and also I'm new using jOOQ, > so my question is: is there a way to continue with the build process of the > project without these limitations of getting data from our database server, > something like skipping the generation of code or simulate it? Is jOOQ > optimized for Continuous Integration/Continuous Delivery? Do you have > examples of how to perform this kind of implementation? Is it a limitation > of AWS CI/CD tools or from the jOOQ side? > > I'm currently doing research on how to create a pipeline with AWS CI/CD > tools, and everything works fine with the first phase (Continuous > Integration) but I'm stuck when working with AWS CodeBuild and trying to > generate the artifacts with Maven and jOOQ plugin. > I'm using a YML file that specifies what to do during the build process > and that file contains some Ubuntu commands only (these commands are > executed from a docker image with Ubuntu). > > Thanks in advance for your help and assistance. > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jooq-user+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to jooq-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
