March 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-814) Add support to the field plugin for specifying optional associations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-814?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-814. --------------------------------- Resolution: Done Fix Version set > Add support to the field plugin for specifying optional associations > -------------------------------------------------------------------- > > Key: FORGE-814 > URL: https://issues.jboss.org/browse/FORGE-814 > 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 > > > JPA allows for specifying whether an association is optional or not, for @ManyToOne and @OneToOne relationships. The field plugin must support this. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-814) Add support to the field plugin for specifying optional associations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-814?page=com.atlassian.jira.plugin.... ] George Gastaldi reopened FORGE-814: ----------------------------------- Reopening to set the version > Add support to the field plugin for specifying optional associations > -------------------------------------------------------------------- > > Key: FORGE-814 > URL: https://issues.jboss.org/browse/FORGE-814 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > JPA allows for specifying whether an association is optional or not, for @ManyToOne and @OneToOne relationships. The field plugin must support this. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-814) Add support to the field plugin for specifying optional associations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-814?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-814: ---------------------------------- Fix Version/s: 1.2.3.Final Affects Version/s: 1.2.2.Final > Add support to the field plugin for specifying optional associations > -------------------------------------------------------------------- > > Key: FORGE-814 > URL: https://issues.jboss.org/browse/FORGE-814 > 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 > > > JPA allows for specifying whether an association is optional or not, for @ManyToOne and @OneToOne relationships. The field plugin must support this. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-814) Add support to the field plugin for specifying optional associations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-814?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-814: ---------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done Implemented as a --required flag. Merged, thanks ! > Add support to the field plugin for specifying optional associations > -------------------------------------------------------------------- > > Key: FORGE-814 > URL: https://issues.jboss.org/browse/FORGE-814 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > JPA allows for specifying whether an association is optional or not, for @ManyToOne and @OneToOne relationships. The field plugin must support this. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-815) Add support to the field plugin for specifying CascadeTypes

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-815: ------------------------------------- Summary: Add support to the field plugin for specifying CascadeTypes Key: FORGE-815 URL: https://issues.jboss.org/browse/FORGE-815 Project: Forge Issue Type: Feature Request Components: Java EE APIs 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-814) Add support to the field plugin for specifying optional associations

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-814?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-814: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/296 Allows for optional attribute values to be specified for {{@ManyToOne}} and {{@OneToOne}} annotations. When not specified in the field command, this attribute is omitted, to avoid annotation 'noise'. > Add support to the field plugin for specifying optional associations > -------------------------------------------------------------------- > > Key: FORGE-814 > URL: https://issues.jboss.org/browse/FORGE-814 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > JPA allows for specifying whether an association is optional or not, for @ManyToOne and @OneToOne relationships. The field plugin must support this. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-814) Add support to the field plugin for specifying optional associations

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-814: ------------------------------------- Summary: Add support to the field plugin for specifying optional associations Key: FORGE-814 URL: https://issues.jboss.org/browse/FORGE-814 Project: Forge Issue Type: Feature Request Components: Java EE APIs Reporter: Vineet Reynolds Assignee: Vineet Reynolds JPA allows for specifying whether an association is optional or not, for @ManyToOne and @OneToOne relationships. The field plugin must support this. -- 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, 2 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)

Vineet Reynolds created FORGE-813: ------------------------------------- Summary: 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-809) Support Container listeners

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-809?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-809. --------------------------------- Fix Version/s: 2.0.0.Alpha1 Resolution: Done Implemented ContainerLifecycleListener > Support Container listeners > --------------------------- > > Key: FORGE-809 > URL: https://issues.jboss.org/browse/FORGE-809 > Project: Forge > Issue Type: Enhancement > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Forge 2 should allow the registration of container lifecycle listeners to attach behavior in a decoupled way, such as > - install required addons > - show a welcome screen > - log actions > It's probably also need a few more like AddonRegistryListener, ServiceRegistryListener, etc -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-93) AbstractResource.getFullyQualifiedName() returns wrong file path on Windows

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-93?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-93: --------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > AbstractResource.getFullyQualifiedName() returns wrong file path on Windows > --------------------------------------------------------------------------- > > Key: FORGE-93 > URL: https://issues.jboss.org/browse/FORGE-93 > Project: Forge > Issue Type: Bug > Components: Resources API > Affects Versions: 1.0.6.Final > Reporter: Liu Jianhong > Assignee: Koen Aers > Priority: Minor > Fix For: 1.2.3.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 1,cd to C:\Users > 2,Get path use AbstractResource.getFullyQualifiedName() and it returns /Users > 3,Execute "cd /Users" produces error of "[cd] no such resources:Users" > So,the following test failed: > org.junit.ComparisonFailure: expected:</Users[/Administrator]> but was:</Users[]> > at org.junit.Assert.assertEquals(Assert.java:123) > at org.junit.Assert.assertEquals(Assert.java:145) > at org.jboss.forge.shell.test.plugins.builtin.ChangeDirectoryPluginTest.testAbsolutePath(ChangeDirectoryPluginTest.java:137) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:251) > at org.jboss.arquillian.protocol.local.LocalMethodExecutor.invoke(LocalMethodExecutor.java:40) > at org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:50) > at org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:40) > at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) > at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) > at org.jboss.arquillian.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:157) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:244) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:207) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:225) > at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:221) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:163) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:186) > at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:182) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:127) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2013