December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2421) Forgot password feature

by Christian Bauer (JIRA)

Forgot password feature ----------------------- Key: JBSEAM-2421 URL: http://jira.jboss.com/jira/browse/JBSEAM-2421 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor Procedure for forgotten password: - User clicks on link, enters username and email address - Data is validated against accounts - Generate new activation code and store in database - E-mail with activation code will be send - User clicks on link and can enter new password - If user doesn't click on link, old password stays - need to think about activation code, right now that means account is inactive if there is an activation code present -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1863) Pager plugin for previous/next document in a directory

by Christian Bauer (JIRA)

Pager plugin for previous/next document in a directory ------------------------------------------------------ Key: JBSEAM-1863 URL: http://jira.jboss.com/jira/browse/JBSEAM-1863 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Trivial A plugin I can put on top or at the bottom of a page which renders links to previous/next page in the current directory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2440) Exception rules in pages.xml redirect to a 404 page if redirect destination isn't in web root.

by Fijai Cairo (JIRA)

Exception rules in pages.xml redirect to a 404 page if redirect destination isn't in web root. ---------------------------------------------------------------------------------------------- Key: JBSEAM-2440 URL: http://jira.jboss.com/jira/browse/JBSEAM-2440 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: JBoss 4.20 GA/ JBoss 4.22 GA, OSX 10.5.1, JRE 1.5.0_13 Reporter: Fijai Cairo Exception redirections rules in pages.xml to error pages that reside anywhere besides the web root always yield a 404 page. This rule in pages.xml works. When the exception is raised, the user is redirected to the correct error page <exception class="com.myApp.exception.GatewayException"> <redirect view-id="/gatewayerror.xhtml"> <message>GatewayException.</message> </redirect> </exception> This rule doesn't work. I have the error file in a directory named "errors". When the exception is raised, the user is directed to a 404 page even though the Url reflects the right path. <exception class="com.myApp.exception.GatewayException"> <redirect view-id="/errors/gatewayerror.xhtml"> <message>GatewayException.</message> </redirect> </exception> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2438) Clarification of differences between request and event scope

by Ajay Gupta (JIRA)

Clarification of differences between request and event scope ------------------------------------------------------------ Key: JBSEAM-2438 URL: http://jira.jboss.com/jira/browse/JBSEAM-2438 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.CR1 Reporter: Ajay Gupta Priority: Minor In SEAM reference documentation, please clarify that the request and event scope are not the same. After reading the documentation, it was not very clear. This will help clarify things. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2437) @In(create=true, value="#{...}") throws exceptions if required = false is not specified

by Ajay Gupta (JIRA)

@In(create=true, value="#{...}") throws exceptions if required = false is not specified --------------------------------------------------------------------------------------- Key: JBSEAM-2437 URL: http://jira.jboss.com/jira/browse/JBSEAM-2437 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.CR1 Reporter: Ajay Gupta I have a SEAM component as follows: @Name("customer") @Scope(CONVERSATION) public class Customer { @In (create=true) private Address address; @Factory(value="address") public void getAddress() { this.address = ....//logic to populate address attribute in Customer. } public void doSomething() { .... } } In this case, when Customer.doSomething() is called and if customer.address = null, then the code as shown above fails with an exception stating: "non-null address value should not be null". To make the code above to work, I have to add required = false to the @In annotation. SEAM still calls the factory method for address to populate the Address attribute in Customer before calling Customer.doSomething(). I would think that if create=true is specified on an @In annotation and required attribute is not specified on @In, then an exception should only be thrown if the attribute is truly null (if the attribute can be given a non-null value using a @Factory method, then required=true should not be enforced). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2435) SeamTest doesn't run when jboss.org is down

by Christian Bauer (JIRA)

