July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1530) Seam-gen: @Length in char(1) property

by Luiz Augusto Ruiz (JIRA)

Seam-gen: @Length in char(1) property ------------------------------------- Key: JBSEAM-1530 URL: http://jira.jboss.com/jira/browse/JBSEAM-1530 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.3.0.ALPHA Reporter: Luiz Augusto Ruiz Seam-gen put a @Length Hibernate validator in char property. When a field of a table is CHAR(1) Hibernate generates a char property and seam-gen put a @Length(size=1). This can be fixed updating the template pojo/GetPropertyAnnotation.ftl: <#include "Ejb3PropertyGetAnnotation.ftl"/> <#if !property.optional> @${pojo.importType("org.hibernate.validator.NotNull")} </#if> <#if property.columnSpan==1> <#assign column = property.getColumnIterator().next()/> <#if !c2h.isManyToOne(property) && !c2h.isTemporalValue(property) && column.length!=255 && column.length!=1> @${pojo.importType("org.hibernate.validator.Length")}(max=${column.length?c}) </#if> </#if> " && column.length!=1" fix the bug. -- 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, 10 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1274) Not able to query FacesMessages to determine if any messages have been added.

by Nathaniel Stoddard (JIRA)

Not able to query FacesMessages to determine if any messages have been added. ----------------------------------------------------------------------------- Key: JBSEAM-1274 URL: http://jira.jboss.com/jira/browse/JBSEAM-1274 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Reporter: Nathaniel Stoddard It would be helpful to determine if messages have been added to FacesMessages. At this point, it is impossible to determine if messages are present in FacesMessages. -- 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, 10 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-715) Allow multiple pages.xml files

by Stephan Bublava (JIRA)

Allow multiple pages.xml files ------------------------------ Key: JBSEAM-715 URL: http://jira.jboss.com/jira/browse/JBSEAM-715 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.1.1.GA Reporter: Stephan Bublava Currently it's possible to use one global pages.xml file or one file per page. I believe that both options are not well-suited for large applications. Consider an application like: /catalog/foo.xhtml /bar.xhtml /... /basket/foo.xhtml /bar.xhtml /... /admin/foo.xhtml /bar.xhtml /... In this case using a global file would be too convoluted, but at the same time one file per page is too fine grained. It would be great to allow one file per directory ("module"), either using a similar naming convention to page.xml or by adding an "import" tag to pages.xml. -- 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, 10 months

9
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-863) Remember-Me automatic authentication

by H T (JIRA)

Remember-Me automatic authentication ------------------------------------ Key: JBSEAM-863 URL: http://jira.jboss.com/jira/browse/JBSEAM-863 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: H T Fix For: 1.1.7.GA Extend the behaviour of Remember-Me to automatically authenticate the user after they have selected the "Remember Me" service rather than have him or her re-enter their password each time. -- 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, 10 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1491) Seam-managed persistence contexts and REQUIRES_NEW

by Gavin King (JIRA)

Seam-managed persistence contexts and REQUIRES_NEW -------------------------------------------------- Key: JBSEAM-1491 URL: http://jira.jboss.com/jira/browse/JBSEAM-1491 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.GA It's always wrong to try and propagate a PC across REQUIRES_NEW. But indeed that is exactly what Seam does with conversation scoped PCs. Of course, the correct thing to do is use @PersistenceContext in this case. But how many users know they are supposed to do this? Is there some way we can *detect* this problem? We should at the very least document it... -- 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, 10 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1289) Conversation Propagation andTrinidad Dialogs

by Brian Smith (JIRA)

