[forge-issues] [JBoss JIRA] (FORGE-2752) Introduce extension points in the existing Java EE commands

[Chris Laprun (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421555#comment-13421555 ] 

Chris Laprun commented on FORGE-2752:
-------------------------------------

[~gastaldi] an example of being able to modify the value of inputs would be to automatically set the generator to use the Spring Boot one when on a Spring Boot project and requesting REST endpoint generation from entities. CommandExecutionListener wouldn't let me do that since I can't access the inputs from UICommand.

> 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.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)