[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-927?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds updated FORGE-927:
----------------------------------
Affects Version/s: 1.3.0.Final
(was: 1.3.1.Final)
> Add Ajax support for Searching entities.
> ----------------------------------------
>
> Key: FORGE-927
> URL: https://issues.jboss.org/browse/FORGE-927
> Project: Forge
> Issue Type: Feature Request
> Components: Scaffold
> Affects Versions: 1.3.0.Final
> Environment: Any
> Reporter: Hanine Hanynowsky
> Priority: Optional
> Fix For: 2.x Future
>
>
> For a better user experience, adding ajax support for searching entities will be appreciated.
> Here are the modifications to have such support:
> For example: Let's consider the entity : *World.java*
> 1- change the method {{public void paginate(){}}} to {{public void paginate(AjaxBehaviorEvent event){}}} in *WorldBean.java*
> 2- in */world/search.xhtml* : change =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" />}}
> bq. to =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
> 3- embed : {{<f:ajax />}} in {{<h:inputText}} fields and/or {{<h:selecOneMenu}} ... components.....this way:
> {{<h:inputText ........>}}
> {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} {{execute="@form" />}}
> {{</h:inputText>}}
> Remark: the ajax event for SelectOneMenu is click, not keyup.
> 4- finally in *WorldBean.java*, modify the create method, so that it becomes:
> bq. {{public String create() {}}
> {{if (this.conversation.isTransient()) {}}
> {{this.conversation.begin();}}
> {{} else {}}
> {{this.conversation.end();}}
> {{}}}
> {{return "create?faces-redirect=true";}}
> {{}}}}}
> 5- Optional: remove the search button in *search.xhtml*
> That's all.
> Ideally, Forge should let the developer specify if he/she would like to generate these statements in order to enable Ajax or not. Example:
> {{*scaffold-x from World.java --enableAjax true*}}
--
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
10 years, 10 months
[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-927?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-927:
----------------------------------
Affects Version/s: 1.3.1.Final
(was: 2.0.0.Alpha4)
> Add Ajax support for Searching entities.
> ----------------------------------------
>
> Key: FORGE-927
> URL: https://issues.jboss.org/browse/FORGE-927
> Project: Forge
> Issue Type: Feature Request
> Components: Scaffold
> Affects Versions: 1.3.1.Final
> Environment: Any
> Reporter: Hanine Hanynowsky
> Priority: Optional
> Fix For: 2.x Future
>
>
> For a better user experience, adding ajax support for searching entities will be appreciated.
> Here are the modifications to have such support:
> For example: Let's consider the entity : *World.java*
> 1- change the method {{public void paginate(){}}} to {{public void paginate(AjaxBehaviorEvent event){}}} in *WorldBean.java*
> 2- in */world/search.xhtml* : change =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" />}}
> bq. to =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
> 3- embed : {{<f:ajax />}} in {{<h:inputText}} fields and/or {{<h:selecOneMenu}} ... components.....this way:
> {{<h:inputText ........>}}
> {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} {{execute="@form" />}}
> {{</h:inputText>}}
> Remark: the ajax event for SelectOneMenu is click, not keyup.
> 4- finally in *WorldBean.java*, modify the create method, so that it becomes:
> bq. {{public String create() {}}
> {{if (this.conversation.isTransient()) {}}
> {{this.conversation.begin();}}
> {{} else {}}
> {{this.conversation.end();}}
> {{}}}
> {{return "create?faces-redirect=true";}}
> {{}}}}}
> 5- Optional: remove the search button in *search.xhtml*
> That's all.
> Ideally, Forge should let the developer specify if he/she would like to generate these statements in order to enable Ajax or not. Example:
> {{*scaffold-x from World.java --enableAjax true*}}
--
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
10 years, 10 months
[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-927?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-927:
----------------------------------
Fix Version/s: 2.x Future
(was: 1.x Future)
> Add Ajax support for Searching entities.
> ----------------------------------------
>
> Key: FORGE-927
> URL: https://issues.jboss.org/browse/FORGE-927
> Project: Forge
> Issue Type: Feature Request
> Components: Scaffold
> Affects Versions: 2.0.0.Alpha4
> Environment: Any
> Reporter: Hanine Hanynowsky
> Priority: Optional
> Fix For: 2.x Future
>
>
> For a better user experience, adding ajax support for searching entities will be appreciated.
> Here are the modifications to have such support:
> For example: Let's consider the entity : *World.java*
> 1- change the method {{public void paginate(){}}} to {{public void paginate(AjaxBehaviorEvent event){}}} in *WorldBean.java*
> 2- in */world/search.xhtml* : change =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" />}}
> bq. to =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
> 3- embed : {{<f:ajax />}} in {{<h:inputText}} fields and/or {{<h:selecOneMenu}} ... components.....this way:
> {{<h:inputText ........>}}
> {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} {{execute="@form" />}}
> {{</h:inputText>}}
> Remark: the ajax event for SelectOneMenu is click, not keyup.
> 4- finally in *WorldBean.java*, modify the create method, so that it becomes:
> bq. {{public String create() {}}
> {{if (this.conversation.isTransient()) {}}
> {{this.conversation.begin();}}
> {{} else {}}
> {{this.conversation.end();}}
> {{}}}
> {{return "create?faces-redirect=true";}}
> {{}}}}}
> 5- Optional: remove the search button in *search.xhtml*
> That's all.
> Ideally, Forge should let the developer specify if he/she would like to generate these statements in order to enable Ajax or not. Example:
> {{*scaffold-x from World.java --enableAjax true*}}
--
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
10 years, 10 months
[JBoss JIRA] (FORGE-518) projectFactory.createProjet doesn't work out of embeded plugins
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-518?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-518.
---------------------------------
Fix Version/s: 2.0.0.Alpha5
(was: 1.x Future)
Resolution: Done
Fixed in Forge 2.0.0.Alpha5
> projectFactory.createProjet doesn't work out of embeded plugins
> ---------------------------------------------------------------
>
> Key: FORGE-518
> URL: https://issues.jboss.org/browse/FORGE-518
> Project: Forge
> Issue Type: Bug
> Components: Builtin Plugins, Forge Build
> Affects Versions: 1.0.0.Final
> Environment: Windows XP Professional Service Pack 3 - 32 bits
> Reporter: Guillaume Gustin
> Labels: projectFactory.createProject
> Fix For: 2.0.0.Alpha5
>
> Attachments: ajf-forge.zip, aTest-compacted.zip, forge-screenshot.png
>
>
> I want to create a new plugin which allow to create a solution (set of projects) based on a specific solution model. But when the forge execute the project building code "projectFactory.createProject(targetProjectDir, DependencyFacet.class, MetadataFacet.class, JavaSourceFacet.class, ResourceFacet.class)" i receive the exception "org.jboss.forge.project.ProjectModelException" with the message "Could not create Maven project building request"
> When i fire my new plugin, my forge promps is "[no project] myTempdir $ ", I have the same exception when I copy the "new-project plugin" as "new-new-project plugin".
--
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
10 years, 10 months
[JBoss JIRA] (FORGE-914) Rework the handling of 1:M relationships by the Faces/RichFaces scaffold
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/FORGE-914?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated FORGE-914:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=977956
> Rework the handling of 1:M relationships by the Faces/RichFaces scaffold
> ------------------------------------------------------------------------
>
> Key: FORGE-914
> URL: https://issues.jboss.org/browse/FORGE-914
> 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.x Future
>
>
> The generated Faces scaffold for 1:M relationships does not handle certain usability aspects.
> For example, a new row is automatically added by default when displaying a 1:M relationship upon create. However, unless the add button is clicked, the contents of the row are not added to the underlying managed bean. If the add button is not clicked, the contents of the row are not treated as a new item to be added. This is very confusing.
> Also, if bean validation is performed on the entities (in the rows of the 1:M relationship), and if it fails, then the contents need to be corrected, even though they may not be persisted in the database. Again, this is confusing behavior.
> Additionally, deletion of entities from the collection (1-side of the association) seems to be broken.
--
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
10 years, 10 months
[JBoss JIRA] (FORGE-914) Rework the handling of 1:M relationships by the Faces/RichFaces scaffold
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/FORGE-914?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on FORGE-914:
-----------------------------------------------
Vineet Reynolds <vpereira(a)redhat.com> made a comment on [bug 977956|https://bugzilla.redhat.com/show_bug.cgi?id=977956]
Description of problem:
The following issues were discovered in the generated administration section whenever 1:M relationships were involved in the TicketMonster object model:
1. When adding/editing a venue, there is a blank row with "green plus" button for adding the new section to the venue. If you click on "save" button, this blank row is validated and it prevents you from editing/adding venue. Also, if the row is populated with valid values and saved, the newly created venue loses the section.
2. Add/Edit show - there are two "green plus" buttons, if you click on 2nd one (for Ticket Prices), the validation of Performance Date is triggered, that is wrong.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
For issue 1:
1. Click the 'Create New' button in the Venue screen.
2. Enter a name for the venue and click 'Save'.
3. Correct the validation errors triggered for the blank row in the Section field/property.
4. Click 'Save' again and view the newly created Venue.
For issue 2:
1. Click the 'Create New' button in the Show screen.
2. Select an Event and a Venue.
3. Click the Plus button in the Ticket Prices section, to add a new Ticket Price.
Actual results:
For issue 1:
The Section when saved with valid values, disappears and is not visible in the View Venue screen.
For issue 2:
An error message 'may not be null' is displayed against the Performance Date field when adding a Ticket Price.
Expected results:
For issue 1:
The Section entered in the Create Venue screen should be saved and visible in the View Venue screen.
For issue 2:
The validation of the Performance date should be done on Save and not when adding a new Ticket Price.
Additional info:
This an underlying issue in JBoss Forge and not in the TicketMonster example .No workaround for this issue is currently known.
> Rework the handling of 1:M relationships by the Faces/RichFaces scaffold
> ------------------------------------------------------------------------
>
> Key: FORGE-914
> URL: https://issues.jboss.org/browse/FORGE-914
> 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.x Future
>
>
> The generated Faces scaffold for 1:M relationships does not handle certain usability aspects.
> For example, a new row is automatically added by default when displaying a 1:M relationship upon create. However, unless the add button is clicked, the contents of the row are not added to the underlying managed bean. If the add button is not clicked, the contents of the row are not treated as a new item to be added. This is very confusing.
> Also, if bean validation is performed on the entities (in the rows of the 1:M relationship), and if it fails, then the contents need to be corrected, even though they may not be persisted in the database. Again, this is confusing behavior.
> Additionally, deletion of entities from the collection (1-side of the association) seems to be broken.
--
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
10 years, 10 months
[JBoss JIRA] (FORGE-972) The generated Faces scaffold contains functional errors for entities with immutable properties or collections of immutable properties
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-972:
-------------------------------------
Summary: The generated Faces scaffold contains functional errors for entities with immutable properties or collections of immutable properties
Key: FORGE-972
URL: https://issues.jboss.org/browse/FORGE-972
Project: Forge
Issue Type: Bug
Components: Scaffold
Affects Versions: 1.3.1.Final
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
This is related to an issue in the generated scaffold of the TicketMonster model: JDF-391.
The generated Faces scaffold does not treat immutable properties and collections of immutable properties differently. Differential treatment is required since immutable properties lack setters and hence instances of them need to be created via the specialized constructors that exist for the immutable entities.
Updates of immutable properties will require deletion of existing immutable instances followed by creation of new ones.
--
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
10 years, 10 months
[JBoss JIRA] (FORGE-916) Faces scaffold does not handle deletion of entities with bidirectional relationships
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-916?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds updated FORGE-916:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/core/pull/326
Added support into ForgeInspector to detect the owning and inverse sides of a bi-directional relationship.
Based on the availability of these attributes during the RemoveEntityWidget Metawidget construction, enhanced deletion logic is made available given the knowledege of the bidirectional relationships. The relationships are modified in both directions during deletion of a JPA entity.
> Faces scaffold does not handle deletion of entities with bidirectional relationships
> ------------------------------------------------------------------------------------
>
> Key: FORGE-916
> URL: https://issues.jboss.org/browse/FORGE-916
> 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.x Future
>
>
> The generated Faces scaffold contains code to handle deletion. But this works only for some scenarios.
> For bidirectional relationships, the generated code in the View Beans should perform deletion on both sides of the relationship. Currently, this is performed on only one side - the side corresponding to the view from where deletion was triggered.
--
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
10 years, 10 months