June 2011 - forge-dev - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-214) promptChoice from map doesn't work for last item when selecting by it's index

by Paul Bakker (JIRA)

promptChoice from map doesn't work for last item when selecting by it's index ----------------------------------------------------------------------------- Key: SEAMFORGE-214 URL: https://issues.jboss.org/browse/SEAMFORGE-214 Project: Seam Forge Issue Type: Bug Components: Shell Reporter: Paul Bakker Assignee: Paul Bakker The last (or only) item in a map can't be selected by using it's index due to a stupid bug. Patch on the way. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-217) Redirect console output in tests to assert on it

by Paul Bakker (JIRA)

Redirect console output in tests to assert on it ------------------------------------------------ Key: SEAMFORGE-217 URL: https://issues.jboss.org/browse/SEAMFORGE-217 Project: Seam Forge Issue Type: Feature Request Components: Test Harness Reporter: Paul Bakker For some tests it's difficult to assert just looking at the side effects. It might be much easier to assert on console output. We need a way to redirect console output to an in-memory list or something so you can read from that in tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-216) 'First steps' app fails to deploy on clean JBoss-6.0.0.Final

by Richard Kennard (JIRA)

'First steps' app fails to deploy on clean JBoss-6.0.0.Final ------------------------------------------------------------ Key: SEAMFORGE-216 URL: https://issues.jboss.org/browse/SEAMFORGE-216 Project: Seam Forge Issue Type: Bug Environment: Windows 7 64-bit Reporter: Richard Kennard Hi guys, I tried following the instructions here: https://docs.jboss.org/author/display/SEAMFORGE/First+steps+with+Scaffolding (resulting project attached) And deployed to a fresh copy of JBoss-6.0.0.Final, but I get this error: 10:06:39,373 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=vfs:///Z:/jboss-6.0.0.Final/server/d efault/deploy/TestApp.war_WeldBootstrapBean state=Create: org.jboss.weld.exceptions.WeldException: by java.lang.ClassFormatError: Illegal class name " com/testapp/view/org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Z:$jboss-6$0$0$Final$server$default$deploy$TestApp$war"-SessionBean-CustomerBeancom$ testapp$view$CustomerBean[@javax$ejb$Stateful(description=,mappedName=,name=)@javax$enterprise$context$RequestScoped()@javax$inject$Named(value=)@org$ jboss$seam$transaction$Transactional(value=REQUIRED)@org$jboss$seam$transaction$TransactionalInterceptorBinding()]{org$jboss$forge$persistence$Persist enceUtil$entityManager[@javax$inject$Inject()]$}_$$_WeldProxy" in class file com/testapp/view/org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Z:$jbos s-6$0$0$Final$server$default$deploy$TestApp$war"-SessionBean-CustomerBeancom$testapp$view$CustomerBean[@javax$ejb$Stateful(description=,mappedName=,na me=)@javax$enterprise$context$RequestScoped()@javax$inject$Named(value=)@org$jboss$seam$transaction$Transactional(value=REQUIRED)@org$jboss$seam$trans action$TransactionalInterceptorBinding()]{org$jboss$forge$persistence$PersistenceUtil$entityManager[@ja at org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:285) [:6.0.0.Final] at org.jboss.weld.bean.SessionBean.initProxyClass(SessionBean.java:254) [:6.0.0.Final] at org.jboss.weld.bean.SessionBean.initialize(SessionBean.java:176) [:6.0.0.Final] at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:113) [:6.0.0.Final] at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:214) [:6.0.0.Final] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:363) [:6.0.0.Final] at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.boot(BootstrapBean.java:92) [:6.0.0.Final] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_25] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_25] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_25] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_25] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.0.GA] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.0.GA] at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.0.GA] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-kernel.jar:2.2.0.GA] at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.GA] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-k ernel.jar:2.2.0.GA] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.ja r:2.2.0.GA] at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.GA] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.GA] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-depende ncy.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2. 0.GA] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0 .GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.G A] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2] at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2 ] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_25] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_25] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_25] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_25] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_25] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25] at java.lang.Thread.run(Thread.java:662) [:1.6.0_25] Caused by: javassist.CannotCompileException: by java.lang.ClassFormatError: Illegal class name "com/testapp/view/org$jboss$weld$bean-jboss$classloader :id="vfs:$$$Z:$jboss-6$0$0$Final$server$default$deploy$TestApp$war"-SessionBean-CustomerBeancom$testapp$view$CustomerBean[@javax$ejb$Stateful(descript ion=,mappedName=,name=)@javax$enterprise$context$RequestScoped()@javax$inject$Named(value=)@org$jboss$seam$transaction$Transactional(value=REQUIRED)@o rg$jboss$seam$transaction$TransactionalInterceptorBinding()]{org$jboss$forge$persistence$PersistenceUtil$entityManager[@javax$inject$Inject()]$}_$$_We ldProxy" in class file com/testapp/view/org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Z:$jboss-6$0$0$Final$server$default$deploy$TestApp$war"-Sessi onBean-CustomerBeancom$testapp$view$CustomerBean[@javax$ejb$Stateful(description=,mappedName=,name=)@javax$enterprise$context$RequestScoped()@javax$in ject$Named(value=)@org$jboss$seam$transaction$Transactional(value=REQUIRED)@org$jboss$seam$transaction$TransactionalInterceptorBinding()]{org$jboss$fo rge$persistence$PersistenceUtil$entityManager[@ja at org.jboss.weld.util.bytecode.ClassFileUtils.toClass(ClassFileUtils.java:117) [:6.0.0.Final] at org.jboss.weld.bean.proxy.ProxyFactory.createProxyClass(ProxyFactory.java:392) [:6.0.0.Final] at org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:281) [:6.0.0.Final] ... 57 more Caused by: java.lang.ClassFormatError: Illegal class name "com/testapp/view/org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Z:$jboss-6$0$0$Final$serv er$default$deploy$TestApp$war"-SessionBean-CustomerBeancom$testapp$view$CustomerBean[@javax$ejb$Stateful(description=,mappedName=,name=)@javax$enterpr ise$context$RequestScoped()@javax$inject$Named(value=)@org$jboss$seam$transaction$Transactional(value=REQUIRED)@org$jboss$seam$transaction$Transaction alInterceptorBinding()]{org$jboss$forge$persistence$PersistenceUtil$entityManager[@javax$inject$Inject()]$}_$$_WeldProxy" in class file com/testapp/vi ew/org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Z:$jboss-6$0$0$Final$server$default$deploy$TestApp$war"-SessionBean-CustomerBeancom$testapp$view$C ustomerBean[@javax$ejb$Stateful(description=,mappedName=,name=)@javax$enterprise$context$RequestScoped()@javax$inject$Named(value=)@org$jboss$seam$tra nsaction$Transactional(value=REQUIRED)@org$jboss$seam$transaction$TransactionalInterceptorBinding()]{org$jboss$forge$persistence$PersistenceUtil$entit yManager[@ja at java.lang.ClassLoader.defineClass1(Native Method) [:1.6.0_25] at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [:1.6.0_25] at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [:1.6.0_25] at java.lang.ClassLoader.defineClass(ClassLoader.java:465) [:1.6.0_25] at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) [:1.6.0_25] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_25] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_25] at org.jboss.weld.util.bytecode.ClassFileUtils.toClass2(ClassFileUtils.java:143) [:6.0.0.Final] at org.jboss.weld.util.bytecode.ClassFileUtils.toClass(ClassFileUtils.java:109) [:6.0.0.Final] ... 59 more 10:06:39,458 WARN [org.jboss.profileservice.deployment.hotdeploy.HDScanner] Scan failed: org.jboss.deployers.client.spi.IncompleteDeploymentException : Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-147) JPA settings not correct in persistence.xml

