December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3301) Planner's "presumedScore is corrupted because it is not the realScore" exception should analyse and clearly list what could be wrong.

by Geoffrey De Smet (Created) (JIRA)

Planner's "presumedScore is corrupted because it is not the realScore" exception should analyse and clearly list what could be wrong. ------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3301 URL: https://issues.jboss.org/browse/JBRULES-3301 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.3.0.Final Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Critical Fix For: 5.4.0.Beta1 The exception "presumedScore is corrupted because it is not the realScore", can occur for multiple reasons: - The Move.createUndoMove() method is incorrectly implemented. If a Move A moves from X to Z, then the undo Move should move A from Z to X. - The score constraints do insertLogical's of something else than a class that extends ConstraintOccurrence. Although it is technically not 100% required to do this, there are specific technical requirements on those logically inserted classes by Drools Expert to keep the score uncorrupted. So it's far easier just to use IntConstraintOccurrence or to extend ConstraintOccurrence correctly. - The score constraints, which do insertLogical's of ConstraintOccurrence, forget to add a cause too little or too much. The exception message should identify which of the ConstraintOccurrences are corrupted and only list those. - Drools Expert 5.1 or lower is used (these possibly have bugs in the statefull working memory. From drools 5.2 this is proven not the be the case). -- 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

13 years

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-9095) Management only mode

by Brian Stansberry (JIRA)

Management only mode -------------------- Key: JBAS-9095 URL: https://issues.jboss.org/browse/JBAS-9095 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.Beta4 There is a requirement that "Instances will still be configurable even if they are not currently running. Changes will become active when the instance is next started." That could be interpreted as meaning the xml config files are human editable (which they are), but it would be nice to support something richer; i.e. starting standalone server or ProcessController+HostController processes that install no runtime services beyond what's needed to accept, process and persist management changes. This is a container task; there will be subtasks for standalone mode and domain mode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

5
6
0 / 0

[JBoss JIRA] (AS7-1485) Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory

by Philippe Guinot (Commented) (JIRA)

