January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1981) enable validation on file upload component

by Bruno Bieth (JIRA)

enable validation on file upload component ------------------------------------------ Key: JBSEAM-1981 URL: http://jira.jboss.com/jira/browse/JBSEAM-1981 Project: JBoss Seam Issue Type: Patch Reporter: Bruno Bieth Currently file upload can't be validated. The attached patch allow to use the hibernate validation framework with byte[] attribute. You may have, for instance, to check if an uploaded file is an Image. About the patch : First the submittedValue is not set so the validation phase is skipped, second file upload doesn't use the standard "value" attribute (needed by the ModelValidator) but "data". To work you have to use a value attribute to your fileupload component. At the moment this work only with Facelets. For backward compatibility the data attribute is kept (but validation won't work). -- 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

16 years, 5 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1387) Support for overriding .cfg.xml properties in HibernateFactory (patch included)

by Przemyslaw Jaskierski (JIRA)

Support for overriding .cfg.xml properties in HibernateFactory (patch included) -------------------------------------------------------------------------------- Key: JBSEAM-1387 URL: http://jira.jboss.com/jira/browse/JBSEAM-1387 Project: JBoss Seam Issue Type: Feature Request Environment: Microcontainer Reporter: Przemyslaw Jaskierski Fix For: 1.3.0.ALPHA Attachments: HibernateFactory-patch.diff.zip Currently HibernateFactory supports only one type of configuration at a time: .cfg.xml file or "programmatic" one passed by the cfgProperties property. It would be great to have the ability to override individual properties from the specified .cfg.xml file using cfgProperties property. For example, when you want to have special value for hibernate.hbm2ddl.auto in case of tests only, and normal one in case of production environment. Applying my patch makes the following thing possible (instead of maintaing two almost identicall hibernate.cfg.xml files): <bean name="pecpHibernateSessionFactoryFactory" class="pecp.core.seam.HibernateFactory"> <property name="cfgResourceName"> <inject bean="pecpHibernateConfigurationLocation"/> </property> <property name="namingStrategy"> <inject bean="underscoreAwareNamingStrategy"/> </property> <property name="cfgProperties"> <map class="java.util.Hashtable" keyClass="java.lang.String" valueClass="java.lang.String"> <entry> <key>hibernate.hbm2ddl.auto</key> <value>create-drop</value> </entry> </map> </property> </bean> I've kept original logical code flow intact, so when there is no cfgResourceName and no cfgProperties set, Seam (as in original case) tries to call configuration.configure() and try to configure from hibernate.cfg.xml file. To make override functionality work you need to specify cfgResourceName property. -- 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

16 years, 5 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1961) ConversationEntry.isCurrent returns incorrect value when the ConversationEntry represents a temporary conversation

by Chris Rudd (JIRA)

ConversationEntry.isCurrent returns incorrect value when the ConversationEntry represents a temporary conversation ------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-1961 URL: http://jira.jboss.com/jira/browse/JBSEAM-1961 Project: JBoss Seam Issue Type: Bug Reporter: Chris Rudd ConversationEntry.isCurrent always returns false for the CE that represents the current conversaion if that conversation is not long running. This was discovered when attempting to to work around JBSEAM-1901. I would expect the CE to return true if it represents the current conversation reguarless of the longRunning/temporary state of the conversation. -- 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

16 years, 5 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2321) only generate-entities creates views that begin with uppercase

by Dan Allen (JIRA)

only generate-entities creates views that begin with uppercase -------------------------------------------------------------- Key: JBSEAM-2321 URL: http://jira.jboss.com/jira/browse/JBSEAM-2321 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Reporter: Dan Allen Fix For: 2.0.x This is a blaring bug that has someone been overlooked up until now. The generate-entities command (now generate-ui) creates pages using the naming pattern FooBar.xhtml whereas all of the other commands use the naming pattern fooBar.xhtml. We should definitely bring generate-entities in line with the rest of the crowd. It is very unconventional to start pages with uppercase characters (going by experience) -- 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

16 years, 5 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2549) s:decorate + a4jsf tidy filter causes silent a4jsf failures

by Stuart Robertson (JIRA)

