You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(22) |
Nov
(85) |
Dec
(20) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(47) |
Feb
(127) |
Mar
(268) |
Apr
(78) |
May
(47) |
Jun
(38) |
Jul
(131) |
Aug
(221) |
Sep
(187) |
Oct
(54) |
Nov
(111) |
Dec
(84) |
2011 |
Jan
(152) |
Feb
(106) |
Mar
(94) |
Apr
(90) |
May
(53) |
Jun
(20) |
Jul
(24) |
Aug
(37) |
Sep
(32) |
Oct
(70) |
Nov
(22) |
Dec
(15) |
2012 |
Jan
(33) |
Feb
(110) |
Mar
(24) |
Apr
(1) |
May
(11) |
Jun
(8) |
Jul
(12) |
Aug
(37) |
Sep
(39) |
Oct
(81) |
Nov
(38) |
Dec
(50) |
2013 |
Jan
(23) |
Feb
(53) |
Mar
(23) |
Apr
(5) |
May
(19) |
Jun
(16) |
Jul
(16) |
Aug
(9) |
Sep
(21) |
Oct
(1) |
Nov
(2) |
Dec
(8) |
2014 |
Jan
(16) |
Feb
(6) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(1) |
Jul
(4) |
Aug
(10) |
Sep
(19) |
Oct
(22) |
Nov
(4) |
Dec
(6) |
2015 |
Jan
(3) |
Feb
(6) |
Mar
(9) |
Apr
|
May
(11) |
Jun
(23) |
Jul
(14) |
Aug
(10) |
Sep
(10) |
Oct
(9) |
Nov
(18) |
Dec
(4) |
2016 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(15) |
Jun
(2) |
Jul
(8) |
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
(2) |
Feb
(12) |
Mar
(22) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(19) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Loren C. <lor...@gm...> - 2010-03-21 22:31:08
|
Turning on OpenID in extensions/local.build.properties does not compile the OpenID code. On Mar 21, 2010, at 04:38 PM, Dmitriy Shabanov wrote: > On Fri, 2010-03-19 at 22:48 +0500, Dmitriy Shabanov wrote: >> This week end I will commit changes that affects authentication way. >> >> Plan: >> - move validation from user class to manager class > > This one is done. Let me know if any problem. > > -- > Cheers, > > Dmitriy Shabanov > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev_______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
From: Dmitriy S. <sha...@gm...> - 2010-03-21 21:40:14
|
On Fri, 2010-03-19 at 22:48 +0500, Dmitriy Shabanov wrote: > This week end I will commit changes that affects authentication way. > > Plan: > - move validation from user class to manager class This one is done. Let me know if any problem. -- Cheers, Dmitriy Shabanov |
From: Dmitriy S. <sha...@gm...> - 2010-03-21 21:33:57
|
On Sun, 2010-03-21 at 22:10 +0100, Dannes Wessels wrote: > > My suggestion is to enable cache, math and scheduler (math has been > enabled in previous releases anyway) +1 for math -- Cheers, Dmitriy Shabanov |
From: Evgeny G. <gaz...@gm...> - 2010-03-21 21:22:22
|
> My suggestion is to enable cache, math and scheduler (math has been enabled in previous releases anyway) Agree gate is not module, and you are miss the "lib" (may be rename too?) module ---------- Evgeny |
From: Dannes W. <di...@ex...> - 2010-03-21 21:10:43
|
Hoi, I found out that some of the modules are disabled by default: include.feature.debugger = false include.feature.gate = false include.feature.security.openid = false * include.module.cache = false include.module.context = false include.module.jfreechart = false ** include.module.jndi = false include.module.math = false include.module.scheduler = false include.module.simpleql = false include.module.sql = false include.module.svn = false ** include.module.xmpp = false ** include.module.xslfo = false ** For sure, some of these modules some side effects occur when enabled: openId is not required for many of us, the ** marked modules causes a large set of goodies to be downloaded...... And some introduce some system risks. 'file' is okay these days, but I am not sure about e.g. the jndi. I'd like to discuss which of the modules can / should be enabled. Think of the risks or the side effects! My suggestion is to enable cache, math and scheduler (math has been enabled in previous releases anyway) Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
From: Dannes W. <di...@ex...> - 2010-03-21 21:01:26
|
Hi, On 21 Mar 2010, at 21:35 , Andrzej Jan Taramina wrote: > Yup....or at least it should be all done remotely, tested then checked in all in one piece. > > Trunk should always be pretty much runnable...not a personal scratchpad area! > > My 2 cents worth. But what do I know? I've only been developing code for close on 40 years! LOL As I understood these changes are really required and... have been announced clearly. Dmitriy works very hard at this moment, it will be okay soon.... if it isn't OK already Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
From: Andrzej J. T. <an...@ch...> - 2010-03-21 20:35:57
|
>> Shouldn't this stuff be done in a branch, fully tested, and only then >> committed en mass to Trunk? >> >> > That seems to be a better Idea for me. can't work right now due to the > trunk status :-( Yup....or at least it should be all done remotely, tested then checked in all in one piece. Trunk should always be pretty much runnable...not a personal scratchpad area! My 2 cents worth. But what do I know? I've only been developing code for close on 40 years! LOL -- Andrzej Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |
From: Wolfgang M. <wol...@ex...> - 2010-03-21 20:34:17
|
I would prefer if logically related changes could be grouped into a single commit (see change sets in intellij idea) instead of sending out many small ones. This way breaking the build can mostly be avoided. Wolfgang |
From: Dannes W. <di...@ex...> - 2010-03-21 20:10:24
|
hi, On 21 Mar 2010, at 20:41 , Andrzej Jan Taramina wrote: > Shouldn't this stuff be done in a branch, fully tested, and only then committed en mass to Trunk? > > That seems to be a better Idea for me. can't work right now due to the trunk status :-( Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
From: Dmitriy S. <sha...@gm...> - 2010-03-21 20:02:33
|
On Sun, 2010-03-21 at 15:41 -0400, Andrzej Jan Taramina wrote: > > refactoring authentication way (user.valitate -> securityManager.authenticate) > > This has me very, very nervous. Especially since it looks like the new code is being trickled into Trunk. It change the methods' way, not a logic one. > Shouldn't this stuff be done in a branch, fully tested, and only then committed en mass to Trunk? This way is already used by OpenID interface. All I want to finish refactoring. > If you break authentication for existing users, I (and many others) are gonna be very pissed! Do you mean lose users' password? That must not happen. > You've been warned! ;-) You was too :-) (Do backup & inform me if any problem, promising fast fix, but hope it will not ... ) -- Cheers, Dmitriy Shabanov |
From: Andrzej J. T. <an...@ch...> - 2010-03-21 19:41:58
|
> refactoring authentication way (user.valitate -> securityManager.authenticate) This has me very, very nervous. Especially since it looks like the new code is being trickled into Trunk. Shouldn't this stuff be done in a branch, fully tested, and only then committed en mass to Trunk? If you break authentication for existing users, I (and many others) are gonna be very pissed! You've been warned! ;-) -- Andrzej Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |
From: Thomas W. <tho...@gm...> - 2010-03-20 13:35:28
|
Dear all, I would like to volunteer to organise and maintain a code repository with working name "*eXist Code Gallery"* that will allow developers to share code snippets, modules, even whole applications and also tips and tricks and number of FAQ and success stories. I have been thinking about eXist code repository for a while and I decided it is a high time that we start collect and reuse community's code and experience. Next week I am going to come up with the a proposal about how I see the code repository, formats, tools etc. I am very interested in what you think about it. We need to find a simple and quick solution that will get a critical mass quickly. Thomas ------ Thomas White Mobile:+44 7711 922 966 Skype: thomaswhite gTalk: thomas.0007 Linked-In:http://www.linkedin.com/in/thomaswhite0007 facebook: http://www.facebook.com/thomas.0007 |
From: Dmitriy S. <sha...@gm...> - 2010-03-20 13:03:58
|
I was thinking about http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/ref-preferences-code-generation.htm http://www.jetbrains.com/idea/features/code_style.html Well, I should call it code style :-) -- Cheers, Dmitriy Shabanov On Sat, 2010-03-20 at 07:44 -0500, Loren Cahlander wrote: > Everyone should check > out: http://exist-db.org/devguide_codereview.html > > > If we disagree on any of these, then this document should be updated. > > > Loren > > On Mar 20, 2010, at 07:32 AM, Dmitriy Shabanov wrote: > > > Hey, > > > > We need agreement on source format. Any requirements or > > recommendations? |
From: Loren C. <lor...@gm...> - 2010-03-20 12:45:08
|
Everyone should check out: http://exist-db.org/devguide_codereview.html If we disagree on any of these, then this document should be updated. Loren On Mar 20, 2010, at 07:32 AM, Dmitriy Shabanov wrote: > Hey, > > We need agreement on source format. Any requirements or recommendations? > > -- > Cheers, > > Dmitriy Shabanov > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev_______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
From: Dmitriy S. <sha...@gm...> - 2010-03-20 12:34:08
|
Hey, We need agreement on source format. Any requirements or recommendations? -- Cheers, Dmitriy Shabanov |
From: Dannes W. <da...@ex...> - 2010-03-20 11:40:12
|
Dmitriy, sure I saw the repairs, that triggered me. I tried to analyze the risks for the project. Are there more locations? pity we do need see the deprecation warnings during build. We needed to switch it off because otherwise the build is flooded. cheers Dannes On Sat, Mar 20, 2010 at 12:32 PM, Dmitriy Shabanov <sha...@gm...> wrote: > Not this. Check TC, 11467 & 11468 commits > > On Sat, 2010-03-20 at 11:32 +0100, Dannes Wessels wrote: >> Hi, >> >> On Sat, Mar 20, 2010 at 7:24 AM, <sha...@us...> wrote: >> > [ignore] use SecurityManager.GUEST instead of UserImpl.DEFAULT >> >> > trunk/eXist/test/src/org/exist/validation/DatabaseInsertResources_NoValidation_Test.java >> > trunk/eXist/test/src/org/exist/validation/DatabaseInsertResources_WithValidation_Test.java >> > - broker = pool.get(UserImpl.DEFAULT); >> > + broker = pool.get(SecurityManager.GUEST); >> >> I was a bit surprised that this little change made the junit test >> fail. Do we have any idea why we did not see this before? Did we run >> the test suite locally? >> >> Anyway, what are the risks here? At this moment we found this issue in >> the not related validation tests by accident... did we check whether >> there are more locations where this can happen? >> >> Couldn't these UserImpl.DEFAULT and SecurityManager.GUEST be made >> identical, making it a pure replacement, so there is no risk? >> >> regards >> >> Dannes >> > -- > Cheers, > > Dmitriy Shabanov > -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
From: Dmitriy S. <sha...@gm...> - 2010-03-20 11:33:51
|
Not this. Check TC, 11467 & 11468 commits On Sat, 2010-03-20 at 11:32 +0100, Dannes Wessels wrote: > Hi, > > On Sat, Mar 20, 2010 at 7:24 AM, <sha...@us...> wrote: > > [ignore] use SecurityManager.GUEST instead of UserImpl.DEFAULT > > > trunk/eXist/test/src/org/exist/validation/DatabaseInsertResources_NoValidation_Test.java > > trunk/eXist/test/src/org/exist/validation/DatabaseInsertResources_WithValidation_Test.java > > - broker = pool.get(UserImpl.DEFAULT); > > + broker = pool.get(SecurityManager.GUEST); > > I was a bit surprised that this little change made the junit test > fail. Do we have any idea why we did not see this before? Did we run > the test suite locally? > > Anyway, what are the risks here? At this moment we found this issue in > the not related validation tests by accident... did we check whether > there are more locations where this can happen? > > Couldn't these UserImpl.DEFAULT and SecurityManager.GUEST be made > identical, making it a pure replacement, so there is no risk? > > regards > > Dannes > -- Cheers, Dmitriy Shabanov |
From: Dannes W. <da...@ex...> - 2010-03-20 10:33:20
|
Hi, On Sat, Mar 20, 2010 at 7:24 AM, <sha...@us...> wrote: > [ignore] use SecurityManager.GUEST instead of UserImpl.DEFAULT > trunk/eXist/test/src/org/exist/validation/DatabaseInsertResources_NoValidation_Test.java > trunk/eXist/test/src/org/exist/validation/DatabaseInsertResources_WithValidation_Test.java > - broker = pool.get(UserImpl.DEFAULT); > + broker = pool.get(SecurityManager.GUEST); I was a bit surprised that this little change made the junit test fail. Do we have any idea why we did not see this before? Did we run the test suite locally? Anyway, what are the risks here? At this moment we found this issue in the not related validation tests by accident... did we check whether there are more locations where this can happen? Couldn't these UserImpl.DEFAULT and SecurityManager.GUEST be made identical, making it a pure replacement, so there is no risk? regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
From: Dmitriy S. <sha...@gm...> - 2010-03-20 06:13:35
|
On Fri, 2010-03-19 at 21:01 +0100, Wolfgang Meier wrote: > > - move validation from user class to manager class > > - SHA as default password encryption algorithm > > please remember: user validation has to be backwards compatible with > all older eXist versions by default! Reason: I do not know the clear > text passwords of my user. If you change the algorithm, they would be > all lost. Yes, for sure. -- Cheers, Dmitriy Shabanov |
From: Loren C. <lor...@gm...> - 2010-03-19 21:49:21
|
This is from the validation section of the conf.xml. Mode is set to no. The validation finction module has not been listed yet. <!-- Settings for XML validation - mode should XML source files be validated against a schema or DTD before storing them? The setting is passed to the XML parser. The actual effects depend on the parser you use. eXist comes with Xerces which can validate against both: schemas and DTDs. Possible values: "yes", "no", "auto". "auto" will leave validation to the parser. --> <validation mode="no"> <!-- Specify the location of one or more catalog files. Catalogs are used to resolve external entities in XML documents. "${WEBAPP_HOME}" can be used as magic string. --> <entity-resolver> <catalog uri="${WEBAPP_HOME}/WEB-INF/catalog.xml"/> </entity-resolver> </validation> On Mar 19, 2010, at 04:37 PM, Dannes Wessels wrote: > Hmmm, > > do I read the validation extension functions are turned off? why is that? > > regards > > Dannes > > -- > eXist-db Native XML Database - http://exist-db.org > Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
From: Dannes W. <da...@ex...> - 2010-03-19 21:38:18
|
Hmmm, do I read the validation extension functions are turned off? why is that? regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
From: Wolfgang M. <wol...@ex...> - 2010-03-19 21:36:01
|
Evgeny, > As you can see this is extension, like fluent. > and eXist could be compiled without one. > So your suggestion is not correct, sorry. Unfortunately, your webstart extension is enabled by default and overwrites the old /webstart path. This is not the way to go and has to be changed. The old code worked and was tested on all major systems. Your module is not. If you want to keep your module somehow, it has to become a real extension at least. Second, you did not yet answer my questions about the purpose and functionality of the sharepoint commit. If you commit new stuff, you need to explain what it is good for. As a linux user, I have heard of sharepoint, but I have no idea what I would use it for. So how should I decide what to do with your extension? Please explain during the following days. Otherwise I must assume it's not worth the effort to fix the problems you introduced (bad property files, overwritten /webdav) and I will roll your changes back. Wolfgang |
From: James F. <jam...@gm...> - 2010-03-19 21:24:02
|
looks good, please add xproc with - extensions/build.properties - webapp/WEB-INF/web.xml initial state: on also I would say it maybe nice to have green background on the status cell when on J On Fri, Mar 19, 2010 at 9:51 PM, Loren Cahlander <lor...@gm...>wrote: > As part of my reviewing the eXist documentation, I am also trying to come > up with a simple at a glance view of the features and services in eXist and > where that configuration entries for each feature resides. This is a simple > first pass at this after only two hours work. > > As you can see, the description entry is blank for most of these. It is > also not in any order. It was important to start getting something down in > writing. I do not want to get this table bloated with a lot of information. > I will be adding a link for each feature to a page with details on the > configuration of the feature and any other relevant information. This table > is in webapp/configuration.xml. It may eventually move to another location, > but it is there for now. > > Given all of the above disclaimers, I would appreciate any comments and > suggestions. > > Thank you, > > Loren > > Services > > The following table lists which services and modules ship with eXist; a > description of each; the resources in the eXist installation where they are > configured; and whether they are active by default in an out-of-the box > configuration. > ServiceDescriptionResourcesInitial StateCocoon > > - extensions/build.properties > - webapp/WEB-INF/web.xml > - webapp/WEB-INF/cocoon.xconf > - webapp/WEB-INF/logkit.xconf > - webapp/WEB-INF/instrumentation.xconf > > Ondebugger > > - extensions/build.properties > > Offfluent > > - extensions/build.properties > > OnSharepoint > > - extensions/build.properties > > OffOpenID > > - extensions/build.properties > > OffVersioning > > - extensions/build.properties > > OnXQDoc > > - extensions/build.properties > > OnXSLT > > - extensions/build.properties > - webapp/WEB-INF/web.xml > > OnCache > > - extensions/build.properties > > OffCompression > > - extensions/build.properties > > OnContext > > - extensions/build.properties > > OffCounter > > - extensions/build.properties > > OnDatetime > > - extensions/build.properties > > OnExample > > - extensions/build.properties > > OnFile > > - extensions/build.properties > > OnHttp Client > > - extensions/build.properties > > OnImage > > - extensions/build.properties > > OnJFreechart > > - extensions/build.properties > > OffJNDI > > - extensions/build.properties > > OffLib > > - extensions/build.properties > > OnMail > > - extensions/build.properties > > OnMath > > - extensions/build.properties > > OffScheduler function module > > - extensions/build.properties > - conf.xml > > OffSimpleQL > > - extensions/build.properties > > OffSQL > > - extensions/build.properties > > OffSubversion > > - extensions/build.properties > > OffXMLDiff > > - extensions/build.properties > > OnXMPP > > - extensions/build.properties > > OffXSL FO > > - extensions/build.properties > > OffXML RPC > > - webapp/WEB-INF/web.xml > > OnDatabaseAdminServletthis servlet can be used to ensure that eXist is > running in the background. Just set the start-parameter to true and > load-on-startup to 1 > > - webapp/WEB-INF/web.xml > - conf.xml > > webDAV > > - webapp/WEB-INF/web.xml > > OnXQueryServletgenerates HTML from an XQuery file > > - webapp/WEB-INF/web.xml > > OnXQueryURLRewrite > > - webapp/WEB-INF/web.xml > - webapp/WEB-INF/controller-config.xml > > OnAxis/SOAPAxis provides eXist's web-services via SOAP > > - webapp/WEB-INF/web.xml > > OnAtomAtom Publishing Protocol > > - webapp/WEB-INF/web.xml > > OnWebstart (jnlp) > > - webapp/WEB-INF/web.xml > > OnCluster > > - conf.xml > > Security > > - conf.xml > > Indexing > > - conf.xml > > SchedulerThis module executes scheduled system tasks. > > - conf.xml > > OnSerializer > > - conf.xml > > OnXSLT TransformerDefault settings for the XSLT Transformer. Allow's for a > choice of implementation. > > - conf.xml > > OnXML Validation > > - conf.xml > > Off > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > > |
From: Loren C. <lor...@gm...> - 2010-03-19 20:51:55
|
As part of my reviewing the eXist documentation, I am also trying to come up with a simple at a glance view of the features and services in eXist and where that configuration entries for each feature resides. This is a simple first pass at this after only two hours work. As you can see, the description entry is blank for most of these. It is also not in any order. It was important to start getting something down in writing. I do not want to get this table bloated with a lot of information. I will be adding a link for each feature to a page with details on the configuration of the feature and any other relevant information. This table is in webapp/configuration.xml. It may eventually move to another location, but it is there for now. Given all of the above disclaimers, I would appreciate any comments and suggestions. Thank you, Loren Services The following table lists which services and modules ship with eXist; a description of each; the resources in the eXist installation where they are configured; and whether they are active by default in an out-of-the box configuration. Service Description Resources Initial State Cocoon extensions/build.properties webapp/WEB-INF/web.xml webapp/WEB-INF/cocoon.xconf webapp/WEB-INF/logkit.xconf webapp/WEB-INF/instrumentation.xconf On debugger extensions/build.properties Off fluent extensions/build.properties On Sharepoint extensions/build.properties Off OpenID extensions/build.properties Off Versioning extensions/build.properties On XQDoc extensions/build.properties On XSLT extensions/build.properties webapp/WEB-INF/web.xml On Cache extensions/build.properties Off Compression extensions/build.properties On Context extensions/build.properties Off Counter extensions/build.properties On Datetime extensions/build.properties On Example extensions/build.properties On File extensions/build.properties On Http Client extensions/build.properties On Image extensions/build.properties On JFreechart extensions/build.properties Off JNDI extensions/build.properties Off Lib extensions/build.properties On Mail extensions/build.properties On Math extensions/build.properties Off Scheduler function module extensions/build.properties conf.xml Off SimpleQL extensions/build.properties Off SQL extensions/build.properties Off Subversion extensions/build.properties Off XMLDiff extensions/build.properties On XMPP extensions/build.properties Off XSL FO extensions/build.properties Off XML RPC webapp/WEB-INF/web.xml On DatabaseAdminServlet this servlet can be used to ensure that eXist is running in the background. Just set the start-parameter to true and load-on-startup to 1 webapp/WEB-INF/web.xml conf.xml webDAV webapp/WEB-INF/web.xml On XQueryServlet generates HTML from an XQuery file webapp/WEB-INF/web.xml On XQueryURLRewrite webapp/WEB-INF/web.xml webapp/WEB-INF/controller-config.xml On Axis/SOAP Axis provides eXist's web-services via SOAP webapp/WEB-INF/web.xml On Atom Atom Publishing Protocol webapp/WEB-INF/web.xml On Webstart (jnlp) webapp/WEB-INF/web.xml On Cluster conf.xml Security conf.xml Indexing conf.xml Scheduler This module executes scheduled system tasks. conf.xml On Serializer conf.xml On XSLT Transformer Default settings for the XSLT Transformer. Allow's for a choice of implementation. conf.xml On XML Validation conf.xml Off |
From: Wolfgang M. <wol...@ex...> - 2010-03-19 20:02:00
|
Hi, > - move validation from user class to manager class > - SHA as default password encryption algorithm please remember: user validation has to be backwards compatible with all older eXist versions by default! Reason: I do not know the clear text passwords of my user. If you change the algorithm, they would be all lost. Wolfgang |