March 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-827) Allows a command to be vetoed

by George Gastaldi (JIRA)

George Gastaldi created FORGE-827: ------------------------------------- Summary: Allows a command to be vetoed Key: FORGE-827 URL: https://issues.jboss.org/browse/FORGE-827 Project: Forge Issue Type: Feature Request Components: Plugin API Affects Versions: 1.2.2.Final Reporter: George Gastaldi Fix For: 1.2.3.Final Introduce an event that is fired before the command is executed. This event may allow a command to be vetoed from execution as introduce messages before the command is executed. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-827) Introduce an event to listen for command executions before it is actually executed

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-827?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-827: ---------------------------------- Summary: Introduce an event to listen for command executions before it is actually executed (was: Allows a command to be vetoed) > Introduce an event to listen for command executions before it is actually executed > ---------------------------------------------------------------------------------- > > Key: FORGE-827 > URL: https://issues.jboss.org/browse/FORGE-827 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.2.2.Final > Reporter: George Gastaldi > Fix For: 1.2.3.Final > > > Introduce an event that is fired before the command is executed. This event may allow a command to be vetoed from execution as introduce messages before the command is executed. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-826) Display a ***WARNING*** when executing a @Deprecated command or plugin.

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-826: ---------------------------------------- Summary: Display a ***WARNING*** when executing a @Deprecated command or plugin. Key: FORGE-826 URL: https://issues.jboss.org/browse/FORGE-826 Project: Forge Issue Type: Feature Request Components: Plugin API Affects Versions: 1.2.2.Final Reporter: Lincoln Baxter III Fix For: 1.2.3.Final Display a ***WARNING*** when executing a @Deprecated command or plugin. Simply need to inspect for the existence of the @Deprecated annotation. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-825) Provide a JPQL query builder API to make it easier for plugins to generate JPQL queries

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-825: ------------------------------------- Summary: Provide a JPQL query builder API to make it easier for plugins to generate JPQL queries Key: FORGE-825 URL: https://issues.jboss.org/browse/FORGE-825 Project: Forge Issue Type: Feature Request Reporter: Vineet Reynolds Coming in from the FORGE-813 issue, I believe it would be beneficial to have an API that would allow plugin developers to generate JPQL queries based on JavaClass instances provided to it. It is akin to the JPA metamodel, except that the model here is based on Forge JavaClass instances. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-824) Test

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-824?page=com.atlassian.jira.plugin.... ] George Gastaldi deleted FORGE-824: ---------------------------------- > Test > ---- > > Key: FORGE-824 > URL: https://issues.jboss.org/browse/FORGE-824 > Project: Forge > Issue Type: Feature Request > Reporter: Vineet Reynolds > > Mistake. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-813) Implement a strategy to fix the open session in view problem in the generated REST resources

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-813?page=com.atlassian.jira.plugin.... ] Vineet Reynolds reassigned FORGE-813: ------------------------------------- Assignee: Vineet Reynolds > Implement a strategy to fix the open session in view problem in the generated REST resources > -------------------------------------------------------------------------------------------- > > Key: FORGE-813 > URL: https://issues.jboss.org/browse/FORGE-813 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The generated REST resources for objects with 1:M and M:M relations, require eager fetching to be enabled on the related JPA entities, to bypass the open-session-in-view problem. > The generated REST resources should not require the entities themselves to use eager fetching by default. It would be better to use specialized JPQL queries to achieve this. > Or for that matter, use a combination of specialized JPQL queries that limit the objects being retrieved (say, one-level deep) and custom serializers that can operate on this partial object graph. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-813) Implement a strategy to fix the open session in view problem in the generated REST resources

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-813?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-813: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/299 The JOIN FETCH expressions ensure that immediate collections are fetched. This fits in well, with the upcoming changes for FORGE-606, where the first immediate properties of an object are serialized, thus avoiding the open-session in view. Collections at a deeper level in the related entities may be fetched, depending on the EAGER/LAZY fetchType values on the nested collections. Also replaced Seam Render usage with FreeMarker. > Implement a strategy to fix the open session in view problem in the generated REST resources > -------------------------------------------------------------------------------------------- > > Key: FORGE-813 > URL: https://issues.jboss.org/browse/FORGE-813 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Reporter: Vineet Reynolds > > The generated REST resources for objects with 1:M and M:M relations, require eager fetching to be enabled on the related JPA entities, to bypass the open-session-in-view problem. > The generated REST resources should not require the entities themselves to use eager fetching by default. It would be better to use specialized JPQL queries to achieve this. > Or for that matter, use a combination of specialized JPQL queries that limit the objects being retrieved (say, one-level deep) and custom serializers that can operate on this partial object graph. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-824) Test

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-824?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-824: ---------------------------------- Summary: Test (was: The REST plugin should fetch the ) Description: Mistake. > Test > ---- > > Key: FORGE-824 > URL: https://issues.jboss.org/browse/FORGE-824 > Project: Forge > Issue Type: Feature Request > Reporter: Vineet Reynolds > > Mistake. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-824) Test

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-824?page=com.atlassian.jira.plugin.... ] Vineet Reynolds closed FORGE-824. --------------------------------- Resolution: Rejected > Test > ---- > > Key: FORGE-824 > URL: https://issues.jboss.org/browse/FORGE-824 > Project: Forge > Issue Type: Feature Request > Reporter: Vineet Reynolds > > Mistake. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-824) The REST plugin should fetch the

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-824: ------------------------------------- Summary: The REST plugin should fetch the Key: FORGE-824 URL: https://issues.jboss.org/browse/FORGE-824 Project: Forge Issue Type: Feature Request Reporter: Vineet Reynolds -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2013