[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-927?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky updated FORGE-927:
------------------------------------
Description:
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(AjaxBehavioreven 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:
bq.{{<h:inputText ........>}}
bq. {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} bq. {{execute="@form" />}}
bq. {{</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*}}
was:
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(AjaxBehavioreven 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:
bq.{{<h:inputText ........>}}
bq. {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} bq. {{execute="@form" />}}
bq. {{</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*}}
> 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
>
> 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(AjaxBehavioreven 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:
> bq.{{<h:inputText ........>}}
> bq. {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} bq. {{execute="@form" />}}
> bq. {{</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
11 years, 7 months
[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-927?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky updated FORGE-927:
------------------------------------
Description:
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(AjaxBehavioreven 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*}}
was:
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(AjaxBehavioreven 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:
bq.{{<h:inputText ........>}}
bq. {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} bq. {{execute="@form" />}}
bq. {{</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*}}
> 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
>
> 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(AjaxBehavioreven 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
11 years, 7 months
[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-927?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky updated FORGE-927:
------------------------------------
Description:
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(AjaxBehavioreven 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:
bq.{{<h:inputText ........>}}
bq. {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} bq. {{execute="@form" />}}
bq. {{</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*}}
was:
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(AjaxBehavioreven event){} }} in *WorldBean.java*
2- in */world/search.xhtml* : change =>
bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" /> }}
to =>
{{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
3- embed : {{<f:ajax />}} in {{<h:inputText }} fields and/or {{<h:selecOneMenu}} ... components.....this way:
bq.{{<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*}}
> 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
>
> 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(AjaxBehavioreven 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:
> bq.{{<h:inputText ........>}}
> bq. {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} bq. {{execute="@form" />}}
> bq. {{</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
11 years, 7 months
[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-927?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky updated FORGE-927:
------------------------------------
Description:
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(AjaxBehavioreven event){} }} in *WorldBean.java*
2- in */world/search.xhtml* : change =>
bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" /> }}
to =>
{{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
3- embed : {{<f:ajax />}} in {{<h:inputText }} fields and/or {{<h:selecOneMenu}} ... components.....this way:
bq.{{<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*}}
was:
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(AjaxBehavioreven event){} }} in *WorldBean.java*
2- in */world/search.xhtml* : change =>
bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" /> }}
to =>
{{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
3- embed : {{<f:ajax />}} in {{<h:inputText }} fields and/or {{<h:selecOneMenu}} ... components.....this way:
bq.{{<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*}}
> 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
>
> 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(AjaxBehavioreven event){} }} in *WorldBean.java*
> 2- in */world/search.xhtml* : change =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" /> }}
> to =>
> {{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
> 3- embed : {{<f:ajax />}} in {{<h:inputText }} fields and/or {{<h:selecOneMenu}} ... components.....this way:
> bq.{{<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
11 years, 7 months
[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-927?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky updated FORGE-927:
------------------------------------
Description:
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(AjaxBehavioreven event){} }} in *WorldBean.java*
2- in */world/search.xhtml* : change =>
bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" /> }}
to =>
{{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
3- embed : {{<f:ajax />}} in {{<h:inputText }} fields and/or {{<h:selecOneMenu}} ... components.....this way:
bq.{{<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*}}
was:
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(AjaxBehavioreven event){} in WorldBean.java
2- in /world/search.xhtml : change =>
<f:event type="preRenderView" listener="#{helpBean.paginate()}" />
to =>
<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:
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 speicify if he/she would like to generate these statements in order to enable Ajax or not. Example:
scaffold-x from World.java --enableAjax true
> 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
>
> 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(AjaxBehavioreven event){} }} in *WorldBean.java*
> 2- in */world/search.xhtml* : change =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" /> }}
> to =>
> {{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
> 3- embed : {{<f:ajax />}} in {{<h:inputText }} fields and/or {{<h:selecOneMenu}} ... components.....this way:
> bq.{{<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
11 years, 7 months
[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by Hanine Hanynowsky (JIRA)
Hanine Hanynowsky created FORGE-927:
---------------------------------------
Summary: 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
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(AjaxBehavioreven event){} in WorldBean.java
2- in /world/search.xhtml : change =>
<f:event type="preRenderView" listener="#{helpBean.paginate()}" />
to =>
<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:
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 speicify 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
11 years, 7 months
[JBoss JIRA] (FORGE-911) Scaffolding from a Join table with more than two primary key columns is not supported
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-911?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky commented on FORGE-911:
-----------------------------------------
Please change the type of the issue from Story to Enhancement or Feature request!
> Scaffolding from a Join table with more than two primary key columns is not supported
> -------------------------------------------------------------------------------------
>
> Key: FORGE-911
> URL: https://issues.jboss.org/browse/FORGE-911
> Project: Forge
> Issue Type: Story
> Components: Scaffold
> Affects Versions: 1.2.3.Final, 1.3.0.Final
> Environment: Linux 3.8 - Firefox - MySQL 5.5 - PostgreSQl 9.1
> Reporter: Hanine Hanynowsky
>
> Using JForge (latest version); one will have a hibernate error complaining about the M2M join table (linking two objects) having more than 2 key columns.
> Naturally, if you join a table with one key column with a another table with a composite primary key (two columns key), in order to get a Many to Many relationship, you'll end up with a join table that has three key columns.
>
> When Forge finished scaffolding no error is displayed. You get the error when deploying to the container (JBoss as 7.1.1 for example). And the app is not deployed (rolled back).
>
> Is this a bug? A feature request?
>
> It seems to me that with the EmbeddedId bug, this one is also serious stuff!!
--
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, 7 months
[JBoss JIRA] (FORGE-912) UI Scaffolding does not support entities with EmbeddedId
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-912?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky commented on FORGE-912:
-----------------------------------------
Please change the type of this issue report from Story to Enhancement!
> UI Scaffolding does not support entities with EmbeddedId
> --------------------------------------------------------
>
> Key: FORGE-912
> URL: https://issues.jboss.org/browse/FORGE-912
> Project: Forge
> Issue Type: Story
> Components: Scaffold
> Affects Versions: 1.3.0.Final
> Environment: Linux 3.8 - Firefox 20 - MySQL 5.5 - PostgresSQL 9.1
> Reporter: Hanine Hanynowsky
> Priority: Critical
>
> UI Scaffolding does not support Entities with EnbeddedId.
> The value of ID generated is always null and there is no way to view a corresponding object.
> The generated entity and EmbeddedId class seem fine to me. The issue is with the VIEW scaffolding (The beans and the way XHTML files values are binded).
--
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, 7 months
[JBoss JIRA] (FORGE-926) It should be : maxlength instead of maxLength
by Hanine Hanynowsky (JIRA)
Hanine Hanynowsky created FORGE-926:
---------------------------------------
Summary: It should be : maxlength instead of maxLength
Key: FORGE-926
URL: https://issues.jboss.org/browse/FORGE-926
Project: Forge
Issue Type: Bug
Components: Scaffold
Affects Versions: 1.3.0.Final, 1.2.2.Final, 1.2.1.Final, 1.2.0.Final
Environment: Any
Reporter: Hanine Hanynowsky
Priority: Minor
The JBoss Forge UI scaffold uses maxLength as the attribute name instead of maxlength, when generating <h:inpuText /> components, in .xhtml files.
So this is a typo error (capital L instead of a lowercase l).
People using Eclipse or JBoss developer might notice it since, these IDEs do not complain about it. If you use Netbeans or IntelliJidea, you would be prompted to correct the error.
This has no critical consequences so far, but should be changed to correct name.
--
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, 7 months