February 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1294) XSD validation fails with AUTH protocol

by Manuel Dominguez Sarmiento (JIRA)

XSD validation fails with AUTH protocol --------------------------------------- Key: JGRP-1294 URL: https://issues.jboss.org/browse/JGRP-1294 Project: JGroups Issue Type: Bug Affects Versions: 2.12 Reporter: Manuel Dominguez Sarmiento Assignee: Bela Ban Priority: Minor The config properties for the AUTH protocol depend on the actual auth_class being used. However this results in XSD validation failing, since the auth_class implementation properties are not defined. We fixed our local XSD to define the props. required by MD5Token. I'm not sure how this should be handled generically, since end users might define their own auth_classes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2904) KnowledgeAgent unsubscribes monitors, doesn't resubscribe them

by Laird Nelson (JIRA)

KnowledgeAgent unsubscribes monitors, doesn't resubscribe them -------------------------------------------------------------- Key: JBRULES-2904 URL: https://issues.jboss.org/browse/JBRULES-2904 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.1.FINAL Reporter: Laird Nelson Assignee: Mark Proctor A KnowledgeAgent set up to monitor a .drl file, and set to perform incremental builds, will correctly monitor that file for changes. When a change to that file, however, results in a DRL syntax exception (or any other KnowledgeBuilder errors), the KnowledgeAgent no longer monitors the resource for changes. This means that a typo in the file effectively stops the KnowledgeAgent from ever seeing that file again. Consequently, an error in the DRL file requires a restart to whatever server is using the KnowledgeAgent. Esteban and I have found that the error is related to lines 337 and following of KnowledgeAgentImpl.java. Here is a snippet from one of his emails to me: "The problem seems to be related to the lines you mentioned. When a resource is modified, all its knowledgeDefinition->resource are cleared and reconstructed later. I don't see any reason to unsubscribe the listener though. So the call to Set<KnowledgeDefinition> definitions = this.removeResourceMapping(resource, true); should be Set<KnowledgeDefinition> definitions = this.removeResourceMapping(resource, false); "That means: remove all the mappings but don't unsubscribe me (the kagent) as a listener." Further background can be found at http://drools-java-rules-engine.46999.n3.nabble.com/Drools-5-1-What-happe... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8879) webservices.xml creates a web context with the jar's name

by Ståle Pedersen (JIRA)

webservices.xml creates a web context with the jar's name --------------------------------------------------------- Key: JBAS-8879 URL: https://issues.jboss.org/browse/JBAS-8879 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 6.0.0.Final Reporter: Ståle Pedersen Assignee: Richard Opalka Fix For: 6.1.0 Deploying the SpecjEnterprise2010 benchmark on JBoss6-Final result in a deployment exception reporting that the war application is already installed. The .ear contains: META-INF/ META-INF/MANIFEST.MF META-INF/jboss-app.xml specj-hornetq-jms.xml lib/ META-INF/application.xml jboss-mysql-ds.xml lib/generated-ws-buyer.jar mdb-service.xml specj.jar specj.war supplier.war The specj.jar contains a webservice.xml file and it seems to create a web context with the same name as the jar which causes the specj.war to fail to deploy. This worked on JBoss5. Im not allowed to attach the benchmark, but ill attach the webservices.xml file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-7292) jboss.dtd is missing definition for ignore-dependency

by Larry O'Leary (JIRA)

jboss.dtd is missing definition for ignore-dependency ----------------------------------------------------- Key: JBAS-7292 URL: https://jira.jboss.org/jira/browse/JBAS-7292 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.1.0.GA Environment: jboss.xml with doctype definition of: <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.2//EN" "http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd"> or <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 5.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd"> Reporter: Larry O'Leary Assignee: Carlo de Wolf When using <ignore-dependency /> in jboss.xml for an EJB3 and attempting to validate the XML document against the DTD, an error is thrown indicating ignore-dependency is not a valid element for <ejb-ref>. Looking through the DTD, the element does not exist. -- 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

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1847) Error when creating a variable name equals the class name of the fact

by Nicolas Heron (JIRA)

Error when creating a variable name equals the class name of the fact ---------------------------------------------------------------------- Key: JBRULES-1847 URL: https://jira.jboss.org/jira/browse/JBRULES-1847 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.0.M2 Environment: Linux - Jboss 4.2.2 GA Reporter: Nicolas Heron Assignee: Mark Proctor Hello, in the BRMS, if you add a fact wih a variable name equals the class name of the fact, it does not work The good solution would be to avoid being able to create a fact variable name = class name when Calcul : Calcul() then end -- 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

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2690) Expand the KnowledgeAgent API

by Tihomir Surdilovic (JIRA)

Expand the KnowledgeAgent API ----------------------------- Key: JBRULES-2690 URL: https://jira.jboss.org/browse/JBRULES-2690 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.0.FINAL Reporter: Tihomir Surdilovic Assignee: Mark Proctor In a situations where multiple BRMS versions are deployed in HA environment the current KnowledgeAgent API is not capable to scan multiple locations for rule resources. KnowledgeAgent API should be able to scan multiple locations for the same resource or number of resources and be able to determine which location holds the "latest" version and pick that one up. Also, If one of the BRMS instances goes down, KnowledgeAgent API should be able to switch to receive resource updates only from the BRMS instance that is still up. -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-842) Extract/index rule fact info on save

by Michael Neale (JIRA)

Extract/index rule fact info on save ------------------------------------ Key: JBRULES-842 URL: http://jira.jboss.com/jira/browse/JBRULES-842 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-836) DSL expression browser

by Michael Neale (JIRA)

DSL expression browser ---------------------- Key: JBRULES-836 URL: http://jira.jboss.com/jira/browse/JBRULES-836 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8016) Complete Site and Documentation for AS6 Remoting

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 Remoting ------------------------------------------------ Key: JBAS-8016 URL: https://jira.jboss.org/jira/browse/JBAS-8016 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert -- 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

15 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-8832) Upgrade to Hibernate 3.6.1.Final

by Shelly McGowan (JIRA)

Upgrade to Hibernate 3.6.1.Final -------------------------------- Key: JBAS-8832 URL: https://issues.jboss.org/browse/JBAS-8832 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Hibernate service Reporter: Shelly McGowan Assignee: Steve Ebersole Fix For: 6.0.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

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