November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-236) Include documentation in the gpd distro

by Thomas Diesler (JIRA)

Include documentation in the gpd distro --------------------------------------- Key: GPD-236 URL: https://jira.jboss.org/jira/browse/GPD-236 Project: JBoss jBPM GPD Issue Type: Task Reporter: Thomas Diesler Assignee: Koen Aers Fix For: jBPM jPDL Designer 3.1.5 -- 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

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (GPD-239) Release gpd-3.1.5

by Thomas Diesler (JIRA)

Release gpd-3.1.5 ----------------- Key: GPD-239 URL: https://jira.jboss.org/jira/browse/GPD-239 Project: JBoss jBPM GPD Issue Type: Task Reporter: Thomas Diesler Assignee: Koen Aers Fix For: jBPM jPDL Designer 3.1.5 Please release in time for jbpm-3.3.0.GA -- 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

17 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (GPD-237) Allign groupid with the rest of jbpm

by Thomas Diesler (JIRA)

Allign groupid with the rest of jbpm ------------------------------------ Key: GPD-237 URL: https://jira.jboss.org/jira/browse/GPD-237 Project: JBoss jBPM GPD Issue Type: Task Reporter: Thomas Diesler Assignee: Koen Aers Fix For: jBPM jPDL Designer 3.1.5 jBPM uses org.jboss.jbpm for its maven artefacts -- 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

17 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-215) org.jboss.hibernate.jbc.cacheprovider.TreeCacheProvider must implement org.hibernate.cache.CacheProvider

by Galder Zamarreno (JIRA)

org.jboss.hibernate.jbc.cacheprovider.TreeCacheProvider must implement org.hibernate.cache.CacheProvider -------------------------------------------------------------------------------------------------------- Key: JBCLUSTER-215 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-215 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Components: Hibernate-Cache-Provider Affects Versions: 1.0.0.GA Reporter: Galder Zamarreno Assignee: Galder Zamarreno Thanks to Matt Jensen for reporting this in my blog: http://galder.zamarreno.com/?p=56#comment-12 Matt Jensen 21:59 on October 29th, 2008 Am I missing something? I get ClassCastExceptions when I try to use org.jboss.hibernate.jbc.cacheprovider.TreeCacheProvider. Looking at the code, the class does not implement org.hibernate.cache.CacheProvider. It was implemented in Beta 3, but it does not implement it in 1.0.0.GA. Recompiling with "implements org.hibernate.cache.CacheProvider" on TreeCacheProvider *does* work.. -- 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

17 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1830) field names don't show up when using multiple field constraint in guided editor

by Jaroslaw Kijanowski (JIRA)

field names don't show up when using multiple field constraint in guided editor ------------------------------------------------------------------------------- Key: JBRULES-1830 URL: https://jira.jboss.org/jira/browse/JBRULES-1830 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.0.M2 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale trunk rev 23693 I'm creating a business rule using the guided editor. Adding a restriction on a filed works fine. However when I select a multiple field constraint (All of or Any of) and then add a restriction on a field, the name of the field does not show up. See screen shots for details. -- 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

17 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-3928) Replace jmx-invoker-service.xml with jmx-remoting.sar

by Scott M Stark (JIRA)

Replace jmx-invoker-service.xml with jmx-remoting.sar ----------------------------------------------------- Key: JBAS-3928 URL: http://jira.jboss.com/jira/browse/JBAS-3928 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX, Remoting Reporter: Scott M Stark Assigned To: Scott M Stark We need to complete the org.jboss.mx.remoting.service.JMXConnectorServerService jmx invoker to be at least as complete as the RMIAdaptor so we can replace the jmx-invoker-service.xml with the jmx-remoting.sar. -- 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

17 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6168) Modify the Bootstrap spi to pass the kernel deployments loaded by the Server bootstrap

by Scott M Stark (JIRA)

Modify the Bootstrap spi to pass the kernel deployments loaded by the Server bootstrap -------------------------------------------------------------------------------------- Key: JBAS-6168 URL: https://jira.jboss.org/jira/browse/JBAS-6168 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR2 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA Any KernelDeployments loaded by the Server implementation during the bootstrap need to be made available to the Bootstrap implementations registered with the server. -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-129) Release JBoss Deployers 2.0.0.CR5

by Ales Justin (JIRA)

Release JBoss Deployers 2.0.0.CR5 --------------------------------- Key: JBDEPLOY-129 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-129 Project: JBoss Deployers Issue Type: Release Components: release Affects Versions: JBDEPLOY-2.0.0.CR4 Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.0.0.GA Release notes: - -- 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

17 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1340) In memory session replication

by Tim Fox (JIRA)

In memory session replication ----------------------------- Key: JBMESSAGING-1340 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1340 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Priority: Critical Fix For: 2.0.0 Beta Implement in memory replication of sessions. It will be possible to replicate sessions to a backup node. The replication needs to happen in memory sychronously. Write to journal on both nodes can be lazy (asynchronous) since on failover we can be sure it is in memory on backup so no single point of failover. But can persist to disk asynchronously?? I think we can persist to disk asynchrnously on the master node, but needs to be synchronous on the backup node, in case we get a failure of the backup too shortly after failure of the master. If we can tolerate duplicate messages (or messages thought sent but not store) in a double failure then can do asynchronous storage on both master and slave. -- 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

17 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-128) Update JBoss VFS to 2.0.0.CR5

by Ales Justin (JIRA)

Update JBoss VFS to 2.0.0.CR5 ----------------------------- Key: JBDEPLOY-128 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-128 Project: JBoss Deployers Issue Type: Thirdparty Change Components: release Affects Versions: JBDEPLOY-2.0.0.CR4 Reporter: Ales Justin Assignee: Ales Justin Priority: Minor Fix For: JBDEPLOY-2.0.0.GA -- 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

17 years, 8 months

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