February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-674) Propagate changes in server list back to client when server side view change occurs

by Ovidiu Feodorov (JIRA)

Propagate changes in server list back to client when server side view change occurs ----------------------------------------------------------------------------------- Key: JBMESSAGING-674 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-674 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Clustering Reporter: Ovidiu Feodorov Fix For: 1.2.0.Beta1 Piggyback? Asynchronous notification? -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-840) Shutting down the Messaging service on JBoss 4.0.1sp1 fails

by Ovidiu Feodorov (JIRA)

Shutting down the Messaging service on JBoss 4.0.1sp1 fails ----------------------------------------------------------- Key: JBMESSAGING-840 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-840 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1267) Remove link border from tree images in the management portlet

by Thomas Heute (JIRA)

Remove link border from tree images in the management portlet ------------------------------------------------------------- Key: JBPORTAL-1267 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1267 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6.Beta1 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1261) Creation of new portal user into LDAP fails - not given role 'Authenticated' and password coded incorrectly

by Ian White (JIRA)

Creation of new portal user into LDAP fails - not given role 'Authenticated' and password coded incorrectly ----------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1261 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1261 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.Alpha2 Environment: AS 4.0.5.GA, Portal 2.6-alpha2, Win XP, Oracle 9i, OpenDS Reporter: Ian White Create a new portal user, either self register or do it via as the admin user. 2 problems stop the new user logging in: - The user gets created in my OpenDS repository, and is assigned the 'User' role, but not the 'Authenticated' role. - The password won't work 2 manual fixes are required before that user can login: - Using an LDAP GUI (JXeplorer), add the new user to the 'Authenticated' role (by adding a member attribute) - Using an LDAP GUI, change the password tp what it was supposed to be (get encoded again) Now you can login as that new user. Another way to do the above fixes without having to use an LDAP GUI is to create the new user using the admin account, then using the role and user portlets, assign the required roles to the new user and then change the new users password. QUESTION - why does there have to be that additional role ''Authenticated'anyway ? -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-727) ServerPeer.destroyQueue/destroTopic just undeploys, does not destroy

by Tim Fox (JIRA)

ServerPeer.destroyQueue/destroTopic just undeploys, does not destroy -------------------------------------------------------------------- Key: JBMESSAGING-727 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-727 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.CR1 The server peer methods destroyQueue/destroyTopic only undeploy the queue/topic, but do not destroy them (i.e. remove their messages). This differs from JBossMQ functionality where the destroy methods remove the messages too. We should change the implementation of destroyQueue/destroyTopic to actually destroy the destinations and introduce new methods undeploy/deploy to do the deployment. -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBREM-693) Make sure "bisocket" can fully replace "socket" as Messaging's default transport

by Ovidiu Feodorov (JIRA)

Make sure "bisocket" can fully replace "socket" as Messaging's default transport -------------------------------------------------------------------------------- Key: JBREM-693 URL: http://jira.jboss.com/jira/browse/JBREM-693 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ovidiu Feodorov Assigned To: Ron Sigal Priority: Blocker Fix For: 2.2.0.Alpha7 -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-846) release-admin.xml installation script does not correctly configures BindingManager for newly created clustered configurations, in some situations

by Ovidiu Feodorov (JIRA)

release-admin.xml installation script does not correctly configures BindingManager for newly created clustered configurations, in some situations ------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-846 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-846 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.CR1 Noticed with 4.0.1sp1 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-586) DefaultExpander incorrectly strips leading and trailing spaces

by Adam Lewandowski (JIRA)

