jboss-jira February 2009

jboss-jira@lists.jboss.org

1 participants
1936 discussions

[JBoss JIRA] Created: (JBRULES-1811) syntax errors caused by use of special characters in decision table cells

by Frank Langelage (JIRA)

syntax errors caused by use of special characters in decision table cells ------------------------------------------------------------------------- Key: JBRULES-1811 URL: https://jira.jboss.org/jira/browse/JBRULES-1811 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 4.0.7 Environment: JBoss-4.24GA with Drools 4.0.7 on Solaris Sparc 10, Sun JDK 1.6.0_07 Reporter: Frank Langelage Assignee: Mark Proctor A customer entered item codes with special characters into an decision table. This caused syntax errors on the generated code. The item codes contained dimension in inches and they used a double quote for the unit (e.g. '... 24"....'). As this double quotes terminate a string, the generated code out of the decision table is invalid. If a double quote sign is in the cell content this double quote must be masked by inserting a backslash character automatically. So we would get "....24\"...." as the string literal in generated code. >From our opinion it's not acceptable to force the user who fills in the data cells into the spreadsheet to learn java and masquerade problematic characters by inserting the backslash in front of them. -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2279) Can't change theme of Configure Dashboard page

by Fernando Ribeiro (JIRA)

Can't change theme of Configure Dashboard page ---------------------------------------------- Key: JBPORTAL-2279 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2279 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.7.0 Final Reporter: Fernando Ribeiro The theme can't be changed unless you change the layouts in portal-core.war. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2280) Allow Dashboard to be disabled

by Fernando Ribeiro (JIRA)

Allow Dashboard to be disabled ------------------------------ Key: JBPORTAL-2280 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2280 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.7.0 Final Reporter: Fernando Ribeiro In many portal projects, it may not be needed to have dashboards, and they can't really be disabled by changing descriptors or JSPs, for example, in the distribution. -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1440) JTA-prepared message delivered to other consumer.

by szhigunov (JIRA)

JTA-prepared message delivered to other consumer. -------------------------------------------------- Key: JBMESSAGING-1440 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1440 Project: JBoss Messaging Issue Type: Bug Environment: JBoss 4.2.2 + JBM 1.4.0.SP3. Windows XP. Reporter: szhigunov Assignee: Tim Fox The problem is that when fully prepared tx1 fails in the commit phase, JBM delivers the message second time in tx2, while tx1 is still in progress. Eventually recovery commits tx1, so the message gets delivered and committed twice. The attached test (myxatest.zip) is a clean JBoss 4.2.2 + JBM 1.4.0 SP3 with my test MBean: jboss-4.2.2.GA\server\messaging\lib\myxatest.jar (code and source) + jboss-4.2.2.GA\server\messaging\deploy\myxatest-service.xml. Steps to reproduce the problem: 1. Start the server. 2. Go to JMX console + myxatest + service=Test. Invoke send. 3. Go to JMX console + jboss.messaging.destination + name=A.service=Queue. Verify MessageCount=1. 4. Go to JMX console + myxatest + service=Test. Invoke receive. That will start XA transaction; enlist DummyXAResource; get JMS connection from JCA and receive message. DummyXAResource sleeps 60 sec inside the commit call. 5. Verify that DummyXAResource prints "DummyXAResource commit start sleeping for 60 sec" message. 6. Go to JMX console + jboss.jca + name=JmsXA,service=ManagedConnectionPool and invoke stop(). Check that DummyXAResource finished commit and printed "DummyXAResource commit end" message. JBM commit fails. 7. Now we have fully prepared JBM transaction in progress. You can see one record in JBM_TX. 8. Go to JMX console + jboss.jca + name=JmsXA,service=ManagedConnectionPool and invoke start(). 9. Go to JMX console + myxatest + service=Test. Invoke receive again. Same message delivered again. And this is wrong. Wait for a minute and let transaction finish successfully. 10. Got to JBM_TX and verify that transaction is still there (nobody recovered it!). 11. Stop server, enable JBM recovery, start server. In couple minutes the original transaction is found and committed (second time). JBM_TX is empty. -- 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, 9 months

4
19
0 / 0

[JBoss JIRA] Created: (JBMETA-166) rar.xml coverage testcase

by Jeff Zhang (JIRA)

rar.xml coverage testcase ------------------------- Key: JBMETA-166 URL: https://jira.jboss.org/jira/browse/JBMETA-166 Project: JBoss Metadata Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.GA as talked with Jesper, we would like do full coverage test against rar.xml. include positive, negative, piece of xml file includes some elements test -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAOP-582) Javassist cannot find JoinPoint classes

by Flavia Rainone (JIRA)

Javassist cannot find JoinPoint classes --------------------------------------- Key: JBAOP-582 URL: http://jira.jboss.com/jira/browse/JBAOP-582 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR10 Reporter: Flavia Rainone Javassist cannot find JoinPoint classes when the class loader is not a jvm or JBoss class loader. -- 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, 9 months

1
4
0 / 0

← Newer
1
...
191
192
193
194
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2009