by Paul Bakker (JIRA)

JPA settings not correct in persistence.xml ------------------------------------------- Key: SEAMFORGE-147 URL: https://issues.jboss.org/browse/SEAMFORGE-147 Project: Seam Forge Issue Type: Bug Components: Java EE APIs Reporter: Paul Bakker With the following command the generated settings in persistence.xml are not correct. This might also be the case for other databases and settings, but I didn't test that yet. {code} persistence setup --provider HIBERNATE --container JBOSS_AS6 --database MYSQL_INNODB --jndiDataSource java:demo {code} It sets the datasource to: java:/DefaultDS (should be java:demo) It sets the hibernate dialect to: org.hibernate.dialect.HSQLDialect (which should be MySQL5InnoDBDialect) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
9
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-199) Forge should default to built-in 'mvn' command line if Maven is not detected in the underlying system

by Lincoln Baxter III (JIRA)

Forge should default to built-in 'mvn' command line if Maven is not detected in the underlying system ----------------------------------------------------------------------------------------------------- Key: SEAMFORGE-199 URL: https://issues.jboss.org/browse/SEAMFORGE-199 Project: Seam Forge Issue Type: Feature Request Components: Builtin Plugins, Maven Integration Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Fix For: 1.0.0.Alpha4 'mvn' MvnPlugin -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-213) Maven Dependency Facet hasDepenency returns false for transitive dependencies

