August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-1279) shutdown -u -p options are not working

by krish p (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1279?page=comments#action_12373400 ] krish p commented on JBAS-1279: ------------------------------- Is this fixed in 4.0.5? I see this issue when JBoss Portal 2.6 is deployed in JBoss and I try running "shutdown.sh -S -u admin". I've used a custom security realm and updated jmx-invoker-service.xml accordingly. > shutdown -u -p options are not working > -------------------------------------- > > Key: JBAS-1279 > URL: http://jira.jboss.com/jira/browse/JBAS-1279 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.1 Final > Reporter: Wonne Keysers > Assigned To: Scott M Stark > Fix For: JBossAS-4.0.2RC1 > > > This feature does work in 3.2.x, but is apparently not yet implemented in 4.0.1 ? > Unable to shutdown the server when the following is commented out in jmx-invoker-service.xml: > <descriptors> > <interceptors> > <interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor" > securityDomain="java:/jaas/jmx-console"/> > </interceptors> > </descriptors> -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1101) MVEL direct property accessors being converted to a ReturnValueConstraint

by Yuri de Wit (JIRA)

MVEL direct property accessors being converted to a ReturnValueConstraint ------------------------------------------------------------------------- Key: JBRULES-1101 URL: http://jira.jboss.com/jira/browse/JBRULES-1101 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.GA Reporter: Yuri de Wit Assigned To: Mark Proctor After narrowing down a performance issue with my drools app, I reached to the dev team and quickly it became clear that for some reason drools was not indexing my field constraints. After some investigation and some help from Conan it became clear that one of the problem was that MVEL direct property accessors were being translated into a ReturnValueConstraint (afaik, an eval), which cannot be indexed by default. So I changed my rules to make sure that i used aliaes for the first 3 constrraints instead of property accessors and I was able to see trememdous perf improvements for my usecases. -- 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

18 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1065) Unable to return Declaration for identifier

by Tong Lee (JIRA)

Unable to return Declaration for identifier ------------------------------------------- Key: JBRULES-1065 URL: http://jira.jboss.com/jira/browse/JBRULES-1065 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.GA Environment: Windows XP, Java 1.6 Reporter: Tong Lee Assigned To: Mark Proctor I've read in the 4.0 features list where implicit binding for value expressions will be available in the 4.0 release. I've downloaded 4.0GA and still getting the compiler error. We have a need for the following and wondering if I'm misunderstanding the functionality: Fact/bean object code: public class Record { private String abc; private String xyz; public String getAbc()... public String getXyz()... ... } DRL code: rule "..." when $record : Record ( abc == xyz) then .... end The PackageBuilder can not resolve the "xyz" I understand we can define the Record alias and then reference xyz using the alias (see example below) but it would be asking too much for our business users. rule "..." when r: Record ( ) $record : Record ( abc == r.xyz) then .... end Any feedback with this is greatly appreciated!!! -- 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

18 years, 11 months

4
12
0 / 0

[JBoss JIRA] Created: (SECURITY-75) SecurityAssociation on the Client Side

by Anil Saldhana (JIRA)

SecurityAssociation on the Client Side -------------------------------------- Key: SECURITY-75 URL: http://jira.jboss.com/jira/browse/SECURITY-75 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.1-BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1-GA Clients may have done deeper integration with security association (in lieu of JAAS). The principal/credential needs to be transferred into a security context. -- 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

18 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1055) Regex-Special characters can not be used in DSLs.

by Michael Wiedmer (JIRA)

Regex-Special characters can not be used in DSLs. ------------------------------------------------- Key: JBRULES-1055 URL: http://jira.jboss.com/jira/browse/JBRULES-1055 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.GA Environment: Windows XP, Java 5 Reporter: Michael Wiedmer Assigned To: Mark Proctor Up until Drools 3.0.6 one could write DSLs to allow expressions such as EXAMPLE IS IN [ "one" "two"] This has changed now. The square brackes (being part of special characters for regular expressions) deny the DefaultDSLMappingEntry class to define a valid keyPattern. Here is a (not) working example, using the default sample project: 8<---- regexError.drl ----- package some.test import com.sample.*; expander regexError.dsl rule "Test" when STRING "UK" IS IN < "USA", "UK", "GERMANY" > then LOG "Square Brackets will not work." end 8<---- regexError.dsl ----- [consequence][]LOG {msg}=System.out.println({msg}); [condition][]STRING "{string}" IS IN < {sequence} >=eval(true == true) 8<---- DroolsTest.javal ----- package com.sample; import java.io.InputStreamReader; import java.io.Reader; import org.drools.RuleBase; import org.drools.RuleBaseFactory; import org.drools.WorkingMemory; import org.drools.compiler.PackageBuilder; import org.drools.rule.Package; public class DroolsTest { public static final void main(String[] args) { try { // load up the rulebase RuleBase ruleBase = readRule(); WorkingMemory workingMemory = ruleBase.newStatefulSession(); // go ! Message message = new Message(); message.setMessage("Hello World"); message.setStatus(Message.HELLO); workingMemory.insert(message); workingMemory.fireAllRules(); } catch (Throwable t) { t.printStackTrace(); } } private static RuleBase readRule() throws Exception { Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/regexError.drl")); Reader dsl = new InputStreamReader(DroolsTest.class.getResourceAsStream("/regexError.dsl")); PackageBuilder builder = new PackageBuilder(); builder.addPackageFromDrl(source, dsl); Package pkg = builder.getPackage(); RuleBase ruleBase = RuleBaseFactory.newRuleBase(); ruleBase.addPackage(pkg); return ruleBase; } } If one was to change the files regexError.dsl and regexError.drl and use square brackets instead of angle brackets, the DroolsTest will fail with the same error as shown in the Eclipse IDE: org.drools.rule.InvalidRulePackage: org.drools.lang.ExpanderException@14c1103[9,2]: unknown:9:2 Unexpected token 'STRING'[9,22]: unknown:9:22 mismatched token: [@31,115:119='"USA"',<20>,9:22]; expecting type RIGHT_SQUARE[11,1]: unknown:11:1 mismatched token: [@43,150:155='System',<8>,11:1]; expecting type RIGHT_PAREN[11,20]: unknown:11:20 mismatched token: [@49,169:200='"Square Brackets will not work."',<20>,11:20]; expecting type RIGHT_PAREN[12,0]: unknown:12:0 mismatched token: [@53,205:207='end',<15>,12:0]; expecting type THEN at org.drools.rule.Package.checkValidity(Package.java:408) at org.drools.common.AbstractRuleBase.addPackage(AbstractRuleBase.java:288) at com.sample.DroolsTest.readRule(DroolsTest.java:44) at com.sample.DroolsTest.main(DroolsTest.java:18) It does not matter what the RHS of the DSL says, as the LHS will not be matched in DefaultExpander.expandLHS(final String lhs, int lineOffset), line 231. -- 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

