[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 @…
[View More]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
[View Less]
11 years, 6 months
[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: …
[View More]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
[View Less]
11 years, 6 months
[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: …
[View More]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
[View Less]
11 years, 6 months