Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2B1CD9F73 for ; Mon, 14 Nov 2011 11:01:18 +0000 (UTC) Received: (qmail 23372 invoked by uid 500); 14 Nov 2011 11:01:17 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 22906 invoked by uid 500); 14 Nov 2011 11:01:16 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 22707 invoked by uid 99); 14 Nov 2011 11:01:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Nov 2011 11:01:15 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Nov 2011 11:01:13 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 494CA82BF7 for ; Mon, 14 Nov 2011 11:00:52 +0000 (UTC) Date: Mon, 14 Nov 2011 11:00:52 +0000 (UTC) From: "Dejan Bosanac (Resolved) (JIRA)" To: dev@activemq.apache.org Message-ID: <40605599.26445.1321268452311.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <5299263.276891296253124261.JavaMail.jira@thor> Subject: [jira] [Resolved] (AMQ-3168) Broker XSD: boolean attributes should permit value injection via Srping's PropertyPlaceholderConfigurer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AMQ-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-3168. -------------------------------- Resolution: Fixed Fix Version/s: 5.6.0 Assignee: Dejan Bosanac BooleanEditor is now used for createConnector property, which will enable it to be substituted even when schema validation is used. For older versions, you can explicitly turn off schema validation by using config "xbean:activemq.xml?validate=false" > Broker XSD: boolean attributes should permit value injection via Srping's PropertyPlaceholderConfigurer > ------------------------------------------------------------------------------------------------------- > > Key: AMQ-3168 > URL: https://issues.apache.org/jira/browse/AMQ-3168 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.4.2 > Environment: Linux (tested), probably all > Reporter: Joe Shisei Niski > Assignee: Dejan Bosanac > Fix For: 5.6.0 > > > i'm working on upgrading from AMQ 5.3.0 to 5.4.2. i'd like to keep schema validation enabled, so i'm carefully re-ordering the elements in activemq.xml. > Our configuration uses PropertyPlaceholderConfigurer to insert values into activemq.xml. One of our configured values is of XSD type "boolean": > > > > i'm seeing this error in the console when i run "activemq/bin/activemq-admin start": > ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 128 in XML document from class path resource [activemq.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: '${enableJmx}' is not a valid value for 'boolean'. > Other replacement tokens that precede this in the file don't produce errors, but they're for string or numeric values, not booleans. Issue AMQ-2939 mentions accomodating numeric vbalues in the broker.xsd. It would be very useful to accomodate boolean values as well, for both configurability and backward compatibility with existing configurations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira