August 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1768) <s:selectItems> enhancement to allow for non-ID field when used with <s:convertEntity/>

by Nicklas Karlsson (JIRA)

<s:selectItems> enhancement to allow for non-ID field when used with <s:convertEntity/> --------------------------------------------------------------------------------------- Key: JBSEAM-1768 URL: http://jira.jboss.com/jira/browse/JBSEAM-1768 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Nicklas Karlsson Priority: Optional When using an entity like @Entity public class Person { @Id private Integer id; private String firstName; private String lastName; private String personnelCode; ... } It would be handy if it could be possible to use <h:selectOneMenu value="#{project.managerCode}"> <s:selectItems value="#{bean.managerList}" var="manager" label="#{manager.lastName}, #{manager.firstName}" insertValue="#{manage.personnelCode}"/> <s:convertEntity /> </h:selectOneMenu> e.g. being able to choose which field (in this case the manager personnel code) would be selected (instead of the entity ID) -- 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

18 years, 3 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1823) Document conversation-required parameter for the page tag

by Przemyslaw Jaskierski (JIRA)

Document conversation-required parameter for the page tag ---------------------------------------------------------- Key: JBSEAM-1823 URL: http://jira.jboss.com/jira/browse/JBSEAM-1823 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.0.BETA1 Reporter: Przemyslaw Jaskierski Priority: Minor Fix For: 2.0.0.GA Reporting as requested by Pete. @See forum thread... -- 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

18 years, 3 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1552) Rich text support

by Chunyun Zhao (JIRA)

Rich text support ----------------- Key: JBSEAM-1552 URL: http://jira.jboss.com/jira/browse/JBSEAM-1552 Project: JBoss Seam Issue Type: Feature Request Reporter: Chunyun Zhao Web applications often use rich text editors such as TinyMCE to allow the user to enter rich text and store the content as html snippets. Currently seam pdf component doesn't have a component to renders html snippets. -- 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

18 years, 4 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1781) Add support for Spring @Component and @Repository annotations

by Michael Youngstrom (JIRA)

Add support for Spring @Component and @Repository annotations ------------------------------------------------------------- Key: JBSEAM-1781 URL: http://jira.jboss.com/jira/browse/JBSEAM-1781 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 2.0.0.BETA1 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.0.1.GA Once Spring 2.1 is released it might be nice to add support for the spring annotations doing something like: @org.springframework.stereotype.Component @Name("someName") public class SomeComponent { .... } Which would make a standard installed Seam component spring instantiated allowing for creation time injection using spring injection annotations, SpringAOP/aspectj support to Seam components, etc. As well as provide a bunch of Seam features to spring beans, @Synchronized, @Asynchronous, bijection, etc. Basically would provide the same functionality that currently exists with <seam:component/> but with an easier to use annotation and with correct Seam @Install semantics. -- 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

18 years, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-492) NPE in ParamMethodExpression

by Stas Garifulin (JIRA)

NPE in ParamMethodExpression ---------------------------- Key: JBSEAM-492 URL: http://jira.jboss.com/jira/browse/JBSEAM-492 Project: JBoss Seam Issue Type: Bug Environment: jboss seam cvs head jsf-ri 1.2.03 facelets 1.1.11 Reporter: Stas Garifulin Forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985161#3985161 -- 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

18 years, 4 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1541) BPM enhancements for WS/mail

by Gavin King (JIRA)

BPM enhancements for WS/mail ---------------------------- Key: JBSEAM-1541 URL: http://jira.jboss.com/jira/browse/JBSEAM-1541 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Fix For: 1.3.0.GA A couple of things that would make using jBPM with services much nicer: * possibility to map conversation id == process id and have a co-extensive conversation and process scope * auto-end conversation when the current process completes Perhaps its better to model this as a persistent SERVICE_CONVERSATION context, as suggested in another JIRA issue -- 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

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-971) Conversations with business ids

by Gavin King (JIRA)

Conversations with business ids ------------------------------- Key: JBSEAM-971 URL: http://jira.jboss.com/jira/browse/JBSEAM-971 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Shane Bryzak Priority: Critical By defining a <conversation/> in pages.xml, pages can have the conversation propagated via a meaningful (restful) request parameter. By the way, we can make conversationIsLongRunning stuff disabled by default, unless its name is explicitly defined in components.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

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1873) Change

by Felix Ho?feld (JIRA)

Change ------- Key: JBSEAM-1873 URL: http://jira.jboss.com/jira/browse/JBSEAM-1873 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 2.0.0.BETA1 Environment: Seam 2.0.0.Beta1 Reporter: Felix Ho?feld The documentation (--> 25.2.1. Packaging) still recommends including jboss-el-api.jar into the application. However, including jboss-el-api into your ear and deploying to JBoss 4.2 with an insolated class loader will cause the application server to hang during the deployment since jboss-el-api.jar is already available from the server's lib directory. I have not yet tried using <loader-repository-config> java2ParentDelegation=false </loader-repository-config> in such a configuration. -- 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

18 years, 4 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1880) Hibernate validator does not use the seam locale

by Franck MARTIN (JIRA)

Hibernate validator does not use the seam locale ------------------------------------------------ Key: JBSEAM-1880 URL: http://jira.jboss.com/jira/browse/JBSEAM-1880 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Franck MARTIN Using Seam2 (CVS.2007-08-21) When i use the built-in Seam component localeSelector to change the user locale, hibernate validator continues to use the locale defined in the browser settings (accept-language http header) rather than the seam locale for the error messages. -- 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

18 years, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1866) Seam 2Beta - Examples - Todo Example - button attribute

by Tomas (JIRA)

Seam 2Beta - Examples - Todo Example - button attribute ------------------------------------------------------- Key: JBSEAM-1866 URL: http://jira.jboss.com/jira/browse/JBSEAM-1866 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.0.BETA1 Environment: Ubuntu Linux, JBoss AS 4.2.1 Reporter: Tomas Priority: Trivial Fix For: 2.0.0.GA I was browsing Seam 2 examples and the third one had minor problem it is in JSP so it took longer time :) To finish task is in documentation ---------------------------------------------------- <h:column> <s:button value="Done" action="#{todoList.done}" taskInstance="#{task}"/> </h:column> ---------------------------------------------------- but server cried. this works ---------------------------------------------------- <s:button action="#{todoList.done}" value="Done"> <s:taskId name="taskInstance" value="#{task}"></s:taskId> </s:button> ---------------------------------------------------- Hopefully will help How should I put it into JIRA system I was looking for duplicity but I did not find it? Tomas -- 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

18 years, 4 months

2
3
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 August 2007