January 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-22) Forge needs documentation, even at a basic level

by Lincoln Baxter III (JIRA)

Forge needs documentation, even at a basic level ------------------------------------------------ Key: SEAMFORGE-22 URL: https://issues.jboss.org/browse/SEAMFORGE-22 Project: Seam Forge Issue Type: Feature Request Components: Documentation Affects Versions: 1.0.0.Alpha1 Reporter: Lincoln Baxter III Fix For: 1.0.0.Alpha2 Forge needs some kind of tutorial / getting-started / how-to write plugins documentation, even if very simple and broad (not diving into package names and specific locations of APIs/API choices.) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-21) Forge should provide Groovy

by Lincoln Baxter III (JIRA)

Forge should provide Groovy --------------------------- Key: SEAMFORGE-21 URL: https://issues.jboss.org/browse/SEAMFORGE-21 Project: Seam Forge Issue Type: Feature Request Components: Brainstorming Affects Versions: 1.0.0.Alpha1 Environment: All Reporter: Lincoln Baxter III Fix For: 1.0.0.Alpha2 By providing a standard Groovy version / API in the Forge Plugin API / Core Shell, developers would be empowered to write plugins entirely in groovy. This is a plus. Hot-swap w/CDI would not be possible, but it would be possible to package groovied plugins. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-20) Forge needs to provide an XML manipulation library similar to the Java Parser

by Lincoln Baxter III (JIRA)

Forge needs to provide an XML manipulation library similar to the Java Parser ----------------------------------------------------------------------------- Key: SEAMFORGE-20 URL: https://issues.jboss.org/browse/SEAMFORGE-20 Project: Seam Forge Issue Type: Feature Request Components: Java Parser Affects Versions: 1.0.0.Alpha1 Environment: All Reporter: Lincoln Baxter III Fix For: 1.0.0.Alpha2 As part of project generation, manipulation, and general grokkage, Forge needs to be able to consume XML files in a manner that is relatively easy for both developers and thusly for the users of the plugins they provide. Potential options: 1) GPath - http://groovy.codehaus.org/Reading+XML+using+Groovy%27s+XmlParser 2) XPath - http://www.ibm.com/developerworks/library/x-javaxpathapi.html 3) MVEL - using property handlers to expose XML ------ By simply adding groovy dep to the parent POM (and the relevant API poms), we could enable the use of Groovy in plugins, which would enable GPath if developers do not want to use XPath. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-19) mvn clean install: failing org.jboss.seam.forge.test.project.MavenFacetsTest (testAbsoluteUnknownProjectCannotInstantiate)

by Michael Schuetz (JIRA)

