[JBoss JIRA] (FORGE-813) Implement a strategy to fix the open session in view problem in the generated REST resources
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-813?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-813:
----------------------------------
Fix Version/s: 1.2.3.Final
Affects Version/s: 1.2.2.Final
> 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
> Affects Versions: 1.2.2.Final
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
> Fix For: 1.2.3.Final
>
>
> 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
[JBoss JIRA] (FORGE-192) Make Forge console i18n and L10n compatible
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/FORGE-192?page=com.atlassian.jira.plugin.... ]
James Perkins commented on FORGE-192:
-------------------------------------
Maybe in the API you could have something like:
{code:java}
public abstract class ConsoleMessages {
public interface MessageKey {
String getKey();
}
public String getMessage(final MessageKey key) {
return getBundle().getString(key.getKey());
}
public String getFormattedMessage(final MessageKey key, final Object param) {
return String.format(getMessage(key), param);
}
public String getFormattedMessage(final MessageKey key, final Object param1, final Object param2) {
return String.format(getMessage(key), param1, param2);
}
public String getFormattedMessage(final MessageKey key, final Object... params) {
return String.format(getMessage(key), params);
}
protected abstract ResourceBundle getBundle();
}
{code}
Then maybe in the {{ShellPrintWriter}} and {{ShellPrompt}} you have respective {{ShellPrintWriter.write(ConsoleMessage cm, MessageKey key, Object... paramers)}} methods.
> Make Forge console i18n and L10n compatible
> -------------------------------------------
>
> Key: FORGE-192
> URL: https://issues.jboss.org/browse/FORGE-192
> Project: Forge
> Issue Type: Feature Request
> Components: Brainstorming, Shell
> Affects Versions: 1.0.6.Final
> Reporter: George Gastaldi
> Fix For: 2.0.0.Alpha2
>
>
> Forge should allow different languages to be used, so that the help messages and commands could be typed on the native speaker developer language.
> Example: When a Brazilian Portuguese developer is creating a new project, he would type: "novo-projeto" instead of "new-project".
--
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
[JBoss JIRA] (FORGE-192) Make Forge console i18n and L10n compatible
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/FORGE-192?page=com.atlassian.jira.plugin.... ]
James Perkins commented on FORGE-192:
-------------------------------------
Notes for using JBoss Logging for core i18n https://community.jboss.org/wiki/InternationalizedLoggingAndExceptions. I'm not sure the best solution for messages passed to the shell though. I would assume most plugins don't actually log to anything but the console.
One idea might be to write a custom handler where the plugin developer would log through a normal logger and the the handler would write the message to the console.
> Make Forge console i18n and L10n compatible
> -------------------------------------------
>
> Key: FORGE-192
> URL: https://issues.jboss.org/browse/FORGE-192
> Project: Forge
> Issue Type: Feature Request
> Components: Brainstorming, Shell
> Affects Versions: 1.0.6.Final
> Reporter: George Gastaldi
> Fix For: 2.0.0.Alpha2
>
>
> Forge should allow different languages to be used, so that the help messages and commands could be typed on the native speaker developer language.
> Example: When a Brazilian Portuguese developer is creating a new project, he would type: "novo-projeto" instead of "new-project".
--
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