April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4378) Welcome page ignores console-enabled setting

by Carlo de Wolf (JIRA)

Carlo de Wolf created AS7-4378: ---------------------------------- Summary: Welcome page ignores console-enabled setting Key: AS7-4378 URL: https://issues.jboss.org/browse/AS7-4378 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.1.Final Environment: Fedora 17 Reporter: Carlo de Wolf Assignee: Remy Maucherat The welcome web context is populated either with console links or without based on the existence of the http management port. This is wrong as it might just have the [HTTP Management API|https://docs.jboss.org/author/display/AS71/The+HTTP+management+API] enabled. Setting console-enabled to false also has no affect. See WelcomeContextConsoleServlet and WelcomeContextService. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-776) quiet parameter

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-776: ------------------------------------- Summary: quiet parameter Key: JBJCA-776 URL: https://issues.jboss.org/browse/JBJCA-776 Project: IronJacamar Issue Type: Bug Components: Validator Affects Versions: 1.1.0.Alpha6, 1.0.9.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Minor Fix For: 1.0.10.Final, 1.1.0.Alpha7 The quiet parameter is done as "quite" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1665) put offending rule name in exception messages

by Alex McCarrier (JIRA)

put offending rule name in exception messages --------------------------------------------- Key: JBRULES-1665 URL: http://jira.jboss.com/jira/browse/JBRULES-1665 Project: JBoss Drools Issue Type: Feature Request Components: Drl Parser/Builder Affects Versions: FUTURE Environment: all Reporter: Alex McCarrier Assigned To: Mark Proctor Priority: Minor It would be nice if drools compiler error messages would include the rule that caused the error. For instance, predicate eval errors, or "unable to resolve property" errors would state which rule was being evaluated when it encountered an error. Currently the developer has to go through the rules file looking for lines similar to the one reported in the error. Also, when it's this much work for a developer to find the offending rule, it is pretty much impossible for business users to figure out which rule they messed up. If it's at all possible to add the rule name to these error messages, please do so. It would make our lives a lot easier. :) -- 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

14 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-680) Support real-time problem modification during solving with utils for the single thread subsystem

by Geoffrey De Smet (JIRA)

Support real-time problem modification during solving with utils for the single thread subsystem ------------------------------------------------------------------------------------------------ Key: JBRULES-680 URL: http://jira.jboss.com/jira/browse/JBRULES-680 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Rete/Drools is single threaded, and so is the current implementation of the localsearchsolver, but this single thread subsystem should be documented and utils should be provided to allow for real-time problem modification A simple way would be to use a producer-consumer pattern with a non blocking queue which holds "problem moves". Each step the problem moves could be used. Problems: - bestsolutionrecalled also needs it's score adjusted. so we'll need a 2th working memory: -- EITHER temporary, just for the problem move (or set of problem moves) -- EITHER all the time, but then we'd have to hold a chain of moves, some of which might not be doable at the end - cached selectors must be notified of refreshing their cache - solution cloning normally doesn't clone the problem facts, just the proposed solution references. Do we need a full clone now? -- 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

14 years

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2748) Missing drools-flow-compiler dependency in trunk\drools-examples\drools-examples-fusion\pom.xml

by Michael Anstis (JIRA)

Missing drools-flow-compiler dependency in trunk\drools-examples\drools-examples-fusion\pom.xml ----------------------------------------------------------------------------------------------- Key: JBRULES-2748 URL: https://jira.jboss.org/browse/JBRULES-2748 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Environment: All Reporter: Michael Anstis Assignee: Mark Proctor Fix For: FUTURE java.lang.NullPointerException at org.drools.compiler.PackageBuilder.addProcessFromXml(PackageBuilder.java:432) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:468) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) at org.drools.examples.broker.Broker.loadRuleBase(Broker.java:95) at org.drools.examples.broker.Broker.createSession(Broker.java:80) at org.drools.examples.broker.Broker.<init>(Broker.java:57) at org.drools.examples.broker.Main.main(Main.java:53) When running drools-examples Fusion Broker example. Patch:- Index: pom.xml =================================================================== --- pom.xml (revision 35658) +++ pom.xml (working copy) @@ -26,6 +26,10 @@ <groupId>org.drools</groupId> <artifactId>drools-compiler</artifactId> </dependency> + <dependency> + <groupId>org.drools</groupId> + <artifactId>drools-flow-compiler</artifactId> + </dependency>  <dependency> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (JBRULES-3443) issue test