Conversation Propagation andTrinidad Dialogs -------------------------------------------- Key: JBSEAM-1289 URL: http://jira.jboss.com/jira/browse/JBSEAM-1289 Project: JBoss Seam Issue Type: Feature Request Environment: JBoss 4.0.4GA Reporter: Brian Smith Seam does not automatically support Trinidad's dialog feature in terms of propagating long running conversations to the dialog window. Forum User dajevtic has provided a custom phase listener and action listener to enable propagation but it requires a specific naming convention for the dialog page. It would be nice to enable support directly using standard Seam notation like the s:conversationPropagation tag or @Begin(join = true) Here are the relevant phase listener and action listener *Phase Listener* private static final String CONVERSATION_ID_SESSION_PARAMETER = "conversationId"; private Map createParameterMapForConversationRestore(String conversationId) { Map paramterMap = new Hashtable(); paramterMap.put(CONVERSATION_ID_SESSION_PARAMETER, conversationId); return paramterMap; } private void restoreConversation(Context context) { if (context.isSet(CONVERSATION_ID_SESSION_PARAMETER)) { String convId = context.get(CONVERSATION_ID_SESSION_PARAMETER).toString(); Manager.instance().restoreConversation(createParameterMapForConversationRestore(convId)); context.remove(CONVERSATION_ID_SESSION_PARAMETER); } } public void afterPhase(PhaseEvent event) { try { if (event.getPhaseId().equals(PhaseId.RESTORE_VIEW)) { UIViewRoot root = event.getFacesContext().getViewRoot(); if (root != null) { String viewId = root.getViewId(); if ((viewId != null) && viewId.endsWith("_dlg.jspx")) { restoreConversation(Contexts.getSessionContext()); } } } else { log.info("after " + event.getPhaseId()); } } catch (Exception e) { log.error("Could not restore Seam conversation", e); } } *Action Listener* public void processAction(ActionEvent actionEvent) throws AbortProcessingException { if (actionEvent.getComponent() instanceof CoreCommandLink) { CoreCommandLink link = (CoreCommandLink)actionEvent.getComponent(); if (link.isUseWindow()) { Contexts.getSessionContext().set("conversationId", Manager.instance().getCurrentConversationId()); } } super.processAction(actionEvent); } -- 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, 10 months

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1643) Complain when user tries to define the same view-id twice in pages.xml

by Matt Drees (JIRA)

Complain when user tries to define the same view-id twice in pages.xml ---------------------------------------------------------------------- Key: JBSEAM-1643 URL: http://jira.jboss.com/jira/browse/JBSEAM-1643 Project: JBoss Seam Issue Type: Feature Request Reporter: Matt Drees Priority: Minor Fix For: 2.0.0.CR1 If you define two page elements with the same view-id in pages.xml, Seam doesn't complain at all. This can be confusing. -- 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, 10 months

6
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1266) Mathematical captcha & Email obfuscator

by Stephan Kleine (JIRA)

Mathematical captcha & Email obfuscator --------------------------------------- Key: JBSEAM-1266 URL: http://jira.jboss.com/jira/browse/JBSEAM-1266 Project: JBoss Seam Issue Type: Patch Affects Versions: 1.3.0.BETA1 Environment: Tested with Seam CVS on JBoss AS 4.2.0CR2 Reporter: Stephan Kleine Hello, I would like to donate some stuff to seam: 1. A component that converts strings into (hexa)decimal html entities. 2. A tag to use this obfuscator (mainly a shortcut for h:outputText escape="false" ...). 3. A mathematical captcha that asks for the solutions of simple equations (like they use at jroller). The equation can be obuscated with the tag described at 2.. 4. A tag to obfuscate email addresses (see [url]http://www.seowebsitepromotion.com/obfuscate_email.asp[/url] for more details). Would be great if you include it in 1.3 ;) Regards Stephan -- 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, 10 months

4
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1531) Document pages.xsd and maybe other .xsds with xsd:documentation

by Michael Youngstrom (JIRA)

Document pages.xsd and maybe other .xsds with xsd:documentation --------------------------------------------------------------- Key: JBSEAM-1531 URL: http://jira.jboss.com/jira/browse/JBSEAM-1531 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.3.0.ALPHA Reporter: Michael Youngstrom The pages.xsd is fairly vast. It could benefit greatly by some <xsd:documentation> elements. XML editors such as Eclipse WTP will pick up these xsd:documentation elements and provide context help. -- 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, 11 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1165) RGB color support for pdf

by Dustin Norlander (JIRA)

RGB color support for pdf ------------------------- Key: JBSEAM-1165 URL: http://jira.jboss.com/jira/browse/JBSEAM-1165 Project: JBoss Seam Issue Type: Feature Request Components: PDF Reporter: Dustin Norlander Support colors of the form: rgb(255,0,0) or rgb(100%, 0%, 0%) -- 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, 11 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2007