December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3854) seam-gen test fails if there is a space in the path to the project

by Jay Balunas (JIRA)

seam-gen test fails if there is a space in the path to the project ------------------------------------------------------------------ Key: JBSEAM-3854 URL: https://jira.jboss.org/jira/browse/JBSEAM-3854 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: Windows XP JDK 5 Reporter: Jay Balunas Fix For: 2.1.2.CR1 If there is a space in the path to seam-gen project and you attempt to execute "seam test" you will see an exception like the one below. ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Parse: name=vfsfile:/C:/dev/projects/seam/2.1.1.GA/seam%20gen/seamGenEar/bootstrap/deploy/jboss-local-jdbc.rar state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error parsing meta data jboss-local-jdbc.rar/META-INF/ra.xml at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.vfs.spi.deployer.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:124) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:199) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) at org.jboss.embedded.DeploymentScanner.start(DeploymentScanner.java:105) 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:585) at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56) at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110) at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:214) at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:69) at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:309) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:279) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130) at org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXMLDeployer.java:96) at org.jboss.embedded.Bootstrap.deployBaseBootstrapUrl(Bootstrap.java:130) at org.jboss.embedded.Bootstrap.bootstrapURL(Bootstrap.java:142) at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:183) at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:195) at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:11) at org.jboss.seam.mock.AbstractSeamTest.startJbossEmbeddedIfNecessary(AbstractSeamTest.java:1024) at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915) at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58) 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:585) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:394) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:142) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:261) at org.testng.SuiteRunner.run(SuiteRunner.java:190) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792) at org.testng.TestNG.runSuitesLocally(TestNG.java:765) at org.testng.TestNG.run(TestNG.java:699) at org.testng.TestNG.privateMain(TestNG.java:824) at org.testng.TestNG.main(TestNG.java:802) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: vfsfile:/C:/dev/projects/seam/2.1.1.GA/seam gen/seamGenEar/bootstrap/deploy/jboss-local-jdbc.rar/META-INF/ra.xml at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:177) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:186) at org.jboss.deployers.vfs.spi.deployer.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:120) ... 68 more Caused by: java.io.FileNotFoundException: File does not exist: C:\dev\projects\seam\2.1.1.GA\seam%20gen at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtualFileHandler(FileSystemContext.java:249) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtualFileHandler(FileSystemContext.java:186) at org.jboss.virtual.plugins.context.file.FileHandler.createChildHandler(FileHandler.java:216) at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:291) at org.jboss.virtual.plugins.context.file.FileHandler.findChild(FileHandler.java:199) at org.jboss.virtual.plugins.context.AbstractVFSContext.findChild(AbstractVFSContext.java:118) at org.jboss.virtual.VFS.findChild(VFS.java:205) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveCachedVirtualFile(VirtualFileURLConnection.java:90) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:105) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:117) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:173) ... 70 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3866) datasource redeployed on explode

by Dan Allen (JIRA)

datasource redeployed on explode -------------------------------- Key: JBSEAM-3866 URL: https://jira.jboss.org/jira/browse/JBSEAM-3866 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.1.2.CR1 The datasource is being redeployed during hot deployment (ant explode) as a result of the -ds.xml file being copied with overwrite="true". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3871) Member cann't access wikiNode which read_access_level setted to himself

by wu haixing (JIRA)

Member cann't access wikiNode which read_access_level setted to himself ----------------------------------------------------------------------- Key: JBSEAM-3871 URL: https://jira.jboss.org/jira/browse/JBSEAM-3871 Project: Seam Issue Type: Bug Components: Wiki Affects Versions: 2.1.1.GA Reporter: wu haixing Assignee: Christian Bauer If a member create a document want to see by himself,currentAccessLevel Filter cann't get the document because the member's access level obviously less than WikiNode's READ_ACCESS_LEVEL setted to administrator's accessLevel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3997) Need to document on-postback flag for page actions

by Nate Ridderman (JIRA)

Need to document on-postback flag for page actions -------------------------------------------------- Key: JBSEAM-3997 URL: https://jira.jboss.org/jira/browse/JBSEAM-3997 Project: Seam Issue Type: Sub-task Components: Documentation Issues Affects Versions: 2.1.1.CR1 Reporter: Nate Ridderman Priority: Minor Bug 2469 introduced a new flag for page actions. This isn't documented in the reference manual. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3894) Upgrade to RichFaces 3.3.0.GA

by Jay Balunas (JIRA)

