April 2008 - jboss-jira - Jboss List Archives

[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, 6 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, 6 months

3
14
0 / 0

[JBoss JIRA] Created: (JBRULES-1422) Prefix 'and' and infix 'and' not interchangeable

by Alexandre Gattiker (JIRA)

Prefix 'and' and infix 'and' not interchangeable ------------------------------------------------ Key: JBRULES-1422 URL: http://jira.jboss.com/jira/browse/JBRULES-1422 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.2 Reporter: Alexandre Gattiker The documentation on the 'and' Conditional Element seems to imply that these constructs are equivalent: $p1:Entity($code1:code) not (and $p2:Entity(code == $code1) eval(MyStaticClass.match($p1, $p2)) ) $p1:Entity($code1:code) not ( $p2:Entity(code == $code1) and eval(MyStaticClass.match($p1, $p2)) ) Actually, the first version crashes with this message: unknown:93:7 Unexpected token 'and'[96,2]: unknown:96:2 mismatched token: [@792,3685:3685=')',<12>,96:2]; expecting type THEN I'm on drools 4.0.2 and mvel14-1.2.8. -- 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, 6 months

3
11
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, 6 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, 6 months

4
17
0 / 0

[JBoss JIRA] Created: (JBAS-5326) Shutdown during deployment needs tiding up

by Adrian Brock (JIRA)

Shutdown during deployment needs tiding up ------------------------------------------ Key: JBAS-5326 URL: http://jira.jboss.com/jira/browse/JBAS-5326 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: MicroContainer bus Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.CR1 The shutdown while deployment/startup is occuring is a real mess at the moment this needs fixing such that we get at most one error (there will always be race conditions between internal service deployment and undeployment that are unexpected - but should be fixed as they are found) and with better communication between the "layers" no errors. -- 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, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-5328) Better signalling of shutdown

by Adrian Brock (JIRA)

Better signalling of shutdown ----------------------------- Key: JBAS-5328 URL: http://jira.jboss.com/jira/browse/JBAS-5328 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: MicroContainer bus Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.CR1 Currently within the shutdown we generally just do something like AtomicBoolean shutdown = new AutomaticBoolean(false); public void shutdown() { while (still deployments) removeDeployments(); shutdown.set(true); } public void deploy() { if (shutdown.get()) throw new IllegalStateException("Already shutdown"); } This needs improving to 1) Have a prepareShutdown() so we can signal that new deployments are not allowed earlier 2) The IllegalStateException should be replaced with a ShutdownException such that the caller can ignore such errors and deal with the shutdown more gracefully -- 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, 6 months

4
5
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, 6 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-3765) AOP-based version of RetryInterceptor

by Brian Stansberry (JIRA)

AOP-based version of RetryInterceptor ------------------------------------- Key: JBAS-3765 URL: http://jira.jboss.com/jira/browse/JBAS-3765 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB2, EJB3, Remoting Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta The (Single)RetryInterceptor only works for EJB 2. Need to: 1) Create a version that uses the AOP interceptor model rather than org.jboss.invocation. 2) Ensure all proxy factories bind an InvokerLocator in JNDI and include in the proxy metadata the location of the binding. 3) Add the interceptor to the various interceptor stack configs. -- 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, 6 months

8
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008