December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1687) Include GanttChart into Charting

by Samuel Mendenhall (JIRA)

Include GanttChart into Charting -------------------------------- Key: JBSEAM-1687 URL: http://jira.jboss.com/jira/browse/JBSEAM-1687 Project: JBoss Seam Issue Type: Feature Request Reporter: Samuel Mendenhall Priority: Minor Including GanttChart into Seams charting package. -- 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

14 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3833) Be able to find out the Event type in observers

by Sanne Grinovero (JIRA)

Be able to find out the Event type in observers ----------------------------------------------- Key: JBSEAM-3833 URL: https://jira.jboss.org/jira/browse/JBSEAM-3833 Project: Seam Issue Type: Feature Request Components: Core Reporter: Sanne Grinovero To "find out" I mean programmatically. As the same method could be listening for more Events, it's possible we need actually to detect all types, not just one, or be sure to be fired once for each event. This is a requirement for PBR-58 -- 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, 7 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-560) seam new-query

by Gavin King (JIRA)

seam new-query -------------- Key: JBSEAM-560 URL: http://jira.jboss.com/jira/browse/JBSEAM-560 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Gavin King Assigned To: Norman Richards To generate a stub query page -- 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

14 years, 7 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2069) itext example tests

by Norman Richards (JIRA)

itext example tests ------------------- Key: JBSEAM-2069 URL: http://jira.jboss.com/jira/browse/JBSEAM-2069 Project: JBoss Seam Issue Type: Task Reporter: Norman Richards Assigned To: Norman Richards Priority: Minor Fix For: 2.0.0.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

14 years, 7 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1758) DocumentStorePhaseListener fails if installed before SeamPhaseListener when used in a portlet

by Chris Rudd (JIRA)

DocumentStorePhaseListener fails if installed before SeamPhaseListener when used in a portlet --------------------------------------------------------------------------------------------- Key: JBSEAM-1758 URL: http://jira.jboss.com/jira/browse/JBSEAM-1758 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd When the DocumentStorePhaseListener is installed before the SeamPhaseListener (this can happend when the jboss-seam.jar sits in the ear, and the jboss-seam-pdf.jar sits in the war) in a portlet environment, a "No active application context" exception is thrown during Portlet.render. This is becaus the SeamPhaseListener hasn't had a chance to setup the Seam contexts yet. I would suggest changing the code so that it responds to the Phase events that the SeamPhaseListener publishes ( org.jboss.seam.beforePhase ) so that its guaranteed to be executed after the SeamPhaseListener has property set things up. -- 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

14 years, 7 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2253) UIHeaderFooter should allow different elements than just Phrase

by Bolke de Bruin (JIRA)

UIHeaderFooter should allow different elements than just Phrase --------------------------------------------------------------- Key: JBSEAM-2253 URL: http://jira.jboss.com/jira/browse/JBSEAM-2253 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.0.GA Reporter: Bolke de Bruin Currently the UIHeaderFooter does not allow anything else than Text (Phrase). This makes it unusable to generate something with for example a company logo on every page. I am currently working on a alternative implementation and I'll will attach it it as soon as it is ready. -- 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

14 years, 7 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1625) <param> node in <exception> in pages.xml is not used

by Zalder R (JIRA)

<param> node in <exception> in pages.xml is not used ---------------------------------------------------- Key: JBSEAM-1625 URL: http://jira.jboss.com/jira/browse/JBSEAM-1625 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: jboss 4.2, seam 2.0.0.B1 Reporter: Zalder R The param option in an exception node in pages.xml is not used : <exception class="org.my.Exception"> <redirect view-id="/mypage.xhtml"> <param name="u" value="#{user.username}"/> <message severity="warn">#{messages['MSG.ERROR.MAX_TEXT_REACHED']}</message> </redirect> </exception> When the exception is triggered : redirect is done to mypage.xhtml ... not mypage.xhtml?u=whatever -- 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

14 years, 7 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1841) Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality

by steve tynor (JIRA)

Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1841 URL: http://jira.jboss.com/jira/browse/JBSEAM-1841 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 2.0.0.BETA1 Reporter: steve tynor Please add some documentation, perhaps an example project, that uses seamgen-generated EntityHome classes in order to demonstrate the intended use of the wire(), isWired(), createInstance(), getDefinedInstance(), setId(), etc. functions. Some discussion on how these related to <param> and <f:param> in XHTML is also needed. As it stands, these are completely undocumented without any explanation of their intended use, so those of us that have boostrapped a project with seamgen, have no guidance on how to maintian these classes as our application changes (new properties added to entities, etc.) -- 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

14 years, 7 months

5
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2620) Provide support for tables in RTF documents created by Seam PDF

by Terry (JIRA)

Provide support for tables in RTF documents created by Seam PDF --------------------------------------------------------------- Key: JBSEAM-2620 URL: http://jira.jboss.com/jira/browse/JBSEAM-2620 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.1.GA Reporter: Terry Priority: Minor Fix For: 2.1.0.GA Currently RTF documents created by Seam PDF ignore pdf. Provide support for tables in RTF documents as is in PDF documents. -- 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

14 years, 7 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2938) org.jboss.seam.util.XML doesn't validate

by Christian Bauer (JIRA)

org.jboss.seam.util.XML doesn't validate ---------------------------------------- Key: JBSEAM-2938 URL: http://jira.jboss.com/jira/browse/JBSEAM-2938 Project: Seam Issue Type: Bug Components: Core Reporter: Christian Bauer Assigned To: Norman Richards Priority: Minor The getRootElement() method is probably supposed to validate the XML file. However, it only sets a DTD EntityResolver: SAXReader saxReader = new SAXReader(); saxReader.setEntityResolver(new DTDEntityResolver()); saxReader.setMergeAdjacentText(true); return saxReader.read(stream).getRootElement(); This might trigger some magic flag that says "validate against this DTD", but the dom4j documentation says otherwise: http://www.dom4j.org/faq.html#how-validate I've implemented my own routine which validates against my schema properly: try { SAXReader saxReader = new SAXReader(); if (isSchemaValidating()) { saxReader.setEntityResolver(new DTDEntityResolver()); saxReader.setValidation(true); saxReader.setFeature("http://apache.org/xml/features/validation/schema",true); } saxReader.setMergeAdjacentText(true); elements.put(fileInputStream.getKey(), saxReader.read(fileInputStream.getValue()).getRootElement()); } catch (DocumentException dex) { Throwable nested = dex.getNestedException(); if (nested != null) { if (nested instanceof FileNotFoundException) { throw new RuntimeException( "Can't find schema/DTD reference for file: " + fileInputStream.getKey() + "': " + nested.getMessage(), dex ); } else if (nested instanceof UnknownHostException) { throw new RuntimeException( "Cannot connect to host from schema/DTD reference: " + nested.getMessage() + " - check that your schema/DTD reference is current", dex ); } } throw new RuntimeException("Could not parse XML file: " + fileInputStream.getKey() ,dex); } catch (Exception ex) { throw new RuntimeException("Could not parse XML file: " + fileInputStream.getKey() ,ex); } I can use that with the classpath:// feature of the DTDEntityResolver (which is the same as in Hibernate): <?xml version="1.0" encoding="UTF-8"?> <plugin key="hw" label="Hello World" xmlns="http://jboss.com/products/seam/wiki/plugin" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://jboss.com/products/seam/wiki/plugin classpath://org/jboss/seam/wiki/core/plugin/plugin-1.0.xsd"> ... -- 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

14 years, 7 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008