July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5674) Web components without top-level annotations not processed correctly

by Scott M Stark (JIRA)

Web components without top-level annotations not processed correctly -------------------------------------------------------------------- Key: JBAS-5674 URL: http://jira.jboss.com/jira/browse/JBAS-5674 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.CR1 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR2 web components without top-level annotations are not picked up by the AnnotationMetaDataDeployer and are not having their annotations processed until the TomcatInjectionContainer handles the instance creation. At this point resolution logic has to be redone. This should have already been handled by the MappedReferenceMetaDataResolverDeployer. -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1394) Refactor transaction logic

by Manik Surtani (JIRA)

Refactor transaction logic -------------------------- Key: JBCACHE-1394 URL: https://jira.jboss.org/jira/browse/JBCACHE-1394 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Transactions Reporter: Manik Surtani Assignee: Mircea Markus Fix For: 3.1.0 There are some redundancies here, which need tidying up. Specifically: 1. Redundant behaviour between TxInterceptor and InvocationContextInterceptor. ICI should *just* be in change of setting up and clearing down contexts. TxI should start implicit txs if needed, register syncs, handle remote prepares, commits and rollbacks, etc. 2. InvocationContext and TransactionContext has some redundanceis which can be cleaned up and optimised. 3. TransactionTable has an unnecessary number of Maps - these can be improved. It basically needs to be able to look up a Transaction and TransactionContext given a GlobalTransaction (for remote transactions coming in), as well as look up a GlobalTransaction and a TransactionContext given a Transaction (local transactions, retrieved from the TransactionManager). It is probably best to wait for Optimistic and Pessimistic Locking to be removed before this since a lot of this is legacy support code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1389) DataVersion implemenation that always returns false

by Brian Stansberry (JIRA)

DataVersion implemenation that always returns false --------------------------------------------------- Key: JBCACHE-1389 URL: http://jira.jboss.com/jira/browse/JBCACHE-1389 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 3.0.0 For use in structural nodes, a DataVersion implementation that always returns false. For use in cases where the structural nodes hold no data and changing the child map is not treated as a meaningful change, so there can be no meaningful version conflict. The Hibernate/JBC integration has long had such a class, but it seems like a common use case, so why not provide the impl in JBC itself. -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5818) Pausing on first request to Seam page

by Henning Sommerkamp (JIRA)

Pausing on first request to Seam page ------------------------------------- Key: JBAS-5818 URL: https://jira.jboss.org/jira/browse/JBAS-5818 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.0.0.CR1 Environment: JBoss 5.0.0.CR1 and jboss-seam-2.0.3.CR1 on both Windows XP and MacOSX Reporter: Henning Sommerkamp Assignee: Scott M Stark After the server has started up and the seam application has been deployed the followin problem occures: When requesting a .seam page the first time, a session object is created an all seam comonents are initialized. Then something locks up the server for about 1 minute, until the page is served to the browser. Further requests to .seam pages are delivered immediately, without this pause. please see the seam forum, where this problem is discussed in more detail: http://www.seamframework.org/Community/PossiblePerformanceIssueInStarting... Pete Muir expects this to be an Application Server problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-63) JBossCache benchmarks

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-63?page=com.atlassian.jira.plu... ] Manik Surtani updated JBCACHE-63: --------------------------------- Fix Version/s: 3.0.0.GA (was: 2.2.0.GA) > JBossCache benchmarks > --------------------- > > Key: JBCACHE-63 > URL: https://jira.jboss.org/jira/browse/JBCACHE-63 > Project: JBoss Cache > Issue Type: Task > Affects Versions: 1.2.4SP1 > Reporter: Bela Ban > Assignee: Mircea Markus > Fix For: 3.0.0.GA > > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Also bench against other caches -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1351) Write a JBossCache tutorial to publicise 2.2.0

by Manik Surtani (JIRA)

Write a JBossCache tutorial to publicise 2.2.0 ---------------------------------------------- Key: JBCACHE-1351 URL: http://jira.jboss.com/jira/browse/JBCACHE-1351 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Training Reporter: Manik Surtani Assigned To: Bela Ban Fix For: 2.2.0.GA Should write this on the JBoss Cache blog, and send links to OnJava, TSS, InfoQ, etc. -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-772) State transfer not handled properly in case of reconnect

by Brian Stansberry (JIRA)

State transfer not handled properly in case of reconnect -------------------------------------------------------- Key: JBCACHE-772 URL: http://jira.jboss.com/jira/browse/JBCACHE-772 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 1.4.0.SP1, 1.4.0, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0, 1.2.4SP2, 1.2.4SP1, 1.2.4 Reporter: Brian Stansberry Assigned To: Manik Surtani Fix For: 2.1.0 In createService(), TreeCache set Channel.AUTO_GET_STATE to true. This should only be done if the cache is configured to do an initial state transfer. That's easy to fix. What's harder to fix is what to do when region-based marshalling is in effect. Probably, something like the following: 1) In viewAccepted, monitor for the case where a view is issue that doesn't include the current node. Set a flag and ??? (throw exceptions when attempts are made to use the cache???) 2) When another view is accepted that once again includes the current node, iterate through the various marshalling regions, inactivating and then reactivating them (reactivation will cause a partial state transfer). -- 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

16 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1704) BRMS: tab switches to another GUI element when writing a technical rule

by Jaroslaw Kijanowski (JIRA)

BRMS: tab switches to another GUI element when writing a technical rule ----------------------------------------------------------------------- Key: JBRULES-1704 URL: https://jira.jboss.org/jira/browse/JBRULES-1704 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Priority: Minor Fix For: 5.0.0.M2 When I write a "technical rule" and use <tab> in the editor a /t is inserted but then the focus moves to the "View source" button. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1214) Can the cache be backed by LinkedHashSet instead of HashSet

by Carl Shelbourne (JIRA)

Can the cache be backed by LinkedHashSet instead of HashSet ----------------------------------------------------------- Key: JBCACHE-1214 URL: http://jira.jboss.com/jira/browse/JBCACHE-1214 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: RFC Reporter: Carl Shelbourne Assigned To: Manik Surtani Priority: Optional Looking at the code it is noted that the cache is backed by a HashSet. Would it be possible to change this so that it is backed by a LinkedHashSet. There may or may not be performance benefits to this dependant on the usage. The primary reason for wanting it to be backed by a LinkedHashSet is the guaranteed ordering of the elements when iterated over. Having this guarantee would facilitate implementations of say a TableModel, but would make other iterations more predictable too. -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Updated: (JBCACHE-471) Handle JGroups MERGE

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-471?page=com.atlassian.jira.pl... ] Manik Surtani updated JBCACHE-471: ---------------------------------- Fix Version/s: 3.1.0 (was: 3.0.0.GA) > Handle JGroups MERGE > -------------------- > > Key: JBCACHE-471 > URL: https://jira.jboss.org/jira/browse/JBCACHE-471 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.2.4 > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 3.1.0 > > > When JGroups needs to do a merge due to a temporary break in the group structure, JGroups does not handle the merging of data. This is usually left up to the application to handle. > JBossCache should support pluggable merge policies, we could provide some simple merge policies and allow users to write their own. > 1. Evict on merge policy - when a merge occurs, evict the entire in-memory state. Useful for Hibernate or when used with a shared cache loader. > 2. Other merge algos ... ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

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 July 2008