February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-807) Document limitations of FileCacheLoader

by Brian Stansberry (JIRA)

Document limitations of FileCacheLoader --------------------------------------- Key: JBCACHE-807 URL: http://jira.jboss.com/jira/browse/JBCACHE-807 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0 We often discuss that FileCacheLoader is not appropriate for many production use cases. But this is not indicated in the formal docs. We need to discuss this in the docbook docs, and at least touch on it in the class javadoc for FileCacheLoader. -- 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, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-845) Clonability of Configuration classes

by Brian Stansberry (JIRA)

Clonability of Configuration classes ------------------------------------ Key: JBCACHE-845 URL: http://jira.jboss.com/jira/browse/JBCACHE-845 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.GA Need to think through whether/how the classes that compose a Configuration should implement clone(). -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-942) Refactor Optimistic{Node|CreateIfNotExists|Validation}Interceptors for readability

by Manik Surtani (JIRA)

Refactor Optimistic{Node|CreateIfNotExists|Validation}Interceptors for readability ---------------------------------------------------------------------------------- Key: JBCACHE-942 URL: http://jira.jboss.com/jira/browse/JBCACHE-942 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.BETA2 They're a bit spidery at the moment, a result of the direct import from the classes that were contributed back in the 1.3.0 timeframe. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-852) setPooledActors in AssignmentHandler doesn't work

by Diego Tobaldi (JIRA)

setPooledActors in AssignmentHandler doesn't work ------------------------------------------------- Key: JBPM-852 URL: http://jira.jboss.com/jira/browse/JBPM-852 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: windows, jbpm-starters-kit-3.1.4 Reporter: Diego Tobaldi Assigned To: Tom Baeyens I'd implemented an AssignmentHandler and can´t to assign a task to several users. Example: public class TestAssignmentHandler implements AssignmentHandler { public void assign(Assignable assignable, ExecutionContext executionContext) throws Exception { String[] actors= new String[]{"bert", "ernie"}; assignable.setActorId(null); assignable.setPooledActors(actors); } -- 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, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBCOMMON-13) Release JBossCommon 1.0.4.GA

by Dimitris Andreadis (JIRA)

Release JBossCommon 1.0.4.GA ---------------------------- Key: JBCOMMON-13 URL: http://jira.jboss.com/jira/browse/JBCOMMON-13 Project: JBoss Common Issue Type: Task Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 1.0.4.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

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4106) Allow use of classes from scoped loaders in ClusterPartition RPC calls

by Brian Stansberry (JIRA)

Allow use of classes from scoped loaders in ClusterPartition RPC calls ---------------------------------------------------------------------- Key: JBAS-4106 URL: http://jira.jboss.com/jira/browse/JBAS-4106 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 ClusterPartition RPC calls will currently fail if any classes in the RPC or in the return value are not visible to ClusterPartition's classloader. This is because message unmarshalling will fail to resolve the scoped class. To fix this: 1) Add overloaded method registerRPCHandler(String key, Object handler, Classloader classloader) to ClusterPartition. 2) Add field ConcurrentHashMap<String, WeakReference<Classloader>> to ClusterPartition. 3) Refactor the way the service name is passed in the marshalled RPC. Now it is dot appended to the RPC's method name. Instead marshall it separately; e.g. the marshalled data structure could be new Object[] { serviceName, new MarshalledValue(methodCall) } or something like that. 4) Unmarshalling deserializes the above, reads the serviceName, looks up the classloader in the map; if found sets the TCCL, and then calls MarshalledValue.get() to get the MethodCall. Alternative is not to create a separate map for the classloaders, but change the current map that stores the handlers to instead store a simple data type that wraps the handler and the classloader. Have to use a WeakReference for the classloader though. The existing usage where no classloader is registered still has to work; i.e. if no classloader is found don't touch the TCCL. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-725) Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files.

by Stefan Lang (JIRA)

Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files. -------------------------------------------------------------------------------------- Key: JBPM-725 URL: http://jira.jboss.com/jira/browse/JBPM-725 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM 3.1.2, jBPM 3.1.1 Reporter: Stefan Lang Assigned To: Tom Baeyens The auto-import attribute of the hibernate-mapping elements in all hbm.xml files is not set. Thus it is possible to use unqualified class names in Hibernate queries. The problem is that name clashes with client code are very probable. E.g. we have an "Event" entity class, jbpm has one too, so the following: "select Event as e ..." causes a hibernate exception. We have set the auto-import attribute to "false" in all jbpm hbm files and it works now as expected. -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3906) 4.2 testsuite on RHEL4 (JRockit jdk5)

by Dimitris Andreadis (JIRA)

4.2 testsuite on RHEL4 (JRockit jdk5) ------------------------------------- Key: JBAS-3906 URL: http://jira.jboss.com/jira/browse/JBAS-3906 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3611) Get the jboss-4.0-testsuite-sun-1.5 passing

by Dimitris Andreadis (JIRA)

Get the jboss-4.0-testsuite-sun-1.5 passing ------------------------------------------- Key: JBAS-3611 URL: http://jira.jboss.com/jira/browse/JBAS-3611 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA Container task for sun jdk1.5 test run failures -- 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, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4163) Interation between custom jboss trace and log4j trace levels

by Scott M Stark (JIRA)

Interation between custom jboss trace and log4j trace levels ------------------------------------------------------------ Key: JBAS-4163 URL: http://jira.jboss.com/jira/browse/JBAS-4163 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System, Logging Affects Versions: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.0.GA I believe the following type of configuration should work with the current log4j version as it now supports trace natively: <category name="org.jboss.profileservice"> <priority value="TRACE"/> <appender-ref ref="PROFILESERVICE"/> </category> While messages do appear in the PROFILESERVICE appender, no trace level messages are there. Most likely the jboss Logger is getting in the way of mapping this priority and an update to the common logging spi is needed. -- 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, 3 months

2
4
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 February 2007