by yousof farzipur (JIRA)

yousof farzipur created JBRULES-3443: ---------------------------------------- Summary: issue test Key: JBRULES-3443 URL: https://issues.jboss.org/browse/JBRULES-3443 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: yousof farzipur Assignee: Mark Proctor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] (JBJCA-775) We can't distribute the file common/src/main/resources/dtd/connector_1_0.dtd

by Ricardo Arguello (JIRA)

Ricardo Arguello created JBJCA-775: -------------------------------------- Summary: We can't distribute the file common/src/main/resources/dtd/connector_1_0.dtd Key: JBJCA-775 URL: https://issues.jboss.org/browse/JBJCA-775 Project: IronJacamar Issue Type: Bug Affects Versions: 1.0.9.Final Reporter: Ricardo Arguello Assignee: Jesper Pedersen The DTD file common/src/main/resources/dtd/connector_1_0.dtd includes a copyright notice from Sun Microsystems. You can read it here: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-jca/tags/IRONJACAMA... It looks like we can't include it in the source code repository. Please confirm. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (AS7-4106) Admin console - management of infinispan caches - unable to change attributes

by Jan Martiska (JIRA)

Jan Martiska created AS7-4106: --------------------------------- Summary: Admin console - management of infinispan caches - unable to change attributes Key: AS7-4106 URL: https://issues.jboss.org/browse/AS7-4106 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Jan Martiska Assignee: Stan Silvert For infinispan caches, I am unable to change any attributes under its tabs except for "Attributes" tab (that means Store, JDBC Store, Locking, etc.). No error message is shown either. This happens on latest upstream snapshot build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
7
0 / 0

[JBoss JIRA] (AS7-4285) Add deploy and undeploy meta-commands to CLI GUI

by Stan Silvert (JIRA)

Stan Silvert created AS7-4285: --------------------------------- Summary: Add deploy and undeploy meta-commands to CLI GUI Key: AS7-4285 URL: https://issues.jboss.org/browse/AS7-4285 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.1.Final Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 7.0.2.SP1 CLI GUI does not yet support any of the meta-commands that exist in the regular CLI. The first and most important are deploy and undeploy. For deploy, the CLI GUI should provide the ability to select a deployment using a GUI file selector. For undeploy it should provide a table of current deployments so you can select the one you want to undeploy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
3
0 / 0

[JBoss JIRA] (JBMAN-97) Passwords are getting logged through org.jboss.resource.connectionmanager.ManagedConnectionFactoryDeployment Class if we keep the logging level in debug mode.

by Rahul Singh (JIRA)

Rahul Singh created JBMAN-97: -------------------------------- Summary: Passwords are getting logged through org.jboss.resource.connectionmanager.ManagedConnectionFactoryDeployment Class if we keep the logging level in debug mode. Key: JBMAN-97 URL: https://issues.jboss.org/browse/JBMAN-97 Project: JBoss Managed Issue Type: Bug Reporter: Rahul Singh The passwords are getting logged in debug level For example we can see the below entries in logs 2012-03-08 12:21:28,108 DEBUG [org.jboss.resource.connectionmanager.ManagedConnectionFactoryDeployment] [ main] setting property: XADataSourceProperties to value URL=jdbc:sqlserver://xxxxx:1433;databaseName=password;responseBuffering=full;SelectMethod=cursor; User=sa Password=root Password is coming in plain text through debug logging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
3
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 April 2012