April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-352) @Consumer example

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-352?page=all ] Tim Fox updated JBMESSAGING-352: -------------------------------- Assignee: (was: Ovidiu Feodorov) > @Consumer example > ----------------- > > Key: JBMESSAGING-352 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-352 > Project: JBoss Messaging > Issue Type: Sub-task > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Add a Consumer example, as described in http://docs.jboss.org/ejb3/app-server/tutorial/consumer/consumer.html -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-354) Start a database with use case info

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-354?page=all ] Tim Fox updated JBMESSAGING-354: -------------------------------- Assignee: (was: Ovidiu Feodorov) > Start a database with use case info > ----------------------------------- > > Key: JBMESSAGING-354 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-354 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-153) JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred)

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-153?page=all ] Tim Fox updated JBMESSAGING-153: -------------------------------- Assignee: (was: Ovidiu Feodorov) > JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred) > --------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-153 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-153 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Affects Versions: 1.0.0 alpha PR3 > Reporter: Karl de Boer > Fix For: Unscheduled > > Original Estimate: 4 minutes > Remaining Estimate: 4 minutes > > As dicussed during JBW Barcelona i want to ask to investigate if it is posible to reliably sent very big messages from one jboss messaging node to another one (most likely on top of HTTPS(S). The business case is: mulitple organisations working in one workflow on digitally signed documents where Quality of Service is extremely important for instance patent applications. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-342) Functional tests bundled with the release should be functional

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-342?page=all ] Tim Fox updated JBMESSAGING-342: -------------------------------- Assignee: (was: Ovidiu Feodorov) > Functional tests bundled with the release should be functional > -------------------------------------------------------------- > > Key: JBMESSAGING-342 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-342 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The functional tests whose source code comes with the release should be compilable and runnable, so they can validate the release at unpacking. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-16) A PointToMultipoint should be able to do delivery on separate threads

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-16?page=all ] Tim Fox updated JBMESSAGING-16: ------------------------------- Assignee: (was: Ovidiu Feodorov) > A PointToMultipoint should be able to do delivery on separate threads > --------------------------------------------------------------------- > > Key: JBMESSAGING-16 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-16 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Messaging Core > Affects Versions: 1.2.0.Alpha1 > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-177) Server-side message persistence/caching should be done by an AOP interceptor

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-177?page=all ] Tim Fox updated JBMESSAGING-177: -------------------------------- Assignee: (was: Ovidiu Feodorov) > Server-side message persistence/caching should be done by an AOP interceptor > ---------------------------------------------------------------------------- > > Key: JBMESSAGING-177 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-177 > Project: JBoss Messaging > Issue Type: Task > Components: AOP Support > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-412) Please use build.properties for jboss.home in examples and the auto-install script

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-412?page=all ] Tim Fox updated JBMESSAGING-412: -------------------------------- Assignee: (was: Ovidiu Feodorov) > Please use build.properties for jboss.home in examples and the auto-install script > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-412 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-412 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Build System > Reporter: Michael Yuan > Priority: Minor > Fix For: Unscheduled > > > Right now, the build relies on JBOSS_HOME system variable. It is not the way most other projects do and it is broken on Mac. I would suggest to use a build.properties file in the root of the distribution. It has a jboss.home property that the user can edit. The user edits it once and can then use all ant tasks (auto install, examples etc.) in the distribution. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-383) Modify jboss-head build script to include Messaging instead of JBossMQ in the "default" configuration

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-383?page=all ] Tim Fox updated JBMESSAGING-383: -------------------------------- Assignee: (was: Ovidiu Feodorov) > Modify jboss-head build script to include Messaging instead of JBossMQ in the "default" configuration > ----------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-383 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-383 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Reporter: Ovidiu Feodorov > Priority: Critical > Fix For: Unscheduled > > > Make sure JBossMQ still works as an alternate JMS provider -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-10) Training Material

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-10?page=all ] Tim Fox updated JBMESSAGING-10: ------------------------------- Assignee: (was: Ovidiu Feodorov) > Training Material > ----------------- > > Key: JBMESSAGING-10 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-10 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Documentation and Training > Reporter: Ivelin Ivanov > Fix For: Unscheduled > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-87) Light-weight JMS 1.1 / JGroups package

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-87?page=all ] Tim Fox updated JBMESSAGING-87: ------------------------------- Assignee: (was: Ovidiu Feodorov) > Light-weight JMS 1.1 / JGroups package > -------------------------------------- > > Key: JBMESSAGING-87 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-87 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Bela Ban > Fix For: Unscheduled > > > Motivation: people want to use JGroups, but need to program against a standard API, like JMS 1.1. > Create a distribution which includes only the relevant parts of the JMS 1.1 implementation that runs on top of JGroups (the 'Serverless JMS' part, not the client/server part). -- 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, 3 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

jboss-jira April 2007