April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCACHE-165) Option to exclude fields from "aspectized" in aop

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-165?page=all ] Jason T. Greene updated JBCACHE-165: ------------------------------------ Assignee: Jason T. Greene (was: Ben Wang) > Option to exclude fields from "aspectized" in aop > ------------------------------------------------- > > Key: JBCACHE-165 > URL: http://jira.jboss.com/jira/browse/JBCACHE-165 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Jason T. Greene > Priority: Minor > Fix For: 2.1.0.GA > > Original Estimate: 2 days > Remaining Estimate: 2 days > > There may a time when a user wants certain fields in the POJO to be excluded from TreeCacheAop management. Currently, if a field is declared "transient", we have that effect. But still we may want to have a flag for this specific purpose. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1007) Synchronization impls should scrub state in afterCompletion

by Brian Stansberry (JIRA)

Synchronization impls should scrub state in afterCompletion ----------------------------------------------------------- Key: JBCACHE-1007 URL: http://jira.jboss.com/jira/browse/JBCACHE-1007 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Minor Fix For: 2.0.0.CR1 I've seen cases where transaction manager's hold refs to Synchronization objects for a while after the tx commits. This can give the appearance of memory leaks if the Synchronization holds state and someone is testing for leaks of objects linked to that state. Also, a user reports that JOTM is not releasing refs to Synchronizations, thus leaking anything referred to from the Synchronization (see forum thread.) Solution to this is to have the Synchronization clear its internal state in a finally block in afterCompletion(). Once that method executes, the state is no longer needed. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104067 for more on this. If possible, it's also good to have the Synchronization impl be a static class, so there is no, for example, TxInterceptor.this ref leading back to the interceptor from TxInterceptor$RemoteSynchronizationHandler. This is a minor issue, since if the TM does what it should and eventually drops the ref to the Synchronization, the issue cleans itself up. But clearing the Synchronization state aggressively helps avoid the appearance of leaks, and also helps unit tests that check for classloader leaks to ignore spurious stuff. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1018) DOCS: FAQ pdf version not getting created

by Rajesh Rajasekaran (JIRA)

DOCS: FAQ pdf version not getting created ----------------------------------------- Key: JBCACHE-1018 URL: http://jira.jboss.com/jira/browse/JBCACHE-1018 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Training Reporter: Rajesh Rajasekaran Assigned To: Bela Ban Fix For: 2.0.0.CR1 The pdf version for the faq section in the docs is not getting created when building the distribution. ./build.sh dist -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4251) JMS persistance configuration for db2 (db2-jdbc2-service.xml)

by Rajesh Rajasekaran (JIRA)

JMS persistance configuration for db2 (db2-jdbc2-service.xml) ------------------------------------------------------------- Key: JBAS-4251 URL: http://jira.jboss.com/jira/browse/JBAS-4251 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMS service Reporter: Rajesh Rajasekaran Assigned To: Adrian Brock Fix For: JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1 We need a db2-jdbc2-service.xml to be ship with jboss-4.2.x (and also jboss-4.0.x) to support DB2 databases. To start with i copied oracle-jdbc2-service.xml to db2-jdbc2-service.xml and made a few SQL changes. 1.) With DB2 all primary keys should be explicitly mentioned NOT NULL I added NOT NULL to TXID column. CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER NOT NULL, PRIMARY KEY (TXID) ) WIth this persistance configurations work with DB2 8.0 2.) With DB2 7.2 the following query throws an error: db2 => CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION)) DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0604N The length, precision, or scale attribute for column, distinct type, structured type, attribute of structured type, function, or type mapping "MESSAGEBLOB" is not valid. SQLSTATE=42611 -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4240) SQL error in uuid-key-generator.sar jboss-service.xml against DB2 7.2

by Rajesh Rajasekaran (JIRA)