SeamTest doesn't run when jboss.org is down ------------------------------------------- Key: JBSEAM-2435 URL: http://jira.jboss.com/jira/browse/JBSEAM-2435 Project: JBoss Seam Issue Type: Bug Components: Test Harness Reporter: Christian Bauer Priority: Blocker This is my ds.xml file (same as all other Seam examples): <!DOCTYPE datasources PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN" "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd"> Tonight jboss.org was down. SeamTest.init() either hangs or throws this fantastic exception: [testng] ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Parse: name=vfsfile:/Users/turin/work/remote/jboss/public/jboss-seam/examples/wiki/build/testclasses/ state=Not Installed mode=Manual requiredState=Parse [testng] org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/Users/turin/work/remote/jboss/public/jboss-seam/examples/wiki/build/testclasses/wiki-ds.xml [testng] at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [testng] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:232) [testng] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:199) [testng] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162) [testng] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) [testng] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) [testng] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:906) [testng] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) [testng] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) [testng] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) [testng] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) [testng] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) [testng] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) [testng] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) [testng] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) [testng] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) [testng] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) [testng] at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:127) [testng] at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:289) [testng] at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:16) [testng] at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1005) [testng] at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:929) [testng] at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) [testng] at org.jboss.seam.wiki.test.util.DBUnitSeamTest.init(DBUnitSeamTest.java:139) [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [testng] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [testng] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [testng] at java.lang.reflect.Method.invoke(Method.java:585) [testng] at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604) [testng] at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:394) [testng] at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:142) [testng] at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79) [testng] at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:165) [testng] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103) [testng] at org.testng.TestRunner.runWorkers(TestRunner.java:678) [testng] at org.testng.TestRunner.privateRun(TestRunner.java:624) [testng] at org.testng.TestRunner.run(TestRunner.java:495) [testng] at org.testng.SuiteRunner.runTest(SuiteRunner.java:300) [testng] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:295) [testng] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:275) [testng] at org.testng.SuiteRunner.run(SuiteRunner.java:190) [testng] at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792) [testng] at org.testng.TestNG.runSuitesLocally(TestNG.java:765) [testng] at org.testng.TestNG.run(TestNG.java:699) [testng] at org.testng.TestNG.privateMain(TestNG.java:824) [testng] at org.testng.TestNG.main(TestNG.java:802) [testng] Caused by: javax.xml.bind.UnmarshalException [testng] - with linked exception: [testng] [org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed.] [testng] at javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:315) [testng] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalException(UnmarshallerImpl.java:506) [testng] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:215) [testng] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:190) [testng] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:241) [testng] at org.jboss.resource.deployers.ManagedConnectionFactoryParserDeployer.parse(ManagedConnectionFactoryParserDeployer.java:100) [testng] at org.jboss.resource.deployers.ManagedConnectionFactoryParserDeployer.parse(ManagedConnectionFactoryParserDeployer.java:47) [testng] at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:112) [testng] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:225) [testng] ... 44 more [testng] Caused by: org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed. [testng] at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) [testng] at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) [testng] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [testng] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [testng] at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) [testng] at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source) [testng] at org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDExternalSubset(Unknown Source) [testng] at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source) [testng] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) [testng] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [testng] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [testng] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) [testng] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) [testng] at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) [testng] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:211) [testng] ... 50 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2433) Adding accessibility information to JSF tag documentation

by Nils Kassube (JIRA)

Adding accessibility information to JSF tag documentation --------------------------------------------------------- Key: JBSEAM-2433 URL: http://jira.jboss.com/jira/browse/JBSEAM-2433 Project: JBoss Seam Issue Type: Feature Request Components: Documentation, JSF Affects Versions: 2.0.1.CR1 Reporter: Nils Kassube Currently the JSF tags lack crucial information regarding their ability to e.g. render without JavaScript support. In many European countries building web applications which are accessible by disabled users is now required by law for work done for the government and large companies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2152) Exception thrown from method expression causing re-evaluation as value expression

by Matthew Lieder (JIRA)

Exception thrown from method expression causing re-evaluation as value expression --------------------------------------------------------------------------------- Key: JBSEAM-2152 URL: http://jira.jboss.com/jira/browse/JBSEAM-2152 Project: JBoss Seam Issue Type: Bug Components: BPM, EL Affects Versions: 2.0.0.CR2 Reporter: Matthew Lieder To reproduce: In a Seam component called "bean": public void method() { throw new RuntimeException("my error"); } In a jPDL pageflow, inside a transition element: <action expression="#{bean.method}" /> When the action is executed, an exception about "method" not being a property of the "bean" class is thrown (the real exception is never shown). See the forum thread for analysis of the underlying cause. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2384) PDF Templating

by Samuel Mendenhall (JIRA)

PDF Templating -------------- Key: JBSEAM-2384 URL: http://jira.jboss.com/jira/browse/JBSEAM-2384 Project: JBoss Seam Issue Type: Feature Request Components: PDF Reporter: Samuel Mendenhall Priority: Minor There should be some means of templating PDF xhtml files like how it is done with mail or any way to be able to logically break apart a large pdf and ui:include different sections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2428) build\sample.build.properties: jboss.home typo

by Yanis Kekatos (JIRA)

build\sample.build.properties: jboss.home typo ---------------------------------------------- Key: JBSEAM-2428 URL: http://jira.jboss.com/jira/browse/JBSEAM-2428 Project: JBoss Seam Issue Type: Bug Components: Build Affects Versions: 2.0.0.GA Environment: windows XP SP2, JDK 1.5 Reporter: Yanis Kekatos Priority: Minor typo in build\sample.build.properties file #jboss.home C:\\jboss-4.2.1.GA should be: #jboss.home = C:\\jboss-4.2.1.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007