s:decorate + a4jsf tidy filter causes silent a4jsf failures ----------------------------------------------------------- Key: JBSEAM-2549 URL: http://jira.jboss.com/jira/browse/JBSEAM-2549 Project: JBoss Seam Issue Type: Bug Components: JSF Controls Environment: Seam 2.0.1CR, Richfaces 3.1.4CR4, Jboss 4.2.x Reporter: Stuart Robertson In short, the tidy filter can cause ajax behaviors to silently fail in a manner that is nearly impossible to troubleshoot. This occurs if the tidy filter silently removes markup that it determines isn't valid html, meaning that the browser client receives less markup than the component tree actually renders. Here's how I ran into this, and how you can reproduce. First, create a s:decorate-suitable file that renders an input control as a series of columns: <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:s="http://jboss.com/products/seam/taglib"> <td class="name #{invalid?'errors':''}"> <s:label styleClass="label"><ui:insert name="label"/></s:label> <s:span styleClass="required" rendered="#{required}">*</s:span> </td> <td class="value #{invalid?'errors':''}"> <s:validateAll> <ui:insert/> </s:validateAll> </td> <td class="errorcolumn"> <s:message styleClass="error errors"/> </td> </ui:composition> Now include this in a table which is referenced in a reRender attribute. Expected behavior would be that the above would come back in the output, and be inserted into the dom client-side. In fact, the above doesn't get included in the ajax response at all. Why? Here's what the default configuration of the a4jsf filter does: 02:56:34,824 DEBUG [SeamPhaseListener] committing transaction after phase: RENDER_RESPONSE 6 02:56:34,837 DEBUG [BaseXMLFilter] Process response to well-formed XML for AJAX XMLHttpRequest parser 02:56:34,837 DEBUG [ConfigurableXMLFilter] default tidy parser properties loaded 02:56:34,838 DEBUG [TidyParser] Print output as XML 02:56:34,844 DEBUG [TidyParser] Message for HTML parsing : missing <!DOCTYPE> declaration 02:56:34,844 DEBUG [TidyParser] Message for HTML parsing : inserting missing 'title' element 02:56:34,845 DEBUG [TidyParser] Message for HTML parsing : missing <tbody> 02:56:34,850 DEBUG [TidyParser] Message for HTML parsing : missing <tbody> 02:56:34,850 DEBUG [TidyParser] Message for HTML parsing : <div> isn't allowed in <tr> elements 02:56:34,850 DEBUG [TidyParser] Message for HTML parsing : missing </div> before <td> ... and so on. TidyParser happily trims out invalid html. Which is fine I guess, but nothing makes it clear that this is what is happening. Suddenly the richfaces ajax magic stops working... Absolutely maddening (this kept me busy for about a day, I'm embarrassed to say). A few suggestions. One is to think of how Seam/Ajax4Jsf can communicate to a developer when a destructive parser is responsible for removing markup from a rendered view. One suggestion would be to add something to the xml response, a flag or something, indicating that tidy removed content. Another would be to write out a message to INFO when the TidyParser removed markup. I'm not sure I understand why TIDY is enabled by default (as in this is how seamgen-produced projects are setup). This same markup is presented to the browser directly when not sent via an ajax update, and given that most seam projects are using facelets, the markup is at the very least well formed. I can see how TIDY may be useful at a certain point in development, but to have it on by default, where it can silently break ajax functionality and also eat up resources in production... hmm. Another issue this highlights is that s:decorate seems to be needlessly limited. Why must it wrap content in a div? DecorateRenderBase renders a div in all cases, which is a shame. It means we can't decorate input controls as I attempted above without causing Tidy to (correctly?) point out that divs can't come between a <tr> and it's <td>. -- 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

16 years, 5 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2540) no-conversation-view-id not working in pageflow definition

by Bernard Labno (JIRA)

no-conversation-view-id not working in pageflow definition ---------------------------------------------------------- Key: JBSEAM-2540 URL: http://jira.jboss.com/jira/browse/JBSEAM-2540 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.1.CR1 Environment: Linux Reporter: Bernard Labno Priority: Minor Putting no-conversation-view-id only in pageflow definition file does not redirect if there is no conversation. Redirection takes place only if both "conversation-required" and "no-conversation-view-id" attributes are provided in pages.xml Shouldn't it be possible to place no-conversation-view-id only in pageflow file and live pages.xml empty ? -- 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

16 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2537) Document pluggable deployment handler

by Pete Muir (JIRA)

Document pluggable deployment handler ------------------------------------- Key: JBSEAM-2537 URL: http://jira.jboss.com/jira/browse/JBSEAM-2537 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor Fix For: 2.0.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

16 years, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2431) Finish of StyleResource

by Pete Muir (JIRA)

Finish of StyleResource ----------------------- Key: JBSEAM-2431 URL: http://jira.jboss.com/jira/browse/JBSEAM-2431 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor Fix For: 2.0.x Split out the id prefixing stuff and merge back into wiki. Document the style resource stuff. -- 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

16 years, 5 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2250) Listing returns no records found if current page number is higher than expected results

by Terry (JIRA)

Listing returns no records found if current page number is higher than expected results --------------------------------------------------------------------------------------- Key: JBSEAM-2250 URL: http://jira.jboss.com/jira/browse/JBSEAM-2250 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Win XP, JDK 6, JBoss AS 4.2.2. Reporter: Terry Priority: Minor When browsing search results based on EntityQuery, and current results page number is higher than results based on further search criteria entered. Then seam returns no records found. See Forum issue for further details. -- 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

16 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2128) annotations on components installed by default can't be overriden

by Matt Drees (JIRA)

annotations on components installed by default can't be overriden ----------------------------------------------------------------- Key: JBSEAM-2128 URL: http://jira.jboss.com/jira/browse/JBSEAM-2128 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Reporter: Matt Drees Priority: Minor This may actually be intended; I can't tell for sure. Certain annotation shouldn't be overrideable, like @Install or @Name. But it seems to me some should ( like @Scope or @JndiName). I'll attach a test case with more comments inline. It'd be helpful if a seam dev could look it over and say "Yes, it's behaving correctly", or "Something's broken". -- 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

16 years, 5 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008