18 years, 11 months

3
5
0 / 0

[JBoss JIRA] Commented: (JBAS-2853) Integrate JBoss Cache 2.0 into AS 5.0

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2853?page=comments#action_12373339 ] Brian Stansberry commented on JBAS-2853: ---------------------------------------- I have to sort it out with Tim Fox, i.e. get consensus on adding it to the JBM component-info.xml. Otherwise build breaks. We chatted a bit about that around beg of July, but it got somewhat sidetracked with some discussion about JBM in 4.2. ;) I'll ping him again. > Integrate JBoss Cache 2.0 into AS 5.0 > ------------------------------------- > > Key: JBAS-2853 > URL: http://jira.jboss.com/jira/browse/JBAS-2853 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Manik Surtani > Assigned To: Brian Stansberry > Priority: Critical > Fix For: JBossAS-5.0.0.Beta3 > > > JBC 2.0.0.ALPHA1 was produced for JB5, Beta1. > I'm assigning this issue to the next beta, to track further integration issues. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-403) Add config parameter to specify groupId in jboss deploy plugin

by Paul Gier (JIRA)

Add config parameter to specify groupId in jboss deploy plugin -------------------------------------------------------------- Key: JBBUILD-403 URL: http://jira.jboss.com/jira/browse/JBBUILD-403 Project: JBoss Build System Issue Type: Feature Request Components: maven-jboss-deploy-plugin Affects Versions: maven-jboss-deploy-plugin-1.3 Reporter: Paul Gier Add a parameter to use a different groupId. This will allow deployment to the jboss directory when the maven groupId is "org.jboss.something". -- 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

18 years, 11 months

1
3
0 / 0

[JBoss JIRA] Commented: (JBAS-2853) Integrate JBoss Cache 2.0 into AS 5.0

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2853?page=comments#action_12373333 ] Dimitris Andreadis commented on JBAS-2853: ------------------------------------------ I see the trunk moved to 2.0.0.GA. Are we updating JGroups, too? (2.5) > Integrate JBoss Cache 2.0 into AS 5.0 > ------------------------------------- > > Key: JBAS-2853 > URL: http://jira.jboss.com/jira/browse/JBAS-2853 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Manik Surtani > Assigned To: Brian Stansberry > Priority: Critical > Fix For: JBossAS-5.0.0.Beta3 > > > JBC 2.0.0.ALPHA1 was produced for JB5, Beta1. > I'm assigning this issue to the next beta, to track further integration issues. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBBUILD-259) Migrate AOP builds to maven

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-259?page=all ] Paul Gier updated JBBUILD-259: ------------------------------ Summary: Migrate AOP builds to maven (was: AOP pom) > Migrate AOP builds to maven > --------------------------- > > Key: JBBUILD-259 > URL: http://jira.jboss.com/jira/browse/JBBUILD-259 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: Maven Build - App Server > > Time Spent: 1 day > Remaining Estimate: 3 days > > Migrate AOP builds to maven. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JGRP-203) Primary Partiton approach for handling of partitions

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-203?page=comments#action_12373306 ] Bela Ban commented on JGRP-203: ------------------------------- I don't see why PRIMARY_PARTITION needs to sort the MergeView is receives: a MergeView is only created by the *merge leader*, and therefore it will be exactly the same on all merge cordinators. So we don't need to sort it. A much simpler implementation could be to deterministically find out the primary partition and then send EXIT events to all members in non-primary partitions. Even simpler: there could be an option in JChannel that triggers an EXIT if we're not in the primary partition on reception of a MergeView. User code could be called to determine the primary partition > Primary Partiton approach for handling of partitions > ---------------------------------------------------- > > Key: JGRP-203 > URL: http://jira.jboss.com/jira/browse/JGRP-203 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.6 > > Attachments: PRIMARY_PARTITION.java > > > Add this approach to JGroups. Members in a non-primary partition will shut down, become read-only etc. > Google for "primary partition AND group communication" for the relevant literature on this -- 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

18 years, 11 months

1
0
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 August 2007