November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-2853) Integrate JBoss Cache 2.0 into AS 5.0

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2853?page=comments#action_12347036 ] Brian Stansberry commented on JBAS-2853: ---------------------------------------- Manik, assigned this to myself, as I'm doing the integration work. > Integrate JBoss Cache 2.0 into AS 5.0 > ------------------------------------- > > Key: JBAS-2853 > URL: http://jira.jboss.com/jira/browse/JBAS-2853 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Manik Surtani > Assigned To: Brian Stansberry > Priority: Critical > Fix For: JBossAS-5.0.0.Beta1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2853) Integrate JBoss Cache 2.0 into AS 5.0

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2853?page=all ] Brian Stansberry reassigned JBAS-2853: -------------------------------------- Assignee: Brian Stansberry (was: Manik Surtani) > Integrate JBoss Cache 2.0 into AS 5.0 > ------------------------------------- > > Key: JBAS-2853 > URL: http://jira.jboss.com/jira/browse/JBAS-2853 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Manik Surtani > Assigned To: Brian Stansberry > Priority: Critical > Fix For: JBossAS-5.0.0.Beta1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-591) Convert all state transfer to use channel's partial state transfer

by Vladimir Blagojevic (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-591?page=all ] Vladimir Blagojevic resolved JBCACHE-591. ----------------------------------------- Fix Version/s: 2.0.0.GA (was: 2.1.0.GA) Resolution: Done Commited for 2.0.0 Alpha. > Convert all state transfer to use channel's partial state transfer > ------------------------------------------------------------------ > > Key: JBCACHE-591 > URL: http://jira.jboss.com/jira/browse/JBCACHE-591 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Vladimir Blagojevic > Priority: Blocker > Fix For: 2.0.0.GA > > > Currently initial state transfer uses a call to JChannel.getState() but partial state transfer after region activation and state transfer after addition to a buddy group both use RpcDispatcher calls. Need to unify around the JChannel's partial state feature. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3273) Update JBossRemoting to version 2.2.0

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3273?page=all ] Dimitris Andreadis closed JBAS-3273. ------------------------------------ Resolution: Done JBoss Beta1 will go with out with remoting 2.2.0.Alpha2, so I guess we can close this. I created JBAS-3856 to track the update to a final release. > Update JBossRemoting to version 2.2.0 > ------------------------------------- > > Key: JBAS-3273 > URL: http://jira.jboss.com/jira/browse/JBAS-3273 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Remoting > Reporter: Tom Elrod > Assigned To: Tom Elrod > Priority: Critical > Fix For: JBossAS-5.0.0.Beta1 > > > Need to update JBossAS to include jboss-remoting.jar for version 2.0.0.GA of JBossRemoting. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3273) Update JBossRemoting to version 2.2.0

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3273?page=all ] Dimitris Andreadis updated JBAS-3273: ------------------------------------- Summary: Update JBossRemoting to version 2.2.0 (was: update JBossRemoting to version 2.0.0) > Update JBossRemoting to version 2.2.0 > ------------------------------------- > > Key: JBAS-3273 > URL: http://jira.jboss.com/jira/browse/JBAS-3273 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Remoting > Reporter: Tom Elrod > Assigned To: Tom Elrod > Priority: Critical > Fix For: JBossAS-5.0.0.Beta1 > > > Need to update JBossAS to include jboss-remoting.jar for version 2.0.0.GA of JBossRemoting. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3151) Convert HA-JNDI stubs to Remoting

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3151?page=all ] Dimitris Andreadis updated JBAS-3151: ------------------------------------- Fix Version/s: JBossAS-5.0.0.Beta2 (was: JBossAS-5.0.0.Beta1) > Convert HA-JNDI stubs to Remoting > --------------------------------- > > Key: JBAS-3151 > URL: http://jira.jboss.com/jira/browse/JBAS-3151 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering, Naming, Remoting > Reporter: Brian Stansberry > Assigned To: Tom Elrod > Fix For: JBossAS-5.0.0.Beta2 > > > The HA-JNDI naming service proxy is based on the old HARMIClient and HARMIServer code. We should convert this to use Remoting. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-59) JCA work for JBoss-5.0.0Beta

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-59?page=all ] Dimitris Andreadis updated JBAS-59: ----------------------------------- Fix Version/s: JBossAS-5.0.0.Beta2 (was: JBossAS-5.0.0.Beta1) Assignee: Weston Price Assign to Weston, rescheduling. > JCA work for JBoss-5.0.0Beta > ---------------------------- > > Key: JBAS-59 > URL: http://jira.jboss.com/jira/browse/JBAS-59 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Weston Price > Fix For: JBossAS-5.0.0.Beta2 > > > Schedule -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1435) Interceptors

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1435?page=all ] Dimitris Andreadis updated JBAS-1435: ------------------------------------- Assignee: Weston Price Assign to Weston. > Interceptors > ------------ > > Key: JBAS-1435 > URL: http://jira.jboss.com/jira/browse/JBAS-1435 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Weston Price > Priority: Minor > Fix For: JBossAS-5.0.1.CR1 > > > Forums discussion thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48683 > This is really a major rewrite of the JCA implementation to be less monolithic > so this will need some careful design and consideration and > breaking up into more fine grained tasks. > The idea is to provide containers/interceptors for the components within the JCA module > such that these components can be more easily customised and developed according to > the needs of each user. > There are three main interceptor stacks that I can think of: > 1) ConnectionManager (connection allocation) > This provides an interceptor stack behind the ConnectionFactory/DataSource proxy > to process the allocateConnection invocation. > It will look something like: > ConnectionFactory proxy -> ConnectionManager interceptor -> Pooling interceptor > 2) ManagedConnection/ConnectionEventListener (connection management) > This stack provides most of the features that are currently performed by the > BaseManagerConnection2$ConnectionListener and their supporting methods, > but as an interceptor stack. > As now they will largely be driven by the events from the resource adapter, > and it this object that is actually pooled. > 3) Resource Adaptors > The JDBC and JMS adaptors should be implemented as interceptor stacks > to allow optional interceptors like statistics collection, custom behaviour > and also to perform vendor specific processing/workarounds. > Where AOP can be used, we could actually instrument the vendor classes so > we can also expose vendor specific methods, not just the JDBC interfaces. > This would remove the requirement to do things like getUnderlyingConection() by user code. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2870) Separate the HA aspect from the invoker proxy

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2870?page=all ] Dimitris Andreadis updated JBAS-2870: ------------------------------------- Fix Version/s: JBossAS-5.0.0.Beta2 (was: JBossAS-5.0.0.Beta1) Move to Beta2 > Separate the HA aspect from the invoker proxy > --------------------------------------------- > > Key: JBAS-2870 > URL: http://jira.jboss.com/jira/browse/JBAS-2870 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.Beta2 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Comment from Scott Stark (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926369#3926369) > HA proxy invokers like JRMPInvokerProxyHA should not exist. The only difference between an ha proxy and regular proxy would be an interceptor that selected from the available targets and set the invocation proxy such that the common Invoker proxy was told the transport proxy to use. Even an unclustered proxy could have a recover/ha sematic like blocking until the server is availble with this configuration. HA is an aspect that should not be embedded in the transport specific proxy. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2505) Hibernate integration in JBoss5

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2505?page=all ] Dimitris Andreadis updated JBAS-2505: ------------------------------------- Fix Version/s: JBossAS-5.0.0.Beta2 (was: JBossAS-5.0.0.Beta1) > Hibernate integration in JBoss5 > ------------------------------- > > Key: JBAS-2505 > URL: http://jira.jboss.com/jira/browse/JBAS-2505 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Scott M Stark > Assigned To: Steve Ebersole > Fix For: JBossAS-5.0.0.Beta2 > > > A containing task for Hiberate integration issues for the JBoss5 release -- 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, 6 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 November 2006