SQL error in uuid-key-generator.sar jboss-service.xml against DB2 7.2 --------------------------------------------------------------------- Key: JBAS-4240 URL: http://jira.jboss.com/jira/browse/JBAS-4240 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Assigned To: Rajesh Rajasekaran Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1 The spaces at the end of each line of the SQL doesn not work with DB2 7.2  <attribute name="CreateTableDdl"> create table HILOSEQUENCES ( SEQUENCENAME varchar(50) not null, HIGHVALUES integer not null, constraint hilo_pk primary key (SEQUENCENAME) ) </attribute> The following error occurs on server startup: 2007-03-23 14:34:47,234 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Executing DDL: create table HILOSEQUENCES ( SEQUENCENAME varchar(50) not null, HIGHVALUES integer not null, constraint hilo_pk primary key (SEQUENCENAME) ) 2007-03-23 14:34:47,437 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting failed jboss:service=KeyGeneratorFactory,type=HiLo com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -7, SQLSTATE: 42601, SQLERRMC: ;able HILOSEQUENCES ( at com.ibm.db2.jcc.c.fg.e(fg.java:1596) at com.ibm.db2.jcc.c.fg.b(fg.java:1160) at com.ibm.db2.jcc.b.gb.h(gb.java:217) at com.ibm.db2.jcc.b.gb.b(gb.java:46) at com.ibm.db2.jcc.b.w.b(w.java:40) at com.ibm.db2.jcc.b.vb.f(vb.java:118) at com.ibm.db2.jcc.c.fg.m(fg.java:1155) Going through the db2 reference says: db2 => ? sql0007 SQL0007N The character "<character>" following "<text>" is not valid. Explanation: The specified "<character>" is not a valid character in SQL statements. The "<text>" field indicates the 20 characters of the SQL statement that preceded the character that is not valid. Hence I am wrapping up the SQL in a single line. However this problem does not exist with DB2 8.0 -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4284) Duplicate 4446 binding in sample-bindings.xml

by Brian Stansberry (JIRA)

Duplicate 4446 binding in sample-bindings.xml --------------------------------------------- Key: JBAS-4284 URL: http://jira.jboss.com/jira/browse/JBAS-4284 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.0.CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.GA In the sample-bindings.xml, in ports-default 4446 is used for both pooled-invoker-ha and the remoting connector. The standard pooled invoker HA has been changed to 4448, so it should be updated to a sequence based on that in sample-bindings.xml. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Closed: (JBPM-606) create component for starting a new process

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-606?page=all ] David Lloyd closed JBPM-606. ---------------------------- Resolution: Duplicate Issue Duplicates JBPM-567 > create component for starting a new process > ------------------------------------------- > > Key: JBPM-606 > URL: http://jira.jboss.com/jira/browse/JBPM-606 > Project: JBoss jBPM > Issue Type: Task > Components: Web Interface > Reporter: Tom Baeyens > Assigned To: David Lloyd > Fix For: jBPM 3.3 > > > a ui component and facelets tag support should be created for the process definition list with command links for starting these process definitions. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-605) create group task list component

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-605?page=all ] David Lloyd closed JBPM-605. ---------------------------- Resolution: Duplicate Issue Duplicates JBPM-567 > create group task list component > -------------------------------- > > Key: JBPM-605 > URL: http://jira.jboss.com/jira/browse/JBPM-605 > Project: JBoss jBPM > Issue Type: Task > Components: Web Interface > Reporter: Tom Baeyens > Assigned To: David Lloyd > Fix For: jBPM 3.3 > > > a component and facelets tag support should be added for the group tasklist. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-603) create ui component for comments

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-603?page=all ] David Lloyd closed JBPM-603. ---------------------------- Resolution: Duplicate Issue Duplicates JBPM-567 > create ui component for comments > -------------------------------- > > Key: JBPM-603 > URL: http://jira.jboss.com/jira/browse/JBPM-603 > Project: JBoss jBPM > Issue Type: Task > Components: Web Interface > Reporter: Tom Baeyens > Assigned To: David Lloyd > Fix For: jBPM 3.3 > > > 2 jsf UI components should be created based on the dataTable for showing comments. > 1 component/tag for taskInstance comments and 1 for token comments. > This should be a shortcut for something like this: > <c:if test="#{taskBean.comments != null}"> > <h:dataTable var="comment" value="#{taskBean.comments}"> > <f:facet name="header">Comments</f:facet> > <h:column> > <f:facet name="header">Actor</f:facet> > <h:outputText value="#{comment.actorId}"/> > </h:column> > <h:column> > <f:facet name="header">Time</f:facet> > <h:outputText value="#{comment.time}"> > <f:convertDateTime type="both" /> > </h:outputText> > </h:column> > <h:column> > <f:facet name="header">Message</f:facet> > <h:outputText value="#{comment.message}"/> > </h:column> > </h:dataTable> > </c:if> -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-604) create tasklist component

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-604?page=all ] David Lloyd closed JBPM-604. ---------------------------- Resolution: Duplicate Issue Duplicates JBPM-567 > create tasklist component > ------------------------- > > Key: JBPM-604 > URL: http://jira.jboss.com/jira/browse/JBPM-604 > Project: JBoss jBPM > Issue Type: Task > Components: Web Interface > Reporter: Tom Baeyens > Assigned To: David Lloyd > Fix For: jBPM 3.3 > > > create a task list component + facelets tag support, preferrably based on the JSF dataTable. > if the component doesn't have the line highlighting as there is now, that is not a problem. -- 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, 1 month

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 April 2007