]
Chris Laprun commented on FORGE-2752:
-------------------------------------
Example of things that could also make it easier to reuse commands:
- Make it easier to parse results (i.e. make it possible to know is a result is a success
or failure)
- Make it possible to modify the values of inputs of commands (for example to
automatically provide values to inputs) when using a command transformer.
Introduce extension points in the existing Java EE commands
-----------------------------------------------------------
Key: FORGE-2752
URL:
https://issues.jboss.org/browse/FORGE-2752
Project: Forge
Issue Type: Enhancement
Components: Java EE
Affects Versions: 3.7.0.Final
Reporter: George Gastaldi
Fix For: 3.x Future
JPA and REST commands are used in the Java EE addon but could perform differently when
using another technology (like Spring Boot, for example).
Example:
JPA: In Spring Boot, there is no {{persistence.xml}}, but an {{application.properties}}
file that contains the necessary information.
REST: Even though JAX-RS is not used, the generated REST endpoints would need extra
annotations to perform correctly. This is accomplished now
Right now the JPASetupWizard for example delegates the action to a PersistenceOperations
class directly. It would be nice if we could introduce some indirection (or even extract
to a common addon) in the commands.execute() method.
One idea is to have a Command -> Facet -> Operations sequence, so other
technologies (like Spring Boot) could reuse the same command by only implementing a
different facet.