September 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1221) scaffold views template uses backslashes instead of forward slashes

by Esteve Aviles (JIRA)

[ https://issues.jboss.org/browse/FORGE-1221?page=com.atlassian.jira.plugin... ] Esteve Aviles updated FORGE-1221: --------------------------------- Affects Version/s: 1.4.0.Final > scaffold views template uses backslashes instead of forward slashes > ------------------------------------------------------------------- > > Key: FORGE-1221 > URL: https://issues.jboss.org/browse/FORGE-1221 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.4.0.Final, 1.4.1.Final > Environment: Windows > Reporter: Gerry Matte > > In every generated view page (search.xhtml, create.xhtml, view.xhtml) the file prolog contains a template reference which uses backslashes. > This causes a java.io.FileNotFoundException whenever such a page is displayed. > The template references should contain forward slashes instead of backslashes. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1221) scaffold views template uses backslashes instead of forward slashes

by Esteve Aviles (JIRA)

[ https://issues.jboss.org/browse/FORGE-1221?page=com.atlassian.jira.plugin... ] Esteve Aviles updated FORGE-1221: --------------------------------- Priority: Major (was: Minor) > scaffold views template uses backslashes instead of forward slashes > ------------------------------------------------------------------- > > Key: FORGE-1221 > URL: https://issues.jboss.org/browse/FORGE-1221 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.4.1.Final > Environment: Windows > Reporter: Gerry Matte > > In every generated view page (search.xhtml, create.xhtml, view.xhtml) the file prolog contains a template reference which uses backslashes. > This causes a java.io.FileNotFoundException whenever such a page is displayed. > The template references should contain forward slashes instead of backslashes. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-609) @RequiresFacet and @RequiresProject should be Interceptor bindings instead of static constraints.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-609?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-609: ---------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > @RequiresFacet and @RequiresProject should be Interceptor bindings instead of static constraints. > ------------------------------------------------------------------------------------------------- > > Key: FORGE-609 > URL: https://issues.jboss.org/browse/FORGE-609 > Project: Forge > Issue Type: Enhancement > Components: Plugin API, UI - Shell > Affects Versions: 1.0.5.Final > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > This would also incorporate FORGE-214, since these constraints could now be used on any bean Class or 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1233) Support Global Alternatives

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1233: -------------------------------------- Summary: Support Global Alternatives Key: FORGE-1233 URL: https://issues.jboss.org/browse/FORGE-1233 Project: Forge Issue Type: Feature Request Components: Furnace (Container) Affects Versions: 2.0.0.Alpha12 Environment: CDI Reporter: George Gastaldi Fix For: 2.x Future Support @Alternatives according the CDI 1.1 spec -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1232) Support Global Decorators

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1232: -------------------------------------- Summary: Support Global Decorators Key: FORGE-1232 URL: https://issues.jboss.org/browse/FORGE-1232 Project: Forge Issue Type: Feature Request Components: Furnace (Container) Affects Versions: 2.0.0.Alpha12 Environment: CDI Reporter: George Gastaldi Fix For: 2.x Future -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1231) Support Global Interceptors

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1231: -------------------------------------- Summary: Support Global Interceptors Key: FORGE-1231 URL: https://issues.jboss.org/browse/FORGE-1231 Project: Forge Issue Type: Feature Request Components: Furnace (Container) Affects Versions: 2.0.0.Alpha12 Environment: CDI Reporter: George Gastaldi Fix For: 2.x Future -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1230) Usage of @Alternative has non-deterministic behavior

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1230: -------------------------------------- Summary: Usage of @Alternative has non-deterministic behavior Key: FORGE-1230 URL: https://issues.jboss.org/browse/FORGE-1230 Project: Forge Issue Type: Feature Request Components: Furnace (Container), Test Harness Affects Versions: 2.0.0.Alpha12 Reporter: George Gastaldi Fix For: 2.x Future When using an @Alternative class in a test to mock a service, and enabling it globally (by using @Priority), the test presents some random failures, probably due to the alternative class not being used. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1228) increase conversation timeout to 30 minutes

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1228?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1228: ---------------------------------------- Hi Gerry, It means providing a patch using GitHub. This is what it is: https://help.github.com/articles/using-pull-requests And here is how you can provide patches to Forge: http://forge.jboss.org/docs/get_involved/contribute.html#content We appreciate your feedback. > increase conversation timeout to 30 minutes > ------------------------------------------- > > Key: FORGE-1228 > URL: https://issues.jboss.org/browse/FORGE-1228 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 1.4.1.Final > Reporter: Gerry Matte > Priority: Minor > Fix For: 1.x Future, 2.x Future > > > The scaffold generated entity DAO beans contain two conversation.begin() commands [in the create() and retrieve() methods] > After each conversation.begin() please insert: > this.conversation.setTimeout(1800000); > which will extend the conversation timeout from the default ten minutes to thirty minutes (same as the session timeout) > For me, complex data entry screens often have their conversation expire during the period that a user composes and keys their data. Very frustrating ! -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1228) increase conversation timeout to 30 minutes

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1228?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1228: ----------------------------------- Fix Version/s: 1.x Future 2.x Future > increase conversation timeout to 30 minutes > ------------------------------------------- > > Key: FORGE-1228 > URL: https://issues.jboss.org/browse/FORGE-1228 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 1.4.1.Final > Reporter: Gerry Matte > Priority: Minor > Fix For: 1.x Future, 2.x Future > > > The scaffold generated entity DAO beans contain two conversation.begin() commands [in the create() and retrieve() methods] > After each conversation.begin() please insert: > this.conversation.setTimeout(1800000); > which will extend the conversation timeout from the default ten minutes to thirty minutes (same as the session timeout) > For me, complex data entry screens often have their conversation expire during the period that a user composes and keys their data. Very frustrating ! -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1228) increase conversation timeout to 30 minutes

by Gerry Matte (JIRA)

[ https://issues.jboss.org/browse/FORGE-1228?page=com.atlassian.jira.plugin... ] Gerry Matte commented on FORGE-1228: ------------------------------------ I don't know what a pull request is. If it involves more than 1/2 hour of my time, I can't afford it right now. Possibly in a couple weeks however...... > increase conversation timeout to 30 minutes > ------------------------------------------- > > Key: FORGE-1228 > URL: https://issues.jboss.org/browse/FORGE-1228 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 1.4.1.Final > Reporter: Gerry Matte > Priority: Minor > > The scaffold generated entity DAO beans contain two conversation.begin() commands [in the create() and retrieve() methods] > After each conversation.begin() please insert: > this.conversation.setTimeout(1800000); > which will extend the conversation timeout from the default ten minutes to thirty minutes (same as the session timeout) > For me, complex data entry screens often have their conversation expire during the period that a user composes and keys their data. Very frustrating ! -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2013