October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-374) Normalize the event model

by Gavin King (JIRA)

Normalize the event model ------------------------- Key: JBSEAM-374 URL: http://jira.jboss.com/jira/browse/JBSEAM-374 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 Currently some events can be handled by either an @Observer method, or a method binding in events.xml. Ideally we would like this to be true for ALL events, but for now our integration with JSF and jBPM is not quite that deep. Nevertheless, there are some things we could do to allow a more consistent model where everything can be handled by either a method binding or an annotated method: (1) Rebuild the page actions functionality on top of the Seam event bus - defining standard org.jboss.seam.page.<viewId> events that can be handled via @Observer("org.jboss.seam.page./myViewId.xhtml") (2) Introduce "outcome observers" for JSF: if I have <h:commandButton action="myOutcome"/>, allow us to handle it using @Observer("org.jboss.seam.outcome.myOutcome") (3) Ditto for jBPM: if I have <transition name="myTransition" ... />, allow us to handle it using @Observer("org.jboss.seam.transition.myTransition") (4) Finally, introduce annotations layered over @Observer: @RenderPage("/myViewId.xhtml"), @Outcome("myOutcome"), @Transition("myTransition") -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-395) Alternate "dispatcher" strategies

by Gavin King (JIRA)

Alternate "dispatcher" strategies --------------------------------- Key: JBSEAM-395 URL: http://jira.jboss.com/jira/browse/JBSEAM-395 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-419) @ReadOnly annotation

by Gavin King (JIRA)

@ReadOnly annotation -------------------- Key: JBSEAM-419 URL: http://jira.jboss.com/jira/browse/JBSEAM-419 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 optimize replication stuff for immutable objects / readonly methods. At class level: mark bean as not needing replication At method level: mark method as not changing state -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-420) Propagate business process context to MDB components

by Gavin King (JIRA)

Propagate business process context to MDB components ---------------------------------------------------- Key: JBSEAM-420 URL: http://jira.jboss.com/jira/browse/JBSEAM-420 Project: JBoss Seam Issue Type: Feature Request Components: EJB3 Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1 We might even be able to make this transparent..... -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-414) "Reduce" dependency to EJB3 classes

by Gavin King (JIRA)

"Reduce" dependency to EJB3 classes ----------------------------------- Key: JBSEAM-414 URL: http://jira.jboss.com/jira/browse/JBSEAM-414 Project: JBoss Seam Issue Type: Feature Request Reporter: Gavin King Assigned To: Gavin King Priority: Blocker Fix For: 1.1 People who want to run Seam in J2EE containers will run into problems because Seam has a hard dependency to EJB 3.0 versions of the EJB interfaces. We need to make the Seam/Hibernate stack run without any dependency to the EJB3 jars. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-413) Support <foo>value</foo> as well as <property name="foo">value</property> in components.xml

by Gavin King (JIRA)

Support <foo>value</foo> as well as <property name="foo">value</property> in components.xml ------------------------------------------------------------------------------------------- Key: JBSEAM-413 URL: http://jira.jboss.com/jira/browse/JBSEAM-413 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-412) EJB 2 integration

by Gavin King (JIRA)

EJB 2 integration ----------------- Key: JBSEAM-412 URL: http://jira.jboss.com/jira/browse/JBSEAM-412 Project: JBoss Seam Issue Type: Feature Request Components: EJB3 Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 At least let EJB2 session beans be discovered and injected. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-408) actionListener="#foo, bar}" where bar() has no ActionEvent parameter

by Gavin King (JIRA)

actionListener="#foo,bar}" where bar() has no ActionEvent parameter ------------------------------------------------------------------- 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 Reporter: Gavin King Assigned To: Gavin King Priority: Minor Fix For: 1.1 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-401) Contexts.destroy(BusinessProcessContext) hits the database after the seam managed transaction ends

by Gavin King (JIRA)

Contexts.destroy(BusinessProcessContext) hits the database after the seam managed transaction ends -------------------------------------------------------------------------------------------------- Key: JBSEAM-401 URL: http://jira.jboss.com/jira/browse/JBSEAM-401 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1 Reporter: Gavin King Assigned To: Gavin King Priority: Blocker Fix For: 1.1 -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-421) Update to Seam i18n to support DatabaseResourceBundle

by Todd Smart (JIRA)

Update to Seam i18n to support DatabaseResourceBundle ----------------------------------------------------- Key: JBSEAM-421 URL: http://jira.jboss.com/jira/browse/JBSEAM-421 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1 Reporter: Todd Smart Fix For: 1.1 The current Seam i18n ResourceBundle class only supports loading java.util.ResourceBundle resource bundles. For ref, the loadBundle() method is: {code} private void loadBundle() { try { bundle = java.util.ResourceBundle.getBundle( bundleName, Locale.instance(), Thread.currentThread().getContextClassLoader() ); log.debug("loaded resource bundle: " + bundleName); } catch (MissingResourceException mre) { log.debug("resource bundle missing: " + bundleName); } } {code} I've updated the org.seam.core.ResourceBundle class to plug into the org.sadun.util.DatabaseResourceBundle ... providing for a very flexible, db-driven i18n system. The only change required (for the prototype code!) to get this to work was an update to the Seam ResourceBundle was: {code} private void loadBundle() { try { DatabaseResourceBundle databaseResourceBundle = new DatabaseResourceBundle(jdbcUrl, bundleName, Locale.instance()); bundle = databaseResourceBundle; log.debug("loaded resource bundle: " + bundleName); } catch (MissingResourceException mre) { log.debug("resource bundle missing: " + bundleName); } } {code} Beyond the prototype, of course, this will be cleaned up. I'm thinking others may benefit from updating this Seam class to allow for supporting other types of resource bundle repositories. Feature Request: ------------------------ 1) Add an attribute to ResourceBundle called: resourceType (thus allowing a class to be called to load a bundle). This attribute would be configured in seam.properties. 2) Update the loadBundle() method such that if resourceType is not null, to get an instance of ResourceType.instance() followed by a call to resourceType.loadBundle() method I don't mind contributing the code ... just testing the waters first. Regards, Todd Smart todd.smart(a)smartbinary.com -- 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, 2 months

2
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006