[JBoss JIRA] (FORGE-848) Forge should support a @CommandScoped annotation
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-848?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-848:
----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 1.3.1.Final
(was: 1.x Future)
Resolution: Done
> Forge should support a @CommandScoped annotation
> ------------------------------------------------
>
> Key: FORGE-848
> URL: https://issues.jboss.org/browse/FORGE-848
> Project: Forge
> Issue Type: Feature Request
> Components: Container, Plugin API
> Reporter: Vineet Reynolds
> Assignee: George Gastaldi
> Fix For: 1.3.1.Final
>
>
> Forge should support a {{@CommandScoped}} just like the {{@ProjectScoped}} annotation. {{@CommandScoped}} objects would have a shorter lifetime since their lifecycle would be constrained to the execution of a command. This is equivalent to {{@RequestScoped}} instances, so we could renamed {{@CommandScoped}} to {{@RequestScoped}} if appropriate.
> Options passed to the Forge plugins could be made available via this scope. Not a binding requirement, since ambiguous dependencies could be encountered when injecting into managed beans.
--
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
11 years
[JBoss JIRA] (FORGE-917) Faces scaffolding omits fields in the create/edit/search views when they do not have setter methods
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-917?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-917:
----------------------------------
Status: Closed (was: Pull Request Sent)
Resolution: Done
> Faces scaffolding omits fields in the create/edit/search views when they do not have setter methods
> ---------------------------------------------------------------------------------------------------
>
> Key: FORGE-917
> URL: https://issues.jboss.org/browse/FORGE-917
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.0.5.Final, 1.3.0.Final
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
> Fix For: 1.3.1.Final
>
>
> This is from the TicketMonster model. The create,edit and search views for the {{SectionAllocation}} and {{Ticket}} classes only list the current values of the entities. Creating new entities or editing of existing entities of such classes with user-specified values is not possible. Likewise, searching with a criteria is not possible.
> Both these JPA entities have one thing in common, in that they do not have setters for their fields.
--
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
11 years
[JBoss JIRA] (FORGE-959) ClassCastException with CLAC when the attribute added to UIContext.setAttribute is an Enum
by George Gastaldi (JIRA)
George Gastaldi created FORGE-959:
-------------------------------------
Summary: ClassCastException with CLAC when the attribute added to UIContext.setAttribute is an Enum
Key: FORGE-959
URL: https://issues.jboss.org/browse/FORGE-959
Project: Forge
Issue Type: Bug
Components: Container
Affects Versions: 2.0.0.Alpha5
Reporter: George Gastaldi
Assignee: Lincoln Baxter III
Fix For: 2.x Future
This was spotted in the NewFieldWizard when transitioning to NewFieldRelationshipWizardStep:
{code}
RelationshipType enumValue = ...
UIContext.setAttribute("value", enumValue);
enumValue = (RelationshipType) UIContext.getAttribute("value")// CCE
{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
11 years
[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-378.
---------------------------------
Fix Version/s: (was: 2.x Future)
Resolution: Duplicate Issue
This will be implemented as an Addon in Forge 2. See FORGE-957
> Add "environments" as a first class construct
> ---------------------------------------------
>
> Key: FORGE-378
> URL: https://issues.jboss.org/browse/FORGE-378
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell, Usability
> Reporter: Pete Muir
>
> For example:
> {code}
> set environment JBOSS_AS7 --version 7.1.0.Final
> {code}
> Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7.
> For example, the persistence plugin could read from this, changing
> {code}
> persistence setup --provider HIBERNATE --container JBOSS_AS7
> {code}
> to
> {code}
> persistence setup
> {code}
> Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use.
> Lot's of other places where this could provide better defaulting, or remove the need to ask questions.
> This also seems fairly consistent with the Forge approach - good understanding of the project in question.
--
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
11 years