Upgrade to RichFaces 3.3.0.GA ----------------------------- Key: JBSEAM-3894 URL: https://jira.jboss.org/jira/browse/JBSEAM-3894 Project: Seam Issue Type: Task Components: Build Reporter: Jay Balunas Priority: Critical Fix For: 2.1.2.CR1 RichFaces 3.3.0 has been released and Seam should upgrade to it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3907) Exclude build directories in generated IntelliJ IDEA project

by Pawel Wrzeszcz (JIRA)

Exclude build directories in generated IntelliJ IDEA project ------------------------------------------------------------ Key: JBSEAM-3907 URL: https://jira.jboss.org/jira/browse/JBSEAM-3907 Project: Seam Issue Type: Patch Components: Tools Affects Versions: 2.1.1.GA Reporter: Pawel Wrzeszcz Assignee: Dan Allen Priority: Minor Directories 'dist' and 'exploded-archives' should be marked as excluded in the IntelliJ IDEA module file created by seam-gen. I realize this is minor, but saves a couple of clicks and prevents IDEA from 1) reloading a whole project during the build and 2) detecting facets in the build directories. Really short path attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3782) allow callbacks to components that implement HttpSessionActivationListener interface

by Dan Allen (JIRA)

allow callbacks to components that implement HttpSessionActivationListener interface ------------------------------------------------------------------------------------ Key: JBSEAM-3782 URL: https://jira.jboss.org/jira/browse/JBSEAM-3782 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.CR1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.1.1.CR2 Seam adds the HttpSessionActivationListener interface to all non-EJB components to capture session passivation and activation events. Seam then channels these callbacks to the @PrePassivate and @PostActivate methods on the component, respectively. However, Seam is not honoring components which might have already implemented this interface. Allow calls to sessionWillPassivate and sessionDidActivate to proceed on to the component if the bean class implements HttpSessionActivationListener. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3747) Boolean tests during Initialization consistent with JDK

by Anthony Whitford (JIRA)

Boolean tests during Initialization consistent with JDK ------------------------------------------------------- Key: JBSEAM-3747 URL: https://jira.jboss.org/jira/browse/JBSEAM-3747 Project: Seam Issue Type: Patch Components: Core Affects Versions: 2.1.1.CR1 Reporter: Anthony Whitford Priority: Minor I noticed code like: boolean autoCreate = "true".equals(factory.attributeValue("auto-create")); Java already has some boolean semantics that I would expect to be leveraged for consistency. The line could be replaced with: boolean autoCreate = Boolean.parseBoolean(factory.attributeValue("auto-create")); There is a subtle difference in that parseBoolean will do a case insensitive comparison, but at least this is consistent with core Java. See: http://java.sun.com/javase/6/docs/api/java/lang/Boolean.html#parseBoolean... and: http://java.sun.com/javase/6/docs/api/java/lang/Boolean.html#valueOf(java... The above change also removes "magic values" repeated ("true"). Very minor issue, but also easy to fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3821) seam-gen - entity is not mapped in war project on AS5

by Jozef Hartinger (JIRA)

seam-gen - entity is not mapped in war project on AS5 ----------------------------------------------------- Key: JBSEAM-3821 URL: https://jira.jboss.org/jira/browse/JBSEAM-3821 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.1.CR2 Environment: JDK5 JBoss AS 5.0.0.GA Reporter: Jozef Hartinger Fix For: 2.1.2.CR1 Attachments: genWarRich.txt When accessing generated entity page the application is failing on "org.hibernate.hql.ast.QuerySyntaxException: Vehicle is not mapped [select vehicle from Vehicle vehicle]" . I am using standard release-process.txt database tables. To reproduce the issue: 1.) Create new war project and generate entities. 2.) Log into the application and click PersonList or VehicleList -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3708) Only enable ManagedEntityInterceptor when needed

by Pete Muir (JIRA)

Only enable ManagedEntityInterceptor when needed ------------------------------------------------ Key: JBSEAM-3708 URL: https://jira.jboss.org/jira/browse/JBSEAM-3708 Project: Seam Issue Type: Feature Request Components: Core Reporter: Pete Muir Priority: Critical Fix For: 2.1.1.CR2 The MEI is only needed for: * JavaBeans in a cluster that are conversation scoped or * EJBs that are conversation scoped Add some configuration to <core:init /> to allow the user to enable clustering mode (or autodetect) and upgrade the isInterceptorEnabled method to take account of this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009