April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1214) drools-server should not have .settings commited into svn

by Geoffrey De Smet (JIRA)

drools-server should not have .settings commited into svn --------------------------------------------------------- Key: JBRULES-1214 URL: http://jira.jboss.com/jira/browse/JBRULES-1214 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.1 Reporter: Geoffrey De Smet Assigned To: Mark Proctor Priority: Trivial Fix For: FUTURE See JBRULES-834. As far as I can tell, the commit of /drools-server/.settings is an error because the other server modules explicitly svn:ignore the .settings directory. The svn ignore was probably forgotten, which might have given our good friend eclipse the opportunity to commit it. I could be wrong though. If I am right though, the .settings directory should be deleted in svn, which will cause havoc when everyone updates who's relying on .settings in drools-server, and the svn:ignore should be edited to contain these 3 items: .metadata .settings .wtpmodules This way it uses standardized svn ignores just like the other modules. -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1591) Newline in eval expression causes NullPointerException

by Brian Stiles (JIRA)

Newline in eval expression causes NullPointerException ------------------------------------------------------ Key: JBRULES-1591 URL: http://jira.jboss.com/jira/browse/JBRULES-1591 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Reporter: Brian Stiles Assigned To: Mark Proctor If a newline splits an eval expression, an NPE is thrown at org.drools.rule.PredicateConstraint.createContextEntry(PredicateConstraint.java:201). The following code demonstrates the problem. Removing the newline from the eval expression solves the problem. -- package sample; import java.io.StringReader; import org.drools.RuleBase; import org.drools.RuleBaseConfiguration; import org.drools.RuleBaseFactory; import org.drools.StatefulSession; import org.drools.compiler.PackageBuilder; import org.drools.compiler.PackageBuilderConfiguration; public class ExpressionProblem { public static class Tester { public boolean test(Object o1, Object o2) { return o1.equals(o2); } } public static void main(String[] args) throws Exception { final PackageBuilderConfiguration packageBuilderConfiguration = new PackageBuilderConfiguration(); final PackageBuilder packageBuilder = new PackageBuilder(packageBuilderConfiguration); packageBuilder.addPackageFromDrl(new StringReader("\n" + "package sample\n" + "\n" + "import sample.ExpressionProblem.Tester;\n" + "global sample.ExpressionProblem.Tester tester;\n" + "\n" + "rule MyRule\n" + "\n" + " when\n" + " Integer($f : this, eval(tester.test($f,\n" // OFFENDING NEWLINE + " $f)))\n" + " then \n" + " System.out.println($f);\n" + "end \n" + "")); final RuleBaseConfiguration ruleBaseConfiguration = new RuleBaseConfiguration(); final RuleBase ruleBase = RuleBaseFactory.newRuleBase(ruleBaseConfiguration); ruleBase.addPackage(packageBuilder.getPackage()); final StatefulSession session = ruleBase.newStatefulSession(false); session.setGlobal("tester", new Tester()); session.insert(1); session.fireAllRules(); } } -- 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, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (JBBUILD-346) Mavenize Docbook support

by Paul Gier (JIRA)

Mavenize Docbook support ------------------------ Key: JBBUILD-346 URL: http://jira.jboss.com/jira/browse/JBBUILD-346 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Fix For: MavenBuild 2.0 Migrate docbook-support from ant to maven. https://svn.jboss.org/repos/jbossas/trunk/docbook-support/ -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1241) Address EJB3 TestSuite Regressions

by Andrew Lee Rubinger (JIRA)

Address EJB3 TestSuite Regressions ---------------------------------- Key: EJBTHREE-1241 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1241 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Priority: Critical Fix For: AS 5.0.0.CR1 Parent Task to track regression-related fixes -- 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, 7 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-5182) Retire EJB3 JaccHelper

by Anil Saldhana (JIRA)

Retire EJB3 JaccHelper ---------------------- Key: JBAS-5182 URL: http://jira.jboss.com/jira/browse/JBAS-5182 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3, Security Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Priority: Critical Fix For: JBossAS-5.0.0.CR1 The entire EJB3 Jacc Layer needs to go. The Permissions creation will be done via a separate deployer working on the Metadata. The Policy enforcement will be done by the security layer. We have already consolidated the enforcement for web and ejb2 layers. -- 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, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-3828) spelling mistake in xml tag

by Goran Oberg (JIRA)

spelling mistake in xml tag --------------------------- Key: JBAS-3828 URL: http://jira.jboss.com/jira/browse/JBAS-3828 Project: JBoss Application Server Issue Type: Bug Affects Versions: JBossAS-4.0.4.GA Environment: All Reporter: Goran Oberg Priority: Trivial Just a spelling mistake... Should be <url-delimiter> instead of <url-delimeter> in <ha-local-tx-datasource> -- 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, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-953) wiki not visible

by Sacha Labourey (JIRA)

wiki not visible ---------------- Key: JBPORTAL-953 URL: http://jira.jboss.com/jira/browse/JBPORTAL-953 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: Sacha Labourey deploying wiki.war from portletswap in JBP deploy's folder doesn't make it visible in the list of creatable portlet (admin interface) -- 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, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JGRP-640) Shared protocols

by Bela Ban (JIRA)

Shared protocols ---------------- Key: JGRP-640 URL: http://jira.jboss.com/jira/browse/JGRP-640 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x Like the shared transport, investigate whether we can share other protocols. E.g. FD, FD_SOCK (preventing duplicate server sockets and sockets), Discovery and so on. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1228) Include org.jboss.ejb3.test.regression.unit Test

by Andrew Lee Rubinger (JIRA)

Include org.jboss.ejb3.test.regression.unit Test ------------------------------------------------ Key: EJBTHREE-1228 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1228 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 This pattern is currently not being run. -- 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, 7 months

2
14
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-983) Messages can be delivered after connection is stopped

by Tim Fox (JIRA)

Messages can be delivered after connection is stopped ----------------------------------------------------- Key: JBMESSAGING-983 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-983 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR1 Stopping a connection does not currently block until all current onMessage invocations are complete, as per JMS spec. We need to make sure it does. -- 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, 7 months

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