February 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-673) @Observer doesn't work in components that use @Unwrap

by Stephan Bublava (JIRA)

@Observer doesn't work in components that use @Unwrap ----------------------------------------------------- Key: JBSEAM-673 URL: http://jira.jboss.com/jira/browse/JBSEAM-673 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.1.GA Reporter: Stephan Bublava If a component uses @Unwrap and @Observer at the same time, Events.instance().raiseEvent() attempts to invoke the observer method on the unwrapped object, which usually causes a NoSuchMethodException exception. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-915) Split remoting stuff into jboss-seam-remoting.jar

by Gavin King (JIRA)

Split remoting stuff into jboss-seam-remoting.jar ------------------------------------------------- Key: JBSEAM-915 URL: http://jira.jboss.com/jira/browse/JBSEAM-915 Project: JBoss Seam Issue Type: Task Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.1.8.GA Remoting is certainly an optional part of Seam, and manypeople aren't using it. It belongs in its own src tree and jar. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-946) Hibernate (sessions) persistance do not work anymore

by Carsten H?hne (JIRA)

Hibernate (sessions) persistance do not work anymore ---------------------------------------------------- Key: JBSEAM-946 URL: http://jira.jboss.com/jira/browse/JBSEAM-946 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.0.GA, 1.1.7.CR1 Reporter: Carsten H?hne I had realized that all my DAOs do not work anymore. At best i get a java.lang.ClassCastException: org.jboss.seam.Model With 1.1.6 my app works. with 1.1.7RC1 and 1.2.0GA it stops working:-( Only HibernateEntitys are working correctly and the retrival of objects by id. Querys do not work. Sorry i am not able to hunt this error down, but there is perhaps a chance that it correlate with the changes made in org.jboss.seam persistance, which are introduced with seam1.1.7RC1 -- 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-936) Wanted detail documentaition of using Seam with cache.

by Jie Situ (JIRA)

Wanted detail documentaition of using Seam with cache. ------------------------------------------------------ Key: JBSEAM-936 URL: http://jira.jboss.com/jira/browse/JBSEAM-936 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.1.7.CR1 Reporter: Jie Situ Priority: Minor Generally reading the documentation, I found little information of using Seam with cache. I'm confused about it. And I want more information of 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

19 years, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-945) Support descriptions of fake pages for conversation switching

by Christian Bauer (JIRA)

Support descriptions of fake pages for conversation switching ------------------------------------------------------------- Key: JBSEAM-945 URL: http://jira.jboss.com/jira/browse/JBSEAM-945 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Minor <page view-id="/user/register.xhtml" action="render"> <description>Registration</description> <navigation><render view-id="/userAccount.xhtml"/></navigation> </page> <page view-id="/user/account/edit.xhtml" action="render"> <description>Managing user account '#{userHome.instance.username}'</description> <navigation><render view-id="/userAccount.xhtml"/></navigation> </page> <page view-id="/user/list.xhtml" action="render"> <description>Searching Members (Results: #{userSearch.rowCount})</description> <navigation><render view-id="/userList.xhtml"/></navigation> </page> These fake pages (REST! Hurray!) are not shown in the conversation switcher because the underlying _real_ pages are rendered - and they don't have a description. In fact, besides REST, the whole point of having these fake view-ids is to declare alternating descriptions for the same rendered real 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

19 years, 1 month

1
0
0 / 0

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

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=comments#action_12354403 ] Gavin King commented on JBSEAM-274: ----------------------------------- I don't mean reinvent it, I mean integrate it with pages.xml, or perhaps some other kind of sugar. It might not be worth it, but its worth looking into. > 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.2.1.GA > > > 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] Commented: (JBSEAM-274) More flexible mapping of URLs to view ids

by Christian Bauer (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=comments#action_12354402 ] Christian Bauer commented on JBSEAM-274: ---------------------------------------- I don't think we need to reinvent everything. The URLRewrite thing is cool and works nicely. One config file, one JAR. We could submit a patch to this project to allow configuration through some other mechanism, I think he hardcoded the config file. > 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.2.1.GA > > > 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-929) consistent component naming / remove unused files from CVS

by Guy Veraghtert (JIRA)

consistent component naming / remove unused files from CVS ---------------------------------------------------------- Key: JBSEAM-929 URL: http://jira.jboss.com/jira/browse/JBSEAM-929 Project: JBoss Seam Issue Type: Task Components: JSF Affects Versions: 1.1.7.CR1 Reporter: Guy Veraghtert 1) All seam JSF component names start with UI (e.g. UIDecorate, UICache, ...), except for SelectDate and FileUpload. 2) As far as I can see org/jboss/seam/ui/selectDate.js isn't used anymore. It is replaced by org/jboss/seam/ui/resource/date/calendar.js. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-887) Replicate booking demo fixes to all versions of the demo

by Gavin King (JIRA)

Replicate booking demo fixes to all versions of the demo -------------------------------------------------------- Key: JBSEAM-887 URL: http://jira.jboss.com/jira/browse/JBSEAM-887 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 1.1.7.GA Reporter: Gavin King Assigned To: Gavin King Priority: Blocker Fix For: 1.1.7.GA Attachments: ajax4jsf-patch.diff A couple of patches that need to be replicated. -- 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
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-776) Add more information to the exception thrown when a conversation is started illegally

by Mike Quilleash (JIRA)

Add more information to the exception thrown when a conversation is started illegally ------------------------------------------------------------------------------------- Key: JBSEAM-776 URL: http://jira.jboss.com/jira/browse/JBSEAM-776 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.0.GA Environment: Any Reporter: Mike Quilleash Would be useful for debugging if the ConversationInterceptor.endOrBeginLongRunningConversation() could add more information (such as target method and object type) to the IllegalStateException thrown when a @Begin is encountered with a LRC in progress and nested/join is not set to true. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2007