March 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-988) upgrade to itext 2.0

by Norman Richards (JIRA)

upgrade to itext 2.0 -------------------- Key: JBSEAM-988 URL: http://jira.jboss.com/jira/browse/JBSEAM-988 Project: JBoss Seam Issue Type: Task Reporter: Norman Richards In addition to bugfixes, there have been a few API changes made especially for Seam. -- 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

19 years, 1 month

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-822) XSDs should not have jndi-name for components which are not session beans

by Gavin King (JIRA)

XSDs should not have jndi-name for components which are not session beans ------------------------------------------------------------------------- Key: JBSEAM-822 URL: http://jira.jboss.com/jira/browse/JBSEAM-822 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Gavin King Fix For: 1.1.7.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

19 years, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-941) Replicate password page fix to all bookingish examples

by Gavin King (JIRA)

Replicate password page fix to all bookingish examples ------------------------------------------------------ Key: JBSEAM-941 URL: http://jira.jboss.com/jira/browse/JBSEAM-941 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.2.0.GA Reporter: Gavin King Priority: Minor Fix For: 1.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

19 years, 1 month

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-144) Display validation messages on components for validation issues on child objects

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-144?page=all ] Gavin King updated JBSEAM-144: ------------------------------ Fix Version/s: 1.3.0.BETA1 (was: 1.2.1.GA) > Display validation messages on components for validation issues on child objects > -------------------------------------------------------------------------------- > > Key: JBSEAM-144 > URL: http://jira.jboss.com/jira/browse/JBSEAM-144 > Project: JBoss Seam > Issue Type: Patch > Components: JSF > Affects Versions: 1.0 beta 2 > Reporter: Andrew > Assigned To: Gavin King > Fix For: 1.3.0.BETA1 > > Attachments: JBSEAM-144.diff > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I have submitted a patch to hibernate-annotations: ANN-208 (http://opensource2.atlassian.com/projects/hibernate/browse/ANN-208) > This patch creates validation issues for child objects. The format is: > mbean.collection[collection-index].childProperty > Example: > user.addresses[1].street > This patch allows the ValidationInterceptor to attempt to find the "street" UIComponent. It does this by using the "dataTable" naming: > addresses:1:street > Which would be produced by: > <t:dataTable var="address" value="#{user.addresses}"> > <t:column> > <t:inputText value="#{addresss.street}" /> > ... -- 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

19 years, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-632) ajax4jsf a:commandLink stops working if page is defined in pages.xml with an action, or if page is opened from s:link

by Dan Liu (JIRA)

ajax4jsf a:commandLink stops working if page is defined in pages.xml with an action, or if page is opened from s:link --------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-632 URL: http://jira.jboss.com/jira/browse/JBSEAM-632 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.1.0.GA Environment: any Reporter: Dan Liu Priority: Critical a4j a:commandLink stops working in following two situations: 1. If the containing page is defined in pages.xml with an action defined, the action method defined in pages.xml is always triggered and a:commandLink specified method is never triggered. 2. If the containing page is bookmarkable and is opened through s:link, the a:commandLink in this page would stop working. -- 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

19 years, 1 month

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-274) More flexible mapping of URLs to view ids

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=all ] Gavin King updated JBSEAM-274: ------------------------------ Fix Version/s: 1.3.0.BETA1 (was: 1.2.1.GA) > More flexible mapping of URLs to view ids > ----------------------------------------- > > Key: JBSEAM-274 > URL: http://jira.jboss.com/jira/browse/JBSEAM-274 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.3.0.BETA1 > > > For example, I want to be able to use a URL like this: > http://mydomain.com/myblog/archive/200306 > To get me to archive.xhtml with a request parameter 200306 (not really a request parameter, but we could try to abstract that so that it can be used with @RequestParameter). > Not sure if this is possible without changing the JSF implementation. -- 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

19 years, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-957) Support transaction interceptor with JavaBeans and custom servlets

by Christian Bauer (JIRA)

Support transaction interceptor with JavaBeans and custom servlets ------------------------------------------------------------------ Key: JBSEAM-957 URL: http://jira.jboss.com/jira/browse/JBSEAM-957 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Minor I'm using <web:context-filter url-pattern="/files/*"/> and a custom FileServlet: This works: @Override protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { String id = request.getParameter("fileId"); NodeDAO nodeDAO = (NodeDAO) org.jboss.seam.Component.getInstance("nodeDAO"); org.jboss.seam.wiki.core.node.File file; UserTransaction userTx = null; try { userTx = Transactions.getUserTransaction(); userTx.begin(); file = (id != null && !"".equals(id)) ? nodeDAO.findFile(Long.getLong(id)) : null; userTx.commit(); } catch (Exception ex) { try { if (userTx != null) userTx.rollback(); } catch (Exception rbEx) { rbEx.printStackTrace(); } throw new RuntimeException(ex); } This doesn't work because no JTA transaction is active when my JavaBean DAO is called (all methods there are annotated @Transactional): @Override protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { String id = request.getParameter("fileId"); NodeDAO nodeDAO = (NodeDAO) org.jboss.seam.Component.getInstance("nodeDAO"); org.jboss.seam.wiki.core.node.File file = (id != null && !"".equals(id)) ? nodeDAO.findFile(Long.getLong(id)) : null; The Seam (seamspace) examples use EJB components, so this probably never came up before. -- 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

19 years, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-408) actionListener="#{foo.bar}" where bar() has no ActionEvent parameter in JSP

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-408?page=all ] Gavin King updated JBSEAM-408: ------------------------------ Summary: actionListener="#{foo.bar}" where bar() has no ActionEvent parameter in JSP (was: actionListener="#{foo.bar}" where bar() has no ActionEvent parameter) Fix Version/s: (was: 1.2.1.GA) > actionListener="#{foo.bar}" where bar() has no ActionEvent parameter in JSP > --------------------------------------------------------------------------- > > Key: JBSEAM-408 > URL: http://jira.jboss.com/jira/browse/JBSEAM-408 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > > I hate the useless ActionEvent polluting my business code. I already fixed this in facelets, need a solution for JSP also. -- 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

19 years, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-913) Nicely handle <s:validate(All)> misuse

by Matt Drees (JIRA)

Nicely handle <s:validate(All)> misuse -------------------------------------- Key: JBSEAM-913 URL: http://jira.jboss.com/jira/browse/JBSEAM-913 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.6.GA Reporter: Matt Drees Priority: Minor Don't blow up with a NPE when <s:validate> or <s:validateAll> is used on a binding when it shouldn't be used; throw a descriptive exception instead. -- 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

19 years, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-924) Upgrade to MyFaces 1.1.5 and test on Tomcat

by Gavin King (JIRA)

Upgrade to MyFaces 1.1.5 and test on Tomcat ------------------------------------------- Key: JBSEAM-924 URL: http://jira.jboss.com/jira/browse/JBSEAM-924 Project: JBoss Seam Issue Type: Task Components: JSF Affects Versions: 1.1.7.CR1, 1.1.6.GA Reporter: Gavin King Assigned To: Norman Richards Fix For: 1.1.7.GA MyFaces did a new release. Norman, will you have time to take care of this one before the 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

19 years, 1 month

1
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 March 2007