[JBoss JIRA] (FORGE-1479) Explicitly setup in Bean Validation, not in JPA
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1479?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1479:
------------------------------------------
It's either one or the other. At the moment, if you do not setup jpa, you can still create entities (but it doesn't work because there is no persistence.xml). If you do not setup Bean Validation, you cannot add a constraint.
Forge 1.x goes "you need to set it up before using it", but I wonder if Forge 2.x should go "I will set it up for you if you do not explicitelly tell me otherwise". I like this approach (less typing, less bugs), but it's up to you
> Explicitly setup in Bean Validation, not in JPA
> -----------------------------------------------
>
> Key: FORGE-1479
> URL: https://issues.jboss.org/browse/FORGE-1479
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR1
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> Just after a creating a project, a create a new entity without setting up the persistence ({{jpa-setup}}) :
> {code}
> ***SUCCESS*** Project named 'test' has been created.
> [test]$ jpa-new-entity --named Author
> [Author.java]$ jpa-new-field --named firstname --length 50
> ***SUCCESS*** Field firstname created
> {code}
> This hasn't created a {{persistence.xml}} file. But on the other hand, if I want to add a constraint on the entity, I need to explicitelly setup Bean Validation :
> {code}
> [Author.java]$ con
> connection-profile-create connection-profile-remove constraint-setup
> [Author.java]$ constraint-setup
> ***SUCCESS*** Bean Validation is installed.
> [Author.java]$ con
> connection-profile-create connection-profile-remove constraint-add constraint-setup
> [Author.java]$ constraint-add --constraint NotNull --onProperty firstname
> ***SUCCESS*** Constraint NotNull successfully configured
> {code}
> if most of the information is giving at project creation, do we still need to explicitly setup Java EE components ? At the moment we have the following :
> {code}
> servlet-setup
> ejb-setup
> soap-setup
> cdi-setup
> jms-setup
> rest-setup
> jpa-setup
> faces-setup
> jstl-setup
> jta-setup
> constraint-setup
> {code}
> Most of these commands do not have parameters (except for persistence, rest, validation). So why not activate them by default (or only if {{export ACCEPT_DEFAULTS=true}} ) ? Something like : "if the command {{constraint-add}} is entered, Forge would go {{if constraint is not setup, then I invoke constraint-setup}}", "if the command {{ejb-new}} is entered, Forge would go {{if ejb is not setup, then I invoke ejb-setup}}"
> That would save some bugs (developers forgetting to setup things), less typing and shorter scripts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (FORGE-1479) Explicitly setup in Bean Validation, not in JPA
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1479?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1479:
-------------------------------------------
So basically you want the setup steps to be "transparently" handled when running one of the other commands for the first time?
This is certainly doable, but I wonder if that is a bit confusing in itself. Alternatively, we could go the other direction, and disable the other commands in the scope of a project until setup is run.
Just a thought.
> Explicitly setup in Bean Validation, not in JPA
> -----------------------------------------------
>
> Key: FORGE-1479
> URL: https://issues.jboss.org/browse/FORGE-1479
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR1
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> Just after a creating a project, a create a new entity without setting up the persistence ({{jpa-setup}}) :
> {code}
> ***SUCCESS*** Project named 'test' has been created.
> [test]$ jpa-new-entity --named Author
> [Author.java]$ jpa-new-field --named firstname --length 50
> ***SUCCESS*** Field firstname created
> {code}
> This hasn't created a {{persistence.xml}} file. But on the other hand, if I want to add a constraint on the entity, I need to explicitelly setup Bean Validation :
> {code}
> [Author.java]$ con
> connection-profile-create connection-profile-remove constraint-setup
> [Author.java]$ constraint-setup
> ***SUCCESS*** Bean Validation is installed.
> [Author.java]$ con
> connection-profile-create connection-profile-remove constraint-add constraint-setup
> [Author.java]$ constraint-add --constraint NotNull --onProperty firstname
> ***SUCCESS*** Constraint NotNull successfully configured
> {code}
> if most of the information is giving at project creation, do we still need to explicitly setup Java EE components ? At the moment we have the following :
> {code}
> servlet-setup
> ejb-setup
> soap-setup
> cdi-setup
> jms-setup
> rest-setup
> jpa-setup
> faces-setup
> jstl-setup
> jta-setup
> constraint-setup
> {code}
> Most of these commands do not have parameters (except for persistence, rest, validation). So why not activate them by default (or only if {{export ACCEPT_DEFAULTS=true}} ) ? Something like : "if the command {{constraint-add}} is entered, Forge would go {{if constraint is not setup, then I invoke constraint-setup}}", "if the command {{ejb-new}} is entered, Forge would go {{if ejb is not setup, then I invoke ejb-setup}}"
> That would save some bugs (developers forgetting to setup things), less typing and shorter scripts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III closed FORGE-1432.
-------------------------------------
Assignee: Lincoln Baxter III
Fix Version/s: 2.0.0.Final
(was: 2.x Future)
Resolution: Done
Currently not supported:
* Prompting from scripted commands
* Probably more :)
> run command is missing (and with it, scripting)
> -----------------------------------------------
>
> Key: FORGE-1432
> URL: https://issues.jboss.org/browse/FORGE-1432
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Assignee: Lincoln Baxter III
> Fix For: 2.0.0.Final
>
>
> I use a lot of scripts to start my projects, add/remove Maven dependencies.... So when I'm in Forge console, I type {{run ../myScript.fsh}}. For example, here is a script I use to get ride of EE 6 dependencies and add EE7 :
> {code}
> @/* ====================================== */;
> @/* == From Java EE 6 to 7 Dependencies == */;
> @/* ====================================== */;
> project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ;
> project remove-dependency javax.validation:validation-api ;
> project remove-dependency org.hibernate:hibernate-validator ;
> project remove-dependency javax.enterprise:cdi-api ;
> project remove-dependency org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ;
> project remove-dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec ;
> project remove-dependency org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec ;
> project add-dependency javax:javaee-api:7.0:provided ;
> project add-dependency org.primefaces:primefaces:4.0 ;
> project add-repository primefaces-repo http://repository.primefaces.org ;
> {code}
> I have other scripts like that. The good this is, without leaving the console, I can write :
> {code}
> [Forge]$ run script1.fsh
> [Forge]$ run script2.fsh
> [Forge]$ run script3.fsh
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1432:
-------------------------------------------
Implemented the 'run' command. This does not solve the lack of FSH script support, but that will be a separate issue.
> run command is missing (and with it, scripting)
> -----------------------------------------------
>
> Key: FORGE-1432
> URL: https://issues.jboss.org/browse/FORGE-1432
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I use a lot of scripts to start my projects, add/remove Maven dependencies.... So when I'm in Forge console, I type {{run ../myScript.fsh}}. For example, here is a script I use to get ride of EE 6 dependencies and add EE7 :
> {code}
> @/* ====================================== */;
> @/* == From Java EE 6 to 7 Dependencies == */;
> @/* ====================================== */;
> project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ;
> project remove-dependency javax.validation:validation-api ;
> project remove-dependency org.hibernate:hibernate-validator ;
> project remove-dependency javax.enterprise:cdi-api ;
> project remove-dependency org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ;
> project remove-dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec ;
> project remove-dependency org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec ;
> project add-dependency javax:javaee-api:7.0:provided ;
> project add-dependency org.primefaces:primefaces:4.0 ;
> project add-repository primefaces-repo http://repository.primefaces.org ;
> {code}
> I have other scripts like that. The good this is, without leaving the console, I can write :
> {code}
> [Forge]$ run script1.fsh
> [Forge]$ run script2.fsh
> [Forge]$ run script3.fsh
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (FORGE-1313) Support commands without UI
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1313?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1313.
----------------------------------
Resolution: Done
> Support commands without UI
> ---------------------------
>
> Key: FORGE-1313
> URL: https://issues.jboss.org/browse/FORGE-1313
> Project: Forge
> Issue Type: Feature Request
> Components: UI - API, UI - Eclipse
> Affects Versions: 2.0.0.Beta2
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.0.0.Final
>
>
> Some commands/steps may not need a UI for the user to interact during a wizard. The underlying UI provider should skip it during UI interaction, then execute during execution.
> We could assume that this happens when no input is added to the UIBuilder in the initializeUI method
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (FORGE-1486) NoTransactionAssociatedException when setting up scaffolding
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1486?page=com.atlassian.jira.plugin... ]
Antonio Goncalves closed FORGE-1486.
------------------------------------
Resolution: Cannot Reproduce Bug
I cannot reproduce it (using the latest SNAPSHOT, but I wonder if it's because of that)
> NoTransactionAssociatedException when setting up scaffolding
> ------------------------------------------------------------
>
> Key: FORGE-1486
> URL: https://issues.jboss.org/browse/FORGE-1486
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR1
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I've allowed to have track changes ({{transaction-track-changes}}), and then I setup scaffolding ({{scaffold-setup}}) and I get
> {code}
> [Book.java]$ scaffold-setup
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/pom.xml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF/beans.xml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF/beans.xml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/pom.xml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF/faces-config.xml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF/faces-config.xml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF/web.xml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/WEB-INF/web.xml
> Exception in thread "Resource File Monitor" Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/error.xhtml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/error.xhtml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/index.html
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/index.html
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/index.xhtml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/index.xhtml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/add.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/add.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/bootstrap.css
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/bootstrap.css
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/false.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/false.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/favicon.ico
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/favicon.ico
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/forge-logo.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/forge-logo.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/forge-style.css
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/forge-style.css
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/jboss-community.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/jboss-community.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/remove.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/remove.png
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/scaffold
> org.jboss.forge.addon.resource.transaction.ResourceTransactionException: org.xadisk.filesystem.exceptions.NoTransactionAssociatedException: The method that was called can only be called with a transaction associated, butthere is no such transaction present.Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/scaffold
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/scaffold/pageTemplate.xhtml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/scaffold/pageTemplate.xhtml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/scaffold/paginator.xhtml
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/scaffold/paginator.xhtml
> at org.jboss.forge.addon.resource.transaction.file.FileResourceTransactionImpl.fileExistsAndIsDirectory(FileResourceTransactionImpl.java:245)W
> rote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/search.png
> at org.jboss.forge.addon.resource.FileResourceGenerator.getResourceType(FileResourceGenerator.java:29)
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/search.png at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
> Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/true.png
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)Wrote /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/webapp/resources/true.png
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> ***SUCCESS*** CDI has been installed. at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75)
> at org.jboss.forge.addon.resource.FileResourceGenerator_$$_javassist_bdd19dce-9677-4c5e-b872-98bfee50bfed.getResourceType(FileResourceGenerator_$$_javassist_bdd19dce-9677-4c5e-b872-98bfee50bfed.java)***SUCCESS***
> JavaServer Faces has been installed.
> at org.jboss.forge.addon.resource.FileResourceGenerator.getResourceType(FileResourceGenerator.java:5)
> ***SUCCESS*** at org.jboss.forge.addon.resource.ResourceFactoryImpl.create(ResourceFactoryImpl.java:64)Scaffold was setup successfully.
> at org.jboss.forge.addon.resource.monitor.FileAlterationListenerAdapter.onFileChange(FileAlterationListenerAdapter.java:64)
> at org.apache.commons.io.monitor.FileAlterationObserver.doMatch(FileAlterationObserver.java:400)
> at org.apache.commons.io.monitor.FileAlterationObserver.checkAndNotify(FileAlterationObserver.java:334)
> at org.apache.commons.io.monitor.FileAlterationObserver.checkAndNotify(FileAlterationObserver.java:304)
> at org.apache.commons.io.monitor.FileAlterationMonitor.run(FileAlterationMonitor.java:182)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: org.xadisk.filesystem.exceptions.NoTransactionAssociatedException: The method that was called can only be called with a transaction associated, butthere is no such transaction present.
> at org.xadisk.filesystem.NativeSession.checkIfCanContinue(NativeSession.java:1231)
> at org.xadisk.filesystem.NativeSession.fileExistsAndIsDirectory(NativeSession.java:445)
> at org.xadisk.filesystem.NativeSession.fileExistsAndIsDirectory(NativeSession.java:434)
> at org.jboss.forge.addon.resource.transaction.file.FileResourceTransactionImpl.fileExistsAndIsDirectory(FileResourceTransactionImpl.java:232)
> ... 16 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (FORGE-1451) Cannot scaffold REST endpoints using a * target
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1451?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1451:
-------------------------------------
Priority: Critical (was: Major)
> Cannot scaffold REST endpoints using a * target
> -----------------------------------------------
>
> Key: FORGE-1451
> URL: https://issues.jboss.org/browse/FORGE-1451
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR1
> Reporter: Antonio Goncalves
> Priority: Critical
> Fix For: 2.x Future
>
>
> When I want to generate REST enpoints for each of my entities, I can write the following in Forge 1.x :
> {code}
> rest endpoint-from-entity ~.model.* ;
> {code}
> In Forge 2.CR1 I cannot use the '*' and need to specify each entity :
> {code}
> [Book.java]$ rest-endpoint-from-entity --targets ~.model.*
> Targets must be specified.
> [Book.java]$ rest-endpoint-from-entity --targets org.javaone.javaee7.model.*
> Targets must be specified.
> [Book.java]$ rest-endpoint-from-entity --targets org.javaone.javaee7.model.Book org.javaone.javaee7.model.Speaker org.javaone.javaee7.model.Talk
> ***SUCCESS*** Endpoint created
> ***SUCCESS*** EJB has been installed.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (FORGE-1453) Cannot scaffold JSF pages using a * target
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1453?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1453:
-------------------------------------
Priority: Critical (was: Major)
> Cannot scaffold JSF pages using a * target
> ------------------------------------------
>
> Key: FORGE-1453
> URL: https://issues.jboss.org/browse/FORGE-1453
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR1
> Reporter: Antonio Goncalves
> Priority: Critical
> Fix For: 2.x Future
>
>
> When I want to generate JSF pages for each of my entities, I can write the following in Forge 1.x :
> {code}
> scaffold from-entity ~.model.* ;
> {code}
> In Forge 2.CR1 I cannot use the '*' and need to specify each entity :
> {code}
> [TalkEndpoint.java]$ scaffold-generate --targets ~.model.*
> Targets must be specified.
> [TalkEndpoint.java]$ scaffold-generate --targets org.javaone.javaee7.model.*
> Targets must be specified.
> [TalkEndpoint.java]$ scaffold-generate --targets org.javaone.javaee7.model.Book org.javaone.javaee7.model.Speaker org.javaone.javaee7.model.Talk
> ***SUCCESS*** Scaffold was generated successfully.
> [TalkEndpoint.java]$
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (FORGE-1450) Cannot create an enum attribute on an Entity
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1450?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1450:
-------------------------------------
Priority: Critical (was: Major)
> Cannot create an enum attribute on an Entity
> --------------------------------------------
>
> Key: FORGE-1450
> URL: https://issues.jboss.org/browse/FORGE-1450
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR1
> Reporter: Antonio Goncalves
> Priority: Critical
> Fix For: 2.x Future
>
>
> I've created a {{Language}} enum (with {{java-new-enum}}) and then I want my entity {{Book}} to have an attribute of type {{Language}}. In Forge 1.x I would do :
> {code}
> field custom --named language --type org.javaone.javaee7.model.Language.java ;
> {code}
> There is no such {{custom}} attribute in Forge 2.x and the following doesn't work :
> {code}
> jpa-new-field --named language --typeName org.javaone.javaee7.model.Language.java ;
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months