Return-Path: Delivered-To: apmail-mina-dev-archive@www.apache.org Received: (qmail 52442 invoked from network); 22 Apr 2010 05:56:55 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Apr 2010 05:56:55 -0000 Received: (qmail 31433 invoked by uid 500); 22 Apr 2010 05:56:55 -0000 Delivered-To: apmail-mina-dev-archive@mina.apache.org Received: (qmail 31188 invoked by uid 500); 22 Apr 2010 05:56:52 -0000 Mailing-List: contact dev-help@mina.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mina.apache.org Delivered-To: mailing list dev@mina.apache.org Delivered-To: moderator for dev@mina.apache.org Received: (qmail 60496 invoked by uid 99); 22 Apr 2010 01:02:26 -0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Tim.DeBoer@fisglobal.com designates 199.200.24.190 as permitted sender) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAE1B7.66F8D479" Subject: Extending Spring Configuration Definition Date: Wed, 21 Apr 2010 20:01:52 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Extending Spring Configuration Definition Thread-Index: Acrht2VSoTn1yg4mRkmZ6Z9oZ/SJpQ== From: "DeBoer, Tim" To: X-OriginalArrivalTime: 22 Apr 2010 01:01:56.0535 (UTC) FILETIME=[67827C70:01CAE1B7] X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01CAE1B7.66F8D479 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="ISO-8859-1" Hi, =20 I'm looking to make a few customisations to the FTPServer but cannot due to the xsd validation in the configuration. Basically, I want to create a new user-manager and add a sha1 password encrypter with base64 encoding rather than the default hex encoding (historical reasons) but I'm getting xsd validation errors when I try and add sha1 an encryption type in the spring configuration file.=20 =20 I've created a new encryption class called Sha1Base64PasswordEncryptor and added the initialisation in UserManagerBeanDefinitionParser but when I add sha1 to the ftpd-typical.xml config file it blows up with the following exception. =20 "Using XML configuration file ./conf/ftpd-typical.xml... org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 27 in XML document from file [C:\dev\FTPServer\.\conf\ftpd-typical.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cvc-enumeration-valid: Value 'sha1' is not facet-valid with respect to enumeration '[clear, md5, salted]'. It must be a value from the enumeration. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBean Definitions(XmlBeanDefinitionReader.java:404) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDe finitions(XmlBeanDefinitionReader.java:342) ...... Caused by: org.xml.sax.SAXParseException: cvc-enumeration-valid: Value 'sha1' is not facet-valid with respect to enumeration '[clear, md5, salted]'. It must be a value from the enumeration. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXPar seException(ErrorHandlerWrapper.java:195) ......" =20 Can anyone tell me the best way to go about solving this issue? Can I create or override the spring xsd to add these elements or can I copy the spring configuration xsd and refer to it modified from the file system? Any help or advise would be appreciated as I've not much experience with name spaces/DTD's/XSD's or with spring for that matter etc... =20 Thanks in advance. =20 Tim =20 p.s. is this mailing list the place for these questions? Or is there a forum that I haven't been able to find somewhere? _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. _____________ ------_=_NextPart_001_01CAE1B7.66F8D479--