by George Gastaldi (JIRA)

Maven Dependency Facet hasDepenency returns false for transitive dependencies ----------------------------------------------------------------------------- Key: SEAMFORGE-213 URL: https://issues.jboss.org/browse/SEAMFORGE-213 Project: Seam Forge Issue Type: Bug Reporter: George Gastaldi According to the javadoc, dependencyFacet.hasDependency should return true on transitive dependencies as well. The following test case illustrates this behavior: https://gist.github.com/1016948 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-178) Persistence plugin should not use hardcoded domain package

by Dan Allen (JIRA)

Persistence plugin should not use hardcoded domain package ---------------------------------------------------------- Key: SEAMFORGE-178 URL: https://issues.jboss.org/browse/SEAMFORGE-178 Project: Seam Forge Issue Type: Enhancement Components: Java EE APIs Affects Versions: 1.0.0.Alpha3 Reporter: Dan Allen Some developers prefer to name their domain package something other than "domain". Don't use a hardcoded value. Either read it from global config or from project config (prompt). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Updated: (SEAMFORGE-123) DependencyResolver should be able to resolve dependencies from the local repository

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-123?page=com.atlassian.jira.plu... ] Lincoln Baxter III updated SEAMFORGE-123: ----------------------------------------- Comment: was deleted (was: --package is now an option when creating an entity. Also checks to see if you are in a package when creating the entity. Will ask that instead if so. I agree this should still be configurable) > DependencyResolver should be able to resolve dependencies from the local repository > ----------------------------------------------------------------------------------- > > Key: SEAMFORGE-123 > URL: https://issues.jboss.org/browse/SEAMFORGE-123 > Project: Seam Forge > Issue Type: Enhancement > Reporter: Lincoln Baxter III > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-211) Structured options

by Max Rydahl Andersen (JIRA)

Structured options ------------------ Key: SEAMFORGE-211 URL: https://issues.jboss.org/browse/SEAMFORGE-211 Project: Seam Forge Issue Type: Feature Request Reporter: Max Rydahl Andersen ver considered allowing something like generateEntities(@Option String table, @Option String catalog, @Option @Option String schema, @NestedOption final JPADataSource datasource) class DataSource { public DataSource(@Option(...) String name, @Option(..) password, @Option(..) ..) ... ) Which would actually provide some more nested structure and be useful in ui construction in IDE plus better naming of things even in shell ? Would also be good to be able to reference "default" @JPADatasource should be "production", "dev" or "test" if SEAMFORGE-210 comes to life? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-123) DependencyResolver should be able to resolve dependencies from the local repository

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-123?page=com.atlassian.jira.plu... ] Lincoln Baxter III commented on SEAMFORGE-123: ---------------------------------------------- --package is now an option when creating an entity. Also checks to see if you are in a package when creating the entity. Will ask that instead if so. I agree this should still be configurable > DependencyResolver should be able to resolve dependencies from the local repository > ----------------------------------------------------------------------------------- > > Key: SEAMFORGE-123 > URL: https://issues.jboss.org/browse/SEAMFORGE-123 > Project: Seam Forge > Issue Type: Enhancement > Reporter: Lincoln Baxter III > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev June 2011