[JBoss JIRA] (FORGE-915) Faces scaffold should use the server timezone instead of UTC for date and time fields
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-915?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds updated FORGE-915:
----------------------------------
Description:
The generated Faces scaffold uses UTC to represent dates and times in all usages of {{h:outputText}}. This is the default behavior but is confusing and appears incorrect, since end-users would expect to see the dates and times from the perspective of the server timezone (which is used for storage).
Also, the stored dates are displayed with an offset of one day when the server timezone is ahead of UTC.
was:
The generated Faces scaffold uses UTC to represent dates and times. This is the default behavior but is confusing and appears incorrect, since end-users would expect to see the dates and times from the perspective of the server timezone.
Also, the stored dates are displayed with an offset of one day when the server timezone is ahead of UTC.
> Faces scaffold should use the server timezone instead of UTC for date and time fields
> -------------------------------------------------------------------------------------
>
> Key: FORGE-915
> URL: https://issues.jboss.org/browse/FORGE-915
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.0.5.Final, 1.3.0.Final
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
>
> The generated Faces scaffold uses UTC to represent dates and times in all usages of {{h:outputText}}. This is the default behavior but is confusing and appears incorrect, since end-users would expect to see the dates and times from the perspective of the server timezone (which is used for storage).
> Also, the stored dates are displayed with an offset of one day when the server timezone is ahead of UTC.
--
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-915) Faces scaffold should use the server timezone instead of UTC for date and time fields
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-915?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds updated FORGE-915:
----------------------------------
Summary: Faces scaffold should use the server timezone instead of UTC for date and time fields (was: Faces scaffold should use the default system timezone instead of UTC for date and time fields)
> Faces scaffold should use the server timezone instead of UTC for date and time fields
> -------------------------------------------------------------------------------------
>
> Key: FORGE-915
> URL: https://issues.jboss.org/browse/FORGE-915
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.0.5.Final, 1.3.0.Final
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
>
> The generated Faces scaffold uses UTC to represent dates and times. This is the default behavior but is confusing and appears incorrect, since end-users would expect to see the dates and times from the perspective of the server timezone.
> Also, the stored dates are displayed with an offset of one day when the server timezone is ahead of UTC.
--
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-915) Faces scaffold should use the default system timezone instead of UTC for date and time fields
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-915:
-------------------------------------
Summary: Faces scaffold should use the default system timezone instead of UTC for date and time fields
Key: FORGE-915
URL: https://issues.jboss.org/browse/FORGE-915
Project: Forge
Issue Type: Bug
Affects Versions: 1.3.0.Final, 1.0.5.Final
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
The generated Faces scaffold uses UTC to represent dates and times. This is the default behavior but is confusing and appears incorrect, since end-users would expect to see the dates and times from the perspective of the server timezone.
Also, the stored dates are displayed with an offset of one day when the server timezone is ahead of UTC.
--
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-897) LinkageError while accessing classes using ProxyFactory
by Shigeru Chiba (JIRA)
[ https://issues.jboss.org/browse/FORGE-897?page=com.atlassian.jira.plugin.... ]
Shigeru Chiba commented on FORGE-897:
-------------------------------------
I copied this issue into JASSIST-199.
I decided to add an extension point to Javassist so that users can use their own UUID generator. As you said, java.util.UUID would be slow and the generated identifier is very long.
By the way, this failure is really weird. The current simple identifier generation is thread-safe and thus this failure will happen only when:
- ProxyFactory class is loaded twice by different class loaders.
Let's call the two ProxyFactroy classes P and Q (note P and Q are not objects but classes).
- The same user class is proxified by P and then by Q.
Let's call the proxified user classes C and D.
- C and D are loaded by using the same class loader.
Adding to the proxy name the hash code of the class loader for P/Q might address
the problem.
> LinkageError while accessing classes using ProxyFactory
> -------------------------------------------------------
>
> Key: FORGE-897
> URL: https://issues.jboss.org/browse/FORGE-897
> Project: Forge
> Issue Type: Bug
> Components: UI - Eclipse
> Affects Versions: 2.0.0.Alpha3
> Reporter: George Gastaldi
> Assignee: Lincoln Baxter III
> Priority: Blocker
> Fix For: 2.0.0.Alpha4
>
> Attachments: linkage_error2.txt
>
>
> When the Eclipse plugin is started, choose New Project, fill in the required information, select "Forge Addon" as the project type and click next. The following error occurs:
> {code}
> May 10, 2013 8:16:42 PM org.jboss.forge.container.ForgeImpl start
> INFO: Detected changes in repository [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository (Immutable)].
> May 10, 2013 8:16:42 PM org.jboss.forge.container.ForgeImpl start
> INFO: Detected changes in repository [/home/ggastald/.forge/addons].
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:facets,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:addon-manager,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:addons,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:javaee,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:javaee-spi,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:parser-java,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:maven,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:projects,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:dependencies,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:resources,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:ui,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:environment,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:ui-hints,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: > Starting container [org.jboss.forge:convert,2.0.0-SNAPSHOT] [/Downloads/workspace/jbosstools-forge/plugins/org.jboss.tools.forge2.runtime/addon-repository]
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:javaee-spi,2.0.0-SNAPSHOT] - 25ms
> May 10, 2013 8:16:42 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:ui-hints,2.0.0-SNAPSHOT] - 19ms
> May 10, 2013 8:16:42 PM org.jboss.weld.bootstrap.WeldBootstrap <clinit>
> INFO: WELD-000900 2.0.0 (Final)
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
> May 10, 2013 8:16:43 PM org.jboss.weld.interceptor.util.InterceptionTypeRegistry <clinit>
> WARNING: Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled
> May 10, 2013 8:16:43 PM org.jboss.weld.interceptor.util.InterceptionTypeRegistry <clinit>
> WARNING: Class 'javax.ejb.PrePassivate' not found, interception based on it is not enabled
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:parser-java,2.0.0-SNAPSHOT] - [class org.jboss.forge.parser.java.JavaSourceFactoryImpl, class org.jboss.forge.parser.java.resources.JavaResourceGenerator]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:addons,2.0.0-SNAPSHOT] - [class org.jboss.forge.addons.facets.ForgeAddonFacet, class org.jboss.forge.addons.facets.ForgeAddonAPIFacet, class org.jboss.forge.addons.facets.ForgeAddonTestFacet, class org.jboss.forge.addons.ForgeAddonSetupStep, class org.jboss.forge.addons.facets.ForgeContainerAPIFacet, class org.jboss.forge.addons.facets.ForgeAddonSPIFacet, class org.jboss.forge.addons.ForgeAddonProjectType, class org.jboss.forge.addons.facets.ForgeAddonImplFacet]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:convert,2.0.0-SNAPSHOT] - [class org.jboss.forge.convert.impl.Converters$2, interface org.jboss.forge.convert.Converter, class org.jboss.forge.convert.impl.ConverterFactoryImpl, class org.jboss.forge.convert.impl.Converters$1]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:convert,2.0.0-SNAPSHOT] - 1194ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:addons,2.0.0-SNAPSHOT] - 1209ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:parser-java,2.0.0-SNAPSHOT] - 1204ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:facets,2.0.0-SNAPSHOT] - [class org.jboss.forge.facets.FacetFactoryImpl]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:facets,2.0.0-SNAPSHOT] - 1223ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:environment,2.0.0-SNAPSHOT] - [class org.jboss.forge.environment.impl.EnvironmentImpl]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:ui,2.0.0-SNAPSHOT] - [class org.jboss.forge.ui.impl.UISelectOneImpl, interface org.jboss.forge.ui.input.UIInput, class org.jboss.forge.ui.impl.facets.HintsFacetImpl, class org.jboss.forge.ui.impl.UISelectManyImpl, interface org.jboss.forge.ui.input.UISelectMany, interface org.jboss.forge.ui.input.UIInputMany, interface org.jboss.forge.ui.input.UISelectOne]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:ui,2.0.0-SNAPSHOT] - 1214ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:dependencies,2.0.0-SNAPSHOT] - []
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:addon-manager,2.0.0-SNAPSHOT] - [class org.jboss.forge.addon.manager.impl.commands.AddonRemoveCommand, class org.jboss.forge.addon.manager.impl.AddonManagerImpl, class org.jboss.forge.addon.manager.impl.commands.AddonInstallCommand]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:addon-manager,2.0.0-SNAPSHOT] - 1228ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:javaee,2.0.0-SNAPSHOT] - [class org.jboss.forge.javaee.cdi.CDIFacetImpl, class org.jboss.forge.javaee.ejb.EJBFacetImpl]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:projects,2.0.0-SNAPSHOT] - [class org.jboss.forge.projects.impl.NewProjectWizard, class org.jboss.forge.projects.impl.ProjectFactoryImpl, class org.jboss.forge.projects.impl.DependencyInstallerImpl, class org.jboss.forge.projects.impl.NewProjectWizard$2]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:javaee,2.0.0-SNAPSHOT] - 1228ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:dependencies,2.0.0-SNAPSHOT] - 1218ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:resources,2.0.0-SNAPSHOT] - [class org.jboss.forge.resource.converter.FileResourceConverterGenerator, class org.jboss.forge.resource.converter.DirectoryResourceConverter, class org.jboss.forge.resource.FileResourceGenerator, class org.jboss.forge.resource.converter.FileResourceConverter, class org.jboss.forge.resource.converter.ResourceConverterGenerator, class org.jboss.forge.resource.converter.ResourceConverter, class org.jboss.forge.resource.URLResourceGenerator, class org.jboss.forge.resource.converter.DirectoryResourceConverterGenerator, class org.jboss.forge.resource.ResourceFactoryImpl]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:resources,2.0.0-SNAPSHOT] - 1222ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:environment,2.0.0-SNAPSHOT] - 1213ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:projects,2.0.0-SNAPSHOT] - 1221ms
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup call
> INFO: Services loaded from addon [org.jboss.forge:maven,2.0.0-SNAPSHOT] - [class org.jboss.forge.maven.projects.MavenProjectLocator, class org.jboss.forge.maven.projects.facets.MavenResourceFacet, class org.jboss.forge.maven.dependencies.MavenDependencyResolver, class org.jboss.forge.maven.projects.facets.MavenJavaSourceFacet, class org.jboss.forge.maven.projects.facets.MavenPackagingFacet, class org.jboss.forge.maven.projects.MavenProjectType, class org.jboss.forge.maven.projects.MavenMultiModuleProvider, class org.jboss.forge.maven.resources.MavenResourceGenerator, class org.jboss.forge.maven.projects.MavenPluginFacetImpl, class org.jboss.forge.maven.projects.facets.MavenMetadataFacet, class org.jboss.forge.maven.projects.MavenFacetImpl, class org.jboss.forge.maven.projects.facets.MavenDependencyFacet]
> May 10, 2013 8:16:44 PM org.jboss.forge.container.impl.AddonRunnable$3 call
> INFO: >> Started container [org.jboss.forge:maven,2.0.0-SNAPSHOT] - 1331ms
> !SESSION 2013-05-10 20:16:31.096 -----------------------------------------------
> eclipse.buildId=M20120914-1800
> java.version=1.7.0_21
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.sdk.ide
> Command-line arguments: -product org.eclipse.sdk.ide -data /Downloads/workspace/../runtime-EclipseApplication -dev file:/Downloads/workspace/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application/dev.properties -os linux -ws gtk -arch x86_64 -consoleLog
> !ENTRY org.eclipse.ui 4 0 2013-05-10 20:17:32.899
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.RuntimeException: by java.lang.LinkageError: loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader): attempted duplicate class definition for name: "org/jboss/forge/facets/AbstractFaceted_$$_javassist_29"
> at javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:515)
> at javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:492)
> at javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:428)
> at javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:400)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:450)
> at org.jboss.forge.container.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:384)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:173)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback.access$300(ClassLoaderAdapterCallback.java:29)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:83)
> at org.jboss.forge.container.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:58)
> at org.jboss.forge.facets.AbstractFaceted_$$_javassist_35.setValue(AbstractFaceted_$$_javassist_35.java)
> at org.jboss.forge.ui.util.InputComponents.setManyInputValue(InputComponents.java:125)
> at org.jboss.forge.ui.util.InputComponents.setValueFor(InputComponents.java:82)
> at org.jboss.tools.forge.ui.ext.control.CheckboxTableControlBuilder.build(CheckboxTableControlBuilder.java:56)
> at org.jboss.tools.forge.ui.ext.wizards.ForgeWizardPage.createControls(ForgeWizardPage.java:93)
> at org.jboss.tools.forge.ui.ext.wizards.ForgeWizardPage.createControl(ForgeWizardPage.java:73)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1246)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3562)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3186)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.jboss.tools.forge.ui.ext.dialog.UICommandListDialog.openWizard(UICommandListDialog.java:93)
> at org.jboss.tools.forge.ui.ext.dialog.UICommandListDialog.access$0(UICommandListDialog.java:85)
> at org.jboss.tools.forge.ui.ext.dialog.UICommandListDialog$1.widgetDefaultSelected(UICommandListDialog.java:71)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:119)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3562)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3186)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1045)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:940)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:587)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:542)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> Caused by: javassist.CannotCompileException: by java.lang.LinkageError: loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader): attempted duplicate class definition for name: "org/jboss/forge/facets/AbstractFaceted_$$_javassist_29"
> at javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:170)
> at javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:507)
> ... 62 more
> Caused by: java.lang.LinkageError: loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader): attempted duplicate class definition for name: "org/jboss/forge/facets/AbstractFaceted_$$_javassist_29"
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
> at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at javassist.util.proxy.FactoryHelper.toClass2(FactoryHelper.java:182)
> at javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:164)
> ... 63 more
> {code}
--
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-914) Rework the handling of 1:M relationships by the Faces/RichFaces scaffold
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-914:
-------------------------------------
Summary: Rework the handling of 1:M relationships by the Faces/RichFaces scaffold
Key: FORGE-914
URL: https://issues.jboss.org/browse/FORGE-914
Project: Forge
Issue Type: Task
Components: Scaffold
Affects Versions: 1.3.0.Final, 1.0.5.Final
Reporter: Vineet Reynolds
The generated Faces scaffold for 1:M relationships does not handle certain usability aspects.
For example, a new row is automatically added by default when displaying a 1:M relationship upon create. However, unless the add button is clicked, the contents of the row are not added to the underlying managed bean. If the add button is not clicked, the contents of the row are not treated as a new item to be added. This is very confusing.
Also, if bean validation is performed on the entities (in the rows of the 1:M relationship), and if it fails, then the contents need to be corrected, even though they may not be persisted in the database. Again, this is confusing behavior.
This task is a holder to fix such kind of issues in handling associations in the generated scaffold. Create sub-tasks as necessary for the individual issues that need fixing.
--
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-913) RichFaces scaffolding does not handle temporal fields in JPA entities correctly
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-913?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds updated FORGE-913:
----------------------------------
Affects Version/s: 1.0.5.Final
> RichFaces scaffolding does not handle temporal fields in JPA entities correctly
> -------------------------------------------------------------------------------
>
> Key: FORGE-913
> URL: https://issues.jboss.org/browse/FORGE-913
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.0.5.Final, 1.3.0.Final
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
>
> The RichFaces scaffold generator creates {{rich:calendar}} components in the facelets, but without a {{datePattern}} attribute. The behavior of this component in such a case is to not provide the embeddded timepicker. This works for temporal fields of type Date.
> But, this is certainly not sufficient for temporal fields of type Timestamp. A {{datePattern}} with a time pattern like {{MMM d, yyyy HH:mm}} or {{MMM d, yyyy hh:mm:a}} needs to be generated for such fields to allow time inputs.
> For temporal fields of type Time, consider generating a different widget, since the RichFaces calendar widget is not capable of providing the timepicker alone.
--
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-913) RichFaces scaffolding does not handle temporal fields in JPA entities correctly
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-913:
-------------------------------------
Summary: RichFaces scaffolding does not handle temporal fields in JPA entities correctly
Key: FORGE-913
URL: https://issues.jboss.org/browse/FORGE-913
Project: Forge
Issue Type: Bug
Components: Scaffold
Affects Versions: 1.3.0.Final
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
The RichFaces scaffold generator creates {{rich:calendar}} components in the facelets, but without a {{datePattern}} attribute. The behavior of this component in such a case is to not provide the embeddded timepicker. This works for temporal fields of type Date.
But, this is certainly not sufficient for temporal fields of type Timestamp. A {{datePattern}} with a time pattern like {{MMM d, yyyy HH:mm}} or {{MMM d, yyyy hh:mm:a}} needs to be generated for such fields to allow time inputs.
For temporal fields of type Time, consider generating a different widget, since the RichFaces calendar widget is not capable of providing the timepicker alone.
--
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