December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1390) Add support to streams

by Edson Tirelli (JIRA)

Add support to streams ---------------------- Key: JBRULES-1390 URL: http://jira.jboss.com/jira/browse/JBRULES-1390 Project: JBoss Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assigned To: Edson Tirelli -- 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

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1023) Typing the parameter to be replace by DSL/DRL replacement

by christian bastin (JIRA)

Typing the parameter to be replace by DSL/DRL replacement --------------------------------------------------------- Key: JBRULES-1023 URL: http://jira.jboss.com/jira/browse/JBRULES-1023 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: christian bastin Assigned To: Mark Proctor We have a very long DSL including more 150 différent lines (wich could be very similar). We have no posibility to be sure of the replacement operarted by the parsing. We often dicover problem that force us to move the order of the lines in the DSL. This is an simple example of what I think could be improved. If you have a DSL test {code} is {value} this could replace this 2 rules in the DRL rule "Rule-1" when test 10 is 10 then > System.out.println("test 1 OK"); end rule "Rule-1" when test 10 + 10 is 10 then > System.out.println("test 1 OK"); end I would like the ability to type the parameter of my DSL, for example with regular expression. test {code|[0-9]+} is {value|[0-9]+} so the only rule available for replacement should be the first rule ("Rule-1"). The other rule would not find a replacement and should be implemented in the DSL. -- 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

15 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1331) Implement CEP/ESP support into Drools

by Edson Tirelli (JIRA)

Implement CEP/ESP support into Drools ------------------------------------- Key: JBRULES-1331 URL: http://jira.jboss.com/jira/browse/JBRULES-1331 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 4.1.0 This is the parent ticket for CEP/ESP support development -- 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

15 years, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (JBRULES-380) Create some decision table examples

by william hayhurst (JIRA)

Create some decision table examples ----------------------------------- Key: JBRULES-380 URL: http://jira.jboss.com/jira/browse/JBRULES-380 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Decision tables, Documentation Affects Versions: 3.0 Reporter: william hayhurst Assigned To: Mark Proctor Attachments: barbarian.xls As per IRC, some more fleshed out examples of decision tables in action. -- 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

15 years, 4 months

5
14
0 / 0

[JBoss JIRA] Created: (JBAS-3834) i18n of jmx-console

by Ryusuke Kajiyama (JIRA)

i18n of jmx-console ------------------- Key: JBAS-3834 URL: http://jira.jboss.com/jira/browse/JBAS-3834 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.4.GA Environment: Any operating system with multiple language such as MS932 (Japanese) Reporter: Ryusuke Kajiyama We found that there are difference in screen-displayed multibyte characters on using Internet Explorer and Firefox. When using MS932, with IE, characters are returned same as posted, however with Firefox, characters are url-escaped like %xx. Our guess is that html of jmx-console does not have charset and there are no functions to handle encoding request parameter. It could be fixed if there were some filter action something like distinguish character set of posted data, and add <meta> tag into html or set Content-Type. -- 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

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1278) DSL Parser "eval"

by M H (JIRA)

DSL Parser "eval" ----------------- Key: JBRULES-1278 URL: http://jira.jboss.com/jira/browse/JBRULES-1278 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1 Reporter: M H Assigned To: Mark Proctor Priority: Blocker rule "PatternTest" when $pli:Item( title matches "^Test\s*") then # end this one compiles but on Runtime it ends in an Exception when title looks for example like this "BlaBla (Test)". as workaround i thought about using the next part, but rule "PatternTest" when $pli:Item( eval(title.matches("^Test\s*")) ) then # end it resolves into, also it shouldn't (because title.matches() is Java Code a shouldn't be parsed by the DSL Parser itself): SyntaxfehlerRule Compilation error : [Rule name=OnlineStreaming Start, agendaGroup=MAIN, salience=100, no-loop=true] com/p7s1/swi/phoenix/n24/Rule_OnlineStreaming_Start_0.java (19:923) : Invalid escape sequence (valid ones are \b \t \n \f \r \" \' \\ ) -- 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

15 years, 4 months

3
14
0 / 0

[JBoss JIRA] Created: (JGRP-645) Replace use of commons-logging with java.util.logging (JDK logging)

by Bela Ban (JIRA)

Replace use of commons-logging with java.util.logging (JDK logging) ------------------------------------------------------------------- Key: JGRP-645 URL: http://jira.jboss.com/jira/browse/JGRP-645 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 - Wrapper for java.util.logging which provides commons-logging interface to java.util.logging - Once this is done, we can drop commons-logging.jar and log4j.jar -- 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

15 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-4154) Get the server to run under a security manager

by Scott M Stark (JIRA)

Get the server to run under a security manager ---------------------------------------------- Key: JBAS-4154 URL: http://jira.jboss.com/jira/browse/JBAS-4154 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Scott M Stark Assigned To: Scott M Stark The testsuite tests-security-manager target was failing due to the aop layer not creating classes with correct ProtectionDomains. This is fixed in (JBAOP-368). The next problem is that the server.policy needs to use vfsfile urls for the permission assignments. However, because these are URLs and not URIs, there has to be a URL handler available when the policy is read at bootstrap. Currently a policy entry like: grant codeBase "vfsfile:${jboss.home.dir}/lib/-" { permission java.security.AllPermission; }; fails because the jboss vfsfile URL handler is unknown: policy: Adding policy entry: policy: signedBy null policy: codeBase vfsfile:/tmp/trunk/build/output/jboss-5.0.0.Beta2/lib/- java.security.policy: error adding Entry: java.net.MalformedURLException: unknown protocol: vfsfile policy: -- 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

15 years, 4 months

4
17
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-148) Implement ScopedKernel

by Ales Justin (JIRA)

Implement ScopedKernel ---------------------- Key: JBMICROCONT-148 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-148 Project: JBoss MicroContainer Issue Type: Feature Request Components: Kernel Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC-2.0.0.GA Implement support for scoped deployments on top of scoped metadata. -- 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

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-217) Create KernelDeployment from .properties file

by Ales Justin (JIRA)

Create KernelDeployment from .properties file --------------------------------------------- Key: JBMICROCONT-217 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-217 Project: JBoss MicroContainer Issue Type: Feature Request Components: Deployment Reporter: Ales Justin Assigned To: Ales Justin Priority: Minor Fix For: JBossMC-2.0.0.GA Create deployment/bean metadata from -beans.properties files. e.g. test-beans.properties: (deployment).name=PropDeployment mybean.(class)=org.jboss.acme.MyBean mybean.somenumber=123L mybean.somenumber.type=long sndbean.(class)=org.jboss.acme.SndBean sndbean.(constructor).(parameter)=foobar sndbean.(constructor).(parameter)=123 starter.(class)=org.jboss.acme.Starter starter.(start)=onStart starter.(start).(parameter)=(inject).mybean -- 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

15 years, 4 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007