May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1357) Allow to set NamingStrategy in HibernateFactory (patch included)

by Przemyslaw Jaskierski (JIRA)

Allow to set NamingStrategy in HibernateFactory (patch included) ---------------------------------------------------------------- Key: JBSEAM-1357 URL: http://jira.jboss.com/jira/browse/JBSEAM-1357 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Environment: Microcontainer Reporter: Przemyslaw Jaskierski Fix For: 1.3.0.ALPHA Attachments: HibernateFactory.diff.zip I cannot find any way to set my non-default NamingStrategy using microcontainer-instantiated HibernateFactory. My complex mapping cannot be instantiated. Following patch makes this possible. After applying, user can setup NamingStrategy using something like: <bean name="complexNamingStrategy"class="x.y.z.ComplexNamingStrategy"/> <bean name="hibernateSessionFactoryFactory" class="org.jboss.seam.microcontainer.HibernateFactory"> <property name="cfgResourceName">conf/hibernate/hibernate.cfg.xml</property> <property name="namingStrategy"> <inject bean="complexNamingStrategy"/> </property> </bean> -- 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, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1142) Improve Seam deployment/scanning speed

by Mike Quilleash (JIRA)

Improve Seam deployment/scanning speed -------------------------------------- Key: JBSEAM-1142 URL: http://jira.jboss.com/jira/browse/JBSEAM-1142 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Currently the Seam component scanning takes prohibitively long in development when scanning a large project. My project has several thousand java files of which <1% are Seam components. For a Tomcat deployment changing from explicitly specifying the components to using the Seam scanning increases the startup time from 25 seconds to 50 seconds. Most of the 25 seconds is building a hibernate session factory. A possible enhancement would be to allow restriction of the packages that will be scanned via something in the components.xml. e.g. <scanning-config> <include-package name="com.xxx.web.seam.component"/> </scanning-config> Without this present behaviour is default. With it, it will only scan specified packages. Current workaround would be to package into separate jars but that's not always possible esp in development. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1372) Previous conversation never ends when new one begins in the same request cycle

by Dan Allen (JIRA)

Previous conversation never ends when new one begins in the same request cycle ------------------------------------------------------------------------------ Key: JBSEAM-1372 URL: http://jira.jboss.com/jira/browse/JBSEAM-1372 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Ubuntu Linux 7.04 Maven2+Jetty6 Reporter: Dan Allen If you navigate using the s:link tag with propagation="end" OR invoke an action that is marked with the @End annotation (without beforeRedirect) AND THEN render a page which starts a new conversation (either via a factory or a page action), the previous conversation gets recycled. I would expect that conversation id would increment by 1 and the old conversation would be garbage collected. However, this is not the case, and the two conversations merge. Scenario: Create a page that begins a conversation In that page, include a link that ends the conversation and renders the next page: <s:link action="#{myAction.endAndGotoNext}" /> where @End MyAction#endAndGotoNext() In the next page that is rendered begin a conversation (either via a factory or a page action) Now use /debug.seam page to see that the conversation id is never killed from the first 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

18 years, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1381) jBPM SchedulerService based dispatcher

by Gavin King (JIRA)

jBPM SchedulerService based dispatcher -------------------------------------- Key: JBSEAM-1381 URL: http://jira.jboss.com/jira/browse/JBSEAM-1381 Project: JBoss Seam Issue Type: Feature Request Components: Async, BPM Reporter: Gavin King A jBPM-based dispatcher would be great, since jBPM can understand business calendars. -- 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, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1378) Dispatcher based on java.util.Timer

by Gavin King (JIRA)

Dispatcher based on java.util.Timer ----------------------------------- Key: JBSEAM-1378 URL: http://jira.jboss.com/jira/browse/JBSEAM-1378 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Optional java.util.Timer is nice 'cos it has a similar API to the EJB Timer service, so we can reuse the annotations. -- 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, 10 months

1
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1380) JMS Dispatcher

by Gavin King (JIRA)

JMS Dispatcher -------------- Key: JBSEAM-1380 URL: http://jira.jboss.com/jira/browse/JBSEAM-1380 Project: JBoss Seam Issue Type: Feature Request Components: Async Reporter: Gavin King JMS has advantages in terms of well-defined QoS. Otherwise it is semantically similar to ThreadPoolDispatcher. -- 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, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1379) Configurable ThreadPoolDispatcher

by Gavin King (JIRA)

Configurable ThreadPoolDispatcher --------------------------------- Key: JBSEAM-1379 URL: http://jira.jboss.com/jira/browse/JBSEAM-1379 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Minor ThreadPoolExecutor has many optional configs. These should be exposed as properties and on <core:thread-pool-dispatcher/>. -- 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, 10 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-395) Alternate "dispatcher" strategies

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-395?page=all ] Gavin King closed JBSEAM-395. ----------------------------- Resolution: Done It is now possible to "globally" install a new dispatcher strategy. The existing implementations are TimerServiceDispatcher and ThreadPoolDispatcher. Someone can write a QuartzDispatcher and JMSDispatcher. > Alternate "dispatcher" strategies > --------------------------------- > > Key: JBSEAM-395 > URL: http://jira.jboss.com/jira/browse/JBSEAM-395 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.3.0.ALPHA > > > Currently, dispatch of asynchronous calls and events is done via the timer service. There are really good reasons to support other dispatching strategies such as quartz, jBPM, etc. This can be done simply by supporting @Asynchronous(dispatcher="#{name}"). -- 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, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1218) Make LocalDispatcher not dependent on javax.ejb.Timer

by Michael Youngstrom (JIRA)

Make LocalDispatcher not dependent on javax.ejb.Timer ----------------------------------------------------- Key: JBSEAM-1218 URL: http://jira.jboss.com/jira/browse/JBSEAM-1218 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Michael Youngstrom Priority: Minor Fix For: 1.3.0.BETA1 I'm attempting to create a port of the @Asynchronous annotation for Spring. (JBSEAM-1217) It would appear the correct way to do this would be to create a Spring Dispatcher component that would override the core Dispatcher component. However, the LocalDispatcher Interface is dependent on javax.ejb.Timer I can probably wrap my spring dispatch implementation into the javax.ejb.Timer but it would be nice if a seam version of javax.ejb.Timer were created so that the j2ee.jar would not be required for users who wish to use @Asynchronous under a web container. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-197) Order task list by priority

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-197?page=all ] Gavin King closed JBSEAM-197. ----------------------------- Resolution: Done Added taskInstancePriorityList. > Order task list by priority > --------------------------- > > Key: JBSEAM-197 > URL: http://jira.jboss.com/jira/browse/JBSEAM-197 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > Fix For: 1.3.0.ALPHA > > > Should make it possible to sort the tasks in the task list by priority. -- 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, 10 months

1
0
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 May 2007