April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8751) javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL not honored

by Nicklas Karlsson (JIRA)

javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL not honored ----------------------------------------------------------------------- Key: JBAS-8751 URL: https://issues.jboss.org/browse/JBAS-8751 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF Affects Versions: 6.0.0.CR1 Reporter: Nicklas Karlsson Assignee: Stan Silvert Given a model like @javax.enterprise.inject.Model public class Model { private String data; public String getData() { return data; } public void setData(String data) { System.out.println("set data to " + data); this.data = data; } } and a view like <h:form> <h:inputText id="field" value="#{model.data}"/> <h:commandButton value="!"/> </h:form> an empty value is submitted even with <context-param> <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name> <param-value>true</param-value> </context-param> Debugging the application shows that the emptyStringIsNull of the component is true. even with a @FacesConverter(forClass=String.class) which is correctly run and doing a setSubmittedValue(null), the model still sees a "" instead of a null Tested to work correctly on a GF 3.0.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2213) When the decider doesn't pick a move, the DefaultLocalSearchSolver shouldn't terminate by exception by try again, especially with relativeSelection on

by Geoffrey De Smet (JIRA)

When the decider doesn't pick a move, the DefaultLocalSearchSolver shouldn't terminate by exception by try again, especially with relativeSelection on ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-2213 URL: https://jira.jboss.org/jira/browse/JBRULES-2213 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.0.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Critical a random bad relativeSelection could select only moves that are tabu that no reason to stop, because the next relativeSelection could be great. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2962) Knowledge Agent rebuilding KnowledgeBase with scanner/notifier does not work with declared facts

by Ross Hall (JIRA)

Knowledge Agent rebuilding KnowledgeBase with scanner/notifier does not work with declared facts ------------------------------------------------------------------------------------------------ Key: JBRULES-2962 URL: https://issues.jboss.org/browse/JBRULES-2962 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M1, 5.1.1.FINAL Reporter: Ross Hall Assignee: Mark Proctor When reloading rules in a KnowledgeAgent declared facts will cause ClassCastExceptions when new-instance is set to false. When new-instance is set to true, the KnowledgeBase is rebuilt, however declared facts are not recognized and associated rules will not fire. Rules not using declared facts will fire normally. Using POJOs works fine. In both cases the KnowledgeAgent will build the rule base the first time, the issue only seems to occur when the changeset resources are modified and are detected by the resource notifier and scanner. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

8
15
0 / 0

[JBoss JIRA] Created: (JBRULES-2791) Spring's JpaTransactionManager should be used instead of both: DroolsSpringTransactionManager and DroolsSpringJpaManager

by Anatoly Polinsky (JIRA)

Spring's JpaTransactionManager should be used instead of both: DroolsSpringTransactionManager and DroolsSpringJpaManager ------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-2791 URL: https://jira.jboss.org/browse/JBRULES-2791 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL, FUTURE Environment: Spring Based Applications Reporter: Anatoly Polinsky Assignee: Mark Proctor Instead of having two different components: "DroolsSpringTransactionManager" and "DroolsSpringJpaManager" that aim to do the work of "org.springframework.orm.jpa.JpaTransactionManager", and trying to fit a JTA model into it, the Spring's "JpaTransactionManager" itself should be used. And instead of manually managing and constantly getting references to a "proper entity manager" from JpaManger within a SingleSessionCommandService, a @PersistenceContext should be injected. This will decouple SingleSessionCommandService from JpaManager interface, and will allow _any_ JPA provider to inject an entity manager. It has more benefits, such as trust in underline JPA providers ( e.g. Hibernate ) and Spring Transaction Management capabilities to manage the process that they are actually excellent at. /Anatoly -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCOMMON-114) Warning for non File URLs should also check for vfszip URLs

by Darran Lofthouse (JIRA)

Warning for non File URLs should also check for vfszip URLs ----------------------------------------------------------- Key: JBCOMMON-114 URL: https://jira.jboss.org/browse/JBCOMMON-114 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.17.GA Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 2.2.18.GA Within the resolveSystemIDasURL method the following check is performed: - if (warnOnNonFileURLs && url.getProtocol().equalsIgnoreCase("file") == false) { log.warn("Trying to resolve systemId as a non-file URL: " + systemId); } With the introduction of vfszip URLs from JBoss 5 these should also be checked and the warning skipped if it is a vfszip URL. -- 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

11 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-9232) Store config file comments in the model

by Brian Stansberry (JIRA)

Store config file comments in the model --------------------------------------- Key: JBAS-9232 URL: https://issues.jboss.org/browse/JBAS-9232 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

4
10
0 / 0

[JBoss JIRA] Created: (JBRULES-1275) Multiple moves win a step (moves without direct tabu property relations)

by Geoffrey De Smet (JIRA)

Multiple moves win a step (moves without direct tabu property relations) ------------------------------------------------------------------------ Key: JBRULES-1275 URL: http://jira.jboss.com/jira/browse/JBRULES-1275 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional Currently only one move can win a step. If moves are evaluated not on their score, but on "the difference in score", it probably won't be a bad idea to take a low number of improving moves that have not tabu property's in common and do a step of all of them instead of just one, especially in the beginning. -- 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

11 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1328) SelectorConfig, AccepterConfig en other Config's aren't Serializable if they have a direct Selector/Accepter instance configured

by Geoffrey De Smet (JIRA)

SelectorConfig, AccepterConfig en other Config's aren't Serializable if they have a direct Selector/Accepter instance configured -------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-1328 URL: http://jira.jboss.com/jira/browse/JBRULES-1328 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional Because AbstractAccepter references LocalSearchSolver references the drools RuleBase references stuff that isn't Serializable... -- 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

11 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2553) CompositeSelector should support weighting the selection of each sub selector.

by Geoffrey De Smet (JIRA)

CompositeSelector should support weighting the selection of each sub selector. ------------------------------------------------------------------------------ Key: JBRULES-2553 URL: https://jira.jboss.org/browse/JBRULES-2553 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.1.0.M2 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: FUTURE Before the simulated annealing support refactor, this was possible, now it's not because the new CompositeSelector weights them all the same. -- 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

11 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9023) EJB Timers

by David Lloyd (JIRA)

EJB Timers ---------- Key: JBAS-9023 URL: https://issues.jboss.org/browse/JBAS-9023 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 Parent task for EJB Timer implementation items. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

5
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011