From michael.wechner at wyona.com Wed Oct 1 09:48:54 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Oct 1 09:59:10 2008 Subject: [Yanel-dev] Yanel Toolbar does not work properly if XHTML contains no head Message-ID: <48E32B66.2070305@wyona.com> Hi I have noticed that if a resource is generating some XHTML without the element and the Yanel toolbar is turned on, then it will not work properly. In case somebody finds some spare time it would be great to fix this ;-) Thanks Michael From michael.wechner at wyona.com Wed Oct 1 22:06:29 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Oct 1 22:16:46 2008 Subject: [Yanel-dev] Maven2 Mirror Message-ID: <48E3D845.4060706@wyona.com> Hi For those who are interested to learn about the various Maven2 libs might want to take a look at http://mirrors.ibiblio.org/pub/mirrors/maven2/ Cheers Michael From michael.wechner at wyona.com Wed Oct 1 22:15:30 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Oct 1 22:25:52 2008 Subject: [Yanel-dev] copyFile() method Message-ID: <48E3DA62.8050902@wyona.com> Hi Has anyone an idea why the copyFile() method within src/java/org/wyona/commons/io/FileUtil.java is requiring byte[] buffer as an argument and doesn't provide that by itself (I mean within the method), which should simplify the usage quite a bit, so copyFile(File src, File dest) instead copyFile(File src, File dest, byte[] buffer) ? Thanks Michi From simon.litwan at wyona.com Wed Oct 1 22:24:27 2008 From: simon.litwan at wyona.com (simon litwan) Date: Wed Oct 1 22:34:47 2008 Subject: [Yanel-dev] copyFile() method In-Reply-To: <48E3DA62.8050902@wyona.com> References: <48E3DA62.8050902@wyona.com> Message-ID: <48E3DC7B.9090009@wyona.com> Michael Wechner schrieb: > Hi > > Has anyone an idea why the copyFile() method within > > src/java/org/wyona/commons/io/FileUtil.java > > is requiring byte[] buffer as an argument and doesn't provide that by > itself (I mean within the method), which should simplify the usage > quite a bit, so > > copyFile(File src, File dest) > > instead > > copyFile(File src, File dest, byte[] buffer) > > ? i think this would be nice. but is there any problem with http://commons.apache.org/io/api-1.4/org/apache/commons/io/FileUtils.html? cheers simon > > Thanks > > Michi > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From michael.wechner at wyona.com Wed Oct 1 23:40:31 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Oct 1 23:50:52 2008 Subject: [Yanel-dev] copyFile() method In-Reply-To: <48E3DC7B.9090009@wyona.com> References: <48E3DA62.8050902@wyona.com> <48E3DC7B.9090009@wyona.com> Message-ID: <48E3EE4F.1090204@wyona.com> simon litwan schrieb: > Michael Wechner schrieb: >> Hi >> >> Has anyone an idea why the copyFile() method within >> >> src/java/org/wyona/commons/io/FileUtil.java >> >> is requiring byte[] buffer as an argument and doesn't provide that by >> itself (I mean within the method), which should simplify the usage >> quite a bit, so >> >> copyFile(File src, File dest) >> >> instead >> >> copyFile(File src, File dest, byte[] buffer) >> >> ? > i think this would be nice. > > but is there any problem with > http://commons.apache.org/io/api-1.4/org/apache/commons/io/FileUtils.html? > I guess not, but I was refactoring the commons package and it seems to me that the copyFile is mainly used for copyDirectory and I don't know why the apache commons isn't used for this. We might want to set it to deprecated, but I think it's best to ask first if somebody still remembers before doing this. Cheers Michael > > cheers > simon >> >> Thanks >> >> Michi >> _______________________________________________ >> Yanel-development mailing list >> Yanel-development@wyona.com >> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From alec.bickerton at wyona.com Thu Oct 2 10:12:09 2008 From: alec.bickerton at wyona.com (Alec Bickerton) Date: Thu Oct 2 10:22:35 2008 Subject: [Yanel-dev] copyFile() method In-Reply-To: <48E3DA62.8050902@wyona.com> References: <48E3DA62.8050902@wyona.com> Message-ID: <48E48259.3050805@wyona.com> Michael Wechner wrote: > Hi > > Has anyone an idea why the copyFile() method within > > src/java/org/wyona/commons/io/FileUtil.java > > is requiring byte[] buffer as an argument and doesn't provide that by > itself (I mean within the method), which should simplify the usage > quite a bit, so > > copyFile(File src, File dest) > > instead > > copyFile(File src, File dest, byte[] buffer) At a guess I would say its to allow the caller to determine the buffer size. This allows the speed that the copying to be configurable based on filesize or expected memory constraints. I haven't really looked at that code so can't say for sure. To be honest, I would have expected something this generic to appear in a apache-commons library. And it does. http://commons.apache.org/io/api-1.4/org/apache/commons/io/FileUtils.html Why no just use whats already there? Alec. From michael.wechner at wyona.com Thu Oct 2 15:13:34 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Oct 2 15:23:51 2008 Subject: [Yanel-dev] Writing junit and htmlunit tests for Yanel resources Message-ID: <48E4C8FE.1090403@wyona.com> Hi Just as a reminder: One can write junit and htmlunit tests for yanel resources, whereas this is documented at http://yanel.wyona.org/en/documentation/testing-framework.html There was a minor bug though re building custom resources configured within a local resource types config file, but this should be fixed now. Also please note to introduce a subdirectory such as MY_RESOURCE/src/test/junit/CLASSES MY_RESOURCE/src/test/htmlunit/CLASSES Thanks Michi From michael.wechner at wyona.com Thu Oct 2 15:27:02 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Oct 2 15:37:18 2008 Subject: [Yanel-dev] Writing junit and htmlunit tests for Yanel resources In-Reply-To: <48E4C8FE.1090403@wyona.com> References: <48E4C8FE.1090403@wyona.com> Message-ID: <48E4CC26.8000102@wyona.com> btw, please note that the framework currently doesn't support junit and htmlunit tests for realms, but only for Yanel core/impl and resources (whereas the resources can be realm specific) Cheers Michi Michael Wechner schrieb: > Hi > > Just as a reminder: One can write junit and htmlunit tests for yanel > resources, whereas this is documented at > > http://yanel.wyona.org/en/documentation/testing-framework.html > > There was a minor bug though re building custom resources configured > within a local resource types config file, but > this should be fixed now. > > Also please note to introduce a subdirectory such as > > MY_RESOURCE/src/test/junit/CLASSES > MY_RESOURCE/src/test/htmlunit/CLASSES > > Thanks > > Michi > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From michael.wechner at wyona.com Thu Oct 2 15:35:40 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Oct 2 15:45:57 2008 Subject: [Yanel-dev] Has anyone experience with Terracotta? Message-ID: <48E4CE2C.6070209@wyona.com> Hi Has anyone experience with Terracotta? http://www.terracotta.org/ Thanks Michi From guillaume.deflache at wyona.com Thu Oct 2 16:10:34 2008 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Thu Oct 2 16:18:51 2008 Subject: [Yanel-dev] Writing junit and htmlunit tests for Yanel resources In-Reply-To: <48E4C8FE.1090403@wyona.com> References: <48E4C8FE.1090403@wyona.com> Message-ID: <48E4D65A.9060503@wyona.com> Michael Wechner schrieb: > Also please note to introduce a subdirectory such as > > MY_RESOURCE/src/test/junit/CLASSES > MY_RESOURCE/src/test/htmlunit/CLASSES Great stuff! :) Just a minor nit: is there a particular reason why the tests have to be split in two directories, given that the test classes themselves already follow another convention (*Test/*WebTest)? Being able to see all the tests for a given package no matter how they are run could be helpful IMHO. From michael.wechner at wyona.com Thu Oct 2 16:37:37 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Oct 2 16:47:54 2008 Subject: [Yanel-dev] Writing junit and htmlunit tests for Yanel resources In-Reply-To: <48E4D65A.9060503@wyona.com> References: <48E4C8FE.1090403@wyona.com> <48E4D65A.9060503@wyona.com> Message-ID: <48E4DCB1.7050508@wyona.com> Guillaume D?flache schrieb: > Michael Wechner schrieb: >> Also please note to introduce a subdirectory such as >> >> MY_RESOURCE/src/test/junit/CLASSES >> MY_RESOURCE/src/test/htmlunit/CLASSES > > Great stuff! :) > > Just a minor nit: is there a particular reason why the tests have to > be split in two directories, I think the reason is that Test and WebTest are not limited to junit and htmlunit, but could also be implemented by some other framework. But by differentiating this on the file level one can differentiate nicely. Makes sense? > given that the test classes themselves already follow another > convention (*Test/*WebTest)? Being able to see all the tests for a > given package no matter how they are run could be helpful IMHO. agreed, but see above? Any suggestions to how to combine these two arguments? Cheers Michi > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From simon.litwan at wyona.com Fri Oct 3 09:42:53 2008 From: simon.litwan at wyona.com (simon litwan) Date: Fri Oct 3 09:53:16 2008 Subject: [Yanel-dev] Setting of YANEL_HOME In-Reply-To: <48E08AE2.8060702@wyona.com> References: <48DAA48F.7040806@wyona.com> <48E08AE2.8060702@wyona.com> Message-ID: <48E5CCFD.7010003@wyona.com> Michael Wechner schrieb: > Hi > > I have added the check for YANEL_HOME within build.sh, whereas it's > optional and one can continue the build by pressing enter/return key. > > I assume that Hudson will fail now, because YANEL_HOME is not set, > right? For this I see two possibilities, either > set YANEL_HOME also within Hudson and make this check somehow > configurable. i rather would solve this with an ant property. simon > > WDYT? > > Thanks > > Michael > > Michael Wechner schrieb: >> Hi >> >> As recently described one can build resources (and realms) much more >> efficiently by using their specific build.xml files directly. >> >> But in order to do so one needs to know where YANEL_HOME is. I am >> afraid that people do not use this since one needs to set YANEL_HOME >> explicitely. >> >> So my suggestion is that we enhance the core build.sh (build.bat) in >> order to check for YANEL_HOME (just as it already checks for >> JAVA_HOME) and if it hasn't been set yet, either writes a message or >> sets it automagically, whereas I don't think automagic is very >> simple, because it depends very much on the OS and shell (in the case >> of UNIX). >> >> Also I think it would make sense to validate YANEL_HOME, because it >> might be possible that one has two yanel sources on the same computer >> but at various locations and this can result in confusing builds. >> >> WDYT? >> >> Thanks >> >> Michi >> _______________________________________________ >> Yanel-development mailing list >> Yanel-development@wyona.com >> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From michael.wechner at wyona.com Fri Oct 3 14:35:26 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Fri Oct 3 14:45:45 2008 Subject: [Yanel-dev] Setting of YANEL_HOME In-Reply-To: <48E5CCFD.7010003@wyona.com> References: <48DAA48F.7040806@wyona.com> <48E08AE2.8060702@wyona.com> <48E5CCFD.7010003@wyona.com> Message-ID: <48E6118E.5070708@wyona.com> simon litwan schrieb: > Michael Wechner schrieb: >> Hi >> >> I have added the check for YANEL_HOME within build.sh, whereas it's >> optional and one can continue the build by pressing enter/return key. >> >> I assume that Hudson will fail now, because YANEL_HOME is not set, >> right? For this I see two possibilities, either >> set YANEL_HOME also within Hudson and make this check somehow >> configurable. > i rather would solve this with an ant property. ok. Can you describe it a bit more detailed? Thanks Michael > > simon >> >> WDYT? >> >> Thanks >> >> Michael >> >> Michael Wechner schrieb: >>> Hi >>> >>> As recently described one can build resources (and realms) much more >>> efficiently by using their specific build.xml files directly. >>> >>> But in order to do so one needs to know where YANEL_HOME is. I am >>> afraid that people do not use this since one needs to set YANEL_HOME >>> explicitely. >>> >>> So my suggestion is that we enhance the core build.sh (build.bat) in >>> order to check for YANEL_HOME (just as it already checks for >>> JAVA_HOME) and if it hasn't been set yet, either writes a message or >>> sets it automagically, whereas I don't think automagic is very >>> simple, because it depends very much on the OS and shell (in the >>> case of UNIX). >>> >>> Also I think it would make sense to validate YANEL_HOME, because it >>> might be possible that one has two yanel sources on the same >>> computer but at various locations and this can result in confusing >>> builds. >>> >>> WDYT? >>> >>> Thanks >>> >>> Michi >>> _______________________________________________ >>> Yanel-development mailing list >>> Yanel-development@wyona.com >>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development >> >> _______________________________________________ >> Yanel-development mailing list >> Yanel-development@wyona.com >> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From alec.bickerton at wyona.com Fri Oct 3 15:20:11 2008 From: alec.bickerton at wyona.com (Alec Bickerton) Date: Fri Oct 3 15:30:35 2008 Subject: [Yanel-dev] Setting of YANEL_HOME In-Reply-To: <48E6118E.5070708@wyona.com> References: <48DAA48F.7040806@wyona.com> <48E08AE2.8060702@wyona.com> <48E5CCFD.7010003@wyona.com> <48E6118E.5070708@wyona.com> Message-ID: <48E61C0B.7050801@wyona.com> Michael Wechner wrote: > simon litwan schrieb: >> Michael Wechner schrieb: >>> Hi >>> >>> I have added the check for YANEL_HOME within build.sh, whereas it's >>> optional and one can continue the build by pressing enter/return key. >>> >>> I assume that Hudson will fail now, because YANEL_HOME is not set, >>> right? For this I see two possibilities, either >>> set YANEL_HOME also within Hudson and make this check somehow >>> configurable. >> i rather would solve this with an ant property. > > ok. Can you describe it a bit more detailed? If I understand correctly. Your suggesting we each create in our home directories a property file. In this file you would have all your local settings e.g. yanel.home=/home/alec/code/yanel_trunk tomcat.home=/opt/tomcat/ Etc... Then the build.sh first tries to read these properties using the ant variable ${user.home}. Immediately after it will read a default properties file and set whatever was not included. I'm quite familiar with this approach and find it works exceptionally well. The same file can be read by a realm specific build.xml file so that we would only need to call ant in the realms directory to build and then link to yanel/realms. Alec, From michael.wechner at wyona.com Fri Oct 3 16:07:34 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Fri Oct 3 16:17:53 2008 Subject: [Yanel-dev] Setting of YANEL_HOME In-Reply-To: <48E61C0B.7050801@wyona.com> References: <48DAA48F.7040806@wyona.com> <48E08AE2.8060702@wyona.com> <48E5CCFD.7010003@wyona.com> <48E6118E.5070708@wyona.com> <48E61C0B.7050801@wyona.com> Message-ID: <48E62726.70202@wyona.com> Alec Bickerton schrieb: > Michael Wechner wrote: > >> simon litwan schrieb: >> >>> Michael Wechner schrieb: >>> >>>> Hi >>>> >>>> I have added the check for YANEL_HOME within build.sh, whereas it's >>>> optional and one can continue the build by pressing enter/return key. >>>> >>>> I assume that Hudson will fail now, because YANEL_HOME is not set, >>>> right? For this I see two possibilities, either >>>> set YANEL_HOME also within Hudson and make this check somehow >>>> configurable. >>>> >>> i rather would solve this with an ant property. >>> >> ok. Can you describe it a bit more detailed? >> > > If I understand correctly. Your suggesting we each create in our home > directories a property file. > you mean for example /home/michi/.ant-global.properties and referencing it like right? Sounds good to me. Will try to change it. Thanks Michael > In this file you would have all your local settings > e.g. > > yanel.home=/home/alec/code/yanel_trunk > tomcat.home=/opt/tomcat/ > > Etc... > > Then the build.sh first tries to read these properties using the ant > variable ${user.home}. > > Immediately after it will read a default properties file and set > whatever was not included. > > I'm quite familiar with this approach and find it works exceptionally well. > > The same file can be read by a realm specific build.xml file so that we > would only need to call ant in the realms directory to build and then > link to yanel/realms. > > Alec, > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > From alec.bickerton at wyona.com Fri Oct 3 16:38:29 2008 From: alec.bickerton at wyona.com (Alec Bickerton) Date: Fri Oct 3 16:48:53 2008 Subject: [Yanel-dev] Setting of YANEL_HOME In-Reply-To: <48E62726.70202@wyona.com> References: <48DAA48F.7040806@wyona.com> <48E08AE2.8060702@wyona.com> <48E5CCFD.7010003@wyona.com> <48E6118E.5070708@wyona.com> <48E61C0B.7050801@wyona.com> <48E62726.70202@wyona.com> Message-ID: <48E62E65.4050106@wyona.com> Michael Wechner wrote: > Alec Bickerton schrieb: >> Michael Wechner wrote: >> >>> simon litwan schrieb: >>> >>>> Michael Wechner schrieb: >>>> >>>>> Hi >>>>> >>>>> I have added the check for YANEL_HOME within build.sh, whereas it's >>>>> optional and one can continue the build by pressing enter/return key. >>>>> >>>>> I assume that Hudson will fail now, because YANEL_HOME is not set, >>>>> right? For this I see two possibilities, either >>>>> set YANEL_HOME also within Hudson and make this check somehow >>>>> configurable. >>>>> >>>> i rather would solve this with an ant property. >>>> >>> ok. Can you describe it a bit more detailed? >>> >> >> If I understand correctly. Your suggesting we each create in our home >> directories a property file. >> > > you mean for example > > /home/michi/.ant-global.properties > > and referencing it like > > > > right? Yes exactly. Although using a hidden file is probably a bad idea. Alec. From michael.wechner at wyona.com Fri Oct 3 16:53:35 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Fri Oct 3 17:03:54 2008 Subject: [Yanel-dev] Setting of YANEL_HOME In-Reply-To: <48E62E65.4050106@wyona.com> References: <48DAA48F.7040806@wyona.com> <48E08AE2.8060702@wyona.com> <48E5CCFD.7010003@wyona.com> <48E6118E.5070708@wyona.com> <48E61C0B.7050801@wyona.com> <48E62726.70202@wyona.com> <48E62E65.4050106@wyona.com> Message-ID: <48E631EF.8090907@wyona.com> Alec Bickerton schrieb: >>>> >>>> >>> If I understand correctly. Your suggesting we each create in our home >>> directories a property file. >>> >>> >> you mean for example >> >> /home/michi/.ant-global.properties >> >> and referencing it like >> >> >> >> right? >> > > Yes exactly. Although using a hidden file is probably a bad idea. > why? I would assume it's just like all the "other" files .ssh, .bashrc, .svn .... WDYT? Cheers Michael > Alec. > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > From michael.wechner at wyona.com Fri Oct 10 02:45:30 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Fri Oct 10 02:56:02 2008 Subject: [Yanel-dev] XMLHelper added Message-ID: <48EEA5AA.1090304@wyona.com> Hi The Wyona commons lib contains some new XML helper/utility methods https://svn.wyona.com/repos/public/commons/trunk such as for example - read DOM document from input stream - create DOM document from scratch - write DOM document to output stream - .... which are currently duplicated at various places, for example src/core/java/org/wyona/yanel/core/workflow/WorkflowBuilder.java I am currently trying to refactor this, whereas I want to write tests first for the existing code, before actually substituting with the helper methods. Any feedback or help is very much appreciated. Thanks Michael From guillaume.deflache at wyona.com Fri Oct 10 09:22:04 2008 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Fri Oct 10 09:29:40 2008 Subject: [Yanel-dev] XMLHelper added In-Reply-To: <48EEA5AA.1090304@wyona.com> References: <48EEA5AA.1090304@wyona.com> Message-ID: <48EF029C.2050905@wyona.com> Michael Wechner schrieb: > The Wyona commons lib contains some new XML helper/utility methods A few comments on https://svn.wyona.com/repos/public/commons/trunk/src/java/org/wyona/commons/xml/XMLHelper.java follows: Why using arrays in interfaces, and not Iterable (Java 1.5+) or Iterator or Collection? Please avoid implementation-specific classes as parameters: HashMap -> Map: what if wanted to give the method a sorted map? Can someone explain to me what the use case for isFragment is? ...or even write a unit test! :) > if( document == null ){ > log.warn("document to string called with a null document!, don't do this."); > return null; > } > I would rather throw a NPE right here with the same comment than getting it in a maybe distance place! BTW shouldn't we always rethrow exceptions as runtime ones in helper classes? Do we otherwise have an exception handling policy? > I am currently trying to refactor this, whereas I want to write tests > first for the existing code, before actually substituting with the > helper methods. It would definitely be better to have tests 1st, if only to see how the APIs work out/feel in practice in the test cases' code, esp. as regards exception handling. From alec.bickerton at wyona.com Fri Oct 10 12:12:07 2008 From: alec.bickerton at wyona.com (Alec Bickerton) Date: Fri Oct 10 12:22:49 2008 Subject: [Yanel-dev] XMLHelper added In-Reply-To: <48EF029C.2050905@wyona.com> References: <48EEA5AA.1090304@wyona.com> <48EF029C.2050905@wyona.com> Message-ID: <48EF2A77.8010602@wyona.com> Guillaume D?flache wrote: > Michael Wechner schrieb: >> The Wyona commons lib contains some new XML helper/utility methods > > A few comments on > https://svn.wyona.com/repos/public/commons/trunk/src/java/org/wyona/commons/xml/XMLHelper.java > follows: > > Why using arrays in interfaces, and not Iterable (Java 1.5+) or Iterator > or Collection? > > Please avoid implementation-specific classes as parameters: HashMap -> > Map: what if wanted to give the method a sorted map? > > Can someone explain to me what the use case for isFragment is? ...or > even write a unit test! :) isFragment is simply to indicate if the XML declaration should be included. >> if( document == null ){ >> log.warn("document to string called with a null document!, >> don't do this."); >> return null; >> } Fair enough, I personally prefer to only throw exceptions when really necessary. This should be handled by done by the caller. > I would rather throw a NPE right here with the same comment than getting > it in a maybe distance place! > BTW shouldn't we always rethrow exceptions as runtime ones in helper > classes? Do we otherwise have an exception handling policy? I'm open to it but I feel a library is better to be explicit about the exception that it throws. Just throwing a raw exception is not that helpful. >> I am currently trying to refactor this, whereas I want to write tests >> first for the existing code, before actually substituting with the >> helper methods. That sound perfectly reasonable. However as it stands, If no namespace is usedm, a NPE will be thrown. > It would definitely be better to have tests 1st, if only to see how the > APIs work out/feel in practice in the test cases' code, esp. as regards > exception handling. The existing unit tests for the XMLHelper class no longer compile! Also I notice that this library has more dependencies before. Another point relates to code sytle, I personally find code like this awkward to follow when its shown on a single line. javax.xml.transform.TransformerFactory.newInstance().newTransformer().transform(new javax.xml.transform.dom.DOMSource(doc), new javax.xml.transform.stream.StreamResult(out) ); Alec, From alec.bickerton at wyona.com Fri Oct 10 12:15:52 2008 From: alec.bickerton at wyona.com (Alec Bickerton) Date: Fri Oct 10 12:26:34 2008 Subject: [Yanel-dev] XMLHelper added In-Reply-To: <48EF2A77.8010602@wyona.com> References: <48EEA5AA.1090304@wyona.com> <48EF029C.2050905@wyona.com> <48EF2A77.8010602@wyona.com> Message-ID: <48EF2B58.8070001@wyona.com> Alec Bickerton wrote: > Guillaume D?flache wrote: >> Michael Wechner schrieb: >>> The Wyona commons lib contains some new XML helper/utility methods >> A few comments on >> https://svn.wyona.com/repos/public/commons/trunk/src/java/org/wyona/commons/xml/XMLHelper.java >> follows: >> >> Why using arrays in interfaces, and not Iterable (Java 1.5+) or Iterator >> or Collection? >> >> Please avoid implementation-specific classes as parameters: HashMap -> >> Map: what if wanted to give the method a sorted map? >> >> Can someone explain to me what the use case for isFragment is? ...or >> even write a unit test! :) > > isFragment is simply to indicate if the XML declaration should be included. > >>> if( document == null ){ >>> log.warn("document to string called with a null document!, >>> don't do this."); >>> return null; >>> } > > Fair enough, I personally prefer to only throw exceptions when really > necessary. This should be handled by done by the caller. > >> I would rather throw a NPE right here with the same comment than getting >> it in a maybe distance place! >> BTW shouldn't we always rethrow exceptions as runtime ones in helper >> classes? Do we otherwise have an exception handling policy? > > I'm open to it but I feel a library is better to be explicit about the > exception that it throws. Just throwing a raw exception is not that helpful. > >>> I am currently trying to refactor this, whereas I want to write tests >>> first for the existing code, before actually substituting with the >>> helper methods. > > That sound perfectly reasonable. However as it stands, If no namespace > is usedm, a NPE will be thrown. > Correction, It does not. but the code does complain about a missing CatalogManager.properties file. Do we really need to have all this overhead just for creating a DOM Object? From guillaume.deflache at wyona.com Fri Oct 10 13:51:52 2008 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Fri Oct 10 13:59:27 2008 Subject: [Yanel-dev] XMLHelper added In-Reply-To: <48EF2A77.8010602@wyona.com> References: <48EEA5AA.1090304@wyona.com> <48EF029C.2050905@wyona.com> <48EF2A77.8010602@wyona.com> Message-ID: <48EF41D8.3000301@wyona.com> Alec Bickerton schrieb: > Guillaume D?flache wrote: > >> Can someone explain to me what the use case for isFragment is? ...or >> even write a unit test! :) >> > > isFragment is simply to indicate if the XML declaration should be included. > Fine, but in what case(s) would you not want it? >> I would rather throw a NPE right here with the same comment than getting >> it in a maybe distance place! >> BTW shouldn't we always rethrow exceptions as runtime ones in helper >> classes? Do we otherwise have an exception handling policy? >> > > I'm open to it but I feel a library is better to be explicit about the > exception that it throws. Just throwing a raw exception is not that helpful. > I do agree on raw exceptions, I said "with the same comment". Anyway we'll see how it looks in the unit tests then. > Another point relates to code sytle, I personally find code like this > awkward to follow when its shown on a single line. > > javax.xml.transform.TransformerFactory.newInstance().newTransformer().transform(new > javax.xml.transform.dom.DOMSource(doc), new > javax.xml.transform.stream.StreamResult(out) ); > Not using the fully qualified names may help here too! ;) From michael.wechner at wyona.com Tue Oct 14 15:27:48 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Oct 14 15:38:27 2008 Subject: [Yanel-dev] Lucene config sample Message-ID: <48F49E54.2000601@wyona.com> Hi I recently receive the following log messages: WARN org.wyona.yarep.impl.search.lucene.LuceneConfig.deprecatedConfigure():119 - this config schema is deprecated! use the new schema TODO: add config Example. I think we should fix this TODO, whereas I guess it could point to some sample config available via SVN. Or where can this sample config be found? Thanks Michi From alec.bickerton at wyona.com Tue Oct 21 10:32:06 2008 From: alec.bickerton at wyona.com (Alec Bickerton) Date: Tue Oct 21 10:43:17 2008 Subject: [Yanel-dev] Possible problem with the POM file. Message-ID: <48FD9386.8010209@wyona.com> yarep-core-1.0-dev-r38568.jar yarep-core-1.0-dev-r38870.jar yarep-core-1.0-dev-r38914.jar yarep-core-1.0-dev-r39231.jar yarep-impl-1.0-dev-r38568.jar yarep-impl-1.0-dev-r38870.jar yarep-impl-1.0-dev-r38914.jar yarep-impl-1.0-dev-r39231.jar Any idea why we get 4 versions of the same lib. Alec. From michael.wechner at wyona.com Tue Oct 21 10:46:59 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Oct 21 10:57:51 2008 Subject: [Yanel-dev] Possible problem with the POM file. In-Reply-To: <48FD9386.8010209@wyona.com> References: <48FD9386.8010209@wyona.com> Message-ID: <48FD9703.6010308@wyona.com> Alec Bickerton schrieb: > yarep-core-1.0-dev-r38568.jar > yarep-core-1.0-dev-r38870.jar > yarep-core-1.0-dev-r38914.jar > yarep-core-1.0-dev-r39231.jar > > yarep-impl-1.0-dev-r38568.jar > yarep-impl-1.0-dev-r38870.jar > yarep-impl-1.0-dev-r38914.jar > yarep-impl-1.0-dev-r39231.jar > > Any idea why we get 4 versions of the same lib. > where exactly do you receive these files? within local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/ ? (I have only revision 39231 within the lib dir) or you mean within your local maven repo? Cheers Michi > Alec. > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > From simon.litwan at wyona.com Tue Oct 21 11:31:14 2008 From: simon.litwan at wyona.com (simon litwan) Date: Tue Oct 21 11:42:28 2008 Subject: [Yanel-dev] Lucene config sample In-Reply-To: <48F49E54.2000601@wyona.com> References: <48F49E54.2000601@wyona.com> Message-ID: <48FDA162.5020806@wyona.com> Michael Wechner schrieb: > Hi > > I recently receive the following log messages: > > WARN > org.wyona.yarep.impl.search.lucene.LuceneConfig.deprecatedConfigure():119 > - this config schema is deprecated! use the new schema TODO: add > config Example. > > I think we should fix this TODO, whereas I guess it could point to > some sample config available via SVN. > > Or where can this sample config be found? at the moment it can be found under src/test/repository/new-vfs-example/repository.xml i'm not sure where to add it. but i think very handy (but probably a bit hacky) would be to add it to log output. so if one sees the warning one just could copy it from there. but maybe a link to http://svn.wyona.com/repos/public/yarep/trunk/src/test/repository/new-vfs-example/repository.xml would also be fine as well. cheers simon > > Thanks > > Michi > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From michael.wechner at wyona.com Tue Oct 21 11:43:25 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Oct 21 11:54:16 2008 Subject: [Yanel-dev] Setting of YANEL_HOME In-Reply-To: <48E631EF.8090907@wyona.com> References: <48DAA48F.7040806@wyona.com> <48E08AE2.8060702@wyona.com> <48E5CCFD.7010003@wyona.com> <48E6118E.5070708@wyona.com> <48E61C0B.7050801@wyona.com> <48E62726.70202@wyona.com> <48E62E65.4050106@wyona.com> <48E631EF.8090907@wyona.com> Message-ID: <48FDA43D.40305@wyona.com> Michael Wechner schrieb: > Alec Bickerton schrieb: >>>>> >>>> If I understand correctly. Your suggesting we each create in our home >>>> directories a property file. >>>> >>> you mean for example >>> >>> /home/michi/.ant-global.properties >>> >>> and referencing it like >>> >>> ok, I have implemented this now. Please give it a try Thanks Michael >>> >>> right? >>> >> >> Yes exactly. Although using a hidden file is probably a bad idea. >> > > why? I would assume it's just like all the "other" files > > .ssh, .bashrc, .svn .... > > WDYT? > > Cheers > > Michael >> Alec. >> _______________________________________________ >> Yanel-development mailing list >> Yanel-development@wyona.com >> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development >> > > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From alec.bickerton at wyona.com Tue Oct 21 14:32:21 2008 From: alec.bickerton at wyona.com (Alec Bickerton) Date: Tue Oct 21 14:43:41 2008 Subject: [Yanel-dev] Possible problem with the POM file. In-Reply-To: <48FD9703.6010308@wyona.com> References: <48FD9386.8010209@wyona.com> <48FD9703.6010308@wyona.com> Message-ID: <48FDCBD5.2050004@wyona.com> Michael Wechner wrote: > Alec Bickerton schrieb: >> yarep-core-1.0-dev-r38568.jar >> yarep-core-1.0-dev-r38870.jar >> yarep-core-1.0-dev-r38914.jar >> yarep-core-1.0-dev-r39231.jar >> >> yarep-impl-1.0-dev-r38568.jar >> yarep-impl-1.0-dev-r38870.jar >> yarep-impl-1.0-dev-r38914.jar >> yarep-impl-1.0-dev-r39231.jar >> >> Any idea why we get 4 versions of the same lib. >> > > where exactly do you receive these files? > > within local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/ > > ? > > (I have only revision 39231 within the lib dir) > > or you mean within your local maven repo? > These files are recopied everytime I run build.sh from yanel-trunk. Alec From michael.wechner at wyona.com Tue Oct 21 15:46:30 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Oct 21 15:57:21 2008 Subject: [Yanel-dev] Possible problem with the POM file. In-Reply-To: <48FDCBD5.2050004@wyona.com> References: <48FD9386.8010209@wyona.com> <48FD9703.6010308@wyona.com> <48FDCBD5.2050004@wyona.com> Message-ID: <48FDDD36.7030703@wyona.com> Alec Bickerton schrieb: > Michael Wechner wrote: > >> Alec Bickerton schrieb: >> >>> yarep-core-1.0-dev-r38568.jar >>> yarep-core-1.0-dev-r38870.jar >>> yarep-core-1.0-dev-r38914.jar >>> yarep-core-1.0-dev-r39231.jar >>> >>> yarep-impl-1.0-dev-r38568.jar >>> yarep-impl-1.0-dev-r38870.jar >>> yarep-impl-1.0-dev-r38914.jar >>> yarep-impl-1.0-dev-r39231.jar >>> >>> Any idea why we get 4 versions of the same lib. >>> >>> >> where exactly do you receive these files? >> >> within local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/ >> >> ? >> >> (I have only revision 39231 within the lib dir) >> >> or you mean within your local maven repo? >> >> > > These files are recopied everytime I run build.sh from yanel-trunk. > you might have to do a "build clean", because if you haven't done this recently, then you will still have old versions within your YANEL_HOME/build/ dir and all these files will be copied into TOMCAT HTH Michael > Alec > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > From michael.wechner at wyona.com Wed Oct 22 12:01:29 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Oct 22 12:12:20 2008 Subject: [Yanel-dev] Lucene config sample In-Reply-To: <48FDA162.5020806@wyona.com> References: <48F49E54.2000601@wyona.com> <48FDA162.5020806@wyona.com> Message-ID: <48FEF9F9.5060007@wyona.com> simon litwan schrieb: > Michael Wechner schrieb: >> Hi >> >> I recently receive the following log messages: >> >> WARN >> org.wyona.yarep.impl.search.lucene.LuceneConfig.deprecatedConfigure():119 >> - this config schema is deprecated! use the new schema TODO: add >> config Example. >> >> I think we should fix this TODO, whereas I guess it could point to >> some sample config available via SVN. >> >> Or where can this sample config be found? > at the moment it can be found under > src/test/repository/new-vfs-example/repository.xml > > i'm not sure where to add it. but i think very handy (but probably a > bit hacky) would be to add it to log output. so if one sees the > warning one just could copy it from there. > but maybe a link to > http://svn.wyona.com/repos/public/yarep/trunk/src/test/repository/new-vfs-example/repository.xml > would also be fine as well. ok, I have added this link Thanks Michi > > cheers > simon >> >> Thanks >> >> Michi >> _______________________________________________ >> Yanel-development mailing list >> Yanel-development@wyona.com >> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From michael.wechner at wyona.com Wed Oct 22 14:38:37 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Oct 22 14:49:29 2008 Subject: [Yanel-dev] Referencing yanel-webapp instead servlet-api within resources Message-ID: <48FF1ECD.20706@wyona.com> Hi I have noticed, that many resources are referencing the servlet-api directly, which is rather bad, because in case yanel-webapp is using a future servlet API, then all resources need to change this setting. Hence I think it's much better to reference yanel-webapp within the dependencies of a resource, whereas the dependency to the servlet-api is specified within pom-webapp.xml of Yanel + - Cheers Michi From alec.bickerton at wyona.com Thu Oct 23 11:24:42 2008 From: alec.bickerton at wyona.com (Alec Bickerton) Date: Thu Oct 23 11:35:58 2008 Subject: [Yanel-dev] Caching Message-ID: <490042DA.1020605@wyona.com> I'm looking at the performance issues and think it would be good to have a centralised caching mechanism within Yanel. I've had a ook but couldn't find anything like it so can I suggest we use ehcache with a cache manager Servlet/ServletFilter for cache administration. by this I mean. Add, Remove and Invalidation Here's a brief introduction for those that are unfamiliar. http://ehcache.sourceforge.net/samples.html From michael.wechner at wyona.com Thu Oct 23 12:26:58 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Oct 23 12:37:52 2008 Subject: [Yanel-dev] Caching In-Reply-To: <490042DA.1020605@wyona.com> References: <490042DA.1020605@wyona.com> Message-ID: <49005172.2080600@wyona.com> Alec Bickerton schrieb: > I'm looking at the performance issues and think it would be good to have > a centralised caching mechanism within Yanel. > > I've had a ook but couldn't find anything like it so can I suggest we > use ehcache with a cache manager Servlet/ServletFilter for cache > administration. > > by this I mean. > > Add, Remove and Invalidation > > Here's a brief introduction for those that are unfamiliar. > > http://ehcache.sourceforge.net/samples.html > thanks very much. EHCache also seems to be capable of using within a clustered env http://ehcache.sourceforge.net/documentation/distributed_caching.html which would be very important for Yanel. Cheers Michi > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > From michael.wechner at wyona.com Fri Oct 24 11:39:30 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Fri Oct 24 11:50:25 2008 Subject: [Yanel-dev] Problem re endorsed libs with/after revision 39463 Message-ID: <490197D2.3040100@wyona.com> Hi With/after revision 39463 http://lists.wyona.org/pipermail/yanel-commits/2008-October/004495.html --- public/yanel/trunk/src/build/pom-core.xml 2008-10-22 09:54:51 UTC (rev 39462) +++ public/yanel/trunk/src/build/pom-core.xml 2008-10-22 12:08:09 UTC (rev 39463) @@ -31,6 +31,12 @@ 1.0-dev-r39231 + yarep + yarep-impl + + 1.0-dev-r39231 + + wyona-org-commons one suddenly has to include the endorsed libs, because otherwise one receives the following error java.lang.IllegalAccessError: tried to access class org.apache.xml.serializer.ExtendedContentHandler from class org.apache.xalan.transformer.TransformerImpl org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:1152) org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:981) org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1187) org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1170) org.wyona.yanel.servlet.security.impl.DefaultWebAuthenticatorImpl.getXHTMLAuthenticationForm(DefaultWebAuthenticatorImpl.java:423) org.wyona.yanel.servlet.security.impl.DefaultWebAuthenticatorImpl.doAuthenticate(DefaultWebAuthenticatorImpl.java:346) org.wyona.yanel.servlet.YanelServlet.doAuthenticate(YanelServlet.java:1327) org.wyona.yanel.servlet.YanelServlet.doAccessControl(YanelServlet.java:1101) org.wyona.yanel.servlet.YanelServlet.service(YanelServlet.java:192) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.wyona.yanel.servlet.communication.YanelFilter.doFilter(YanelFilter.java:41) Any idea why this is happening? Thanks Michael From michael.wechner at wyona.com Fri Oct 24 11:48:53 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Fri Oct 24 11:59:48 2008 Subject: [Yanel-dev] Problem re endorsed libs with/after revision 39463 In-Reply-To: <490197D2.3040100@wyona.com> References: <490197D2.3040100@wyona.com> Message-ID: <49019A05.2040507@wyona.com> Michael Wechner schrieb: > Hi > > With/after revision 39463 > > http://lists.wyona.org/pipermail/yanel-commits/2008-October/004495.html > > --- public/yanel/trunk/src/build/pom-core.xml 2008-10-22 09:54:51 > UTC (rev 39462) > +++ public/yanel/trunk/src/build/pom-core.xml 2008-10-22 12:08:09 > UTC (rev 39463) > @@ -31,6 +31,12 @@ > 1.0-dev-r39231 > > > + yarep > + yarep-impl > + > + 1.0-dev-r39231 > + > + > wyona-org-commons > > one suddenly has to include the endorsed libs, because otherwise one > receives the following error > > java.lang.IllegalAccessError: tried to access class > org.apache.xml.serializer.ExtendedContentHandler from class > org.apache.xalan.transformer.TransformerImpl > org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:1152) > > org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:981) > > org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1187) > > org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1170) > > org.wyona.yanel.servlet.security.impl.DefaultWebAuthenticatorImpl.getXHTMLAuthenticationForm(DefaultWebAuthenticatorImpl.java:423) > > org.wyona.yanel.servlet.security.impl.DefaultWebAuthenticatorImpl.doAuthenticate(DefaultWebAuthenticatorImpl.java:346) > > org.wyona.yanel.servlet.YanelServlet.doAuthenticate(YanelServlet.java:1327) > > org.wyona.yanel.servlet.YanelServlet.doAccessControl(YanelServlet.java:1101) > > org.wyona.yanel.servlet.YanelServlet.service(YanelServlet.java:192) > javax.servlet.http.HttpServlet.service(HttpServlet.java:803) > org.wyona.yanel.servlet.communication.YanelFilter.doFilter(YanelFilter.java:41) > > > Any idea why this is happening? it seems that this dependency adds multiple Xalan and Xerces to the libs dir: local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xercesImpl-2.7.1.jar local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xercesImpl-2.8.1.jar and local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xalan-2.6.0.jar local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xalan-2.7.0.jar whereas especially xalan-2.6.0 is problematic I think ... Will try to remove these ambiguities Thanks Michi > > Thanks > > Michael > > > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From michael.wechner at wyona.com Fri Oct 24 13:29:09 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Fri Oct 24 13:40:05 2008 Subject: [Yanel-dev] Problem re endorsed libs with/after revision 39463 In-Reply-To: <49019A05.2040507@wyona.com> References: <490197D2.3040100@wyona.com> <49019A05.2040507@wyona.com> Message-ID: <4901B185.7030206@wyona.com> Michael Wechner schrieb: > Michael Wechner schrieb: >> Hi >> >> With/after revision 39463 >> >> http://lists.wyona.org/pipermail/yanel-commits/2008-October/004495.html >> >> --- public/yanel/trunk/src/build/pom-core.xml 2008-10-22 09:54:51 >> UTC (rev 39462) >> +++ public/yanel/trunk/src/build/pom-core.xml 2008-10-22 12:08:09 >> UTC (rev 39463) >> @@ -31,6 +31,12 @@ >> 1.0-dev-r39231 >> >> >> + yarep >> + yarep-impl >> + >> + 1.0-dev-r39231 >> + >> + >> wyona-org-commons >> >> one suddenly has to include the endorsed libs, because otherwise one >> receives the following error >> >> java.lang.IllegalAccessError: tried to access class >> org.apache.xml.serializer.ExtendedContentHandler from class >> org.apache.xalan.transformer.TransformerImpl >> >> org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:1152) >> >> >> org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:981) >> >> >> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1187) >> >> >> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1170) >> >> >> org.wyona.yanel.servlet.security.impl.DefaultWebAuthenticatorImpl.getXHTMLAuthenticationForm(DefaultWebAuthenticatorImpl.java:423) >> >> >> org.wyona.yanel.servlet.security.impl.DefaultWebAuthenticatorImpl.doAuthenticate(DefaultWebAuthenticatorImpl.java:346) >> >> >> org.wyona.yanel.servlet.YanelServlet.doAuthenticate(YanelServlet.java:1327) >> >> >> org.wyona.yanel.servlet.YanelServlet.doAccessControl(YanelServlet.java:1101) >> >> org.wyona.yanel.servlet.YanelServlet.service(YanelServlet.java:192) >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> >> org.wyona.yanel.servlet.communication.YanelFilter.doFilter(YanelFilter.java:41) >> >> >> Any idea why this is happening? > > it seems that this dependency adds multiple Xalan and Xerces to the > libs dir: > > local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xercesImpl-2.7.1.jar > local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xercesImpl-2.8.1.jar > > and > > local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xalan-2.6.0.jar > local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xalan-2.7.0.jar > > whereas especially xalan-2.6.0 is problematic I think ... > > Will try to remove these ambiguities but there is also more commons-lang-2.1.jar commons-lang-2.2.jar and icu4j-2.6.1.jar icu4j-3.4.4.jar and jaxen-1.1.1.jar jaxen-1.1-beta-10.jar and also the following files shouldn't be copied pom-cmdl.xml pom-core.xml pom-impl.xml pom-webapp.xml although these don't really bother Cheers Michael > > Thanks > > Michi >> >> Thanks >> >> Michael >> >> >> _______________________________________________ >> Yanel-development mailing list >> Yanel-development@wyona.com >> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From michael.wechner at wyona.com Fri Oct 24 14:59:44 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Fri Oct 24 15:10:40 2008 Subject: [Yanel-dev] Problem re endorsed libs with/after revision 39463 In-Reply-To: <4901B185.7030206@wyona.com> References: <490197D2.3040100@wyona.com> <49019A05.2040507@wyona.com> <4901B185.7030206@wyona.com> Message-ID: <4901C6C0.4060905@wyona.com> Michael Wechner schrieb: > Michael Wechner schrieb: >> Michael Wechner schrieb: >>> Hi >>> >>> With/after revision 39463 >>> >>> http://lists.wyona.org/pipermail/yanel-commits/2008-October/004495.html >>> >>> --- public/yanel/trunk/src/build/pom-core.xml 2008-10-22 09:54:51 >>> UTC (rev 39462) >>> +++ public/yanel/trunk/src/build/pom-core.xml 2008-10-22 12:08:09 >>> UTC (rev 39463) >>> @@ -31,6 +31,12 @@ >>> 1.0-dev-r39231 >>> >>> >>> + yarep >>> + yarep-impl >>> + >>> + 1.0-dev-r39231 >>> + >>> + >>> wyona-org-commons >>> >>> one suddenly has to include the endorsed libs, because otherwise one >>> receives the following error >>> >>> java.lang.IllegalAccessError: tried to access class >>> org.apache.xml.serializer.ExtendedContentHandler from class >>> org.apache.xalan.transformer.TransformerImpl >>> >>> org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:1152) >>> >>> >>> org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:981) >>> >>> >>> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1187) >>> >>> >>> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1170) >>> >>> >>> org.wyona.yanel.servlet.security.impl.DefaultWebAuthenticatorImpl.getXHTMLAuthenticationForm(DefaultWebAuthenticatorImpl.java:423) >>> >>> >>> org.wyona.yanel.servlet.security.impl.DefaultWebAuthenticatorImpl.doAuthenticate(DefaultWebAuthenticatorImpl.java:346) >>> >>> >>> org.wyona.yanel.servlet.YanelServlet.doAuthenticate(YanelServlet.java:1327) >>> >>> >>> org.wyona.yanel.servlet.YanelServlet.doAccessControl(YanelServlet.java:1101) >>> >>> org.wyona.yanel.servlet.YanelServlet.service(YanelServlet.java:192) >>> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >>> >>> org.wyona.yanel.servlet.communication.YanelFilter.doFilter(YanelFilter.java:41) >>> >>> >>> Any idea why this is happening? >> >> it seems that this dependency adds multiple Xalan and Xerces to the >> libs dir: >> >> local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xercesImpl-2.7.1.jar >> >> local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xercesImpl-2.8.1.jar >> >> >> and >> >> local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xalan-2.6.0.jar >> local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/lib/xalan-2.7.0.jar >> >> whereas especially xalan-2.6.0 is problematic I think ... >> >> Will try to remove these ambiguities > > but there is also more > > commons-lang-2.1.jar > commons-lang-2.2.jar > > and > > icu4j-2.6.1.jar > icu4j-3.4.4.jar > > and > > jaxen-1.1.1.jar > jaxen-1.1-beta-10.jar > > and also the following files shouldn't be copied > > pom-cmdl.xml > pom-core.xml > pom-impl.xml > pom-webapp.xml > > although these don't really bother ok, I have a added a quick fix in order to make it work again. I will now try to improve this further, because the quick fix is not done very nicely, but at least it is working again. Thanks Michael > > Cheers > > Michael >> >> Thanks >> >> Michi >>> >>> Thanks >>> >>> Michael >>> >>> >>> _______________________________________________ >>> Yanel-development mailing list >>> Yanel-development@wyona.com >>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development >> >> _______________________________________________ >> Yanel-development mailing list >> Yanel-development@wyona.com >> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From guillaume.deflache at wyona.com Fri Oct 24 18:10:23 2008 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Fri Oct 24 18:21:11 2008 Subject: [Yanel-dev] Writing junit and htmlunit tests for Yanel resources In-Reply-To: <48E4DCB1.7050508@wyona.com> References: <48E4C8FE.1090403@wyona.com> <48E4D65A.9060503@wyona.com> <48E4DCB1.7050508@wyona.com> Message-ID: <4901F36F.6070200@wyona.com> Michael Wechner schrieb: > Guillaume D?flache schrieb: >> Michael Wechner schrieb: >>> Also please note to introduce a subdirectory such as >>> >>> MY_RESOURCE/src/test/junit/CLASSES >>> MY_RESOURCE/src/test/htmlunit/CLASSES >> >> Great stuff! :) >> >> Just a minor nit: is there a particular reason why the tests have to >> be split in two directories, > > I think the reason is that Test and WebTest are not limited to junit > and htmlunit, but could also be implemented by some other framework. > But by differentiating this on the file level one can differentiate > nicely. > > Makes sense? >> given that the test classes themselves already follow another >> convention (*Test/*WebTest)? Being able to see all the tests for a >> given package no matter how they are run could be helpful IMHO. > > agreed, but see above? > > Any suggestions to how to combine these two arguments? Probably way too late but I would suggest: - MY_RESOURCE/src/test/junit/**/*.Test.java -> MY_RESOURCE/src/test/**/*JUnitTest.java - MY_RESOURCE/src/test/htmlunit/**/*WebTest.java -> MY_RESOURCE/src/test/**/*HTMLUnitTest.java From michael.wechner at wyona.com Mon Oct 27 08:55:55 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Oct 27 09:07:24 2008 Subject: [Yanel-dev] Writing junit and htmlunit tests for Yanel resources In-Reply-To: <4901F36F.6070200@wyona.com> References: <48E4C8FE.1090403@wyona.com> <48E4D65A.9060503@wyona.com> <48E4DCB1.7050508@wyona.com> <4901F36F.6070200@wyona.com> Message-ID: <4905740B.6030905@wyona.com> Guillaume D?flache schrieb: > Michael Wechner schrieb: >> Guillaume D?flache schrieb: >>> Michael Wechner schrieb: >>>> Also please note to introduce a subdirectory such as >>>> >>>> MY_RESOURCE/src/test/junit/CLASSES >>>> MY_RESOURCE/src/test/htmlunit/CLASSES >>> >>> Great stuff! :) >>> >>> Just a minor nit: is there a particular reason why the tests have to >>> be split in two directories, >> >> I think the reason is that Test and WebTest are not limited to junit >> and htmlunit, but could also be implemented by some other framework. >> But by differentiating this on the file level one can differentiate >> nicely. >> >> Makes sense? >>> given that the test classes themselves already follow another >>> convention (*Test/*WebTest)? Being able to see all the tests for a >>> given package no matter how they are run could be helpful IMHO. >> >> agreed, but see above? >> >> Any suggestions to how to combine these two arguments? > > > Probably way too late but I would suggest: > - MY_RESOURCE/src/test/junit/**/*.Test.java -> > MY_RESOURCE/src/test/**/*JUnitTest.java > - MY_RESOURCE/src/test/htmlunit/**/*WebTest.java -> > MY_RESOURCE/src/test/**/*HTMLUnitTest.java +1 Michi > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development From alec.bickerton at wyona.com Tue Oct 28 10:08:01 2008 From: alec.bickerton at wyona.com (Alec Bickerton) Date: Tue Oct 28 10:19:32 2008 Subject: [Yanel-dev] Writing junit and htmlunit tests for Yanel resources In-Reply-To: <4901F36F.6070200@wyona.com> References: <48E4C8FE.1090403@wyona.com> <48E4D65A.9060503@wyona.com> <48E4DCB1.7050508@wyona.com> <4901F36F.6070200@wyona.com> Message-ID: <4906D671.3000103@wyona.com> Guillaume D?flache wrote: > Michael Wechner schrieb: >> Guillaume D?flache schrieb: >>> Michael Wechner schrieb: >>>> Also please note to introduce a subdirectory such as >>>> >>>> MY_RESOURCE/src/test/junit/CLASSES >>>> MY_RESOURCE/src/test/htmlunit/CLASSES >>> >>> Great stuff! :) >>> >>> Just a minor nit: is there a particular reason why the tests have to >>> be split in two directories, >> >> I think the reason is that Test and WebTest are not limited to junit >> and htmlunit, but could also be implemented by some other framework. >> But by differentiating this on the file level one can differentiate >> nicely. >> >> Makes sense? >>> given that the test classes themselves already follow another >>> convention (*Test/*WebTest)? Being able to see all the tests for a >>> given package no matter how they are run could be helpful IMHO. >> >> agreed, but see above? >> >> Any suggestions to how to combine these two arguments? > > > Probably way too late but I would suggest: > - MY_RESOURCE/src/test/junit/**/*.Test.java -> > MY_RESOURCE/src/test/**/*JUnitTest.java > - MY_RESOURCE/src/test/htmlunit/**/*WebTest.java -> > MY_RESOURCE/src/test/**/*HTMLUnitTest.java The information is already in the path. Why be verbose we you don't need to be. -1 From michael.wechner at wyona.com Thu Oct 30 11:34:30 2008 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Oct 30 11:46:29 2008 Subject: ehcache added [WAS: Re: [Yanel-dev] Caching] In-Reply-To: <490042DA.1020605@wyona.com> References: <490042DA.1020605@wyona.com> Message-ID: <49098DB6.2030306@wyona.com> Dear All Please note that we have added now ehcache default config: YANEL_HOME/conf/ehcache.xml dependencies: YANEL_HOME/src/build/dependencies.xml YANEL_HOME/src/build/pom-core.xml Cheers Michael Alec Bickerton schrieb: > I'm looking at the performance issues and think it would be good to have > a centralised caching mechanism within Yanel. > > I've had a ook but couldn't find anything like it so can I suggest we > use ehcache with a cache manager Servlet/ServletFilter for cache > administration. > > by this I mean. > > Add, Remove and Invalidation > > Here's a brief introduction for those that are unfamiliar. > > http://ehcache.sourceforge.net/samples.html > _______________________________________________ > Yanel-development mailing list > Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development >