[ https://issues.jboss.org/browse/AS7-1485?page=com.atlassian.jira.plugin.s... ] Philippe Guinot commented on AS7-1485: -------------------------------------- Hello, I'm actually having troubles because of this JSF patch. Using jsf-impl-1.2_15-jbossorg-1, I can't load any of my facelet: I just get a 404 error ! If I replace in the JBoss module the JAR by jsf-impl-1.2_15.jar, then everything is fine. I've put some breakpoints in the affected classes, but I can't see anything wrong: no exception is thrown. Here are the details about the class loaders: * The previous TCCL: ModuleClassLoader for Module "deployment.My_EAR.ear.My_WAR.war:main" from Service Module Loader * The new class loader ServletContextListener.class.getClassLoader() = ModuleClassLoader for Module "javax.servlet.api:main" from local module loader @ee51b2c If I comment the class loader settings, then it my facelets work again. And I do not use Xerces other than the xercesImpl-2.9.1-jbossas-1 version in the org.apache.xerces module. Thank you for your help. > Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory > ------------------------------------------------------------------------- > > Key: AS7-1485 > URL: https://issues.jboss.org/browse/AS7-1485 > Project: Application Server 7 > Issue Type: Bug > Components: JSF > Affects Versions: 7.0.0.Final, 7.0.2.Final > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: Open To Community > > > Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost]. (main) Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener > java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl cannot be cast to javax.xml.parsers.SAXParserFactory > at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:128) > at com.sun.faces.config.ConfigureListener$WebXmlProcessor.getConfiguredFactory(ConfigureListener.java:702) > at com.sun.faces.config.ConfigureListener$WebXmlProcessor.scanForFacesServlet(ConfigureListener.java:674) > at com.sun.faces.config.ConfigureListener$WebXmlProcessor.<init>(ConfigureListener.java:648) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:156) > at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:60) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4389) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:321) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:145) > at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) > at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (AS7-2891) Implement allRolesMode configuration option for web subsystem

by Richard Opalka (Created) (JIRA)

Implement allRolesMode configuration option for web subsystem ------------------------------------------------------------- Key: AS7-2891 URL: https://issues.jboss.org/browse/AS7-2891 Project: Application Server 7 Issue Type: Task Components: Web Reporter: Richard Opalka Assignee: Remy Maucherat Fix For: 7.1.0.CR1 We used to have allRolesMode attribute in AS6 to allow users to define default allRolesMode for JBossWebRealm. -- 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

13 years

4
3
0 / 0

[JBoss JIRA] (AS7-2896) Wrong class names for example Oracle validator extensions in datasource schema docs

by Nicklas Karlsson (Created) (JIRA)

Wrong class names for example Oracle validator extensions in datasource schema docs ----------------------------------------------------------------------------------- Key: AS7-2896 URL: https://issues.jboss.org/browse/AS7-2896 Project: Application Server 7 Issue Type: Bug Components: Documentation Affects Versions: 7.1.0.Beta1 Reporter: Nicklas Karlsson Priority: Minor The example Oracle validator classes in jboss-as-datasources_1_0.xsd use org.jboss.jca.adapters.jdbc.vendor.oracle as a prefix but I think they are nowadays org.jboss.jca.adapters.jdbc.extensions.oracle -- 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

13 years

2
1
0 / 0

[JBoss JIRA] (AS7-2892) maven archetypes :declare Log field as transient in MemberRegistration

by Fred Bricon (Created) (JIRA)

maven archetypes :declare Log field as transient in MemberRegistration ---------------------------------------------------------------------- Key: AS7-2892 URL: https://issues.jboss.org/browse/AS7-2892 Project: Application Server 7 Issue Type: Bug Environment: Glassfish 3.1.1 Reporter: Fred Bricon -- 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

13 years

2
1
0 / 0

[JBoss JIRA] (AS7-2410) Specify Domain Controller arg to bin/domain.sh

by Rich Sharples (Created) (JIRA)

Specify Domain Controller arg to bin/domain.sh ---------------------------------------------- Key: AS7-2410 URL: https://issues.jboss.org/browse/AS7-2410 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management Affects Versions: 7.1.0.Alpha1 Environment: all Reporter: Rich Sharples Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 When I start a server as part of a remote domain I currently have to specify the remote DC in host.xml : <domain-controller>   <remote host="192.168.1.3" port="9999"/> </domain-controller> would be much more convenient to specify this as a property and be able to specify it on the command line - that way I don't have to touch host.xml. With a large server group / domain that would be a real time-saver. -- 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

13 years

4
5
0 / 0

[JBoss JIRA] (AS7-2876) Use <security-domain> from jboss-app.xml too

by Richard Opalka (Created) (JIRA)

Use <security-domain> from jboss-app.xml too -------------------------------------------- Key: AS7-2876 URL: https://issues.jboss.org/browse/AS7-2876 Project: Application Server 7 Issue Type: Bug Components: Web Services Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.1.0.CR1 -- 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

13 years

2
1
0 / 0

[JBoss JIRA] (AS7-2863) Add wsdl-host and wsdl-port configuration to appclient

by Jim Ma (Created) (JIRA)

Add wsdl-host and wsdl-port configuration to appclient ------------------------------------------------------- Key: AS7-2863 URL: https://issues.jboss.org/browse/AS7-2863 Project: Application Server 7 Issue Type: Task Components: Web Services Affects Versions: 7.1.0.Beta1 Reporter: Jim Ma Assignee: Jim Ma Fix For: 7.1.0.CR1 appclient needs to know the wsdl-host and wsdl-port when it requests server to resolve port-component-link. -- 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

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9097) Management only standalone mode

by Brian Stansberry (JIRA)

Management only standalone mode ------------------------------- Key: JBAS-9097 URL: https://issues.jboss.org/browse/JBAS-9097 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 See parent task for core concept. In standalone mode, the issue is distinguishing operations that provide management services from those that don't. If the server is started in "management only" mode a RuntimeContext should only be provided to handlers for those operations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

5
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2011