May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-64) When opening up processDefintion.xml created in 3.0.13 with the graphic designer all transtions are not showing up visually

by Bill Ted (JIRA)

When opening up processDefintion.xml created in 3.0.13 with the graphic designer all transtions are not showing up visually --------------------------------------------------------------------------------------------------------------------------- Key: GPD-64 URL: http://jira.jboss.com/jira/browse/GPD-64 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.alpha3 Environment: Eclipse 3.2 Reporter: Bill Ted Assigned To: Koen Aers After creating process definitions with the eclipse plugin 3.0.13 and then installing the 3.1 alpha 3 version of the designer plugin you can open up the process definitions, but all the transitions are no longer visable. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBAOP-385) Uniformize Advice Exception Treatment

by Flavia Rainone (JIRA)

Uniformize Advice Exception Treatment ------------------------------------- Key: JBAOP-385 URL: http://jira.jboss.com/jira/browse/JBAOP-385 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Flavia Rainone Assigned To: Flavia Rainone Priority: Minor Fix For: 2.0.0.alpha5 The treatment of exceptions in PerVMAdvice is different from the one in JoinPointGenerator. We need to pick one of them and use the same approach on both cases. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1397) WSRP Consumer configuration GUI improvements

by Chris Laprun (JIRA)

WSRP Consumer configuration GUI improvements -------------------------------------------- Key: JBPORTAL-1397 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1397 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.CR2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6 Final Chris DeLashmutt says: In the WSRP page, the pages portlet should be removed as it duplicates the same information as is in the Navigation tabs. Configured WSRP Consumers View Need more horizontal spacing between the "Create a consumer named:" label and the text box it is a label for. Need more vertical spacing between the consumer creation UI elements, and then defined consumer list. The Legend for the consumer list should not be (or appear to be) a row within the consumer list. This element should be below or above the consumer list. Linking the consumer name and providing an Action called "Configure" that both go to the same function is redundant. Either remove the Configure action or un-link the consumer name. The actions for the consumer should not be styled the same as the consumer name. I could cause confusion as users may percieve the actions are "active", "inactive", or "need refresh". There should be a space after the "pipe" separator in the WSRP consumer list to be consistent with the other action lists in the administrative portal. Consider using icon images (with alt attributes set to the name of the function) for actions in the list. Configuration View The form labels in this view are inconsistent with all the other field labels in the portlets in the administrative portal. I'm not saying they are bad (in fact, I personally prefer the style of these labels over the others), but they need to be made consistent with the rest of the admin portal labels, or the rest of the admin portal labels should be made to look like these labels. The vertical bars in front of the fields in this view are inconsistent with all of the other fields in the admin portal. The bars need to be removed. The buttons "Refresh", "Activate" and "Destroy" shouldn't be in the view that deals with changing the configuration of a WSRP consumer. These buttons should be removed. The "Save" and "Return to list" buttons should be on the left-bottom side of the portlet, and they should be sized, aligned, and padded consistently. The "Return to list" button label should be changed to "Cancel". -- 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
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1043) Upgrade to a reasonably stable JBoss AOP version

by Manik Surtani (JIRA)

Upgrade to a reasonably stable JBoss AOP version ------------------------------------------------ Key: JBCACHE-1043 URL: http://jira.jboss.com/jira/browse/JBCACHE-1043 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 2.0.0.CR1 Reporter: Manik Surtani Assigned To: Jason T. Greene Fix For: 2.0.0.CR2, 2.0.0.GA Need to speak to Kabir -- 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: (JBMESSAGING-793) Modify testing framework to pick the file containing JGroups stack configurations based on the database tests are currently running in top of

by Ovidiu Feodorov (JIRA)

Modify testing framework to pick the file containing JGroups stack configurations based on the database tests are currently running in top of --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-793 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-793 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA A place where this is currently hardcoded to use mysql is org.jboss.test.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOfficeTest.createClusteredPostOffice(). -- 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

4
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-624) Running on DB2

by Tomaz Cerar (JIRA)

Running on DB2 -------------- Key: JBMESSAGING-624 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-624 Project: JBoss Messaging Issue Type: Patch Components: Messaging Core Persistence Affects Versions: 1.0.1.GA Environment: jboss messaging 1.0.1GA, windows xp, DB2 8.2 iSeries Reporter: Tomaz Cerar Assigned To: Ovidiu Feodorov To make jboss messaging 1.0.1GA work with DB2 there must be attribute UsingBinaryStream in class JDBCPersistenceManager made configurable from service file. in JDBCPersistenceManager you add methods: /** * Managed attribute. */ public boolean isUsingBinaryStream()throws Exception { return usingBinaryStream; } /** * Managed attribute. */ public void setUsingBinaryStream(boolean usingBinaryStream)throws Exception { this.usingBinaryStream = usingBinaryStream; } and in JDBCPersistenceManager-xmbean.xml you have to add: <attribute access="read-write" getMethod="isUsingBinaryStream" setMethod="setUsingBinaryStream"> <description>Should JDBC read as binary stream be used?</description> <name>UsingBinaryStream</name> <type>boolean</type> </attribute> db2-persistence-service.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

6
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration

by Ovidiu Feodorov (JIRA)

Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration ------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-861 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-861 Project: JBoss Messaging Issue Type: Feature Request Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA Tim: wrt our discussion about OOM errors in HTTP tests, I notice the service container is currently using the BlockingCallbackStore: String params = "/?" + marshallers + "serializationtype=" + serializationType + "&" + dataType + "socket.check_connection=false&" + "clientLeasePeriod=" + clientLeasePeriod + "&" + "callbackStore=org.jboss.remoting.callback.BlockingCallbackStore&" + "clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&" + "serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper&" + "NumberOfRetries=1&" + "NumberOfCallRetries=2&" + "callbackErrorsAllowed=1&" + "onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool"; but the remoting-service.xml is using the standard callback store: <attribute name="leasePeriod">10000</attribute> <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute> <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute> -- 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
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-919) Revive the performance framework

by Ovidiu Feodorov (JIRA)

Revive the performance framework -------------------------------- Key: JBMESSAGING-919 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-919 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.1.CR1 This is a container for all issues related to re-starting using the perfomance framework -- 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
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-938) Implement maxDeliveryAttempts on destinations

by Tim Fox (JIRA)

Implement maxDeliveryAttempts on destinations --------------------------------------------- Key: JBMESSAGING-938 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-938 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1.CR1 For some reason this seems to have been omitted -- 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
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-960) ClusteredPostOffices are bound to 127.0.0.1 on JGroups config

by Clebert Suconic (JIRA)

ClusteredPostOffices are bound to 127.0.0.1 on JGroups config ------------------------------------------------------------- Key: JBMESSAGING-960 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-960 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.SP1 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.SP2 We should verify what to do with bind-addr: mcast_addr="228.8.8.8" use_outgoing_packet_handler="true" loopback="true" ucast_send_buf_size="32000" ip_ttl="32" bind_addr="127.0.0.1"/> -- 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

4
11
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 May 2007