October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-639) AS Integration

by Ovidiu Feodorov (JIRA)

AS Integration -------------- Key: JBMESSAGING-639 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-639 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 Container task for anything related to integration. -- 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, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-641) Make sure smoke tests pass on an un-scoped JBoss5/Messaging instance

by Ovidiu Feodorov (JIRA)

Make sure smoke tests pass on an un-scoped JBoss5/Messaging instance -------------------------------------------------------------------- Key: JBMESSAGING-641 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-641 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov 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, 3 months

5
11
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-388) Write a JBossMQ to Messaging migration guide

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ] Clebert Suconic closed JBMESSAGING-388. --------------------------------------- Resolution: Done JBM already cover migration (just look at installation docs) > Write a JBossMQ to Messaging migration guide > -------------------------------------------- > > Key: JBMESSAGING-388 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Fix For: AS 5.0 Integration > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-388) Write a JBossMQ to Messaging migration guide

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ] Clebert Suconic closed JBMESSAGING-388. --------------------------------------- Resolution: Done > Write a JBossMQ to Messaging migration guide > -------------------------------------------- > > Key: JBMESSAGING-388 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Fix For: AS 5.0 Integration > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-388) Write a JBossMQ to Messaging migration guide

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ] Clebert Suconic reopened JBMESSAGING-388: ----------------------------------------- Assignee: Clebert Suconic > Write a JBossMQ to Messaging migration guide > -------------------------------------------- > > Key: JBMESSAGING-388 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Fix For: AS 5.0 Integration > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1731) Document / Tutorial Data Display from Database using Hibernate

by Eric Brennan (JIRA)

Document / Tutorial Data Display from Database using Hibernate -------------------------------------------------------------- Key: JBPORTAL-1731 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1731 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Reference Guide Affects Versions: 2.6.2 Final Environment: Portal 2.6.1 GA Oracle backend. Reporter: Eric Brennan Assigned To: Julien Viet Priority: Optional It would be nice to have a tutorial on Displaying records from a Database using hibernate. Could expand the Helloworld example to pull two fields from a database. How to configure Hibernate CFG so that it pulls a generic DS. Nice to have records displayed bases on login ID. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-324) Facility for real-time decision on best InvokerLocator by which to contact a given handler.

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-324?page=comments#action_12379624 ] David Lloyd commented on JBREM-324: ----------------------------------- The Routing/Discovery API of Remoting 3 should facilitate this ability, if I understand correctly. It will maintain a list of paths to endpoints, and choose the best one available at any given time. > Facility for real-time decision on best InvokerLocator by which to contact a given handler. > ------------------------------------------------------------------------------------------- > > Key: JBREM-324 > URL: http://jira.jboss.com/jira/browse/JBREM-324 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.0.0.Beta1 > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 4.0.0.Beta1 > > > The basic idea is to be able to communicate with a single handler by way of different InvokerLocators. For example, if you're working over the internet, compression might be advantageous, but if you're local it might not be. So you could have two Connectors sharing a handler, one using the compression marshaller and one not. > How about a client that > 1. gets the InvokerLocators for all of the Connectors for a certain handler, via a detector, > 2. sends some sample invocations to each and times them, and > 3. displays the results. > It could be used for real time decision making or to collect information for a set of rules. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-305) Provide support for JMS transport

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12379620 ] David Lloyd commented on JBREM-305: ----------------------------------- Thomas, are there any specific requirements regarding the format of the JMS message? Or do you just want your message to be moved from one endpoint to another? > Provide support for JMS transport > --------------------------------- > > Key: JBREM-305 > URL: http://jira.jboss.com/jira/browse/JBREM-305 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 beta > Reporter: Thomas Diesler > Assigned To: Tom Elrod > Fix For: 4.0.0.Beta1 > > > The web service layer has a need for JMS transport -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-45) Remoting watchdog

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-45?page=all ] David Lloyd closed JBREM-45. ---------------------------- Resolution: Out of Date Assignee: David Lloyd (was: Tom Elrod) This issue is in three parts: 1) Build in ability for the server to be aware of clients that exist and their status. Remoting 3 does not have a notion of client vs. server. That said, an Endpoint will always be aware of the status of its Sessions. 2) Add distributed garbage collection for clients that maintain a remote stub. Will detect that client is no longer available (via watchdog) and will clean up server side references. This is probably out of scope for Remoting 3 - I'm inclined to let this die until a specific issue arises. Specifically, Remoting 3 doesn't normally utilize the idea of a remote object. Anything that does, will be built on top of Remoting 3 and will probably be responsible for dealing with this functionality. 3) Need ability to disconnect client from server when there has been an extended period of inactivity. This would be very specific to the protocol. Additionally complicated by the addition of Context/Session layers. > Remoting watchdog > ------------------- > > Key: JBREM-45 > URL: http://jira.jboss.com/jira/browse/JBREM-45 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.0.1 beta > Reporter: Tom Elrod > Assigned To: David Lloyd > Fix For: 4.0.0.Beta1 > > > Build in ability for the server to be aware of clients that exist and their status. Will be needed for doing distributed garbage collection, client connection timeout, etc. > Add distributed garbage collection for clients that maintain a remote stub. Will detect that client is no longer available (via watchdog) and will clean up server side references. > Need ability to disconnect client from server when there has been an extended period of inactivity. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3142) Add UnifiedInvoker (JBSer and JavaSer) into Version MatrixTestSuite

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3142?page=all ] Clebert Suconic updated JBAS-3142: ---------------------------------- Priority: Optional (was: Major) > Add UnifiedInvoker (JBSer and JavaSer) into Version MatrixTestSuite > ------------------------------------------------------------------- > > Key: JBAS-3142 > URL: http://jira.jboss.com/jira/browse/JBAS-3142 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Clebert Suconic > Assigned To: Clebert Suconic > Priority: Optional > Fix For: JBossAS-4.2.2.GA > > -- 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, 3 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 October 2007