July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Deleted: (JBMESSAGING-1404) Optimize Journal::postFilesMap

by Clebert Suconic (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1404?page=com.atlassian.ji... ] Clebert Suconic deleted JBMESSAGING-1404: ----------------------------------------- > Optimize Journal::postFilesMap > ------------------------------ > > Key: JBMESSAGING-1404 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1404 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Clebert Suconic > Assignee: Clebert Suconic > > There is a HashMap<Id, PosFilesUsed> called posFilesMap on JournalImpl > It would be possible to store intervals of IDs used per file, instead of soring files per ID, what consumes some memory. -- 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: (JBMESSAGING-1404) Optimize Journal::postFilesMap

by Clebert Suconic (JIRA)

Optimize Journal::postFilesMap ------------------------------ Key: JBMESSAGING-1404 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1404 Project: JBoss Messaging Issue Type: Feature Request Reporter: Clebert Suconic Assignee: Clebert Suconic There is a HashMap<Id, PosFilesUsed> called posFilesMap on JournalImpl It would be possible to store intervals of IDs used per file, instead of soring files per ID, what consumes some memory. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1350) Retry blocks on asynchronous open at the journal

by Clebert Suconic (JIRA)

Retry blocks on asynchronous open at the journal ------------------------------------------------ Key: JBMESSAGING-1350 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1350 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Tim Fox Fix For: 2.0.0 Beta -- 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
4
0 / 0

[JBoss JIRA] Created: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model

by Andrew Lee Rubinger (JIRA)

Decouple Transient "determine*" JNDI Logic from Object Model ------------------------------------------------------------ Key: JBMETA-68 URL: http://jira.jboss.com/jira/browse/JBMETA-68 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Priority: Critical Fix For: 1.0.0.CR1 Current "determineResolved*JndiName()" methods, with default logic, are mixing concerns in the Object Model. Resolution of target JNDI names should be extracted. Following steps to be taken: * Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and children * Remove ClassLoader from DeploymentSummary; this is transient anyway * Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD instance * Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of resolving JNDI Names. * Implement the Resolveable* SPI Interfaces in Decorators * Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from the caller * Update Unit Tests to use new grammars, allow 0% regression For integration with AS: * Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI Binding Policies * Update grammars accordingly -- 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
20
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1246) Interceptor instances must be per EJB, not per container

by Carlo de Wolf (JIRA)

Interceptor instances must be per EJB, not per container -------------------------------------------------------- Key: EJBTHREE-1246 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1246 Project: EJB 3.0 Issue Type: Bug Components: interceptors Reporter: Carlo de Wolf Priority: Blocker Fix For: AS 5.0.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

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1445) getRollbackOnly is not allowed after completion of the transaction

by Carlo de Wolf (JIRA)

getRollbackOnly is not allowed after completion of the transaction ------------------------------------------------------------------ Key: EJBTHREE-1445 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1445 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf EJB 3 4.4.1 It does not make sense to inquire about rollback status after a transaction has been completed. -- 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
5
0 / 0

[JBoss JIRA] Created: (JGRP-796) RpcDispatcher.Marshaller: use Buffer instead of byte[]

by Bela Ban (JIRA)

RpcDispatcher.Marshaller: use Buffer instead of byte[] ------------------------------------------------------ Key: JGRP-796 URL: http://jira.jboss.com/jira/browse/JGRP-796 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.7 A Buffer allows us to pass in byte[] arrays with a different offset and length; more flexible. Maybe create a Marshaller2 (extending Marshaller) -- 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
7
0 / 0

[JBoss JIRA] Created: (JBXB-135) XB analogue of schemaLocation that would point to annotated class

by Alexey Loubyansky (JIRA)

XB analogue of schemaLocation that would point to annotated class ----------------------------------------------------------------- Key: JBXB-135 URL: http://jira.jboss.com/jira/browse/JBXB-135 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossXB-2.0.0.CR8 Adrian suggested a feature to map a namespace to a JAXB-annotated class in the XML by introducing a new attribute that would be an analogue of schemaLocation, e.g. <deployment xmlns:jbxb="urn:jbossxb:2.0" jbxb:schemabinding="urn:jbossjms:5.0 org.jboss.jms.Whatever"/> -- 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
5
0 / 0

[JBoss JIRA] Resolved: (JBMICROCONT-22) Related classes

by Ales Justin (JIRA)

[ https://jira.jboss.org/jira/browse/JBMICROCONT-22?page=com.atlassian.jira... ] Ales Justin resolved JBMICROCONT-22. ------------------------------------ Resolution: Done Added RelatedMetaData interface + impl. BeanMetaDataBuilder has util methods. Tests were also added to bean metadata. > Related classes > --------------- > > Key: JBMICROCONT-22 > URL: https://jira.jboss.org/jira/browse/JBMICROCONT-22 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData (Now in JBMAN) > Reporter: Adrian Brock > Assignee: Ales Justin > Fix For: JBossMC.2.0.0.CR1 > > > Add the ability to define related classes when processing annotations for dependencies. > e.g. a factory creates another class, both need processing to see whether they have > dependencies defined inside the ClassData annotations. -- 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: (JBRULES-1698) BRMS: typo in the initial description of a new enumaration

by Jaroslaw Kijanowski (JIRA)

BRMS: typo in the initial description of a new enumaration ---------------------------------------------------------- Key: JBRULES-1698 URL: https://jira.jboss.org/jira/browse/JBRULES-1698 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Priority: Minor Fix For: 5.0.0.M2 When I create a new enumeration, the initial description filed has a hint: ... The format of this is: 'FactType.fieldName ': ['Value1', 'Value2'] there should be now space between FactType.fieldName and ' However examples are fine. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008