mvn clean install: failing org.jboss.seam.forge.test.project.MavenFacetsTest (testAbsoluteUnknownProjectCannotInstantiate) -------------------------------------------------------------------------------------------------------------------------- Key: SEAMFORGE-19 URL: https://issues.jboss.org/browse/SEAMFORGE-19 Project: Seam Forge Issue Type: Bug Environment: Maven 3.0.1, Win7 64bit, jsk 1.6_21 Reporter: Michael Schuetz ------------------------------------------------------------------------------- Test set: org.jboss.seam.forge.test.project.MavenFacetsTest ------------------------------------------------------------------------------- Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.816 sec <<< FAILURE! testAbsoluteUnknownProjectCannotInstantiate(org.jboss.seam.forge.test.project.MavenFacetsTest) Time elapsed: 0.156 sec <<< FAILURE! java.lang.AssertionError: at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertNull(Assert.java:549) at org.junit.Assert.assertNull(Assert.java:560) at org.jboss.seam.forge.test.project.MavenFacetsTest.testAbsoluteUnknownProjectCannotInstantiate(MavenFacetsTest.java:167) 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.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.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:163) 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.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) at org.apache.maven.surefire.Surefire.run(Surefire.java:180) 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Updated: (SEAMWICKET-6) Create JSR299-Utils for non-contextual dependency injection

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAMWICKET-6?page=com.atlassian.jira.plug... ] Dan Allen updated SEAMWICKET-6: ------------------------------- Parent: (was: SEAMWICKET-5) Issue Type: Enhancement (was: Sub-task) > Create JSR299-Utils for non-contextual dependency injection > ----------------------------------------------------------- > > Key: SEAMWICKET-6 > URL: https://issues.jboss.org/browse/SEAMWICKET-6 > Project: Seam Wicket > Issue Type: Enhancement > Reporter: Clint Popetz > Assignee: Clint Popetz > > This includes: > (a) Create functionality similar to the CurrentManager.rootManager singleton that observes @Initialized Manager to set its instance. > (b) Move NonContextualInjector here and use java reflection rather than org.jboss.webbeans.injection. > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (SEAMWICKET-7) Make Wicket Conversational control optional

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAMWICKET-7?page=com.atlassian.jira.plug... ] Dan Allen updated SEAMWICKET-7: ------------------------------- Parent: (was: SEAMWICKET-5) Issue Type: Enhancement (was: Sub-task) > Make Wicket Conversational control optional > ------------------------------------------- > > Key: SEAMWICKET-7 > URL: https://issues.jboss.org/browse/SEAMWICKET-7 > Project: Seam Wicket > Issue Type: Enhancement > Reporter: Clint Popetz > Assignee: Clint Popetz > > From Pete's suggestions: > - define an api which allows wicket to control conversations > - use service providers (META-INF/services) to discover impls > - provide a built in impl which can use Web Beans, if it (WebBeansManager) is on the classpath > - degrade gracefully if no impl is available -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (SEAMWICKET-7) Make Wicket Conversational control optional

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAMWICKET-7?page=com.atlassian.jira.plug... ] Dan Allen closed SEAMWICKET-7. ------------------------------ Resolution: Duplicate Issue > Make Wicket Conversational control optional > ------------------------------------------- > > Key: SEAMWICKET-7 > URL: https://issues.jboss.org/browse/SEAMWICKET-7 > Project: Seam Wicket > Issue Type: Sub-task > Reporter: Clint Popetz > Assignee: Clint Popetz > > From Pete's suggestions: > - define an api which allows wicket to control conversations > - use service providers (META-INF/services) to discover impls > - provide a built in impl which can use Web Beans, if it (WebBeansManager) is on the classpath > - degrade gracefully if no impl is available -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (SEAMWICKET-7) Make Wicket Conversational control optional

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAMWICKET-7?page=com.atlassian.jira.plug... ] Dan Allen reopened SEAMWICKET-7: -------------------------------- > Make Wicket Conversational control optional > ------------------------------------------- > > Key: SEAMWICKET-7 > URL: https://issues.jboss.org/browse/SEAMWICKET-7 > Project: Seam Wicket > Issue Type: Sub-task > Reporter: Clint Popetz > Assignee: Clint Popetz > > From Pete's suggestions: > - define an api which allows wicket to control conversations > - use service providers (META-INF/services) to discover impls > - provide a built in impl which can use Web Beans, if it (WebBeansManager) is on the classpath > - degrade gracefully if no impl is available -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (SEAMWICKET-7) Make Wicket Conversational control optional

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAMWICKET-7?page=com.atlassian.jira.plug... ] Dan Allen closed SEAMWICKET-7. ------------------------------ Resolution: Done > Make Wicket Conversational control optional > ------------------------------------------- > > Key: SEAMWICKET-7 > URL: https://issues.jboss.org/browse/SEAMWICKET-7 > Project: Seam Wicket > Issue Type: Sub-task > Reporter: Clint Popetz > Assignee: Clint Popetz > > From Pete's suggestions: > - define an api which allows wicket to control conversations > - use service providers (META-INF/services) to discover impls > - provide a built in impl which can use Web Beans, if it (WebBeansManager) is on the classpath > - degrade gracefully if no impl is available -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (SEAMWICKET-6) Create JSR299-Utils for non-contextual dependency injection

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SEAMWICKET-6?page=com.atlassian.jira.plug... ] Dan Allen commented on SEAMWICKET-6: ------------------------------------ Created new issue as an enhancement since the Sub-task issue type is no longer being used. > Create JSR299-Utils for non-contextual dependency injection > ----------------------------------------------------------- > > Key: SEAMWICKET-6 > URL: https://issues.jboss.org/browse/SEAMWICKET-6 > Project: Seam Wicket > Issue Type: Sub-task > Reporter: Clint Popetz > Assignee: Clint Popetz > > This includes: > (a) Create functionality similar to the CurrentManager.rootManager singleton that observes @Initialized Manager to set its instance. > (b) Move NonContextualInjector here and use java reflection rather than org.jboss.webbeans.injection. > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2011