August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-348) Automate test run against all supported databases

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-348?page=all ] Ovidiu Feodorov updated JBMESSAGING-348: ---------------------------------------- Fix Version/s: 1.2.0.CR1 (was: 1.0.2) Assignee: Ryan Campbell (was: Tim Fox) > Automate test run against all supported databases > ------------------------------------------------- > > Key: JBMESSAGING-348 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-348 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Ryan Campbell > Fix For: 1.2.0.CR1 > > > The test suite should be run continuously against all databases we supply a configuration for. > Initially this should be: > Oracle, MSSQL, MySQL, PostgreSQL, DB2, Sybase and Derby. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-381) Add param on destination to disable persistence

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ] Ovidiu Feodorov updated JBMESSAGING-381: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.2) > Add param on destination to disable persistence > ----------------------------------------------- > > Key: JBMESSAGING-381 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent. > This should give equivalent functionality to the JBossMQ NullPersistenceManager. > in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-178) Run TCK continuously in top of JBoss Messaging

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-178?page=all ] Ovidiu Feodorov updated JBMESSAGING-178: ---------------------------------------- Fix Version/s: 1.2.0.CR1 (was: 1.0.2) Assignee: Ryan Campbell (was: Ovidiu Feodorov) Priority: Major (was: Critical) > Run TCK continuously in top of JBoss Messaging > ---------------------------------------------- > > Key: JBMESSAGING-178 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-178 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Ryan Campbell > Fix For: 1.2.0.CR1 > > -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-26) Standalone Messaging configuration.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ] Ovidiu Feodorov updated JBMESSAGING-26: --------------------------------------- Fix Version/s: 1.2.0.CR1 (was: 1.0.2) Assignee: Alex Pinkin (was: Ovidiu Feodorov) > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Alex Pinkin > Fix For: 1.2.0.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-26) Standalone Messaging configuration.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ] Ovidiu Feodorov updated JBMESSAGING-26: --------------------------------------- Attachment: (was: JBMESSAGING-26.tar) > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.0.2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-26) Standalone Messaging configuration.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ] Ovidiu Feodorov updated JBMESSAGING-26: --------------------------------------- Comment: was deleted > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.0.2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-26) Standalone Messaging configuration.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ] Ovidiu Feodorov updated JBMESSAGING-26: --------------------------------------- Comment: was deleted > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.0.2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-26) Standalone Messaging configuration.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ] Ovidiu Feodorov updated JBMESSAGING-26: --------------------------------------- Comment: was deleted > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.0.2 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-25) Integrate ServerPeer with the 5.0 micro-container

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ] Ovidiu Feodorov updated JBMESSAGING-25: --------------------------------------- Attachment: JBMESSAGING-26.tar Initial code drop for pure MC based messaging. Contributed by Arvinder Singh [15/May/06 05:05 PM] Originally attached to JBMESSAGING-26. Comments following attachment: Tim Fox [20/Jun/06 01:47 PM]: I'm not sure what I am looking at here. I don't know much about the MC but it is my understanding that all we need to do is provide POJO versions of our current MBeans. Am I missing something? Arvinder Singh [21/Jun/06 03:39 AM]: Ok it might become clearer with the next set of changes i will upload. Basically I am adding code that belongs in other projects like - NamingService - TransactionService - RemotingService - etc in addition to the MBeans in messaging which I have yet to do. The issue is not providing POJO versions of current messaging MBeans, but other POJO versions from the other sub projects (like above) in order to get this up and running. Let me upload the next set and then we can go over what has been done. > Integrate ServerPeer with the 5.0 micro-container > ------------------------------------------------- > > Key: JBMESSAGING-25 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta1 > > Attachments: JBMESSAGING-26.tar > > Original Estimate: 1 week > Remaining Estimate: 1 week > > This is critical to kick start ESB -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-25) Integrate ServerPeer with the 5.0 micro-container

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ] Ovidiu Feodorov updated JBMESSAGING-25: --------------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.0.2) > Integrate ServerPeer with the 5.0 micro-container > ------------------------------------------------- > > Key: JBMESSAGING-25 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > This is critical to kick start ESB -- 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

17 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006