November 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4049) Drools Custom Consequence Exception handlers

by Tihomir Surdilovic (JIRA)

Drools Custom Consequence Exception handlers -------------------------------------------- Key: JBSEAM-4049 URL: https://jira.jboss.org/jira/browse/JBSEAM-4049 Project: Seam Issue Type: Feature Request Components: Drools Affects Versions: 2.1.1.GA Reporter: Tihomir Surdilovic Assignee: Tihomir Surdilovic Allow to specify a custom user defined handler for consequence exceptions in components.xml. For example: <drools:rule-base name="securityRules"> <drools:rule-files><value>/security.drl</value></drools:rule-files> <drools:consequence-exception-handler><value>myCustomHandler</value</drools:consequence-exception-handler> </drools:rule-base> -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4051) Add metawidget examples

by Dan Allen (JIRA)

Add metawidget examples ----------------------- Key: JBSEAM-4051 URL: https://jira.jboss.org/jira/browse/JBSEAM-4051 Project: Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Priority: Minor Fix For: 2.1.2.CR1 Adopt the Seam metawidget examples from the metawidget examples distribution into the examples directory (booking, groovybooking, dvdstore). Use the same build strategy by copying the source from original example into a staging directory and then overwriting the files that differ. That way, maintenance is kept to a minimum. -- 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-4066) captureCurrentView on redirect should capture all request parameters

by Dan Allen (JIRA)

captureCurrentView on redirect should capture all request parameters -------------------------------------------------------------------- Key: JBSEAM-4066 URL: https://jira.jboss.org/jira/browse/JBSEAM-4066 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.2.0.CR1 Attachments: JBSEAM-4066-trunk-v1.txt When the captureCurrentRequest() method was deprecated and replaced by captureCurrentView(), the behavior changed such that page parameters were being saved instead of request parameters. I'm fine with the idea of preserving page parameters based on how they were bound to the model on the way into the page, but I also think that arbitrary request parameters need to be captured. Otherwise, the redirect back to the current view will in many cases be incomplete and thus fail. The logic I propose is to capture the request parameters and then override the values with the values from the page parameters (giving page parameters the precedence). However, long term, we should also consider the fact that multi-value parameters are not being preserved. Likely they should be captured as well, but there is a lack of infrastructure to support them. -- 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-3987) Integrate RESTEasy with Seam Application fwk for easy CRUD

by Christian Bauer (JIRA)

Integrate RESTEasy with Seam Application fwk for easy CRUD ---------------------------------------------------------- Key: JBSEAM-3987 URL: https://jira.jboss.org/jira/browse/JBSEAM-3987 Project: Seam Issue Type: Feature Request Components: WS Reporter: Christian Bauer Assignee: Jozef Hartinger Similar to what RoR is offering: Allow developers to declaratively map entities for CRUD through RESTful GET/POST/DELETE/PUT requests with customizable resource URI generation strategy. -- 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
5
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-3827) seam-gen setup and create-project with support for individual JBoss domain

by Stephan Heffner (JIRA)

seam-gen setup and create-project with support for individual JBoss domain -------------------------------------------------------------------------- Key: JBSEAM-3827 URL: https://jira.jboss.org/jira/browse/JBSEAM-3827 Project: Seam Issue Type: Patch Components: Build Affects Versions: 2.1.1.CR2 Reporter: Stephan Heffner Priority: Optional Attachments: jboss-seam-gen-domain.patch I'll attach a small patch to support a user defined value of JBoss version and domain. Predefined values are 'default' or 'standard' (Version 5.x). Maybe it's useful for others as well. -- 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
6
0 / 0

[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-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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2009