April 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMJMS-21) Create a MessageScoped scope.

by John Ament (JIRA)

Create a MessageScoped scope. ----------------------------- Key: SEAMJMS-21 URL: https://issues.jboss.org/browse/SEAMJMS-21 Project: Seam JMS Issue Type: Enhancement Components: Injection Reporter: John Ament Fix For: 3.0.0.Alpha2 Currently, you can't inject HTTP bound scopes into JMS since the message listeners (MDBs or other MessageListener impls) are run in background threads. We need to introduce a MessageScoped scope that can bind to these background threads, so that shared objects can fall into the same scope, and be bound together. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMJMS-9) Support dynamic connection factories using solder's generic beans

by John Ament (JIRA)

Support dynamic connection factories using solder's generic beans ----------------------------------------------------------------- Key: SEAMJMS-9 URL: https://issues.jboss.org/browse/SEAMJMS-9 Project: Seam JMS Issue Type: Feature Request Components: Injection Reporter: John Ament In Solder, they now have the concept of generic beans - beans that can be used for configuration. This should fix your overall issue with ConnectionFactory injection. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMJMS-18) Support injecting durable subscribers

by John Ament (JIRA)

Support injecting durable subscribers ------------------------------------- Key: SEAMJMS-18 URL: https://issues.jboss.org/browse/SEAMJMS-18 Project: Seam JMS Issue Type: Feature Request Components: Injection Reporter: John Ament Assignee: John Ament Fix For: 3.0.0.Beta1 Be able to inject durable subscribers, add APIs to the route API to make durable as well. Note: for observer interfaces, it should be enough that resolved destinations are denoted as durable based on however they are produced. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-34) Generation of JavaCC should be automatized

by George Gastaldi (JIRA)

Generation of JavaCC should be automatized ------------------------------------------- Key: SEAMREMOTING-34 URL: https://issues.jboss.org/browse/SEAMREMOTING-34 Project: Seam Remoting Issue Type: Task Reporter: George Gastaldi Priority: Minor Usage of http://mojo.codehaus.org/javacc-maven-plugin/ is a better way to incorporate generation of JavaCC classes in build, so that whenever a change in AnnotationParser.jj file is done, manual recompiling is avoided. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-132) Messages API not working as described in reference docs.

by Murali Mohan Rath (JIRA)

Messages API not working as described in reference docs. -------------------------------------------------------- Key: SEAMFACES-132 URL: https://issues.jboss.org/browse/SEAMFACES-132 Project: Seam Faces Issue Type: Bug Components: Documentation, Messages & i18n Affects Versions: 3.0.0.Final Environment: Win 7, 64 bit , maven 3, jdk6, netbeans 7 b2 Reporter: Murali Mohan Rath Priority: Critical I found the following code in seam faces documentation. @Named public class Example { @Inject Messages messages; public String action() { messages.info("This is an {0} message, and will be displayed to {1}.", "INFO", "the user"); return null; } } My maven pom has a dependency to seam faces 3.0.0.Final. There are no class named Messages in seam-faces and seam-international. Messages class is available in seam 2 but don't have the methods mentioned in the example. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMINTL-39) yoda-time not pulled in

by Nicklas Karlsson (JIRA)

yoda-time not pulled in ----------------------- Key: SEAMINTL-39 URL: https://issues.jboss.org/browse/SEAMINTL-39 Project: Seam International Issue Type: Bug Components: Time zones Affects Versions: 3.0.0.Final Reporter: Nicklas Karlsson Assignee: Ken Finnigan ForwardingDateTimeZone in the api has a dep on yoda-time but it's not pulled in with the pom leading to CNFE for yoda DateTimeZone -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAM-76) Documentation typo in section 7.5

by Beaudoin Gaël (JIRA)

Documentation typo in section 7.5 --------------------------------- Key: SEAM-76 URL: https://issues.jboss.org/browse/SEAM-76 Project: Seam 3 Distribution Issue Type: Bug Components: Common Documentation Affects Versions: 3.0.0.Final Reporter: Beaudoin Gaël Priority: Minor Section 7.5, the sentence "This behavior aligns is with the needs of most application developers." looks buggy :) Link : seam-3.0.0.Final/doc/reference/html_single/index.html#d0e1005 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAM-77) Documentation not complete : chapter 6 introduction

by Beaudoin Gaël (JIRA)

Documentation not complete : chapter 6 introduction --------------------------------------------------- Key: SEAM-77 URL: https://issues.jboss.org/browse/SEAM-77 Project: Seam 3 Distribution Issue Type: Bug Components: Common Documentation Affects Versions: 3.0.0.Final Reporter: Beaudoin Gaël Priority: Minor The paragraph contains 3 ??? placeholders that I guess should have been filled. seam-3.0.0.Final/doc/reference/html_single/index.html#d0e1005 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAM-81) Documentation : property name from weld to solder ?

by Beaudoin Gaël (JIRA)

Documentation : property name from weld to solder ? --------------------------------------------------- Key: SEAM-81 URL: https://issues.jboss.org/browse/SEAM-81 Project: Seam 3 Distribution Issue Type: Bug Components: Common Documentation Affects Versions: 3.0.0.Final Reporter: Beaudoin Gaël Priority: Minor As Weld has been renamed solder, I guess the 20.1 section maven configuration example should use <version>${solder.extensions.version}</version> instead of <version>${weld.extensions.version}</version> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMJMS-17) Create an example(s) demonstrating JMS Features

by Ondrej Skutka (JIRA)

Create an example(s) demonstrating JMS Features ----------------------------------------------- Key: SEAMJMS-17 URL: https://issues.jboss.org/browse/SEAMJMS-17 Project: Seam JMS Issue Type: Task Reporter: Ondrej Skutka Fix For: 3.0.0.Final Create an example(s) demonstrating JMS Features: - JMS resource injection - Event Bridge -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2011