January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-119) @CancelTask

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-119?page=comments#action_12396908 ] Pete Muir commented on JBSEAM-119: ---------------------------------- It would mean that a task is to be cancelled. But I have no idea exactly what semantics Gavin wanted for it. > @CancelTask > ----------- > > Key: JBSEAM-119 > URL: http://jira.jboss.com/jira/browse/JBSEAM-119 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > > I am still arguing with Tom about whether @CancelTask is needed but I think it is. -- 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, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-119) @CancelTask

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-119?page=all ] Pete Muir reassigned JBSEAM-119: -------------------------------- Assignee: (was: Gavin King) > @CancelTask > ----------- > > Key: JBSEAM-119 > URL: http://jira.jboss.com/jira/browse/JBSEAM-119 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > > I am still arguing with Tom about whether @CancelTask is needed but I think it is. -- 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, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-100) Unify datasource configuration factory with E-EJB3

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-100?page=all ] Pete Muir closed JBSEAM-100. ---------------------------- Resolution: Out of Date E-EJB3 and microcontainer integration is gone from Seam. > Unify datasource configuration factory with E-EJB3 > -------------------------------------------------- > > Key: JBSEAM-100 > URL: http://jira.jboss.com/jira/browse/JBSEAM-100 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Christian Bauer > Priority: Trivial > Attachments: JBSEAM-100.zip > > > The org.jboss.resource.adapter.jdbc.local.LocalTxDataSource does the same as org.jboss.seam.microcontainer.DataSourceFactory - they are slightly different in configuration only. > For example: > - connectionUrl vs. connectionURL > - getDatasource vs. getDataSource > - etc. > One internal difference is the CachedConnectionManager. It is injected into the LocalTxDataSource, but instantiated in the seam.microcontainer.DataSourceFactory. > I think we should either unify, or better, kick out one of those two. -- 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, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2536) Complete Annotations for use with Seam JavaBean components in a J2EE environment section

by Pete Muir (JIRA)

Complete Annotations for use with Seam JavaBean components in a J2EE environment section ---------------------------------------------------------------------------------------- Key: JBSEAM-2536 URL: http://jira.jboss.com/jira/browse/JBSEAM-2536 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.1.CR2 Reporter: Pete Muir Fix For: 2.0.1.GA, 2.1.0.GA Some TBDs here! -- 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, 11 months

1
1
0 / 0

[jbossseam-issues] Seam conversation + AJAX

by François Terrier

Hello everyone, I need to regularly poll the progress of a really long operation (getting data from a web service) running in a conversation bean. I do that with Seam Remoting using a @WebRemote annotated method in the conversation bean. Everything works flawlessly, except that when my remote call tries to access the conversation bean, it can't because the thread running my long operation already holds the bean. The result is that Seam creates a new conversation bean for my remote call, causing my Remote call to return incorrect data. Has anyone had this problem before ? I am ready to provide more information if needed. Francois

16 years, 11 months

1
0
0 / 0

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

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=all ] Pete Muir reassigned JBSEAM-274: -------------------------------- Assignee: Norman Richards (was: Pete Muir) > 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: Norman Richards > Fix For: 2.0.2.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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1342) Generic Scanner usability

by Frank Cornelis (JIRA)

Generic Scanner usability ------------------------- Key: JBSEAM-1342 URL: http://jira.jboss.com/jira/browse/JBSEAM-1342 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Frank Cornelis In our project we would like to use the JBoss Seam Scanner class to browse over our EJB classes in search for our custom @Config annotations (see http://cup-of-java.blogspot.com/). Unfortunately the handleItem method on the Scanner class is only package visible. This prevents generic reusability of this really powerful Scanner class. Could you guys make the handleItem method public? Thanks, Frank. -- 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, 11 months

7
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2533) Invalid security message keys in documentation

by Nicklas Karlsson (JIRA)

Invalid security message keys in documentation ---------------------------------------------- Key: JBSEAM-2533 URL: http://jira.jboss.com/jira/browse/JBSEAM-2533 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 2.0.1.CR2 Reporter: Nicklas Karlsson Fix For: 2.01.GA Table 13.1 in section 13.5 lists message keys org.jboss.seam.security.loginSuccessful org.jboss.seam.security.loginFailed org.jboss.seam.security.NotLoggedIn but seam-gen generated messages_en.properties lists org.jboss.seam.loginFailed org.jboss.seam.loginSuccessfu org.jboss.seam.NotLoggedIn -- 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, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2468) Remove deprecated methods from SeamTest and BaseSeamTest

by Pete Muir (JIRA)

Remove deprecated methods from SeamTest and BaseSeamTest -------------------------------------------------------- Key: JBSEAM-2468 URL: http://jira.jboss.com/jira/browse/JBSEAM-2468 Project: JBoss Seam Issue Type: Task Components: Test Harness Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Priority: Minor Fix For: 2.1.0.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, 11 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1779) Skip duplicated call of SeamTest.init() in the same suite

by Dmitriy Lapko (JIRA)

Skip duplicated call of SeamTest.init() in the same suite --------------------------------------------------------- Key: JBSEAM-1779 URL: http://jira.jboss.com/jira/browse/JBSEAM-1779 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Affects Versions: 2.0.0.BETA1 Reporter: Dmitriy Lapko For optimization purposes to achieve faster tests it may be good solution to skip new initialization of Seam Framework before each class, so to go the same way as with JbossEmbedded - use something like startJbossSeamIfNecessary(); , because seam initialization sometimes tooks more then 50% of total time of the whole test suite. -- 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, 11 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008