DefaultExpander incorrectly strips leading and trailing spaces -------------------------------------------------------------- Key: JBRULES-586 URL: http://jira.jboss.com/jira/browse/JBRULES-586 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.5 Reporter: Adam Lewandowski Assigned To: Mark Proctor When using a DSL expander, token values with leading or trailing spaces get the spaces stripped when inserted into the target template. This causes the resulting rule definition to be incorrect. Example: DSL: [when]String is "{value}"=SomeFact(value=="{value}") Input string (note the trailing space): String is "blah " Expanded string (note the lack of a trailing space): SomeFact(value=="blah") The same thing occurs for leading spaces as well. Internal spaces are fine. Also interesting is that if there are more than one leading/trailing space, NLExpressionCompiler throws an IllegalArgumentException: Expression was not expandable: String is " blah" The problem seems to be in the org.drools.lang.dsl.template.Chunk class. It is stripping the leading/trailing spaces from values in the map populated by buildValueMap(). Unit Test: import java.io.StringReader; import org.drools.lang.dsl.DefaultExpander; import junit.framework.TestCase; public class DroolsDslTemplateTest extends TestCase { private DefaultExpander expander; public void setUp() { String DSL = "[when]String is \"{value}\"=SomeFact(value==\"{value}\")"; StringReader dslSrc = new StringReader(DSL); expander = new DefaultExpander(dslSrc); } public void testExpandNoSpaces() { String result = expander.expand("when", "String is \"blah\""); assertEquals("SomeFact(value==\"blah\")", result); } public void testExpandWithLeadingSpace() { String result = expander.expand("when", "String is \" blah\""); assertEquals("SomeFact(value==\" blah\")", result); } public void testExpandWithMultipleLeadingSpaces() { String result = expander.expand("when", "String is \" blah\""); assertEquals("SomeFact(value==\" blah\")", result); } public void testExpandWithTrailingSpace() { String result = expander.expand("when", "String is \" blah \""); assertEquals("SomeFact(value==\"blah \")", result); } public void testExpandWithMultipleTrailingSpaces() { String result = expander.expand("when", "String is \"blah \""); assertEquals("SomeFact(value==\"blah \")", result); } public void testExpandWithInternalSpace() { String result = expander.expand("when", "String is \"bl ah\""); assertEquals("SomeFact(value==\"bl ah\")", result); } public void testExpandWithMultipleInternalSpaces() { String result = expander.expand("when", "String is \"bl ah\""); assertEquals("SomeFact(value==\"bl ah\")", result); } } -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBRULES-268) Line based parser and expanderer

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-268?page=all ] Edson Tirelli closed JBRULES-268. --------------------------------- Fix Version/s: 3.1-m2 (was: 3.1-m3) Resolution: Done $ svn log -r 9538 -v ------------------------------------------------------------------------ r9538 | tirelli | 2007-02-15 17:49:28 -0300 (Thu, 15 Feb 2007) | 12 lines Changed paths: M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/compiler/DrlParser.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/compiler/ParserError.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/DRLLexer.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/DRLParser.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/Expander.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/ExpanderException.java A /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/dsl/DSLMapping.java A /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/dsl/DSLMappingEntry.java A /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/dsl/DSLMappingFile.java A /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/dsl/DSLMappingParseException.java A /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/dsl/DefaultDSLMappingEntry.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/dsl/DefaultExpander.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/dsl/DefaultExpanderResolver.java D /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/dsl/LineBasedExpander.java D /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/dsl/template M /labs/jbossrules/trunk/drools-compiler/src/main/resources/org/drools/lang/DRL.g M /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/integrationtests/IntegrationCases.java M /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/lang/MockExpander.java M /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/lang/RuleParserTest.java A /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/lang/dsl/DSLMappingFileTest.java A /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/lang/dsl/DefaultDSLMappingEntryTest.java A /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/lang/dsl/DefaultExpanderTest.java D /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/lang/dsl/LineExpanderTest.java D /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/lang/dsl/template A /labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/lang/dsl/test_expansion.drl A /labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/lang/dsl/test_metainfo.dsl JBRULES-268 JBRULES-274 JBRULES-351 JBRULES-476 JBRULES-586: * Removed DSL parsing from the DRL parser (JBRULES-351) * Implemented a DSL preprocessor ( Expander ) based on regexp (JBRULES-351) * Implemented a new DSL file parser for map readings * Added ability to expand a DSL and get the result without parsing DRL (JBRULES-268) * Fixed problems with empty lines (JBRULES-274) * Made DSL preprocessor space insentive (JBRULES-476) * Fixed problems with capturing spaces (JBRULES-586) * Added unit tests and integration tests ------------------------------------------------------------------------ > Line based parser and expanderer > -------------------------------- > > Key: JBRULES-268 > URL: http://jira.jboss.com/jira/browse/JBRULES-268 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Affects Versions: 3.0-rc2 > Reporter: Michael Neale > Assigned To: Edson Tirelli > Fix For: 3.1-m2 > > Attachments: line-expander.zip > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Have a need to parse unexpanded DSLs, and then expand them to display, before passing to the parser. > If an error occurs, will need to track errors like the real parser (and possibly add them as real parser errros down the track). > This is needed for UIs, as well as getting rid of expanding from the main parser (which has another JIRA). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-476) DSL constraint appending needs to be tolerant of spaces

by Michael Neale (JIRA)

DSL constraint appending needs to be tolerant of spaces ------------------------------------------------------- Key: JBRULES-476 URL: http://jira.jboss.com/jira/browse/JBRULES-476 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Reporter: Michael Neale Assigned To: Michael Neale If you do [when]-foo bar=Baz() it will fail to expand unless you put a space after the "-". -- 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, 3 months

2
2
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 February 2007