From bugzilla at wyona.com Tue Mar 2 16:39:24 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Tue Mar 2 16:41:02 2010 Subject: [Yanel-dev] [Bug 7288] [wanted1.0+] document 'local.config.home' build option properly in Yanel docs Message-ID: <20100302153924.6DD7A10CA15@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7288 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mehmet.birgi@wyona.com -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From simon at 333.ch Tue Mar 2 18:46:46 2010 From: simon at 333.ch (simon) Date: Tue Mar 2 18:59:09 2010 Subject: [Yanel-dev] simple text editor released Message-ID: <4B8D4F06.7000603@333.ch> hi all i'm happy to announce the release of a simple text editor resource type with syntax highlighting. the highlighting is done with the codemirror [1] lib. the details about the resource type can be found here: http://trac.yanel-contribution.3k3.org/wiki/textedit it is released under a zlib-style license as codemirror is released. as far as i understand it, it's not compatible to apache license. [1] http://marijn.haverbeke.nl/codemirror/ have fun :) simon From simon at 333.ch Tue Mar 2 22:33:51 2010 From: simon at 333.ch (simon) Date: Tue Mar 2 22:48:55 2010 Subject: [Yanel-dev] simple text editor released In-Reply-To: <4B8D4F06.7000603@333.ch> References: <4B8D4F06.7000603@333.ch> Message-ID: <4B8D843F.2030007@333.ch> simon schrieb: > hi all > > i'm happy to announce the release of a simple text editor resource > type with syntax highlighting. the highlighting is done with the > codemirror [1] lib. > > the details about the resource type can be found here: > http://trac.yanel-contribution.3k3.org/wiki/textedit > > it is released under a zlib-style license as codemirror is released. > as far as i understand it, it's not compatible to apache license. i just found http://www.apache.org/legal/resolved.html and it seems to be no problem to release it under apache license. so will change this. simon > > [1] http://marijn.haverbeke.nl/codemirror/ > > have fun :) > simon From michael.wechner at wyona.com Tue Mar 2 22:55:46 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 2 23:08:10 2010 Subject: [Yanel-dev] simple text editor released In-Reply-To: <4B8D843F.2030007@333.ch> References: <4B8D4F06.7000603@333.ch> <4B8D843F.2030007@333.ch> Message-ID: <4B8D8962.7000804@wyona.com> simon wrote: > simon schrieb: >> hi all >> >> i'm happy to announce the release of a simple text editor resource >> type with syntax highlighting. the highlighting is done with the >> codemirror [1] lib. >> >> the details about the resource type can be found here: >> http://trac.yanel-contribution.3k3.org/wiki/textedit >> >> it is released under a zlib-style license as codemirror is released. >> as far as i understand it, it's not compatible to apache license. > i just found http://www.apache.org/legal/resolved.html and it seems to > be no problem to release it under apache license. so will change this. cool, thanks very much I hope to test it shortly: https://svn.3k3.org/repos/public/yanel/resource-types/textedit/ Btw, I have not forgotten about the svg resource type headless ... Cheers Michi > > simon >> >> [1] http://marijn.haverbeke.nl/codemirror/ >> >> have fun :) >> simon > From guillaume.deflache at wyona.com Fri Mar 5 11:15:05 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Fri Mar 5 11:27:23 2010 Subject: [Yanel-dev] mockups and XSLT literal result element stylesheets Message-ID: <4B90D9A9.7040307@wyona.com> Hi! When doing mockups it might be useful to start to with a so-called "literal result element stylesheet" ( cf. http://www.w3.org/TR/xslt#result-element-stylesheet ). Instead of an ordinary XSLT stylesheet this is simply a document in the output format (e.g. HTML) on which one adds an xsl:version attribute on the root element (e.g. the "html" element): see the diff below for more details. This allows to start adding some dynamic things (mainly using "xsl:value-of" or "xsl:for-each") to a mockup XHTML page more easily. Sooner or later though you probably will need to move to a full-fledged XSLT anyway because this form does not support top-level XSLT elements like "xsl:param". For Yanel this gets problematic as soon as you want to e.g. access the many XSLT parameters ('language', 'yanel.back2realm', etc.) that the 'xml' resource-type provides via the BasicXMLResource Java class. More generally I think we should think about streamlining the process of going from an XHTML mockup page with CSS and images to a complete resource-type: using the 'xml' resource-type already helps, I'll try to write down some more good practices as I find them! > --- res-types/user-admin/htdocs/users-groups-matrix-chooser.xsl|(Revision 47943) > +++ res-types/user-admin/htdocs/users-groups-matrix-chooser.xsl|(Arbeitskopie) > @@ -1,7 +1,11 @@ > > + + xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" > +> > + > > + > - xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xsl:version="1.0" > > > [...] > > @@ -29,3 +33,6 @@ >
> > > + > + > + Cheers, Guillaume From michael.wechner at wyona.com Fri Mar 5 14:40:54 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Fri Mar 5 14:53:17 2010 Subject: [Yanel-dev] [Fwd: Jackrabbit 3: Benchmark suite] Message-ID: <4B9109E6.9030902@wyona.com> maybe something to learn from. -------- Original Message -------- Subject: Jackrabbit 3: Benchmark suite Date: Fri, 5 Mar 2010 14:32:09 +0100 From: Jukka Zitting Reply-To: dev@jackrabbit.apache.org To: Jackrabbit Developers Hi, Many of the jr3 design threads call for performance or scalability improvements in specific areas, or may have implications that harm performance in others. We should be able to measure such changes much better than with the ad-hoc tests we've been doing until now. To achieve this, I'd like to see a JCR benchmark suite that's designed like the backwards compatiblity test suite we have in the sandbox. The test suite would consist of a base component where we define all the performance tests we want to run. Each test should produce a single number that indicates the amount of time, memory or other resources consumed by the test. The test suite should take care of eliminating the effect of things like repository or cache startup costs and should run each test a few times to be able to calculate the mean and standard deviation of the test results. This base component should only depend on JCR 1.0. In addition to the base component we'd have test components for all Jackrabbit (and perhaps other JCR implementations) versions and configurations we want to include in the test. All these components should be included in a single Maven build so that we can we can easily run all the tests on the same computer under similar conditions and get comparable results. It's OK if the full test suite takes hours or even days to complete, as we'd only need to run it for major new releases and whenever major performance-affecting changes are made. To start with, the initial tests I had in mind are: * Session login/logout (both time and memory impact) * The above plus reading a few nodes and properties (to simulate a simple webapp use case) * Tree traversal * Writing N^K nodes (i.e. K layers of N nodes each; (N,K) in { (1e1, 6), (1e3, 2), (1e6, 1) }) * Reading an nt:file with N bytes (N in { 1e2, 1e4, 1e6 }) * Writing an nt:file with N bytes (N in { 1e2, 1e4, 1e6 }) We should probably extend this to cover at least search, versioning and access control (and perhaps observation). BR, Jukka Zitting From guillaume.deflache at wyona.com Fri Mar 5 16:03:00 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=) Date: Fri Mar 5 16:15:16 2010 Subject: scheduling APIs (was: Re: [Yanel-dev] Integration of quartz scheduler) In-Reply-To: <4B22259D.2080406@wyona.com> References: <4B21735D.9040809@wyona.com> <4B22259D.2080406@wyona.com> Message-ID: <4B911D24.4040407@wyona.com> Hi! As discussed during lunch with Michi I recently came across EJB 3's souped-up scheduler support via http://www.infoq.com/news/2010/02/jee6_ejb_31 It has not much to do with traditional EJB per se and it's indeed called JEE6 Timer service by Sun: http://java.sun.com/javaee/6/docs/tutorial/doc/bnboy.html See also the API (a bit lost among all EJB stuff, maybe this is also available in a more modularized fashion somehow): http://java.sun.com/javaee/6/docs/api/index.html?javax/ejb/package-summary.html Maybe this can give us some more inspiration on defining an API? HTH, Guillaume From guillaume.deflache at wyona.com Fri Mar 5 16:53:32 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Fri Mar 5 17:05:49 2010 Subject: [Yanel-dev] easier way to view 'source' for resource-types: a bookmarket Message-ID: <4B9128FC.1020801@wyona.com> Hi! Today I had enough fiddling with ?ber-long URLs to add yanel.resource.viewid=source to view the untransformed data, so I though about creating a bookmarket for it. Here it is (*): javascript:(function()%7Bvar%20l=location,q=l.search,h=l.protocol+'//'+l.host+l.pathname+q+(q?'&':'?')+'yanel.resource.viewid=source',n=h.replace(new%20RegExp('[%3A/.?=&-]','g'),'_'),W=open(h,n);/*alert(n);*/W.focus();%7D)() This works in Firefox, IE6 and IE7 AFAICS(*). To use it, simply create a new bookmark with the above URL as link and e.g. "Yanel RT 'source' view" as name. When you will click on it on a suitage page(*), the 'source' view of the resource-type associated with the page will be loaded in another window (or tab depending on your browser configuration). It should work with all kinds of URLs (not sure what will happen on pages loaded through POST though), except it will remove the hash part (#...) as it won't generally make sense for the 'source' view. A neat thing IMHO is that only one window/tab will be loaded per URL which you want the 'source' view for, e.g. you do not have to keep closing many windows/tabs when keeping debugging the same page! :) One could also adapt it to invoke the page info (?yanel.resource.meta) on realms where it is not already (easily) accessible from the toolbar. Ditto for easily adding the toolbar (cf. http://lists.wyona.org/pipermail/yanel-development/2009-August/003978.html for the original feature request). There are probably many other uses I did not think of! ;) (*) Note to self: the regexp-replace hack is for MSIE which does not support many non-alphanumeric characters in window names (there are probably others that I haven't escaped yet). (**): Calling this bookmarklet will only do something on a page generated by a Yanel resource-type that define the 'source' view (preferably in a meaningful way). In general bookmarklets can not show if they are relevant in some given context, i.e. on many pages some should really be disabled, but it's not technically possible. So you just have to try for yourself, the best one can do is make sure they don't break where they do not make sense. HTH, Guillaume From guillaume.deflache at wyona.com Fri Mar 5 16:56:31 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Fri Mar 5 17:08:47 2010 Subject: [Yanel-dev] yanel prefix link in order to activate the Yanel toolbar In-Reply-To: <4A83C277.2090903@wyona.com> References: <4A83C277.2090903@wyona.com> Message-ID: <4B9129AF.7010704@wyona.com> Michael Wechner schrieb: > Hi > > One can activate (and enter Yanel) the toolbar by typing > > http://foo.bar/yanel/REALM_ID/some-page.html?yanel.toolbar=on > > whereas some people add this link to the website (for example at the > bottom) and some people do not want to add this to the website, because > they think it's ugly or don't want this link to be indexed by search > engines or don't wan't to point people where one can enter Yanel. > > Still, somehow one needs to access Yanel and remembering/typing the > above link is a bit cumbersome. > > So I thought why not introduce something like > > http://foo.bar/yanel/REALM_ID/yanel > > as link instead, which I think is much easier to remember and is > configurable within web.xml and gives some identity to Yanel. > > WDYT? > > Thanks > > Michi Also on how to use a bookmarklet to solve this cf. http://lists.wyona.org/pipermail/yanel-development/2010-March/004490.html. From michael.wechner at wyona.com Sun Mar 7 20:53:14 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Sun Mar 7 21:12:19 2010 Subject: [Yanel-dev] Calendar resource type improved Message-ID: <4B94042A.1050905@wyona.com> Hi I have done some improvements on the calendar resource type: - well-formedness check - event node check As soon as I will find some time I will try to base the events on JCR. Cheers Michi From mehmet.birgi at wyona.com Mon Mar 8 14:18:33 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Mon Mar 8 14:31:09 2010 Subject: [Yanel-dev] Yanel build file Message-ID: <5bf1397d1003080518o6e2e7336kf73c5c6ff861778c@mail.gmail.com> Hi When I build yanel on Mac OS X Snow Leopard, I have to press 'Enter' *TWICE* after the following prompts: Endorsed lib is missing 'stax-api-1.0.jar'. Do you want it to be added? (YES/no): [YES] Endorsed lib is missing 'stax-1.1.2-dev.jar'. Do you want it to be added? (YES/no): [YES] This is a bit confusing, does anybody know why? Cheers, Memo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010030= 8/ef56cfcf/attachment.htm From guillaume.deflache at wyona.com Mon Mar 8 14:28:30 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=) Date: Mon Mar 8 14:40:42 2010 Subject: [Yanel-dev] Yanel build file In-Reply-To: <5bf1397d1003080518o6e2e7336kf73c5c6ff861778c@mail.gmail.com> References: <5bf1397d1003080518o6e2e7336kf73c5c6ff861778c@mail.gmail.com> Message-ID: <4B94FB7E.8040508@wyona.com> Mehmet Birgi schrieb: > Hi > > When I build yanel on Mac OS X Snow Leopard, I have to press 'Enter' > *TWICE* after the following prompts: > > Endorsed lib is missing 'stax-api-1.0.jar'. Do you want it to be > added? (YES/no): [YES] > Endorsed lib is missing 'stax-1.1.2-dev.jar'. Do you want it to be > added? (YES/no): [YES] > > This is a bit confusing, does anybody know why? > > Cheers, > > Memo > Hi! I don't know why either, but I saw the same happen under Linux. Cheers, Guillaume From simon at 333.ch Mon Mar 8 17:51:24 2010 From: simon at 333.ch (simon) Date: Mon Mar 8 18:04:03 2010 Subject: [Yanel-dev] SitetreeDOMImpl Message-ID: <4B952B0C.2020008@333.ch> hi all for a long time i would like to implement a sitetree editor. to start i implement the missing methods within NodeDOMImpl. when i started to write a test for it, i noticed something strange. AFAIU the SitetreeDOMImpl it expects/creates a a sitetree xml like this: but all the sitetree.xml (yanel-website, from-scratch-realm etc.) i found within yanel looking like this: Home not sure what's the conclusion. but i think the SitetreeDOMImpl doesn't make much sense at the moment. i'm wondering if this SitetreeDOMImpl has ever been used actually. i think we should create a schema for a yanel sitetree and make the SitetreeDOMImpl fits this schema. WDOT? cheers simon From michael.wechner at wyona.com Mon Mar 8 18:32:51 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Mar 8 18:45:22 2010 Subject: [Yanel-dev] Yanel build file In-Reply-To: <4B94FB7E.8040508@wyona.com> References: <5bf1397d1003080518o6e2e7336kf73c5c6ff861778c@mail.gmail.com> <4B94FB7E.8040508@wyona.com> Message-ID: <4B9534C3.6070600@wyona.com> Guillaume D?flache wrote: > Mehmet Birgi schrieb: >> Hi >> >> When I build yanel on Mac OS X Snow Leopard, I have to press 'Enter' >> *TWICE* after the following prompts: >> >> Endorsed lib is missing 'stax-api-1.0.jar'. Do you want it to be >> added? (YES/no): [YES] >> Endorsed lib is missing 'stax-1.1.2-dev.jar'. Do you want it to be >> added? (YES/no): [YES] >> >> This is a bit confusing, does anybody know why? >> >> Cheers, >> >> Memo >> > > Hi! > > I don't know why either, but I saw the same happen under Linux. I had a look at it some time ago, but wasn't able to figure out why this is happening. If you a have a spare minute please also have a look at it ;-) Thanks Michi > > Cheers, > Guillaume From michael.wechner at wyona.com Mon Mar 8 18:42:29 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Mar 8 18:55:01 2010 Subject: [Yanel-dev] SitetreeDOMImpl In-Reply-To: <4B952B0C.2020008@333.ch> References: <4B952B0C.2020008@333.ch> Message-ID: <4B953705.80101@wyona.com> simon wrote: > hi all > > for a long time i would like to implement a sitetree editor. to start > i implement the missing methods within NodeDOMImpl. when i started to > write a test for it, i noticed something strange. AFAIU the > SitetreeDOMImpl it expects/creates a a sitetree xml like this: > > > > > > > but all the sitetree.xml (yanel-website, from-scratch-realm etc.) i > found within yanel looking like this: > > > > Home > > > > > not sure what's the conclusion. I think it's a bug. I will have a look at it. > but i think the SitetreeDOMImpl doesn't make much sense at the moment. > i'm wondering if this SitetreeDOMImpl has ever been used actually. definitely, but I am afraid mainly within customer projects, whereas I will improve it within the public realms > > i think we should create a schema for a yanel sitetree and make the > SitetreeDOMImpl fits this schema. I agree that we need a schema, but we need to deduce it from the SitetreeDOMImpl, because otherwise we might break backwards compatibility. Btw, I will soon start to implement a sitetree editor for one of our customers, whereas it might not be totally generic, but I am happy to share as much as possible. I can send you the spec offline and you might want to tell me then how much of it you want to re-use or how much we can develop together. Cheers Michi > > WDOT? > > cheers > simon > From michael.wechner at wyona.com Tue Mar 9 12:01:28 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 9 12:13:59 2010 Subject: [Yanel-dev] I18n of UA GWT Message-ID: <4B962A88.2060008@wyona.com> Hi I have started an i18n XML file within res-types/user-admin/htdocs/i18n.xml which should replace the hard-coded labels within res-types/user-admin/src-gwt/java/org/wyona/security/groupmanagement/client/I18n.java in the future. Thanks Michi From guillaume.deflache at wyona.com Wed Mar 10 09:48:37 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=) Date: Wed Mar 10 10:00:48 2010 Subject: [Yanel-dev] I18n of UA GWT In-Reply-To: <4B962A88.2060008@wyona.com> References: <4B962A88.2060008@wyona.com> Message-ID: <4B975CE5.7060907@wyona.com> Hi! Michael Wechner schrieb: > I have started an i18n XML file within > > res-types/user-admin/htdocs/i18n.xml > > which should replace the hard-coded labels within > > res-types/user-admin/src-gwt/java/org/wyona/security/groupmanagement/client/I18n.java > > > in the future. That's fine, but I guess we would also need to introduce an additional i18n XML file for project-specific UA keys. Or should we use the already existing project-specific file in data/app/i18n/? I think putting the project-specific UA keys along with other project-specific keys is OK. This way customers only have to worry about one file to translate, and we may still try to modularize as much as possible as many generic keys as possible for Yanel. Cheers, Guillaume From michael.wechner at wyona.com Wed Mar 10 15:39:50 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Mar 10 15:53:52 2010 Subject: [Yanel-dev] I18n of UA GWT In-Reply-To: <4B975CE5.7060907@wyona.com> References: <4B962A88.2060008@wyona.com> <4B975CE5.7060907@wyona.com> Message-ID: <4B97AF36.8030906@wyona.com> Guillaume D?flache wrote: > Hi! > > Michael Wechner schrieb: >> I have started an i18n XML file within >> >> res-types/user-admin/htdocs/i18n.xml >> >> which should replace the hard-coded labels within >> >> res-types/user-admin/src-gwt/java/org/wyona/security/groupmanagement/client/I18n.java >> >> >> in the future. > > That's fine, but I guess we would also need to introduce an additional > i18n XML file for project-specific UA keys. Or should we use the > already existing project-specific file in data/app/i18n/? yes, I would add these here > > I think putting the project-specific UA keys along with other > project-specific keys is OK. This way customers only have to worry > about one file to translate, and we may still try to modularize as > much as possible as many generic keys as possible for Yanel. let's keep two files for the moment and see how they react to it. Cheers Michi > > Cheers, > Guillaume From michael.wechner at wyona.com Thu Mar 11 09:59:39 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Mar 11 10:12:18 2010 Subject: [Yanel-dev] Involving people outside the mailing list Message-ID: <4B98B0FB.9090407@wyona.com> Hi I think the Mozilla folks have a nice approach to involve people outside the mailing lists: http://limi.net/articles/firefox-ux-team-update-5 Cheers Michi From bugzilla at wyona.com Thu Mar 11 10:58:04 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 11 10:58:06 2010 Subject: [Yanel-dev] [Bug 7511] New: Yanel's HTMLSerializer write empty anchors as instead of Message-ID: <20100311095804.32B9810CA19@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7511 Summary: Yanel's HTMLSerializer write empty anchors as instead of Product: Yanel Version: unspecified Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: General AssignedTo: yanel-development@wyona.com ReportedBy: guillaume.deflache@wyona.com QAContact: yanel-development@wyona.com Minor as a simple workaround is to add a space(*) inside the "a" element. (*): and not an non-breaking space as it may generate a new line if preceeded or followed by block-level elements! -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From bugzilla at wyona.com Thu Mar 11 10:59:52 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 11 10:59:55 2010 Subject: [Yanel-dev] [Bug 7511] Yanel's HTMLSerializer write empty anchors as instead of Message-ID: <20100311095952.15D3F10CA06@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7511 ------- Comment #1 from guillaume.deflache@wyona.com 2010-03-11 10:57 ------- AFAICU "a" just needs to be added to the org.wyona.yanel.core.serialization.HTMLSerializer#nonCollapsableElements array. -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From michael.wechner at wyona.com Thu Mar 11 12:05:46 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Mar 11 12:18:21 2010 Subject: [Yanel-dev] Stax libs within Java 1.6 and why can't we use them Message-ID: <4B98CE8A.8040705@wyona.com> Hi IIRC we override the stax libs within common/endorsed in particular for Java 1.6, but it is not clear to me why we don't actually use the ones which are part Java 1.6? Any idea or pointers? Thanks Michi From guillaume.deflache at wyona.com Thu Mar 11 20:09:56 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=) Date: Thu Mar 11 20:22:06 2010 Subject: [Yanel-dev] Stax libs within Java 1.6 and why can't we use them In-Reply-To: <4B98CE8A.8040705@wyona.com> References: <4B98CE8A.8040705@wyona.com> Message-ID: <4B994004.3060501@wyona.com> Michael Wechner schrieb: > Hi Hi! > IIRC we override the stax libs within common/endorsed in particular for > Java 1.6, but it is not clear > to me why we don't actually use the ones which are part Java 1.6? The whole point of this is that the libraries actually shipped with the JRE may be much older than the versions you would like to use, or that other libraries need as dependencies. For example the Xalan provided with Java 1.4 stayed old and buggy for a long time, and if you wanted a reasonable version you had to override it. Also it allows to make sure that not updated JREs (e.g. 1.4.0 compared to 1.4.2) can still work by forcing them to use newer libraries. Now for StAX and Java 6 using very recent versions may indeed not matter so much, and we may even be currently overriding with an older version that the one that is shipped with the latest JRE 6 updates! Also according to http://java.sun.com/javase/6/docs/technotes/guides/standards/ we probably should override StAX using the complete JAXP JAR: "these technologies may be overridden only by providing a *complete* and newer implementation of the Standalone Technology" [emphasis mine]. Finally I am not sure how to tell Maven that the JRE provides some versions of otherwise standalone libraries like xalan-2.*.jar, xerces-2*.jar, jsr173.jar, stax-api.jar and that it should neither download them nor include them in the compile and runtime classpaths. HTH, Guillaume From michael.wechner at wyona.com Thu Mar 11 22:20:28 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Mar 11 22:33:05 2010 Subject: [Yanel-dev] Stax libs within Java 1.6 and why can't we use them In-Reply-To: <4B994004.3060501@wyona.com> References: <4B98CE8A.8040705@wyona.com> <4B994004.3060501@wyona.com> Message-ID: <4B995E9C.10900@wyona.com> Guillaume D?flache wrote: > Michael Wechner schrieb: >> Hi > > Hi! > > >> IIRC we override the stax libs within common/endorsed in particular >> for Java 1.6, but it is not clear >> to me why we don't actually use the ones which are part Java 1.6? > > The whole point of this is that the libraries actually shipped with > the JRE may be much older than the versions you would like to use, or > that other libraries need as dependencies. > For example the Xalan provided with Java 1.4 stayed old and buggy for > a long time, and if you wanted a reasonable version you had to > override it. > Also it allows to make sure that not updated JREs (e.g. 1.4.0 compared > to 1.4.2) can still work by forcing them to use newer libraries. I agree that we should keep this kind of functionality, but please see below > > Now for StAX and Java 6 using very recent versions may indeed not > matter so much, and we may even be currently overriding with an older > version that the one that is shipped with the latest JRE 6 updates! that's what I am concerned, that we do not really know this and hence I think we need to find out > > Also according to > http://java.sun.com/javase/6/docs/technotes/guides/standards/ we > probably should override StAX using the complete JAXP JAR: "these > technologies may be overridden only by providing a *complete* and > newer implementation of the Standalone Technology" [emphasis mine]. ok > > Finally I am not sure how to tell Maven that the JRE provides some > versions of otherwise standalone libraries like xalan-2.*.jar, > xerces-2*.jar, jsr173.jar, stax-api.jar and that it should neither > download them nor include them in the compile and runtime classpaths. I am not sure I understand. Can you explain a bit more? Thanks Michi > > HTH, > Guillaume From michael.wechner at wyona.com Sun Mar 14 22:56:15 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Sun Mar 14 23:17:23 2010 Subject: [Yanel-dev] Some nice documentation on Apache httpd/Tomcat balancing/clustering Message-ID: <4B9D5B7F.4020500@wyona.com> Hi Just found this nice documentation on load balancing http://people.apache.org/~mturk/docs/article/ftwai.html Cheers Michael From michael.wechner at wyona.com Tue Mar 16 00:17:49 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 16 00:30:32 2010 Subject: [Yanel-dev] Using a JCR based repository for the "From Scratch Realm" Message-ID: <4B9EC01D.3080406@wyona.com> Hi I have added a README to https://svn.wyona.com/repos/public/yanel/trunk/src/realms/from-scratch-realm-template/README.txt which explains how to use a JCR based repository for the "From Scratch realm", whereas JCR is not called directly , but via the Yarep-JCR implementation. It works for reading very nicely so far, but there seems to be something wrong re reading and writing properties and hence checkout/checkin does not work as expected and hence writing does not work. I will try to further improve this, because it shows how flexible Yanel and Yarep is. Also within a recent private discussion I have learned about monodb, which could be connected via http://www.mongodb.org/display/DOCS/Java+Language+Center Cheers Michi From michael.wechner at wyona.com Tue Mar 16 11:55:05 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 16 12:07:50 2010 Subject: [Yanel-dev] TinyMCE resource type improvement re checkout Message-ID: <4B9F6389.5060800@wyona.com> Hi I have noticed when opening TinyMCE and the data is already checkout, then one receives a note re checkout, but one does nevertheless receive the input screen, which doesn't make sense, because one should not be able to edit. I guess the problem is that one cannot differentiate between "fatal" errors (e.g. checjkout) and less "fatal" errors (e.g. well-formedness). I was thinking about checking on errors within src/resources/tinymce/htdocs/tinymce.jelly but I am not sure if this will disallow something which I don't know should be possible. @Simon: Since you did most of the implementation, you might remember? Thanks Michi From michael.wechner at wyona.com Tue Mar 16 18:54:10 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 16 19:06:57 2010 Subject: [Yanel-dev] Using a JCR based repository for the "From Scratch Realm" In-Reply-To: <4B9EC01D.3080406@wyona.com> References: <4B9EC01D.3080406@wyona.com> Message-ID: <4B9FC5C2.8070903@wyona.com> Hi I am very happy to say that writing also works now. Next steps are: - I am currently using PostgreSQL as PersistenceManager and I will try to replace this by something shipped with Yanel, e.g. HSQLDB - Implement tests - Implement support of revisions - Implement search Cheers Michi Michael Wechner wrote: > Hi > > I have added a README to > > https://svn.wyona.com/repos/public/yanel/trunk/src/realms/from-scratch-realm-template/README.txt > > > which explains how to use a JCR based repository for the "From Scratch > realm", whereas JCR is not called directly > , but via the Yarep-JCR implementation. > > It works for reading very nicely so far, but there seems to be > something wrong re reading and writing properties > and hence checkout/checkin does not work as expected and hence writing > does not work. > > I will try to further improve this, because it shows how flexible > Yanel and Yarep is. > > Also within a recent private discussion I have learned about monodb, > which could be connected via > > http://www.mongodb.org/display/DOCS/Java+Language+Center > > Cheers > > Michi > > From michael.wechner at wyona.com Wed Mar 17 10:55:22 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Mar 17 11:08:08 2010 Subject: [Yanel-dev] Bug re resource-types configuration and packages Message-ID: <4BA0A70A.8020701@wyona.com> Hi From an internal discussion I just realized there is a bug re resource-types configuration and packages, e.g. within src/realms/from-scratch-realm-template/resource-types.xml because depending in which order you configure the realms within conf/realms.xml or conf/local/local.realms.xml only the first such package resource will remain within local/apache-tomcat-5.5.20/webapps/yanel/WEB-INF/classes/resource-types.xml I will try to fix this right now, but wanted to let you know anyway ;-) Thanks Michi From bugzilla at wyona.com Thu Mar 18 11:18:13 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 18 11:18:16 2010 Subject: [Yanel-dev] [Bug 6967] ease use of resource types from Eclipse (for instance building them) Message-ID: <20100318101813.E8A8810C98E@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=6967 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http://yanel.org/en/document | |ation/best-practices/rapid- | |development-of- | |components.html and | |http://yanel.org/en/document | |ation/development/build_setu | |p_eclipse_ide.html Status Whiteboard|TODO update docs WRT |TODO update docs WRT |resource-types and Eclipse |resource-types and Eclipse |in |(cf bug's URL) |http://yanel.org/en/document| |ation/best-practices/rapid- | |development-of- | |components.html and | |http://yanel.org/en/document| |ation/development/build_setu| |p_eclipse_ide.html | -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From bugzilla at wyona.com Thu Mar 18 11:25:27 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 18 11:25:30 2010 Subject: [Yanel-dev] [Bug 6942] Eclipse meeting follow-up: notes => experimenting => guidelines Message-ID: <20100318102527.6595110C9B3@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=6942 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http://yanel.org/en/document | |ation/best-practices/rapid- | |development-of- | |components.html Status Whiteboard|TODO update docs WRT |TODO update docs WRT |projects/realms and Eclipse |projects/realms and Eclipse |in |(cf. this bug's and bug |http://yanel.org/en/document|6967's URLs) |ation/best-practices/rapid- | |development-of- | |components.html and | |http://yanel.org/en/document| |ation/development/build_setu| |p_eclipse_ide.html | ------- Comment #18 from guillaume.deflache@wyona.com 2010-03-18 11:22 ------- Since r48178 all resource-types specific to a given realm (e.g. those defined in $REALM_DIR/resource-types.xml) can be imported in one go as Eclipse projects! -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From guillaume.deflache at wyona.com Thu Mar 18 11:37:00 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=) Date: Thu Mar 18 11:49:00 2010 Subject: [Yanel-dev] Using a JCR based repository for the "From Scratch Realm" In-Reply-To: <4B9FC5C2.8070903@wyona.com> References: <4B9EC01D.3080406@wyona.com> <4B9FC5C2.8070903@wyona.com> Message-ID: <4BA2024C.8040905@wyona.com> Hi! Michael Wechner schrieb: > Hi > > I am very happy to say that writing also works now. Neat! > Next steps are: > - I am currently using PostgreSQL as PersistenceManager and I will try > to replace this by something shipped with Yanel, e.g. HSQLDB I wanted to suggest to use JavaDB as I thought it was included in the JRE, but in fact it is only included in *Sun's* *JDK*, as http://developers.sun.com/javadb/ says: > Where is Java DB in Sun Products? > > Java DB is included in the Java SE Development Kit, and is the developer database for the Sun GlassFish Enterprise Server. So something we already ship in/have used with Yanel would indeed be better. > - Implement tests If we add these tests to Yarep IMHO (as already pointed out privately) making sure we can run them separately from the other Yarep tests (e.g. LDAP!) would be very helpful: we would then be able to make them run on Hudson, which we cannot ATM do easily or piece-by-piece because is it either all of them or none. > [...] Cheers, Guillaume From michael.wechner at wyona.com Thu Mar 18 13:57:00 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Mar 18 14:10:01 2010 Subject: [Yanel-dev] [Fwd: [IMAP] JCR implementation complete] Message-ID: <4BA2231C.5090502@wyona.com> Having JCR implemented now within Yarep/Yanel this would be now feasible, whereas I mean we could use James as e-mail server storing the emails within JCR and having Yanel access these emails via JCR in order to aggregrate/re-use with other content or also make it searchable. Cheers Michi -------- Original Message -------- Subject: [IMAP] JCR implementation complete Date: Thu, 18 Mar 2010 11:39:18 +0100 From: Norman Maurer Reply-To: James Developers List To: James Developers List Hi all, the JCR implementation of the Mailbox Store for IMAP is in trunk now. There is some kind of room for improvments but it should be usable now. So if you have comments / ideas, just shout.. Bye, Norman --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org For additional commands, e-mail: server-dev-help@james.apache.org From michael.wechner at wyona.com Thu Mar 18 14:03:51 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Mar 18 14:17:47 2010 Subject: [Yanel-dev] Using a JCR based repository for the "From Scratch Realm" In-Reply-To: <4BA2024C.8040905@wyona.com> References: <4B9EC01D.3080406@wyona.com> <4B9FC5C2.8070903@wyona.com> <4BA2024C.8040905@wyona.com> Message-ID: <4BA224B7.6020401@wyona.com> Guillaume D?flache wrote: > Hi! > > Michael Wechner schrieb: >> Hi >> >> I am very happy to say that writing also works now. > > Neat! > > >> Next steps are: >> - I am currently using PostgreSQL as PersistenceManager and I will >> try to replace this by something shipped with Yanel, e.g. HSQLDB > > I wanted to suggest to use JavaDB as I thought it was included in the > JRE, but in fact it is only included in *Sun's* *JDK*, as > http://developers.sun.com/javadb/ says: >> Where is Java DB in Sun Products? >> >> Java DB is included in the Java SE Development Kit, and is the >> developer database for the Sun GlassFish Enterprise Server. > > So something we already ship in/have used with Yanel would indeed be > better. within one of our customer projects we used HSQLDB and had some good experience with it. It's lightweight, Java and worked reliable, hence it would fit well into our existing environment > > >> - Implement tests > > If we add these tests to Yarep IMHO (as already pointed out privately) > making sure we can run them separately from the other Yarep tests > (e.g. LDAP!) would be very helpful: we would then be able to make them > run on Hudson, which we cannot ATM do easily or piece-by-piece because > is it either all of them or none. I don't fully understand why we have to run these JCR tests independently? Can you explain a bit more? Thanks Michi > >> [...] > > Cheers, > Guillaume From mehmet.birgi at wyona.com Thu Mar 18 14:46:03 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Thu Mar 18 14:58:55 2010 Subject: [Yanel-dev] Yanel in Eclipse Message-ID: <5bf1397d1003180646l47c3dbf4q9580ab7ae1cc5d2e@mail.gmail.com> Hi all I have rewritten the existing documentation for Yanel & Eclipse to reflect the current situation, the old one was not up to date anymore. Please check the draft below for faults/improvements/etc. and give me feedback. I will then publish it on the Yanel website. Thanks, Memo Setting up Yanel in the Eclipse IDE This document will get you started using Eclipse to develop/debug Yanel. To keep things simple and reliable, building and SVN access will be done outside of Eclipse. Also, it is assumed that you are using a unix-like shell for command line processing, if you are using the windows command line, replace the references to the shell scripts below with their aequivalent dos batch files (e.g. replace "build.sh" with "build.bat") and "/" with "\". Depending on what you will be working on, you might need to import several projects into Eclipse. In this context, there are 3 types of projects: realms, resources, and Yanel itself. Please note that importing Yanel into Eclipse as a project will *not* automatically import Yanel's resource types, they have to be imported separately, and one by one, as described below. Importing a realm If you want to work on a realm that has a separate repository from the Yanel source, i.e. that is not one of the realms included with Yanel, follow these steps to import it as a project into Eclipse: 1. Check out Yanel and the external realm, and add the realm to Yanel by following this example . 2. Compile and deploy "yanel-test-1.0-dev-rREVISION.jar": {path/to/yanel/root}/build.sh -f {path/to/yanel/root}/src/test/build.xml install-jar This will build the jar file and deploy it automatically to your maven repository. 3. Build an Eclipse project using the specific "eclipse" target with the realm's build file: {path/to/yanel/root}/build.sh -f {path/to/realm/root}/build.xml eclipse 4. In Eclipse, select *File -> Import*, to open the Import dialog. 5. Select *General -> Existing Projects into Workspace*, then click on * Next*. 6. Check *"Select root directory"*, click on *Browse*, and select the realm's root directory (i.e. where build.xml is located) 7. Make sure the realm project is selected (should be the only one), *"C= opy projects into workspace"* is *not* selected, and click on *Finish*. The realm should now be visible as a project in Eclipse's Package Explorer. Importing resource types If you want to work on a specific resource type that is either a resource type of Yanel, or one belonging to another realm, follow these steps to import it as a project into Eclipse: 1. Follow points #1-2 above if you have not already done so. 2. If the resource type you are importing belongs to an external realm, follow point #3 above in case you have not already done so. 3. If the resource type you are importing belongs to Yanel, build an Eclipse project using the specific "eclipse" target with the resource's build file: {path/to/yanel/root}/build.sh -f {path/to/yanel/root}/build.xml eclipse 4. In Eclipse, select *File -> Import*, to open the Import dialog. 5. Select *General -> Existing Projects into Workspace*, then click on * Next*. 6. Check *"Select root directory"*, click on *Browse*, and select either "{path/to/realm}/res-types" (if you are importing an external realm's resources, they will be imported all at once) or the directory of the Ya= nel resource that you want to import ({path/to/yanel/root}/src/resources/{resource-to-import}, in this case y= ou have to import them one by one). 7. Select the resources that you want to import as projects, make sure *"Copy projects into workspace"* is *not* selected, and click on *Finish*. The resources should now be visible as a projects in Eclipse's Package Explorer. Importing Yanel 1. Check out and build Yanel as usual, if you have not yet done so. 2. Build an Eclipse project using the specific target "eclipse": {path/to/yanel/root}/build.sh eclipse 3. In Eclipse, select *File -> Import*, to open the Import dialog. 4. Select *General -> Existing Projects into Workspace*, then click on * Next*. 5. Check *"Select root directory"*, click on *Browse*, and select the Yanel root directory (i.e. where build.sh is located) 6. Make sure the Yanel project is selected (should be the only one), *"C= opy projects into workspace"* is *not* selected, and click on *Finish*. The project "yanel" should now be visible in the Package Explorer. Debugging To start debugging with Eclipse, start Tomcat in debug mode: {path/to/yanel/root}/local/apache-tomcat-5.5.20/bin/catalina.sh jpda start Alternatively, you can (theoretically) also use the Eclipse Tomcat Launcher. If you succeed in this, please document it here. Notes Windows users, please configure your line endings as LF by setting *Prefere= nces -> General -> Workspace -> New text file line delimiter* to *Unix*. -- = Mehmet Birgi www.wyona.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010031= 8/ee93f986/attachment.htm From bugzilla at wyona.com Thu Mar 18 15:06:45 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 18 15:06:48 2010 Subject: [Yanel-dev] [Bug 7531] New: resource-types package configurations get lost Message-ID: <20100318140645.CA0C510C961@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7531 Summary: resource-types package configurations get lost Product: Yanel Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal (C) Priority: P2 Component: General AssignedTo: michael.wechner@wyona.org ReportedBy: michael.wechner@wyona.org QAContact: yanel-development@wyona.com Pleaes see description of the pronblem at http://lists.wyona.org/pipermail/yanel-development/2010-March/004511.html -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From michael.wechner at wyona.com Thu Mar 18 14:55:35 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Mar 18 15:08:24 2010 Subject: [Yanel-dev] Bug re resource-types configuration and packages In-Reply-To: <4BA0A70A.8020701@wyona.com> References: <4BA0A70A.8020701@wyona.com> Message-ID: <4BA230D7.2090600@wyona.com> Michael Wechner wrote: > > > I will try to fix this right now, but wanted to let you know anyway ;-) unfortunately I won't be able to fix this right now, hence I have opened a bug entry: http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7531 Cheers Michi > > Thanks > > Michi From bugzilla at wyona.com Thu Mar 18 15:09:25 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 18 15:09:26 2010 Subject: [Yanel-dev] [Bug 7531] resource-types package configurations get lost Message-ID: <20100318140925.43EE210C961@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7531 ------- Comment #1 from michael.wechner@wyona.org 2010-03-18 15:06 ------- I think the problem is located within src/build/java/org/wyona/yanel/ant/MergeResourceTypesConfigsTask.java -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From michael.wechner at wyona.com Thu Mar 18 15:00:28 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Thu Mar 18 15:13:18 2010 Subject: Changing Policy Permissions for Revisions [Re: [Yanel-dev] Yanel in Eclipse] In-Reply-To: <5bf1397d1003180646l47c3dbf4q9580ab7ae1cc5d2e@mail.gmail.com> References: <5bf1397d1003180646l47c3dbf4q9580ab7ae1cc5d2e@mail.gmail.com> Message-ID: <4BA231FC.4060501@wyona.com> Hi It just came to my mind, that it would be nice if one could set different access policy permissions for URLs such as http://www.yanel.org/en/documentation/best-practices/rapid-development-of-components.html?yanel.resource.revision=1233228507352 because this would allow an editor to show other people a preview, but because the revision is based on query string this is currently not possible. Any suggestion how to improve this are very welcome. Thanks Michi Mehmet Birgi wrote: > Hi all > > I have rewritten the existing documentation for Yanel & Eclipse to > reflect the current situation, the old one was not up to date anymore. > Please check the draft below for faults/improvements/etc. and give me > feedback. I will then publish it on the Yanel website. > > Thanks, > > Memo > > > > Setting up Yanel in the Eclipse IDE > > This document will get you started using Eclipse to develop/debug > Yanel. To keep things simple and reliable, building and SVN access > will be done outside of Eclipse. Also, it is assumed that you are > using a unix-like shell for command line processing, if you are using > the windows command line, replace the references to the shell scripts > below with their aequivalent dos batch files (e.g. replace "build.sh" > with "build.bat") and "/" with "\". > > Depending on what you will be working on, you might need to import > several projects into Eclipse. In this context, there are 3 types of > projects: realms, resources, and Yanel itself. Please note that > importing Yanel into Eclipse as a project will *not* automatically > import Yanel's resource types, they have to be imported separately, > and one by one, as described below. > > > Importing a realm > > If you want to work on a realm that has a separate repository from the > Yanel source, i.e. that is not one of the realms included with Yanel, > follow these steps to import it as a project into Eclipse: > > 1. Check out Yanel and the external realm, and add the realm to > Yanel by following this example > . > 2. Compile and deploy "yanel-test-1.0-dev-rREVISION.jar": > {path/to/yanel/root}/build.sh -f {path/to/yanel/root}/src/test/build.xml install-jar > > > This will build the jar file and deploy it automatically to your > maven repository. > > 3. Build an Eclipse project using the specific "eclipse" target > with the realm's build file: > {path/to/yanel/root}/build.sh -f {path/to/realm/root}/build.xml eclipse > 4. In Eclipse, select /File -> Import/, to open the Import dialog. > 5. Select /General -> Existing Projects into Workspace/, then click > on /Next/. > 6. Check /"Select root directory"/, click on /Browse/, and select > the realm's root directory (i.e. where build.xml is located) > 7. Make sure the realm project is selected (should be the only > one), /"Copy projects into workspace"/ is *not* selected, and > click on /Finish/. > > The realm should now be visible as a project in Eclipse's Package > Explorer. > > > Importing resource types > > If you want to work on a specific resource type that is either a > resource type of Yanel, or one belonging to another realm, follow > these steps to import it as a project into Eclipse: > > 1. Follow points #1-2 above if you have not already done so. > 2. If the resource type you are importing belongs to an external > realm, follow point #3 above in case you have not already done so. > 3. If the resource type you are importing belongs to Yanel, build > an Eclipse project using the specific "eclipse" target with the > resource's build file: > {path/to/yanel/root}/build.sh -f {path/to/yanel/root}/build.xml eclipse > 4. In Eclipse, select /File -> Import/, to open the Import dialog. > 5. Select /General -> Existing Projects into Workspace/, then click > on /Next/. > 6. Check /"Select root directory"/, click on /Browse/, and select > either "{path/to/realm}/res-types" (if you are importing an > external realm's resources, they will be imported all at once) > or the directory of the Yanel resource that you want to import > ({path/to/yanel/root}/src/resources/{resource-to-import}, in > this case you have to import them one by one). > 7. Select the resources that you want to import as projects, make > sure /"Copy projects into workspace"/ is *not* selected, and > click on /Finish/. > > The resources should now be visible as a projects in Eclipse's Package > Explorer. > > > Importing Yanel > > 1. Check out and build Yanel as usual > , if you have > not yet done so. > 2. Build an Eclipse project using the specific target "eclipse": > {path/to/yanel/root}/build.sh eclipse > 3. In Eclipse, select /File -> Import/, to open the Import dialog. > 4. Select /General -> Existing Projects into Workspace/, then click > on /Next/. > 5. Check /"Select root directory"/, click on /Browse/, and select > the Yanel root directory (i.e. where build.sh is located) > 6. Make sure the Yanel project is selected (should be the only > one), /"Copy projects into workspace"/ is *not* selected, and > click on /Finish/. > > The project "yanel" should now be visible in the Package Explorer. > > > Debugging > > To start debugging with Eclipse, start Tomcat in debug mode: > > {path/to/yanel/root}/local/apache-tomcat-5.5.20/bin/catalina.sh jpda start > > Alternatively, you can (theoretically) also use the Eclipse Tomcat > Launcher. If you succeed in this, please document it here. > > > Notes > > Windows users, please configure your line endings as LF by setting > /Preferences -> General -> Workspace -> New text file line delimiter/ > to /Unix/. > > > > > -- > Mehmet Birgi > www.wyona.com > From mehmet.birgi at wyona.com Thu Mar 18 15:53:05 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Thu Mar 18 16:05:56 2010 Subject: [Yanel-dev] Re: [Dev] Re: Yanel in Eclipse In-Reply-To: <4BA23C26.10303@wyona.com> References: <5bf1397d1003180603x73ffc277i6f4957454165ca66@mail.gmail.com> <4BA22C5C.3000203@wyona.com> <4BA23A6F.6050709@wyona.com> <4BA23C26.10303@wyona.com> Message-ID: <5bf1397d1003180753y43e3d357tcef71b9f80d5643d@mail.gmail.com> Thanks to Guillaume for providing excellent feedback, here is the second draft, with his suggestions incorporated (I'm still open to more feedback): Setting up Yanel in the Eclipse IDE This document will get you started using Eclipse to develop/debug your Yanel project. To keep things simple and reliable, building and SVN access will be done outside of Eclipse. Also, it is assumed that you are using a unix-like shell for command line processing, if you are using the windows command line, replace the references to the shell scripts below with their aequivalent dos batch files (e.g. replace "build.sh" with "build.bat") and "/" with "\". Depending on what you will be working on, you might need to import several projects into Eclipse. In this context, there are 3 types of projects: realms, resources, and Yanel itself. Please note that importing Yanel into Eclipse as a project will *not* automatically import Yanel's resource types, they have to be imported separately, and one by one, as described below. Importing a realm If you want to work on a realm that has a separate directory from the Yanel source, follow these steps to import it as a project into Eclipse: 1. Check out Yanel and the external realm, and add the realm to Yanel . 2. Compile and deploy "yanel-test-1.0-dev-rREVISION.jar": cd {path/to/yanel/root} ./build.sh -f {path/to/yanel/root}/src/test/build.xml install-jar This will build the jar file and deploy it automatically to your maven repository. 3. Build an Eclipse project using the specific "eclipse" target with the realm's build file: cd {path/to/yanel/root} ./build.sh -f {path/to/realm/root}/build.xml eclipse 4. In Eclipse, select *File -> Import*, to open the Import dialog. 5. Select *General -> Existing Projects into Workspace*, then click on * Next*. 6. Check *"Select root directory"*, click on *Browse*, and select the realm's root directory (i.e. where build.xml is located) 7. Make sure the realm project is selected (should be the only one), *"C= opy projects into workspace"* is *not* selected, and click on *Finish*. The realm should now be visible as a project in the Package Explorer view in Eclipse's Java perspective. Importing resource types If you want to work on a specific resource type that is either a resource type of Yanel, or one belonging to another realm, follow these steps to import it as a project into Eclipse: 1. Follow points #1-2above if you have not already done so. 2. If the resource type you are importing belongs to an external realm, follow point #3above in case you have not already done so. If the resource type you are importing belongs to Yanel, build an Eclipse project using the specific "eclipse" target with the resource's build file: cd {path/to/yanel/root} ./build.sh -f {path/to/yanel/root}/src/.../{resource-directory}/build.xml eclipse 3. In Eclipse, select *File -> Import*, to open the Import dialog. 4. Select *General -> Existing Projects into Workspace*, then click on * Next*. 5. Check *"Select root directory"*, click on *Browse*, and select either a directory containing all the resource-types of your realm (they may be imported all at once), or the directory of the Yanel resource that you w= ant to import ({path/to/yanel/root}/src/.../{resource-directory}, in this ca= se you have to import them one by one). 6. Select the resources that you want to import as projects, make sure *"Copy projects into workspace"* is *not* selected, and click on *Finish*. The resources should now be visible as projects in the Package Explorer view in Eclipse's Java perspective. Importing Yanel 1. Check out and build Yanel as usual, if you have not yet done so. 2. Build an Eclipse project using the specific target "eclipse": cd {path/to/yanel/root} ./build.sh eclipse 3. In Eclipse, select *File -> Import*, to open the Import dialog. 4. Select *General -> Existing Projects into Workspace*, then click on * Next*. 5. Check *"Select root directory"*, click on *Browse*, and select the Yanel root directory (i.e. where build.sh is located) 6. Make sure the Yanel project is selected (should be the only one), *"C= opy projects into workspace"* is *not* selected, and click on *Finish*. The project "yanel" should now be visible in the Package Explorer view in Eclipse's Java perspective. Debugging To start debugging with Eclipse, start Tomcat in debug mode: {path/to/yanel/root}/local/apache-tomcat-5.5.20/bin/catalina.sh jpda start Alternatively, you can (theoretically) also use the Eclipse Tomcat Launcher or other Tomcat plugins. If you succeed in this, please document it here, or send a description to the Yanel developers mailing list . Notes Windows users, please configure your line endings as LF by setting *Prefere= nces -> General -> Workspace -> New text file line delimiter* to *"Unix"*. ------------------------------ TODO: Document how to create a debug configuration andhow to debug across multiple resource-types, which may still be tricky. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010031= 8/ee9def21/attachment.htm From Wayne.Bunting at gurit.com Thu Mar 18 17:01:20 2010 From: Wayne.Bunting at gurit.com (Wayne.Bunting@gurit.com) Date: Thu Mar 18 17:15:21 2010 Subject: [Yanel-dev] AUTO: Wayne Bunting is out of the office. (returning 29/03/2010) Message-ID: I am out of the office until 29/03/2010. I will respond to your message when I return. Note: This is an automated response to your message "[Yanel-dev] [Bug 6967] ease use of resource types from Eclipse (for instance building them)" sent on 18/03/2010 10:18:13. This is the only notification you will receive while this person is away. ********************************************************************* All sales of goods are subject to the terms and conditions of sale (the Conditions) of Gurit (UK) Limited (the Company) which are available on request from the Company or may be viewed on the Gurit Website http://www.gurit.com Any advice given by the Company in connection with the sale of goods or the provision of technical, engineering or other services is given in good faith but the company only warrants that advice in writing and in relation to specific services or a specific project is given with reasonable skill and care. All advice is otherwise given subject to the Conditions. The contents of this message and any attachments are confidential and are intended solely for the attention and use of the addressee only. Information contained in this message may be subject to legal, professional or other privilege or may otherwise be protected by other legal rules. This message should not be copied or forwarded to any other person without the express permission of the sender. If you are not the intended recipient you are not authorised to disclose, copy, distribute or retain this message or any part of it. Gurit (UK) Limited registered offices are: St. Cross Business Park, Newport, Isle of Wight, PO30 5WU, UK The Company is registered in England and Wales. Reg No. 1368806 ********************************************************************* From bugzilla at wyona.com Thu Mar 18 17:39:13 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 18 17:39:15 2010 Subject: [Yanel-dev] [Bug 7072] tinyMCE resource-type: editing looses title Message-ID: <20100318163913.60ED410C9EE@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7072 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal (C) |minor Status|CLOSED |REOPENED OS/Version|Linux |All Priority|P2 |P1 Platform|PC |All Resolution|WORKSFORME | ------- Comment #3 from guillaume.deflache@wyona.com 2010-03-18 17:36 ------- Reoopening and P1, because other people have the same problem: - the guys at http://www.cinemacopain.ch/ - memo: http://lists.wyona.org/pipermail/yanel-usage/2010-March/000145.html -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Thu Mar 18 17:39:54 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 18 17:39:56 2010 Subject: [Yanel-dev] [Bug 7072] tinyMCE resource-type: editing looses title Message-ID: <20100318163954.BD98210C9EE@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7072 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|simon.litwan@wyona.org |yanel-development@wyona.com Status|REOPENED |NEW -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From bugzilla at wyona.com Thu Mar 18 17:42:41 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 18 17:42:43 2010 Subject: [Yanel-dev] [Bug 7072] tinyMCE resource-type: editing looses title Message-ID: <20100318164241.AF15610CA07@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7072 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |6984 nThis| | -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From bugzilla at wyona.com Thu Mar 18 17:42:41 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Thu Mar 18 17:42:44 2010 Subject: [Yanel-dev] [Bug 6984] HTML title of many pages (esp. wiki pages) is not set a real title Message-ID: <20100318164241.815BB10C9EE@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=6984 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |7072 Bug 6984 depends on bug 7072, which changed state. Bug 7072 Summary: tinyMCE resource-type: editing looses title http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7072 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME Status|RESOLVED |CLOSED Status|CLOSED |REOPENED Resolution|WORKSFORME | Status|REOPENED |NEW ------- Comment #1 from guillaume.deflache@wyona.com 2010-03-18 17:40 ------- bug 7072 may also be the culprit on non-wiki pages. -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From mehmet.birgi at wyona.com Mon Mar 22 09:13:36 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Mon Mar 22 09:26:34 2010 Subject: [Yanel-dev] Re: [Dev] Re: Yanel in Eclipse In-Reply-To: <5bf1397d1003180753y43e3d357tcef71b9f80d5643d@mail.gmail.com> References: <5bf1397d1003180603x73ffc277i6f4957454165ca66@mail.gmail.com> <4BA22C5C.3000203@wyona.com> <4BA23A6F.6050709@wyona.com> <4BA23C26.10303@wyona.com> <5bf1397d1003180753y43e3d357tcef71b9f80d5643d@mail.gmail.com> Message-ID: <5bf1397d1003220113h1849e571nf298b80dafeac150@mail.gmail.com> Hi All If there is no more feedback, I will check in this current version later today. Cheers, Memo On Thu, Mar 18, 2010 at 3:53 PM, Mehmet Birgi wrote: > Thanks to Guillaume for providing excellent feedback, here is the second > draft, with his suggestions incorporated (I'm still open to more feedback= ): > > > Setting up Yanel in the Eclipse IDE > > This document will get you started using Eclipse to develop/debug your > Yanel project. To keep things simple and reliable, building and SVN access > will be done outside of Eclipse. Also, it is assumed that you are using a > unix-like shell for command line processing, if you are using the windows > command line, replace the references to the shell scripts below with their > aequivalent dos batch files (e.g. replace "build.sh" with "build.bat") and > "/" with "\". > > Depending on what you will be working on, you might need to import several > projects into Eclipse. In this context, there are 3 types of projects: > realms, resources, and Yanel itself. Please note that importing Yanel into > Eclipse as a project will *not* automatically import Yanel's resource > types, they have to be imported separately, and one by one, as described > below. > Importing a realm > > If you want to work on a realm that has a separate directory from the Yan= el > source, follow these steps to import it as a project into Eclipse: > > 1. Check out Yanel and the external realm, and add the realm to Yanel<= http://127.0.0.1:8080/yanel/yanel-website/en/documentation/how-to-add-a-new= -realm.html> > . > 2. Compile and deploy "yanel-test-1.0-dev-rREVISION.jar": > > cd {path/to/yanel/root} > ./build.sh -f {path/to/yanel/root}/src/test/build.xml install-jar > > This will build the jar file and deploy it automatically to your maven > repository. > 3. Build an Eclipse project using the specific "eclipse" target with > the realm's build file: > > cd {path/to/yanel/root} > ./build.sh -f {path/to/realm/root}/build.xml eclipse > > 4. In Eclipse, select *File -> Import*, to open the Import dialog. > 5. Select *General -> Existing Projects into Workspace*, then click on > *Next*. > 6. Check *"Select root directory"*, click on *Browse*, and select the > realm's root directory (i.e. where build.xml is located) > 7. Make sure the realm project is selected (should be the only one), *= "Copy > projects into workspace"* is *not* selected, and click on *Finish*. > > The realm should now be visible as a project in the Package Explorer view > in Eclipse's Java perspective. > Importing resource types > > If you want to work on a specific resource type that is either a resource > type of Yanel, or one belonging to another realm, follow these steps to > import it as a project into Eclipse: > > 1. Follow points #1-2above if you hav= e not already done so. > 2. If the resource type you are importing belongs to an external realm, > follow point #3above in case you have= not already done so. If the resource type you are > importing belongs to Yanel, build an Eclipse project using the specific > "eclipse" target with the resource's build file: > > cd {path/to/yanel/root} > ./build.sh -f {path/to/yanel/root}/src/.../{resource-directory}/build.= xml eclipse > > 3. In Eclipse, select *File -> Import*, to open the Import dialog. > 4. Select *General -> Existing Projects into Workspace*, then click on > *Next*. > 5. Check *"Select root directory"*, click on *Browse*, and select > either a directory containing all the resource-types of your realm (th= ey may > be imported all at once), or the directory of the Yanel resource that = you > want to import ({path/to/yanel/root}/src/.../{resource-directory}, in = this > case you have to import them one by one). > 6. Select the resources that you want to import as projects, make sure > *"Copy projects into workspace"* is *not* selected, and click on * > Finish*. > > The resources should now be visible as projects in the Package Explorer > view in Eclipse's Java perspective. > Importing Yanel > > 1. Check out and build Yanel as usual, > if you have not yet done so. > 2. Build an Eclipse project using the specific target "eclipse": > > cd {path/to/yanel/root} > ./build.sh eclipse > > 3. In Eclipse, select *File -> Import*, to open the Import dialog. > 4. Select *General -> Existing Projects into Workspace*, then click on > *Next*. > 5. Check *"Select root directory"*, click on *Browse*, and select the > Yanel root directory (i.e. where build.sh is located) > 6. Make sure the Yanel project is selected (should be the only one), *= "Copy > projects into workspace"* is *not* selected, and click on *Finish*. > > The project "yanel" should now be visible in the Package Explorer view in > Eclipse's Java perspective. > Debugging > > To start debugging with Eclipse, start Tomcat in debug mode: > > {path/to/yanel/root}/local/apache-tomcat-5.5.20/bin/catalina.sh jpda start > > Alternatively, you can (theoretically) also use the Eclipse Tomcat Launch= er > or other Tomcat plugins. If you succeed in this, please document it here,= or > send a description to the Yanel developers mailing list > . > Notes > > Windows users, please configure your line endings as LF by setting *Prefe= rences > -> General -> Workspace -> New text file line delimiter* to *"Unix"*. > > ------------------------------ > > TODO: Document how to create a debug configuration andhow to debug across > multiple resource-types, which may still be tricky. > > > > > -- = Mehmet Birgi www.wyona.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032= 2/fa4d8e53/attachment.htm From mehmet.birgi at wyona.com Mon Mar 22 09:25:04 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Mon Mar 22 09:38:02 2010 Subject: [Yanel-dev] Debugging Message-ID: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> I would like to add a parameter "debug" to the script yanel.sh that will start yanel in debug mode (by executing "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). Any objections/ideas? -- Mehmet Birgi www.wyona.com From michael.wechner at wyona.com Mon Mar 22 09:46:42 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Mar 22 09:59:42 2010 Subject: [Yanel-dev] Debugging In-Reply-To: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> References: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> Message-ID: <4BA72E72.8090406@wyona.com> Mehmet Birgi wrote: > I would like to add a parameter "debug" to the script yanel.sh that > will start yanel in debug mode (by executing > "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). Any > objections/ideas? > default should be off Also you might want to think about making it configurable within src/build/local.build.properties, whereas you need to make sure that yanel.sh can be run from various locations. Thanks Michi > > -- > Mehmet Birgi > www.wyona.com > From michael.wechner at wyona.com Mon Mar 22 09:53:30 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Mar 22 10:06:26 2010 Subject: [Yanel-dev] Re: [Dev] Re: Yanel in Eclipse In-Reply-To: <5bf1397d1003220113h1849e571nf298b80dafeac150@mail.gmail.com> References: <5bf1397d1003180603x73ffc277i6f4957454165ca66@mail.gmail.com> <4BA22C5C.3000203@wyona.com> <4BA23A6F.6050709@wyona.com> <4BA23C26.10303@wyona.com> <5bf1397d1003180753y43e3d357tcef71b9f80d5643d@mail.gmail.com> <5bf1397d1003220113h1849e571nf298b80dafeac150@mail.gmail.com> Message-ID: <4BA7300A.8010600@wyona.com> Mehmet Birgi wrote: > Hi All > > If there is no more feedback, I will check in this current version > later today. sounds good to me. Thanks Michi > > Cheers, > > Memo > > > > On Thu, Mar 18, 2010 at 3:53 PM, Mehmet Birgi > wrote: > > Thanks to Guillaume for providing excellent feedback, here is the > second draft, with his suggestions incorporated (I'm still open to > more feedback): > > > Setting up Yanel in the Eclipse IDE > > This document will get you started using Eclipse to develop/debug > your Yanel project. To keep things simple and reliable, building > and SVN access will be done outside of Eclipse. Also, it is > assumed that you are using a unix-like shell for command line > processing, if you are using the windows command line, replace the > references to the shell scripts below with their aequivalent dos > batch files (e.g. replace "build.sh" with "build.bat") and "/" > with "\". > > Depending on what you will be working on, you might need to import > several projects into Eclipse. In this context, there are 3 types > of projects: realms, resources, and Yanel itself. Please note that > importing Yanel into Eclipse as a project will *not* automatically > import Yanel's resource types, they have to be imported > separately, and one by one, as described below. > > > Importing a realm > > If you want to work on a realm that has a separate directory from > the Yanel source, follow these steps to import it as a project > into Eclipse: > > 1. Check out Yanel and the external realm, and add the realm to > Yanel > . > 2. Compile and deploy "yanel-test-1.0-dev-rREVISION.jar": > > cd {path/to/yanel/root} > ./build.sh -f {path/to/yanel/root}/src/test/build.xml install-jar > > > This will build the jar file and deploy it automatically to > your maven repository. > > 3. > Build an Eclipse project using the specific "eclipse" target > with the realm's build file: > > cd {path/to/yanel/root} > ./build.sh -f {path/to/realm/root}/build.xml eclipse > > 4. In Eclipse, select /File -> Import/, to open the Import dialog. > 5. Select /General -> Existing Projects into Workspace/, then > click on /Next/. > 6. Check /"Select root directory"/, click on /Browse/, and > select the realm's root directory (i.e. where build.xml is > located) > 7. Make sure the realm project is selected (should be the only > one), /"Copy projects into workspace"/ is *not* selected, > and click on /Finish/. > > The realm should now be visible as a project in the Package > Explorer view in Eclipse's Java perspective. > > > Importing resource types > > If you want to work on a specific resource type that is either a > resource type of Yanel, or one belonging to another realm, follow > these steps to import it as a project into Eclipse: > > 1. Follow points #1-2 > > above if you have not already done so. > 2. If the resource type you are importing belongs to an > external realm, follow point #3 > > above in case you have not already done so. If the resource > type you are importing belongs to Yanel, build an Eclipse > project using the specific "eclipse" target with the > resource's build file: > > cd {path/to/yanel/root} > ./build.sh -f {path/to/yanel/root}/src/.../{resource-directory}/build.xml eclipse > > 3. In Eclipse, select /File -> Import/, to open the Import dialog. > 4. Select /General -> Existing Projects into Workspace/, then > click on /Next/. > 5. Check /"Select root directory"/, click on /Browse/, and > select either a directory containing all the resource-types > of your realm (they may be imported all at once), or the > directory of the Yanel resource that you want to import > ({path/to/yanel/root}/src/.../{resource-directory}, in this > case you have to import them one by one). > 6. Select the resources that you want to import as projects, > make sure /"Copy projects into workspace"/ is *not* > selected, and click on /Finish/. > > The resources should now be visible as projects in the Package > Explorer view in Eclipse's Java perspective. > > > Importing Yanel > > 1. Check out and build Yanel as usual > , if you > have not yet done so. > 2. > Build an Eclipse project using the specific target "eclipse": > > cd {path/to/yanel/root} > ./build.sh eclipse > > 3. In Eclipse, select /File -> Import/, to open the Import dialog. > 4. Select /General -> Existing Projects into Workspace/, then > click on /Next/. > 5. Check /"Select root directory"/, click on /Browse/, and > select the Yanel root directory (i.e. where build.sh is located) > 6. Make sure the Yanel project is selected (should be the only > one), /"Copy projects into workspace"/ is *not* selected, > and click on /Finish/. > > The project "yanel" should now be visible in the Package Explorer > view in Eclipse's Java perspective. > > > Debugging > > To start debugging with Eclipse, start Tomcat in debug mode: > > {path/to/yanel/root}/local/apache-tomcat-5.5.20/bin/catalina.sh jpda start > > Alternatively, you can (theoretically) also use the Eclipse Tomcat > Launcher or other Tomcat plugins. If you succeed in this, please > document it here, or send a description to the Yanel developers > mailing list . > > > Notes > > Windows users, please configure your line endings as LF by setting > /Preferences -> General -> Workspace -> New text file line > delimiter/ to /"Unix"/. > > ------------------------------------------------------------------------ > > TODO: Document how to create a debug configuration andhow to debug > across multiple resource-types, which may still be tricky. > > > > > > > > -- > Mehmet Birgi > www.wyona.com > From mehmet.birgi at wyona.com Mon Mar 22 10:10:38 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Mon Mar 22 10:23:36 2010 Subject: [Yanel-dev] Debugging In-Reply-To: <4BA72E72.8090406@wyona.com> References: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> <4BA72E72.8090406@wyona.com> Message-ID: <5bf1397d1003220210v90fe222gcc48455e360074d6@mail.gmail.com> On Mon, Mar 22, 2010 at 9:46 AM, Michael Wechner wrote: > Mehmet Birgi wrote: >> >> I would like to add a parameter "debug" to the script yanel.sh that >> will start yanel in debug mode (by executing >> "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). Any >> objections/ideas? >> > > default should be off the way i thought of doing it (see below) would only do this if you entered ".../yanel.sh debug" (instead of e.g. ".../yanel.sh start") > > Also you might want to think about making it configurable within > src/build/local.build.properties, > whereas you need to make sure that yanel.sh can be run from various > locations. my idea was to make yanel.sh call ant with target "debug-yanel" which would be added to src/build/build.xml wdyt? From michael.wechner at wyona.com Mon Mar 22 10:20:57 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Mar 22 10:33:52 2010 Subject: [Yanel-dev] Debugging In-Reply-To: <5bf1397d1003220210v90fe222gcc48455e360074d6@mail.gmail.com> References: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> <4BA72E72.8090406@wyona.com> <5bf1397d1003220210v90fe222gcc48455e360074d6@mail.gmail.com> Message-ID: <4BA73679.4090909@wyona.com> Mehmet Birgi wrote: > On Mon, Mar 22, 2010 at 9:46 AM, Michael Wechner > wrote: > >> Mehmet Birgi wrote: >> >>> I would like to add a parameter "debug" to the script yanel.sh that >>> will start yanel in debug mode (by executing >>> "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). Any >>> objections/ideas? >>> >>> >> default should be off >> > > the way i thought of doing it (see below) would only do this if you > entered ".../yanel.sh debug" (instead of e.g. ".../yanel.sh start") > I would rather prefer something like ./yanel.sh --debug start or ./yanel.sh -d start Thanks Michi > >> Also you might want to think about making it configurable within >> src/build/local.build.properties, >> whereas you need to make sure that yanel.sh can be run from various >> locations. >> > > my idea was to make yanel.sh call ant with target "debug-yanel" which > would be added to src/build/build.xml > > wdyt? > From mehmet.birgi at wyona.com Mon Mar 22 10:30:32 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Mon Mar 22 10:43:30 2010 Subject: [Yanel-dev] Debugging In-Reply-To: <4BA73679.4090909@wyona.com> References: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> <4BA72E72.8090406@wyona.com> <5bf1397d1003220210v90fe222gcc48455e360074d6@mail.gmail.com> <4BA73679.4090909@wyona.com> Message-ID: <5bf1397d1003220230m4e679a45y91560454cad49456@mail.gmail.com> On Mon, Mar 22, 2010 at 10:20 AM, Michael Wechner wrote: > Mehmet Birgi wrote: >> >> On Mon, Mar 22, 2010 at 9:46 AM, Michael Wechner >> wrote: >> >>> >>> Mehmet Birgi wrote: >>> >>>> >>>> I would like to add a parameter "debug" to the script yanel.sh that >>>> will start yanel in debug mode (by executing >>>> "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). Any >>>> objections/ideas? >>>> >>>> >>> >>> default should be off >>> >> >> the way i thought of doing it (see below) would only do this if you >> entered ".../yanel.sh debug" (instead of e.g. ".../yanel.sh start") >> > > I would rather prefer something like > > ./yanel.sh --debug start > > or > > ./yanel.sh -d start afaics, this could be done either by modifying the target "startup-tomcat-unix" in ".../src/build/targets/cruise-control/continuous-integration.xml", or adding an additional target in "src/build/build.xml", while i would prefer the second option. wdyt? From michael.wechner at wyona.com Mon Mar 22 11:18:11 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Mar 22 11:31:05 2010 Subject: [Yanel-dev] Debugging In-Reply-To: <5bf1397d1003220230m4e679a45y91560454cad49456@mail.gmail.com> References: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> <4BA72E72.8090406@wyona.com> <5bf1397d1003220210v90fe222gcc48455e360074d6@mail.gmail.com> <4BA73679.4090909@wyona.com> <5bf1397d1003220230m4e679a45y91560454cad49456@mail.gmail.com> Message-ID: <4BA743E3.3010104@wyona.com> Mehmet Birgi wrote: > On Mon, Mar 22, 2010 at 10:20 AM, Michael Wechner > wrote: > >> Mehmet Birgi wrote: >> >>> On Mon, Mar 22, 2010 at 9:46 AM, Michael Wechner >>> wrote: >>> >>> >>>> Mehmet Birgi wrote: >>>> >>>> >>>>> I would like to add a parameter "debug" to the script yanel.sh that >>>>> will start yanel in debug mode (by executing >>>>> "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). Any >>>>> objections/ideas? >>>>> >>>>> >>>>> >>>> default should be off >>>> >>>> >>> the way i thought of doing it (see below) would only do this if you >>> entered ".../yanel.sh debug" (instead of e.g. ".../yanel.sh start") >>> >>> >> I would rather prefer something like >> >> ./yanel.sh --debug start >> >> or >> >> ./yanel.sh -d start >> > > afaics, this could be done either by modifying the target > "startup-tomcat-unix" in > ".../src/build/targets/cruise-control/continuous-integration.xml", or > adding an additional target in "src/build/build.xml", while i would > prefer the second option. wdyt? > I am not sure I understand. Maybe it's best if you make a patch of what you would like to do and add it to bugzilla for review. Thanks Michi From mehmet.birgi at wyona.com Mon Mar 22 11:47:47 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Mon Mar 22 12:00:45 2010 Subject: [Yanel-dev] Debugging In-Reply-To: <4BA743E3.3010104@wyona.com> References: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> <4BA72E72.8090406@wyona.com> <5bf1397d1003220210v90fe222gcc48455e360074d6@mail.gmail.com> <4BA73679.4090909@wyona.com> <5bf1397d1003220230m4e679a45y91560454cad49456@mail.gmail.com> <4BA743E3.3010104@wyona.com> Message-ID: <5bf1397d1003220347k6e03a263u79325edc70e34105@mail.gmail.com> I am not sure how and where to add this to Bugzilla, but I have attached the diffs to this mail as an alternative. Please let me know if there is anything else I need to do. This approach seems to work, at least on my machine (of course, there is no windows version for now, I could try to add it if this is needed, or maybe someone using a windows box should do this?). On Mon, Mar 22, 2010 at 11:18 AM, Michael Wechner wrote: > Mehmet Birgi wrote: >> >> On Mon, Mar 22, 2010 at 10:20 AM, Michael Wechner >> wrote: >> >>> >>> Mehmet Birgi wrote: >>> >>>> >>>> On Mon, Mar 22, 2010 at 9:46 AM, Michael Wechner >>>> wrote: >>>> >>>> >>>>> >>>>> Mehmet Birgi wrote: >>>>> >>>>> >>>>>> >>>>>> I would like to add a parameter "debug" to the script yanel.sh that >>>>>> will start yanel in debug mode (by executing >>>>>> "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). Any >>>>>> objections/ideas? >>>>>> >>>>>> >>>>>> >>>>> >>>>> default should be off >>>>> >>>>> >>>> >>>> the way i thought of doing it (see below) would only do this if you >>>> entered ".../yanel.sh debug" (instead of e.g. ".../yanel.sh start") >>>> >>>> >>> >>> I would rather prefer something like >>> >>> ./yanel.sh --debug start >>> >>> or >>> >>> ./yanel.sh -d start >>> >> >> afaics, this could be done either by modifying the target >> "startup-tomcat-unix" in >> ".../src/build/targets/cruise-control/continuous-integration.xml", or >> adding an additional target in "src/build/build.xml", while i would >> prefer the second option. wdyt? >> > > I am not sure I understand. Maybe it's best if you make a patch of what y= ou > would like to do and add it to bugzilla for review. > > Thanks > > Michi > > -- > Yanel-development mailing list Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > -- = Mehmet Birgi www.wyona.com -------------- next part -------------- Index: src/build/build.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- src/build/build.xml (revision 48179) +++ src/build/build.xml (working copy) @@ -278,4 +278,12 @@ = + + Starting Yanel in debug mode ... + + + + + + Index: yanel.sh =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- yanel.sh (revision 48179) +++ yanel.sh (working copy) @@ -58,6 +58,9 @@ elif [ "$1" =3D "stop" ]; then echo "INFO: Stopping Yanel..." $OUR_ANT stop-tomcat +elif [ "$1" =3D "debug" ]; then + echo "INFO: Starting Yanel in debug mode..." + $OUR_ANT start-tomcat-debug elif [ "$1" =3D "start-jetty" ]; then echo "INFO: Starting Yanel on Jetty..." MAVEN=3D`which mvn` @@ -105,6 +108,7 @@ echo "start - Startup yanel webapp" echo "stop - Shutdown yanel webapp" echo "cmdl - Use yanel on the command line" + echo "debug - Start yanel in debug mode" echo "start-jetty - TODO" echo "configure - TODO" echo "build - TODO" From michael.wechner at wyona.com Mon Mar 22 11:58:52 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Mar 22 12:13:12 2010 Subject: [Yanel-dev] Debugging In-Reply-To: <5bf1397d1003220347k6e03a263u79325edc70e34105@mail.gmail.com> References: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> <4BA72E72.8090406@wyona.com> <5bf1397d1003220210v90fe222gcc48455e360074d6@mail.gmail.com> <4BA73679.4090909@wyona.com> <5bf1397d1003220230m4e679a45y91560454cad49456@mail.gmail.com> <4BA743E3.3010104@wyona.com> <5bf1397d1003220347k6e03a263u79325edc70e34105@mail.gmail.com> Message-ID: <4BA74D6C.3000801@wyona.com> Mehmet Birgi wrote: > I am not sure how and where to add this to Bugzilla, Let's learn it then ... create a new Bugzilla entry: http://www.yanel.org/en/task-bug-tracker.html and then add the patch as attachment to this new Bugzilla entry (see link "Create a new attachment") > but I have > attached the diffs to this mail as an alternative. Please let me know > if there is anything else I need to do. > add it to Bugzilla and I will be happy to review it ;-) Thanks Michi > This approach seems to work, at least on my machine (of course, there > is no windows version for now, I could try to add it if this is > needed, or maybe someone using a windows box should do this?). > > > > On Mon, Mar 22, 2010 at 11:18 AM, Michael Wechner > wrote: > >> Mehmet Birgi wrote: >> >>> On Mon, Mar 22, 2010 at 10:20 AM, Michael Wechner >>> wrote: >>> >>> >>>> Mehmet Birgi wrote: >>>> >>>> >>>>> On Mon, Mar 22, 2010 at 9:46 AM, Michael Wechner >>>>> wrote: >>>>> >>>>> >>>>> >>>>>> Mehmet Birgi wrote: >>>>>> >>>>>> >>>>>> >>>>>>> I would like to add a parameter "debug" to the script yanel.sh that >>>>>>> will start yanel in debug mode (by executing >>>>>>> "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). Any >>>>>>> objections/ideas? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> default should be off >>>>>> >>>>>> >>>>>> >>>>> the way i thought of doing it (see below) would only do this if you >>>>> entered ".../yanel.sh debug" (instead of e.g. ".../yanel.sh start") >>>>> >>>>> >>>>> >>>> I would rather prefer something like >>>> >>>> ./yanel.sh --debug start >>>> >>>> or >>>> >>>> ./yanel.sh -d start >>>> >>>> >>> afaics, this could be done either by modifying the target >>> "startup-tomcat-unix" in >>> ".../src/build/targets/cruise-control/continuous-integration.xml", or >>> adding an additional target in "src/build/build.xml", while i would >>> prefer the second option. wdyt? >>> >>> >> I am not sure I understand. Maybe it's best if you make a patch of what you >> would like to do and add it to bugzilla for review. >> >> Thanks >> >> Michi >> >> -- >> Yanel-development mailing list Yanel-development@wyona.com >> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development >> >> > > > > From bugzilla at wyona.com Mon Mar 22 12:22:18 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 12:22:22 2010 Subject: [Yanel-dev] [Bug 7541] New: Target for debugging in Yanel build system Message-ID: <20100322112218.2437110CAC9@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 Summary: Target for debugging in Yanel build system Product: Yanel Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal (C) Priority: P1 Component: General AssignedTo: mehmet.birgi@wyona.com ReportedBy: mehmet.birgi@wyona.com QAContact: yanel-development@wyona.com I would like to add a parameter "debug" to the script yanel.sh that will start yanel in debug mode (by executing "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). A first attempt will be attached for review. -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 12:23:14 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 12:23:16 2010 Subject: [Yanel-dev] [Bug 7541] Target for debugging in Yanel build system Message-ID: <20100322112314.30CEB10CAC9@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 ------- Comment #1 from mehmet.birgi@wyona.com 2010-03-22 12:20 ------- Created an attachment (id=1278) --> (http://bugzilla.wyona.com/cgi-bin/bugzilla/attachment.cgi?id=1278&action=view) proposed diffs for debug target Diff file attached -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From mehmet.birgi at wyona.com Mon Mar 22 12:11:27 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Mon Mar 22 12:24:23 2010 Subject: [Yanel-dev] Debugging In-Reply-To: <4BA74D6C.3000801@wyona.com> References: <5bf1397d1003220125o73538d64ne5786dd5bc2928e2@mail.gmail.com> <4BA72E72.8090406@wyona.com> <5bf1397d1003220210v90fe222gcc48455e360074d6@mail.gmail.com> <4BA73679.4090909@wyona.com> <5bf1397d1003220230m4e679a45y91560454cad49456@mail.gmail.com> <4BA743E3.3010104@wyona.com> <5bf1397d1003220347k6e03a263u79325edc70e34105@mail.gmail.com> <4BA74D6C.3000801@wyona.com> Message-ID: <5bf1397d1003220411i111af43ambe53d2ba857f5e3d@mail.gmail.com> ok, done :-) On Mon, Mar 22, 2010 at 11:58 AM, Michael Wechner wrote: > Mehmet Birgi wrote: >> >> I am not sure how and where to add this to Bugzilla, > > Let's learn it then ... > > create a new Bugzilla entry: > > http://www.yanel.org/en/task-bug-tracker.html > > and then add the patch as attachment to this new Bugzilla entry (see link > "Create a new attachment") > > >> ?but I have >> attached the diffs to this mail as an alternative. Please let me know >> if there is anything else I need to do. >> > > add it to Bugzilla and I will be happy to review it ;-) > > Thanks > > Michi >> >> This approach seems to work, at least on my machine (of course, there >> is no windows version for now, I could try to add it if this is >> needed, or maybe someone using a windows box should do this?). >> >> >> >> On Mon, Mar 22, 2010 at 11:18 AM, Michael Wechner >> wrote: >> >>> >>> Mehmet Birgi wrote: >>> >>>> >>>> On Mon, Mar 22, 2010 at 10:20 AM, Michael Wechner >>>> wrote: >>>> >>>> >>>>> >>>>> Mehmet Birgi wrote: >>>>> >>>>> >>>>>> >>>>>> On Mon, Mar 22, 2010 at 9:46 AM, Michael Wechner >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> Mehmet Birgi wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> I would like to add a parameter "debug" to the script yanel.sh that >>>>>>>> will start yanel in debug mode (by executing >>>>>>>> "local/apache-tomcat-5.5.20/bin/catalina.sh jpda start"). Any >>>>>>>> objections/ideas? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> default should be off >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> the way i thought of doing it (see below) would only do this if you >>>>>> entered ".../yanel.sh debug" (instead of e.g. ".../yanel.sh start") >>>>>> >>>>>> >>>>>> >>>>> >>>>> I would rather prefer something like >>>>> >>>>> ./yanel.sh --debug start >>>>> >>>>> or >>>>> >>>>> ./yanel.sh -d start >>>>> >>>>> >>>> >>>> afaics, this could be done either by modifying the target >>>> "startup-tomcat-unix" in >>>> ".../src/build/targets/cruise-control/continuous-integration.xml", or >>>> adding an additional target in "src/build/build.xml", while i would >>>> prefer the second option. wdyt? >>>> >>>> >>> >>> I am not sure I understand. Maybe it's best if you make a patch of what >>> you >>> would like to do and add it to bugzilla for review. >>> >>> 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 > -- Mehmet Birgi www.wyona.com From bugzilla at wyona.com Mon Mar 22 12:51:30 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 12:51:33 2010 Subject: [Yanel-dev] [Bug 7541] Target for debugging in Yanel build system Message-ID: <20100322115130.86D7810CAC9@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 ------- Comment #2 from michael.wechner@wyona.org 2010-03-22 12:48 ------- In reason why you do not want to reuse the target startup-tomcat-unix-node1 within src/build/targets/cruise-control/continuous-integration.xml ? As mentioned within my email it seems to me that --debug should be an option for the start argument. Why do you want to use it as a start argument itself instead "--debug start"? How exactly are you using this functionality? Can this only be used by Eclipse? -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 13:10:49 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 13:12:24 2010 Subject: [Yanel-dev] [Bug 7541] Target for debugging in Yanel build system Message-ID: <20100322121049.51AFB10CACF@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 ------- Comment #3 from mehmet.birgi@wyona.com 2010-03-22 13:07 ------- I thought that debugging would be done on a local machine, and not on Hudson, so it seemed more logical not to put this into continuous-integration.xml, but I can change that, of course. And re arg instead of option, it just seemed simpler. Again, I can change that :-) Afaik, this should work with any JPDA capable debugger, but I have only tried it with Eclipse. -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 14:25:59 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 14:28:23 2010 Subject: [Yanel-dev] [Bug 7541] Target for debugging in Yanel build system Message-ID: <20100322132559.0376710CADA@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 ------- Comment #4 from mehmet.birgi@wyona.com 2010-03-22 14:23 ------- Guillaume had the idea to put all tomcat related targets in .../tools/apache-tomcat/build.xml, which exists already, instead of creating yet another build file. I will start with the debug target, without touching the rest for now, but everything that is in "cruise-control" could be moved here eventually for consistency (I could open a new bugzilla entry for this, if everybody approves). -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 14:31:50 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 14:31:51 2010 Subject: [Yanel-dev] [Bug 7541] Target for debugging in Yanel build system Message-ID: <20100322133150.5486810CAD6@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 ------- Comment #5 from michael.wechner@wyona.org 2010-03-22 14:28 ------- as discussed during lunch the startup/shutdown targets have nothing to do with continuous integration and hence these files should be refactored (see Guillaume's suggestion, but please only move these startup/shutdown targets, which let's make "small steps) Re debug as option, yes, please change this. Re "non-eclipse" one might want to use http://www.vim.org/scripts/script.php?script_id=1954 http://www.vim.org/scripts/script.php?script_id=1154 http://articles.techrepublic.com.com/5100-10878_11-6139512.html -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 15:01:52 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 15:01:54 2010 Subject: [Yanel-dev] [Bug 7541] Target for debugging in Yanel build system Message-ID: <20100322140152.40EFD10CADC@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 ------- Comment #6 from mehmet.birgi@wyona.com 2010-03-22 14:58 ------- Created an attachment (id=1279) --> (http://bugzilla.wyona.com/cgi-bin/bugzilla/attachment.cgi?id=1279&action=view) new patch Changed the implementation as suggested, please review again. -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 15:13:50 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 15:13:52 2010 Subject: [Yanel-dev] [Bug 4970] [wanted1.0+][doc] picture of components involved and request process Message-ID: <20100322141350.1F19010CADD@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=4970 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|simon.litwan@wyona.org |mehmet.birgi@wyona.com -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From bugzilla at wyona.com Mon Mar 22 15:14:32 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 15:14:34 2010 Subject: [Yanel-dev] [Bug 5149] [wanted1.0+] [doc] i18n of navigation (see for example the Yanel website) Message-ID: <20100322141432.8150D10CADD@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=5149 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mehmet.birgi@wyona.com -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 15:15:14 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 15:15:15 2010 Subject: [Yanel-dev] [Bug 5944] [wanted1.0+] [doc] sketch of Yanel functionality Message-ID: <20100322141514.3F7B210CAD5@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=5944 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mehmet.birgi@wyona.com -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From bugzilla at wyona.com Mon Mar 22 15:16:27 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 15:16:29 2010 Subject: [Yanel-dev] [Bug 6871] [wanted1.0?] help users with Tomcat port configuration Message-ID: <20100322141627.CF06110CADF@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=6871 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mehmet.birgi@wyona.com -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. You are the assignee for the bug, or are watching the assignee. From bugzilla at wyona.com Mon Mar 22 15:26:15 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 15:26:19 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322142615.EBA1210CADC@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal (C) |enhancement Summary|Target for debugging in |target for debugging in |Yanel build system |Yanel build system ------- Comment #7 from guillaume.deflache@wyona.com 2010-03-22 15:23 ------- Looks OK to me, except maybe s/// -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 15:28:33 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 15:28:35 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322142833.3BB3810CAE0@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1278 is|0 |1 obsolete| | ------- Comment #8 from guillaume.deflache@wyona.com 2010-03-22 15:25 ------- (From update of attachment 1278) Nitpick: please mark obsolete attachments as obsolete! ;) -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 15:29:44 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 15:29:45 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322142944.8273010CAE3@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1279|diff.txt |start-tomcat-debug.diff filename| | Attachment #1279 is|0 |1 patch| | -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From guillaume.deflache at wyona.com Mon Mar 22 15:23:52 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=) Date: Mon Mar 22 15:35:46 2010 Subject: IntelliJ IDEA and Yanel (was: Re: [Yanel-dev] Re: [Dev] Re: Yanel in Eclipse) In-Reply-To: <5bf1397d1003220113h1849e571nf298b80dafeac150@mail.gmail.com> References: <5bf1397d1003180603x73ffc277i6f4957454165ca66@mail.gmail.com> <4BA22C5C.3000203@wyona.com> <4BA23A6F.6050709@wyona.com> <4BA23C26.10303@wyona.com> <5bf1397d1003180753y43e3d357tcef71b9f80d5643d@mail.gmail.com> <5bf1397d1003220113h1849e571nf298b80dafeac150@mail.gmail.com> Message-ID: <4BA77D78.8040107@wyona.com> Mehmet Birgi schrieb: > Hi All Hi! [about the Eclipse documentation now at :] > If there is no more feedback, I will check in this current version later > today. Thanks for doing it (I had no further remarks). You should also empty the page at : pages of this wiki cannot be really deleted (or even made read-only AFAIK), so please proceed as done for http://documentation.yanel.wyona.org/wiki/wiki/Glossary See also It also occurred to me at lunch that I already had checked that IntelliJ IDEA supports importing Eclipse projects just fine (I tested that with Community Edition version 9.0 some time ago). Maybe we should add a note about that somewhere, although I am not sure where. Also having never tried it much more, I am not sure if what we did for Eclipse WRT Java debugging is sufficient for IntelliJ IDEA as well... Feel free to try it! ;) [1]: http://www.jetbrains.com/idea/ widely recognized as the best *commercial* Java IDE productivity-wise, if not the best at all. cheers, Guillaume From guillaume.deflache at wyona.com Mon Mar 22 15:49:06 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Mon Mar 22 16:01:02 2010 Subject: [Yanel-dev] policy viewer refactoring (inside "policymanager" resource-type) Message-ID: <4BA78362.1050309@wyona.com> Hi! For a project I need to implement some specific behaviour for the policy viewer. So as to also reuse existing Yanel code for other unchanged things I'd need to be able to reuse parts of the existing Yanel implementation. ATM alas the policy viewer is implemented by calling the sole static method PolicyViewer#getXHTMLView(PolicyManager pm, GroupManager gm, String path, String contentItemId, [other view options' parameters]) which does not allow any kind of overriding. I'd like to introduce the following method in org.wyona.yanel.impl.resources.policymanager.PolicyManagerResource: protected PolicyViewer getPolicyViewer(PolicyManager pm, GroupManager gm, [other view options' parameters]); with the visible API of PolicyViewer being: InputStream getXHTMLInputStream(String path, String contentItemId) throws Exception Then I would be able to just change the used resource-type in $MY_SPECIFIC_REALM_DIR/src/webapp/global-resource-configs/policy-manager_yanel-rc.xml to one using my own PolicyViewer-based Java class! WDYT? Cheers, Guillaume From mehmet.birgi at wyona.com Mon Mar 22 15:50:19 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Mon Mar 22 16:03:16 2010 Subject: IntelliJ IDEA and Yanel (was: Re: [Yanel-dev] Re: [Dev] Re: Yanel in Eclipse) In-Reply-To: <4BA77D78.8040107@wyona.com> References: <5bf1397d1003180603x73ffc277i6f4957454165ca66@mail.gmail.com> <4BA22C5C.3000203@wyona.com> <4BA23A6F.6050709@wyona.com> <4BA23C26.10303@wyona.com> <5bf1397d1003180753y43e3d357tcef71b9f80d5643d@mail.gmail.com> <5bf1397d1003220113h1849e571nf298b80dafeac150@mail.gmail.com> <4BA77D78.8040107@wyona.com> Message-ID: <5bf1397d1003220750o73c054f3s49cbac527a65f673@mail.gmail.com> Thanks, I have edited the wiki to reflect the changes. 2010/3/22 Guillaume D=E9flache > Mehmet Birgi schrieb: > >> Hi All >> > > Hi! > > > [about the Eclipse documentation now at < > http://yanel.wyona.org/en/documentation/development/build_setup_eclipse_i= de.html > >:] > >> If there is no more feedback, I will check in this current version later >> today. >> > > Thanks for doing it (I had no further remarks). > > You should also empty the page at < > http://documentation.yanel.wyona.org/wiki/wiki/Setup%20Yanel%20in%20Eclip= se%20IDE>: > pages of this wiki cannot be really deleted (or even made read-only AFAIK= ), > so please proceed as done for > http://documentation.yanel.wyona.org/wiki/wiki/Glossary > See also > > > It also occurred to me at lunch that I already had checked that IntelliJ > IDEA supports importing Eclipse projects just fine (I tested that with > Community Edition version 9.0 some time ago). > Maybe we should add a note about that somewhere, although I am not sure > where. > Also having never tried it much more, I am not sure if what we did for > Eclipse WRT Java debugging is sufficient for IntelliJ IDEA as well... Feel > free to try it! ;) > > [1]: http://www.jetbrains.com/idea/ widely recognized as the best > *commercial* Java IDE productivity-wise, if not the best at all. > > > cheers, > Guillaume > -- > Yanel-development mailing list Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > -- = Mehmet Birgi www.wyona.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032= 2/a80445d3/attachment.htm From michael.wechner at wyona.com Mon Mar 22 17:22:51 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Mar 22 17:35:49 2010 Subject: [Yanel-dev] policy viewer refactoring (inside "policymanager" resource-type) In-Reply-To: <4BA78362.1050309@wyona.com> References: <4BA78362.1050309@wyona.com> Message-ID: <4BA7995B.9040901@wyona.com> Guillaume D?flache wrote: > Hi! > > For a project I need to implement some specific behaviour for the > policy viewer. > So as to also reuse existing Yanel code for other unchanged things I'd > need to be able to reuse parts of the existing Yanel implementation. > > > ATM alas the policy viewer is implemented by calling the sole static > method PolicyViewer#getXHTMLView(PolicyManager pm, GroupManager gm, > String path, String contentItemId, [other view options' parameters]) > which does not allow any kind of overriding. > > > I'd like to introduce the following method in > org.wyona.yanel.impl.resources.policymanager.PolicyManagerResource: > > protected PolicyViewer getPolicyViewer(PolicyManager pm, > GroupManager gm, [other view options' parameters]); > > with the visible API of PolicyViewer being: > > InputStream getXHTMLInputStream(String path, String contentItemId) > throws Exception > > Then I would be able to just change the used resource-type in > $MY_SPECIFIC_REALM_DIR/src/webapp/global-resource-configs/policy-manager_yanel-rc.xml > to one using my own PolicyViewer-based Java class! > > WDYT? What exactly would you like to do? The reason I am asking is because I think "overriding/inheritance" is not always a good thing and maybe it's better to introduce appropriate interfaces. Thanks Michi > > > Cheers, > Guillaume > From michael.wechner at wyona.com Mon Mar 22 17:29:01 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon Mar 22 17:43:34 2010 Subject: [Yanel-dev] Re: [Yanel-commits] rev 48212 - public/yanel/trunk/src/contributions/resources/policymanager/src/java/org/wyona/yanel/impl/resources/policymanager In-Reply-To: <201003221522.o2MFMinp009856@cvs-extra.wyona.com> References: <201003221522.o2MFMinp009856@cvs-extra.wyona.com> Message-ID: <4BA79ACD.2000609@wyona.com> Dear Guillaume guillaume@wyona.com wrote: > return sb.toString(); > } catch(Exception e) { > - log.error(e, e); > + log.error(e.getMessage(), e); > Why are you changing these? I am afraid this will lead to a commit war, because I will change it back shortly ;-) So, let's discuss it first and write down some rules how we want to handle it. Thanks Michi From bugzilla at wyona.com Mon Mar 22 17:51:57 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 17:52:00 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322165157.F25BB10C986@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 mehmet.birgi@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #9 from mehmet.birgi@wyona.com 2010-03-22 17:49 ------- target added in r48214 (still TODO: refactor tomcat targets out of cruise-control) -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 17:56:02 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 17:56:06 2010 Subject: [Yanel-dev] [Bug 7542] New: Refactor tomcat targets in build system Message-ID: <20100322165602.DEB4F10C986@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7542 Summary: Refactor tomcat targets in build system Product: Yanel Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: General AssignedTo: mehmet.birgi@wyona.com ReportedBy: mehmet.birgi@wyona.com QAContact: yanel-development@wyona.com Tomcat related ant targets, especially for starting and stopping, are mostly in .../targets/cruise-control, which is outdated. They should be refactored to a better place, e.g. .../tools/apache-tomcat/build.xml. -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 18:22:08 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 18:22:11 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322172208.C0D3B10CA25@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 michael.wechner@wyona.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 18:23:16 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 18:23:18 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322172316.4D2A910CA25@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 michael.wechner@wyona.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW ------- Comment #10 from michael.wechner@wyona.org 2010-03-22 18:20 ------- As discussed offline: - Testing! - Do not commit before review has finished (or shout at least that you would like to commit) -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 18:30:18 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 18:30:19 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322173018.37CB110CA25@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 ------- Comment #11 from michael.wechner@wyona.org 2010-03-22 18:27 ------- As discussed please revert your changes such that you can take your time to figure out what is wrong with your changes. Thanks Michi -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From guillaume.deflache at wyona.com Mon Mar 22 18:58:46 2010 From: guillaume.deflache at wyona.com (=?UTF-8?B?R3VpbGxhdW1lIETDqWZsYWNoZQ==?=) Date: Mon Mar 22 19:10:40 2010 Subject: [Yanel-dev] exceptions, logging and related best practices (was: Re: [Yanel-commits] rev 48212 - public/yanel/trunk/src/contributions/resources/policymanager/src/java/org/wyona/yanel/impl/resources/policymanager) In-Reply-To: <4BA79ACD.2000609@wyona.com> References: <201003221522.o2MFMinp009856@cvs-extra.wyona.com> <4BA79ACD.2000609@wyona.com> Message-ID: <4BA7AFD6.3060105@wyona.com> Michael Wechner schrieb: > Dear Guillaume > > guillaume@wyona.com wrote: >> return sb.toString(); >> } catch(Exception e) { >> - log.error(e, e); >> + log.error(e.getMessage(), e); >> > > Why are you changing these? Because for some reason I believed that toString() called getLocalizedMessage() by default (that would have produced French messages if your JVM locale was set to French, which believe me, are almost uncomprehensible even to French people compared to the English ones!). But after rereading the Javadoc for Throwable it seems I was completely mistaken, so I won't do that anymore from now on! Thanks for noticing it! > I am afraid this will lead to a commit war, because I will change it > back shortly ;-) Indeed toString() seems to provide additional details and to call getMessage() by default: http://java.sun.com/javase/6/docs/api/java/lang/Throwable.html#toString%28%29 And it's also nicely shorter and more readable if a little odd-looking at 1st glance. > So, let's discuss it first and write down some rules how we want to > handle it. I'll start then (notes: T extends Throwable, what is applicable to org.apache.log4j.Logger#error(Object, Throwable) calls is also applicable to other logging methods with similar signatures): 0) vital and always applicable: do not lose stacktraces 0.0) for ignorable exceptions never do: } catch (Exception e) { // empty catch block } ...but instead do at least the following: } catch (Exception e) { if (logger.isDebugEnabled()) logger.debug("swallowed exception "+e, e); } ...because it won't hurt performance much, whereas throwing a lot of exceptions and not knowing about it will! 0.1) never do logger.error(throwable) but do logger.error(throwable, throwable) because else the original stacktrace gets lost ...but not logger.error(throwable.getMessage(), throwable) as explained above 1) very important and almost always applicable: do not "over-log" exceptions 1.0) do not log _and_ throw the same exception: do not do: } catch (Exception e) { log.error(e, e); throw new RuntimeException(e, e); } ...but do: } catch (Exception e) { throw new RuntimeException(e, e); } ...or maybe: } catch (Exception e) { log.error(e, e); // for the administrator and programmer eventuallyUserFacingErrorReportMechanism.addError(friendlyErrorMessage/*, e*/); // for the user (and optionally priviledged users may be allowed to see the exception and related stacktrace) } ...except at the highest level when you are sure no one will log the exception further up, e.g.: - in the 'main' method - in a servlet in the highest-level protected methods inherited from HttpServlet, e.g. 'service', 'destroy', etc. - in the 'run' method of a Thread ...else your stacktraces will get so big they will get truncated! 1.1) avoid rewrapping exceptions that do not need to be rewrapped because they are already of the needed type: e.g. do not do: } catch (Exception e) { throw new RuntimeException(e); } ...but rather do: } catch (RuntimeException e) { throw e; } catch (Exception e) { throw new RuntimeException(e); } ... else your stacktraces will get bigger (see above) That's all I have in mind for now. HTH, Guillaume From guillaume.deflache at wyona.com Mon Mar 22 19:14:34 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Mon Mar 22 19:26:28 2010 Subject: [Yanel-dev] policy viewer refactoring (inside "policymanager" resource-type) In-Reply-To: <4BA7995B.9040901@wyona.com> References: <4BA78362.1050309@wyona.com> <4BA7995B.9040901@wyona.com> Message-ID: <4BA7B38A.90006@wyona.com> Michael Wechner schrieb: > Guillaume D?flache wrote: >> Hi! >> >> For a project I need to implement some specific behaviour for the >> policy viewer. >> So as to also reuse existing Yanel code for other unchanged things I'd >> need to be able to reuse parts of the existing Yanel implementation. >> >> >> ATM alas the policy viewer is implemented by calling the sole static >> method PolicyViewer#getXHTMLView(PolicyManager pm, GroupManager gm, >> String path, String contentItemId, [other view options' parameters]) >> which does not allow any kind of overriding. >> >> >> I'd like to introduce the following method in >> org.wyona.yanel.impl.resources.policymanager.PolicyManagerResource: >> >> protected PolicyViewer getPolicyViewer(PolicyManager pm, >> GroupManager gm, [other view options' parameters]); >> >> with the visible API of PolicyViewer being: >> >> InputStream getXHTMLInputStream(String path, String contentItemId) >> throws Exception >> >> Then I would be able to just change the used resource-type in >> $MY_SPECIFIC_REALM_DIR/src/webapp/global-resource-configs/policy-manager_yanel-rc.xml >> to one using my own PolicyViewer-based Java class! >> >> WDYT? > > What exactly would you like to do? The 1st thing I would like to do is to able to use the existing PolicyManagerResource as it is now, except I'd like to replace the PolicyViewer by another project-specific class, possibly reusing some parts of Yanel's original PolicyViewer implementation at a later stage. > The reason I am asking is because I think "overriding/inheritance" is > not always a good thing and maybe it's better to introduce > appropriate interfaces. I do suggest introducing an API when I write "the visible API of PolicyViewer", even if in this 1st step it would not be a Java interface per se. But indeed we should introduce a PolicyViewerV1 Java interface at some point, except for now I am not 100% sure if what I suggest is sufficient even for my own needs and if I would not need a finer-grained one later on. So I'd rather use a class than an interface at this point to avoid setting it in stone too early. Hope this clears things a bit. Cheers, Guillaume From bugzilla at wyona.com Mon Mar 22 19:34:09 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 19:34:11 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322183409.1F90110CA31@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 mehmet.birgi@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1279 is|0 |1 obsolete| | -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 19:36:34 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 19:36:35 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322183634.1D52B10CA31@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 ------- Comment #12 from mehmet.birgi@wyona.com 2010-03-22 19:33 ------- Created an attachment (id=1280) --> (http://bugzilla.wyona.com/cgi-bin/bugzilla/attachment.cgi?id=1280&action=view) proposed patch (v3) This version is locally tested to work properly, but only for Tomcat node 1, as I only have one running. Please review and comment. -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From bugzilla at wyona.com Mon Mar 22 19:38:20 2010 From: bugzilla at wyona.com (bugzilla@wyona.com) Date: Mon Mar 22 19:38:24 2010 Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system Message-ID: <20100322183820.7297910CA31@server1.example.com> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541 guillaume.deflache@wyona.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1280|application/octet-stream |text/plain mime type| | Attachment #1280 is|0 |1 patch| | -- Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. From michael.wechner at wyona.com Mon Mar 22 23:59:36 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 23 00:12:38 2010 Subject: [Yanel-dev] policy viewer refactoring (inside "policymanager" resource-type) In-Reply-To: <4BA7B38A.90006@wyona.com> References: <4BA78362.1050309@wyona.com> <4BA7995B.9040901@wyona.com> <4BA7B38A.90006@wyona.com> Message-ID: <4BA7F658.9090207@wyona.com> Guillaume D?flache wrote: > Michael Wechner schrieb: >> Guillaume D?flache wrote: >>> Hi! >>> >>> For a project I need to implement some specific behaviour for the >>> policy viewer. >>> So as to also reuse existing Yanel code for other unchanged things >>> I'd need to be able to reuse parts of the existing Yanel >>> implementation. >>> >>> >>> ATM alas the policy viewer is implemented by calling the sole static >>> method PolicyViewer#getXHTMLView(PolicyManager pm, GroupManager gm, >>> String path, String contentItemId, [other view options' parameters]) >>> which does not allow any kind of overriding. >>> >>> >>> I'd like to introduce the following method in >>> org.wyona.yanel.impl.resources.policymanager.PolicyManagerResource: >>> >>> protected PolicyViewer getPolicyViewer(PolicyManager pm, >>> GroupManager gm, [other view options' parameters]); >>> >>> with the visible API of PolicyViewer being: >>> >>> InputStream getXHTMLInputStream(String path, String >>> contentItemId) throws Exception >>> >>> Then I would be able to just change the used resource-type in >>> $MY_SPECIFIC_REALM_DIR/src/webapp/global-resource-configs/policy-manager_yanel-rc.xml >>> to one using my own PolicyViewer-based Java class! >>> >>> WDYT? >> >> What exactly would you like to do? > > The 1st thing I would like to do is to able to use the existing > PolicyManagerResource as it is now, except I'd like to replace the > PolicyViewer by another project-specific class, possibly reusing some > parts of Yanel's original PolicyViewer implementation at a later stage. > > >> The reason I am asking is because I think "overriding/inheritance" is >> not always a good thing and maybe it's better to introduce >> appropriate interfaces. > > I do suggest introducing an API when I write "the visible API of > PolicyViewer", even if in this 1st step it would not be a Java > interface per se. > But indeed we should introduce a PolicyViewerV1 Java interface at some > point, except for now I am not 100% sure if what I suggest is > sufficient even for my own needs and if I would not need a > finer-grained one later what is your suggestion re an API right now? > So I'd rather use a class than an interface at this point to avoid > setting it in stone too early. this is why we use versioned interfaces ... Don't be afraid of suggestion an interface. > > > Hope this clears things a bit. not really, because I still don't know how you would actually like to use it. Thanks Michi > > Cheers, > Guillaume From michael.wechner at wyona.com Tue Mar 23 07:21:53 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 23 07:34:55 2010 Subject: [Yanel-dev] policy viewer refactoring (inside "policymanager" resource-type) In-Reply-To: <4BA7B38A.90006@wyona.com> References: <4BA78362.1050309@wyona.com> <4BA7995B.9040901@wyona.com> <4BA7B38A.90006@wyona.com> Message-ID: <4BA85E01.6040909@wyona.com> One more item (apart from the API spec) which comes to my mind is testing. Do we have tests for the current policy manager resource? If not, then let's write some tests before we continue with the refactoring ... Thanks Michi Guillaume D?flache wrote: > Michael Wechner schrieb: >> Guillaume D?flache wrote: >>> Hi! >>> >>> For a project I need to implement some specific behaviour for the >>> policy viewer. >>> So as to also reuse existing Yanel code for other unchanged things >>> I'd need to be able to reuse parts of the existing Yanel >>> implementation. >>> >>> >>> ATM alas the policy viewer is implemented by calling the sole static >>> method PolicyViewer#getXHTMLView(PolicyManager pm, GroupManager gm, >>> String path, String contentItemId, [other view options' parameters]) >>> which does not allow any kind of overriding. >>> >>> >>> I'd like to introduce the following method in >>> org.wyona.yanel.impl.resources.policymanager.PolicyManagerResource: >>> >>> protected PolicyViewer getPolicyViewer(PolicyManager pm, >>> GroupManager gm, [other view options' parameters]); >>> >>> with the visible API of PolicyViewer being: >>> >>> InputStream getXHTMLInputStream(String path, String >>> contentItemId) throws Exception >>> >>> Then I would be able to just change the used resource-type in >>> $MY_SPECIFIC_REALM_DIR/src/webapp/global-resource-configs/policy-manager_yanel-rc.xml >>> to one using my own PolicyViewer-based Java class! >>> >>> WDYT? >> >> What exactly would you like to do? > > The 1st thing I would like to do is to able to use the existing > PolicyManagerResource as it is now, except I'd like to replace the > PolicyViewer by another project-specific class, possibly reusing some > parts of Yanel's original PolicyViewer implementation at a later stage. > > >> The reason I am asking is because I think "overriding/inheritance" is >> not always a good thing and maybe it's better to introduce >> appropriate interfaces. > > I do suggest introducing an API when I write "the visible API of > PolicyViewer", even if in this 1st step it would not be a Java > interface per se. > But indeed we should introduce a PolicyViewerV1 Java interface at some > point, except for now I am not 100% sure if what I suggest is > sufficient even for my own needs and if I would not need a > finer-grained one later on. So I'd rather use a class than an > interface at this point to avoid setting it in stone too early. > > > Hope this clears things a bit. > > Cheers, > Guillaume From michael.wechner at wyona.com Tue Mar 23 13:59:47 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 23 14:13:19 2010 Subject: [Yanel-dev] Reloading realm configurations Message-ID: <4BA8BB43.4010705@wyona.com> Hi I have added a resource type which allows to reload realm configurations during production http://127.0.0.1:8080/yanel/reload-realms.html which can be handy within a multi-realm environment. Cheers Michi From guillaume.deflache at wyona.com Tue Mar 23 15:12:36 2010 From: guillaume.deflache at wyona.com (=?UTF-8?B?R3VpbGxhdW1lIETDqWZsYWNoZQ==?=) Date: Tue Mar 23 15:24:29 2010 Subject: [Yanel-dev] Javadoc tips (was: Re: [Yanel-commits] rev 48215 - public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation) In-Reply-To: <201003221551.o2MFpchh010045@cvs-extra.wyona.com> References: <201003221551.o2MFpchh010045@cvs-extra.wyona.com> Message-ID: <4BA8CC54.2020607@wyona.com> memo@wyona.com schrieb: > Author: memo > Date: 2010-03-22 16:51:38 +0100 (Mon, 22 Mar 2010) > New Revision: 48215 > > Modified: > public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation/SitetreeDOMImpl.java > Log: > javadoc fixed > > Modified: public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation/SitetreeDOMImpl.java > =================================================================== > --- public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation/SitetreeDOMImpl.java 2010-03-22 15:50:36 UTC (rev 48214) > +++ public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation/SitetreeDOMImpl.java 2010-03-22 15:51:38 UTC (rev 48215) > @@ -27,20 +27,25 @@ > import org.w3c.dom.NodeList; > > /** > - * Based on DOM, whereas persistance is done through the src configuration, for example within realm.xml > - * > - * data-repo/data/sitetree.xml > - * > + * Based on DOM, whereas persistance is done through the src configuration, for example within realm.xml > + * 
> + * <repo-navigation class="org.wyona.yanel.impl.navigation.SitetreeDOMImpl">
> + *   <src>data-repo/data/sitetree.xml</src>
> + * </repo-navigation>
> + *
Using 
{@code ...}
(cf. ) instead would allow to not escape the tags, making the whole thing more readable from the source code. > * > - * or .yanel-rc > + * or .yanel-rc > * > - * > - * > - * yanelrepo:/sitetree.xml > - * > - * > + * 
> + * <yanel:custom-config>
> + *   <s:repo-navigation xmlns:s="http://www.wyona.org/yanel/sitetree-dom-impl/1.0" class="org.wyona.yanel.impl.navigation.SitetreeDOMImpl">
> + *     <s:src>yanelrepo:/sitetree.xml</s:src>
> + *   </s:repo-navigation>
> + * </yanel:custom-config>
> + *
Ditto here. > * > - * Please note that the class org.wyona.yanel.core.map.Realm is using the RealmConfigPathResolver whereas that a resource might use a different resolver implementation! > + * Please note that the class org.wyona.yanel.core.map.Realm > + * is using the RealmConfigPathResolver whereas that a resource might use a different resolver implementation! When one references a Java name for the 1st time, a link is even better, e.g. - {@link org.wyona.yanel.core.map.Realm} or - {@link org.wyona.yanel.core.map.RealmConfigPathResolver RealmConfigPathResolver} (cf. ) > [...] From guillaume.deflache at wyona.com Tue Mar 23 15:35:08 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Tue Mar 23 15:47:01 2010 Subject: [Yanel-dev] policy viewer refactoring (inside "policymanager" resource-type) In-Reply-To: <4BA7F658.9090207@wyona.com> References: <4BA78362.1050309@wyona.com> <4BA7995B.9040901@wyona.com> <4BA7B38A.90006@wyona.com> <4BA7F658.9090207@wyona.com> Message-ID: <4BA8D19C.5010706@wyona.com> Michael Wechner schrieb: > Guillaume D?flache wrote: >> Michael Wechner schrieb: >>> Guillaume D?flache wrote: >>>> Hi! >>>> >>>> For a project I need to implement some specific behaviour for the >>>> policy viewer. >>>> So as to also reuse existing Yanel code for other unchanged things >>>> I'd need to be able to reuse parts of the existing Yanel >>>> implementation. >>>> >>>> >>>> ATM alas the policy viewer is implemented by calling the sole static >>>> method PolicyViewer#getXHTMLView(PolicyManager pm, GroupManager gm, >>>> String path, String contentItemId, [other view options' parameters]) >>>> which does not allow any kind of overriding. >>>> >>>> >>>> I'd like to introduce the following method in >>>> org.wyona.yanel.impl.resources.policymanager.PolicyManagerResource: >>>> >>>> protected PolicyViewer getPolicyViewer(PolicyManager pm, >>>> GroupManager gm, [other view options' parameters]); >>>> >>>> with the visible API of PolicyViewer being: >>>> >>>> InputStream getXHTMLInputStream(String path, String >>>> contentItemId) throws Exception >>>> >>>> Then I would be able to just change the used resource-type in >>>> $MY_SPECIFIC_REALM_DIR/src/webapp/global-resource-configs/policy-manager_yanel-rc.xml >>>> to one using my own PolicyViewer-based Java class! >>>> >>>> WDYT? >>> >>> What exactly would you like to do? >> >> The 1st thing I would like to do is to able to use the existing >> PolicyManagerResource as it is now, except I'd like to replace the >> PolicyViewer by another project-specific class, possibly reusing some >> parts of Yanel's original PolicyViewer implementation at a later stage. >> >> >>> The reason I am asking is because I think "overriding/inheritance" is >>> not always a good thing and maybe it's better to introduce >>> appropriate interfaces. >> >> I do suggest introducing an API when I write "the visible API of >> PolicyViewer", even if in this 1st step it would not be a Java >> interface per se. >> But indeed we should introduce a PolicyViewerV1 Java interface at some >> point, except for now I am not 100% sure if what I suggest is >> sufficient even for my own needs and if I would not need a >> finer-grained one later > > what is your suggestion re an API right now? in src/core/java: package org.wyona.yanel.core[.security].api; interface PolicyViewerV1 { InputStream getXHTMLInputStream(String path, String contentItemId) throws Exception; } But as I tried to explain for this interface to be really usable and get used ATM we need to change org.wyona.yanel.impl.resources.policymanager.PolicyManagerResource as follows: replace the call: PolicyViewer.getXHTMLView(getRealm().getPolicyManager(), getRealm().getIdentityManager().getGroupManager(), getPath(), contentItemID, [other parameters for view options like sort order]) by: PolicyViewer pv = policyViewerFactory.getPolicyViewer(getRealm().getPolicyManager(), getRealm().getIdentityManager().getGroupManager(), [other parameters for view options like sort order]); pv..getXHTMLInputStream(getPath(), contentItemID) ...where policyViewerFactory may be any class implementing the following interface: PolicyViewer getPolicyViewer(PolicyManager pm, GroupManager gm, other parameters for view options like sort order]) ...including PolicyManagerResource itself: my point was that I think we do not need a separate factory for now. If we want to use a separate factory, then we need a way to configure the actual factory class used: I guess we should do it the same as for example PolicyManagerFactory? >> So I'd rather use a class than an interface at this point to avoid >> setting it in stone too early. > > this is why we use versioned interfaces ... > > Don't be afraid of suggestion an interface. I am just unsure at the moment how wide all this should be exposed, given that it is the 1st usecase we have. >> >> >> Hope this clears things a bit. > > not really, because I still don't know how you would actually like to > use it. Is that better? Cheers, Guillaume From guillaume.deflache at wyona.com Tue Mar 23 15:50:40 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Tue Mar 23 16:02:32 2010 Subject: [Yanel-dev] policy viewer refactoring (inside "policymanager" resource-type) In-Reply-To: <4BA85E01.6040909@wyona.com> References: <4BA78362.1050309@wyona.com> <4BA7995B.9040901@wyona.com> <4BA7B38A.90006@wyona.com> <4BA85E01.6040909@wyona.com> Message-ID: <4BA8D540.3090202@wyona.com> Michael Wechner schrieb: > One more item (apart from the API spec) which comes to my mind is > testing. Do we have tests for the current policy manager resource? If > not, then let's write some tests before we continue with the refactoring > ... I could not find any in http://svn.wyona.com/repos/public/yanel/trunk/src/test/junit/org/wyona/yanel/ http://svn.wyona.com/repos/public/yanel/trunk/src/test/htmlunit/org/wyona/yanel/htmlunit the resource-type itself or http://svn.wyona.com/repos/public/yanel/trunk/src/realms/use-cases/yanel/src/test/canoo/tests/ BTW I wonder if Yanel realms themselves should not embark their own Canoo tests, instead of putting them in the 'usecases' realm (AFAICU). We kind of already do that for projects by requiring a Ant property for the realm path, so why not do the same for Yanel realms too? Anyone I will start one existence test and maybe more in src/realms/use-cases/yanel/src/test/canoo/tests/ unless someone objects. From michael.wechner at wyona.com Tue Mar 23 15:55:43 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 23 16:08:40 2010 Subject: [Yanel-dev] policy viewer refactoring (inside "policymanager" resource-type) In-Reply-To: <4BA8D540.3090202@wyona.com> References: <4BA78362.1050309@wyona.com> <4BA7995B.9040901@wyona.com> <4BA7B38A.90006@wyona.com> <4BA85E01.6040909@wyona.com> <4BA8D540.3090202@wyona.com> Message-ID: <4BA8D66F.7010503@wyona.com> Guillaume D?flache wrote: > Michael Wechner schrieb: >> One more item (apart from the API spec) which comes to my mind is >> testing. Do we have tests for the current policy manager resource? If >> not, then let's write some tests before we continue with the >> refactoring ... > > I could not find any in > http://svn.wyona.com/repos/public/yanel/trunk/src/test/junit/org/wyona/yanel/ > http://svn.wyona.com/repos/public/yanel/trunk/src/test/htmlunit/org/wyona/yanel/htmlunit > > the resource-type itself or > http://svn.wyona.com/repos/public/yanel/trunk/src/realms/use-cases/yanel/src/test/canoo/tests/ > > > BTW I wonder if Yanel realms themselves should not embark their own > Canoo tests, instead of putting them in the 'usecases' realm (AFAICU). > We kind of already do that for projects by requiring a Ant property > for the realm path, so why not do the same for Yanel realms too? we have started this for the yanel-website: src/realms/yanel-website/src/test/canoo/ and I also intend to start it for the from scratch realm > > Anyone I will start one existence test and maybe more in > src/realms/use-cases/yanel/src/test/canoo/tests/ unless someone objects. better there than nowhere ;-) Thanks Michi From mehmet.birgi at wyona.com Tue Mar 23 17:01:22 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Tue Mar 23 17:15:06 2010 Subject: [Yanel-dev] Path names in map.rc-map file In-Reply-To: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com> References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com> Message-ID: <5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com> Hi all In the map.rc-map files, the values of the rcpath attribute all start with a '/', which looks like they were absolute paths, while in reality they are relative to the location of the rc-map file (I think). This seems (mildly) confusing to me. Is there a reason for this? -- = Mehmet Birgi www.wyona.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032= 3/73a19cc2/attachment.htm From mehmet.birgi at wyona.com Tue Mar 23 17:45:51 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Tue Mar 23 17:59:22 2010 Subject: [Yanel-dev] Javadoc tips (was: Re: [Yanel-commits] rev 48215 - public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation) In-Reply-To: <4BA8CC54.2020607@wyona.com> References: <201003221551.o2MFpchh010045@cvs-extra.wyona.com> <4BA8CC54.2020607@wyona.com> Message-ID: <5bf1397d1003230945j5997fec3t423717fbf29cf08c@mail.gmail.com> thanks, i will keep that in mind in the future. 2010/3/23 Guillaume D=E9flache > memo@wyona.com schrieb: > >> Author: memo >> Date: 2010-03-22 16:51:38 +0100 (Mon, 22 Mar 2010) >> New Revision: 48215 >> >> Modified: >> >> public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation/Sitetre= eDOMImpl.java >> Log: >> javadoc fixed >> >> Modified: >> public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation/Sitetre= eDOMImpl.java >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- >> public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation/Sitetre= eDOMImpl.java >> 2010-03-22 15:50:36 UTC (rev 48214) >> +++ >> public/yanel/trunk/src/impl/java/org/wyona/yanel/impl/navigation/Sitetre= eDOMImpl.java >> 2010-03-22 15:51:38 UTC (rev 48215) >> @@ -27,20 +27,25 @@ >> import org.w3c.dom.NodeList; >> /** >> - * Based on DOM, whereas persistance is done through the src >> configuration, for example within realm.xml >> - * > class=3D"org.wyona.yanel.impl.navigation.SitetreeDOMImpl"> >> - * data-repo/data/sitetree.xml >> - * >> + * Based on DOM, whereas persistance is done through the src >> configuration, for example within realm.xml >> + * 
>> + * <repo-navigation
>> class=3D"org.wyona.yanel.impl.navigation.SitetreeDOMImpl">
>> + *   <src>data-repo/data/sitetree.xml</src>
>> + * </repo-navigation>
>> + *
>> > > Using 
{@code ...}
(cf. < > http://java.sun.com/javase/6/docs/technotes/tools/windows/javadoc.html#@c= ode>) > instead would allow to not escape the tags, making the whole thing more > readable from the source code. > > > * >> - * or .yanel-rc >> + * or .yanel-rc >> * >> - * >> - * > http://www.wyona.org/yanel/sitetree-dom-impl/1.0" >> class=3D"org.wyona.yanel.impl.navigation.SitetreeDOMImpl"> >> - * yanelrepo:/sitetree.xml >> - * >> - * >> + * 
>> + * <yanel:custom-config>
>> + *   <s:repo-navigation xmlns:s=3D"
>> http://www.wyona.org/yanel/sitetree-dom-impl/1.0"
>> class=3D"org.wyona.yanel.impl.navigation.SitetreeDOMImpl">
>> + *     <s:src>yanelrepo:/sitetree.xml</s:src>
>> + *   </s:repo-navigation>
>> + * </yanel:custom-config>
>> + *
>> > > Ditto here. > > > * >> - * Please note that the class org.wyona.yanel.core.map.Realm is using t= he >> RealmConfigPathResolver whereas that a resource might use a different >> resolver implementation! >> + * Please note that the class org.wyona.yanel.core.map.Realm >> + * is using the RealmConfigPathResolver whereas that a >> resource might use a different resolver implementation! >> > > When one references a Java name for the 1st time, a link is even better, > e.g. > - {@link org.wyona.yanel.core.map.Realm} > or > - {@link org.wyona.yanel.core.map.RealmConfigPathResolver > RealmConfigPathResolver} > (cf. < > http://java.sun.com/javase/6/docs/technotes/tools/windows/javadoc.html#@l= ink > >) > > [...] >> > -- > Yanel-development mailing list Yanel-development@wyona.com > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > -- = Mehmet Birgi www.wyona.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032= 3/7de9d3f6/attachment-0001.htm From michael.wechner at wyona.com Tue Mar 23 22:24:06 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue Mar 23 22:37:05 2010 Subject: [Yanel-dev] Path names in map.rc-map file In-Reply-To: <5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com> References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com> <5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com> Message-ID: <4BA93176.5020500@wyona.com> Mehmet Birgi wrote: > Hi all > > In the map.rc-map files, the values of the rcpath attribute all start > with a '/', which looks like they were absolute paths, while in > reality they are relative to the location of the rc-map file (I > think). This seems (mildly) confusing to me. Is there a reason for this? Each repository is like a harddisk, and so the "resource configuration" repository is also such a harddisk. The map.rc-map (which I think is an unfortunate name) is hence using absolute paths, because it describes at which location nodes can be found within the "resource configuration" repository. Makse sense? Thanks Michi > > > -- > Mehmet Birgi > www.wyona.com > From mehmet.birgi at wyona.com Wed Mar 24 09:41:14 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Wed Mar 24 09:57:32 2010 Subject: [Yanel-dev] Path names in map.rc-map file In-Reply-To: <4BA93176.5020500@wyona.com> References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com> <5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com> <4BA93176.5020500@wyona.com> Message-ID: <5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com> On Tue, Mar 23, 2010 at 10:24 PM, Michael Wechner wrote: > Mehmet Birgi wrote: > >> Hi all >> >> In the map.rc-map files, the values of the rcpath attribute all start wi= th >> a '/', which looks like they were absolute paths, while in reality they = are >> relative to the location of the rc-map file (I think). This seems (mildl= y) >> confusing to me. Is there a reason for this? >> > > Each repository is like a harddisk, and so the "resource configuration" > repository is also such a harddisk. > > The map.rc-map (which I think is an unfortunate name) is hence using > absolute paths, because it describes > at which location nodes can be found within the "resource configuration" > repository. > > Makse sense? > Now it does, thanks :-) I will update the documentation to reflect this. Cheers, memo -- = Mehmet Birgi www.wyona.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032= 4/a8aaf59f/attachment.htm From guillaume.deflache at wyona.com Wed Mar 24 11:12:45 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Wed Mar 24 11:24:37 2010 Subject: [Yanel-dev] permissions for policy edition and view on 'use-cases' realm Message-ID: <4BA9E59D.4000501@wyona.com> Hi! I am trying to access the policy editor and the policy viewer in the 'usecases' realm. I managed to log in with both 'alice' and 'lenya' users, but I still get 'Authorization was denied.' for both and the toolbar. AFAICS there are no policy files in ac-policies/ that would prevent this, and on the from-scratch realm this works OK with the user 'lenya' and apparently no related policy files are there either. What am I missing? Cheers, Guillaume From mehmet.birgi at wyona.com Wed Mar 24 11:15:04 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Wed Mar 24 11:28:05 2010 Subject: [Yanel-dev] Path names in map.rc-map file In-Reply-To: <5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com> References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com> <5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com> <4BA93176.5020500@wyona.com> <5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com> Message-ID: <5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com> Skipped content of type multipart/alternative-------------- next part -----= --------- A non-text attachment was scrubbed... Name: docs.diff Type: application/octet-stream Size: 15283 bytes Desc: not available Url : http://lists.wyona.org/pipermail/yanel-development/attachments/201003= 24/749092ea/docs-0001.obj From michael.wechner at wyona.com Wed Mar 24 11:21:38 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Mar 24 11:34:37 2010 Subject: [Yanel-dev] permissions for policy edition and view on 'use-cases' realm In-Reply-To: <4BA9E59D.4000501@wyona.com> References: <4BA9E59D.4000501@wyona.com> Message-ID: <4BA9E7B2.2060308@wyona.com> Guillaume D?flache wrote: > Hi! > > I am trying to access the policy editor and the policy viewer in the > 'usecases' realm. > I managed to log in with both 'alice' and 'lenya' users, but I still > get 'Authorization was denied.' for both and the toolbar. > AFAICS there are no policy files in ac-policies/ that would prevent > this, and on the from-scratch realm this works OK with the user > 'lenya' and apparently no related policy files are there either. > What am I missing? The rights were missing: Index: ac-policies/.policy =================================================================== --- ac-policies/.policy (revision 48242) +++ ac-policies/.policy (working copy) @@ -31,4 +31,12 @@ + + + + + + + + I will commit them right now Cheers Michi > > Cheers, > Guillaume From guillaume.deflache at wyona.com Wed Mar 24 11:29:43 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=) Date: Wed Mar 24 11:41:34 2010 Subject: [Yanel-dev] Path names in map.rc-map file In-Reply-To: <5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com> References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com> <5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com> <4BA93176.5020500@wyona.com> <5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com> <5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com> Message-ID: <4BA9E997.8000001@wyona.com> Mehmet Birgi schrieb: > I have updated the documentation, pls see the diff to review the > changes, and get back with your comments. Looks like some lines contained in the diff are identical, maybe you changed the line endings somehow? Maybe fixing that will shrink the diffs a bit, but else it could be a good idea to attach the new files as HTML and maybe sum up shortly what the modifications were (this will be useful for the commit message anyway). From guillaume.deflache at wyona.com Wed Mar 24 11:36:56 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Wed Mar 24 11:49:13 2010 Subject: [Yanel-dev] permissions for policy edition and view on 'use-cases' realm In-Reply-To: <4BA9E7B2.2060308@wyona.com> References: <4BA9E59D.4000501@wyona.com> <4BA9E7B2.2060308@wyona.com> Message-ID: <4BA9EB48.10401@wyona.com> Michael Wechner schrieb: > Guillaume D?flache wrote: >> Hi! >> >> I am trying to access the policy editor and the policy viewer in the >> 'usecases' realm. >> I managed to log in with both 'alice' and 'lenya' users, but I still >> get 'Authorization was denied.' for both and the toolbar. >> AFAICS there are no policy files in ac-policies/ that would prevent >> this, and on the from-scratch realm this works OK with the user >> 'lenya' and apparently no related policy files are there either. >> What am I missing? > > The rights were missing: > > Index: ac-policies/.policy > =================================================================== > --- ac-policies/.policy (revision 48242) > +++ ac-policies/.policy (working copy) > @@ -31,4 +31,12 @@ > > > > + > + > + > + > + > + > + > + > > > I will commit them right now OK thanks, sorry I forgot about the .policy file. That reminds me of a remark memo made during lunch recently: this policy file is hidden under Unix and can easily get forgotten, maybe we should allow for an alternative name like "policy" without the leading dot (or COLLECTION.policy so that there is still an extension) so that it can be always visible? Ditto for .yarep files BTW. From mehmet.birgi at wyona.com Wed Mar 24 11:50:51 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Wed Mar 24 12:03:53 2010 Subject: [Yanel-dev] Path names in map.rc-map file In-Reply-To: <4BA9E997.8000001@wyona.com> References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com> <5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com> <4BA93176.5020500@wyona.com> <5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com> <5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com> <4BA9E997.8000001@wyona.com> Message-ID: <5bf1397d1003240350w6d3de028n382c2c6f04f648f@mail.gmail.com> Skipped content of type multipart/alternative-------------- next part -----= --------- A non-text attachment was scrubbed... Name: docs.diff Type: application/octet-stream Size: 14571 bytes Desc: not available Url : http://lists.wyona.org/pipermail/yanel-development/attachments/201003= 24/c8246cdb/docs.obj From michael.wechner at wyona.com Wed Mar 24 11:53:57 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Mar 24 12:06:55 2010 Subject: [Yanel-dev] permissions for policy edition and view on 'use-cases' realm In-Reply-To: <4BA9EB48.10401@wyona.com> References: <4BA9E59D.4000501@wyona.com> <4BA9E7B2.2060308@wyona.com> <4BA9EB48.10401@wyona.com> Message-ID: <4BA9EF45.2070101@wyona.com> Guillaume D?flache wrote: > Michael Wechner schrieb: >> Guillaume D?flache wrote: >>> Hi! >>> >>> I am trying to access the policy editor and the policy viewer in the >>> 'usecases' realm. >>> I managed to log in with both 'alice' and 'lenya' users, but I still >>> get 'Authorization was denied.' for both and the toolbar. >>> AFAICS there are no policy files in ac-policies/ that would prevent >>> this, and on the from-scratch realm this works OK with the user >>> 'lenya' and apparently no related policy files are there either. >>> What am I missing? >> >> The rights were missing: >> >> Index: ac-policies/.policy >> =================================================================== >> --- ac-policies/.policy (revision 48242) >> +++ ac-policies/.policy (working copy) >> @@ -31,4 +31,12 @@ >> >> >> >> + >> + >> + >> + >> + >> + >> + >> + >> >> >> I will commit them right now > > OK thanks, sorry I forgot about the .policy file. > > That reminds me of a remark memo made during lunch recently: this > policy file is hidden under Unix and can easily get forgotten, not if it is documented > maybe we should allow for an alternative name like "policy" without > the leading dot (or COLLECTION.policy so that there is still an > extension) so that it can be always visible? > Ditto for .yarep files BTW. The problem is re conflicts. What if you have directory called COLLECTION? Or ROOT or whatever. Btw, SVN and GIT use the same principle. Cheers Michi From guillaume.deflache at wyona.com Wed Mar 24 12:08:39 2010 From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=) Date: Wed Mar 24 12:20:31 2010 Subject: [Yanel-dev] permissions for policy edition and view on 'use-cases' realm In-Reply-To: <4BA9EF45.2070101@wyona.com> References: <4BA9E59D.4000501@wyona.com> <4BA9E7B2.2060308@wyona.com> <4BA9EB48.10401@wyona.com> <4BA9EF45.2070101@wyona.com> Message-ID: <4BA9F2B7.8080005@wyona.com> Michael Wechner schrieb: > Guillaume D?flache wrote: [...] >> OK thanks, sorry I forgot about the .policy file. >> >> That reminds me of a remark memo made during lunch recently: this >> policy file is hidden under Unix and can easily get forgotten, > > not if it is documented I'd argue one can still forget about it even then, and it is not really "discoverable". >> maybe we should allow for an alternative name like "policy" without >> the leading dot (or COLLECTION.policy so that there is still an >> extension) so that it can be always visible? >> Ditto for .yarep files BTW. > > The problem is re conflicts. What if you have directory called > COLLECTION? Or ROOT or whatever. Granted, and making that prefix configurable would complicate things more and may even not be sufficient as one might need different prefixes for different directory levels in case a conflict appears later on. So maybe 'policy' would be the only sensible alternative? > Btw, SVN and GIT use the same principle. Sure but in our case we have both a hidden file (.policy) and non-hidden files (*.policy) which leads you to think you see all of them when doing a simple `ls`. From michael.wechner at wyona.com Wed Mar 24 12:13:29 2010 From: michael.wechner at wyona.com (Michael Wechner) Date: Wed Mar 24 12:28:00 2010 Subject: [Yanel-dev] Path names in map.rc-map file In-Reply-To: <5bf1397d1003240350w6d3de028n382c2c6f04f648f@mail.gmail.com> References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com> <5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com> <4BA93176.5020500@wyona.com> <5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com> <5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com> <4BA9E997.8000001@wyona.com> <5bf1397d1003240350w6d3de028n382c2c6f04f648f@mail.gmail.com> Message-ID: <4BA9F3D9.3080005@wyona.com> from your patches I assume that you have modified the following pages: /en/documentation/realm/realm-configuration.html /en/documentation/resources/rc-map.html /en/documentation/resources/resource_type_configuration.html right? Why did you change the CSS? Thanks Michi Mehmet Birgi wrote: > Dear Guillaume > > You are right, I have attached a better diff made with the option > "--ignore-eol-style". > > All the html files have been edited only with TinyMCE, so it's TinyMCE > who is probably to blame for the differences in line endings as well > as the missing newlines at the end of the files. Can anyone comment on > that? > > Thanks, > > Memo > > > 2010/3/24 Guillaume D?flache > > > Mehmet Birgi schrieb: > > I have updated the documentation, pls see the diff to review > the changes, and get back with your comments. > > > Looks like some lines contained in the diff are identical, maybe > you changed the line endings somehow? > Maybe fixing that will shrink the diffs a bit, but else it could > be a good idea to attach the new files as HTML and maybe sum up > shortly what the modifications were (this will be useful for the > commit message anyway). > > -- > Yanel-development mailing list Yanel-development@wyona.com > > http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development > > > > > -- > Mehmet Birgi > www.wyona.com > From mehmet.birgi at wyona.com Wed Mar 24 13:37:35 2010 From: mehmet.birgi at wyona.com (Mehmet Birgi) Date: Wed Mar 24 13:50:36 2010 Subject: [Yanel-dev] Path names in map.rc-map file In-Reply-To: <4BA9F3D9.3080005@wyona.com> References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com> <5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com> <4BA93176.5020500@wyona.com> <5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com> <5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com> <4BA9E997.8000001@wyona.com> <5bf1397d1003240350w6d3de028n382c2c6f04f648f@mail.gmail.com> <4BA9F3D9.3080005@wyona.com> Message-ID: <5bf1397d1003240537l6ce3ab42h196160f8e4bad750@mail.gmail.com> I made some small changes to the css to improve the rendering of the and 
 tags, to be able to properly display code snippets and filenames.
Especially  was not defined before, which made it impossible to have
filenames in monospaced font within a normal text paragraph, because 
always makes a new paragraph.



On Wed, Mar 24, 2010 at 12:13 PM, Michael Wechner  wrote:

> from your patches I assume that you have modified the following pages:
>
> /en/documentation/realm/realm-configuration.html
>
> /en/documentation/resources/rc-map.html
> /en/documentation/resources/resource_type_configuration.html
>
> right?
>
> Why did you change the CSS?
>
> Thanks
>
> Michi
>
>
> Mehmet Birgi wrote:
>
>> Dear Guillaume
>>
>> You are right, I have attached a better diff made with the option
>> "--ignore-eol-style".
>>
>> All the html files have been edited only with TinyMCE, so it's TinyMCE w=
ho
>> is probably to blame for the differences in line endings as well as the
>> missing newlines at the end of the files. Can anyone comment on that?
>>
>> Thanks,
>>
>> Memo
>>
>>
>> 2010/3/24 Guillaume D=E9flache > guillaume.deflache@wyona.com>>
>>
>>
>>    Mehmet Birgi schrieb:
>>
>>        I have updated the documentation, pls see the diff to review
>>        the changes, and get back with your comments.
>>
>>
>>    Looks like some lines contained in the diff are identical, maybe
>>    you changed the line endings somehow?
>>    Maybe fixing that will shrink the diffs a bit, but else it could
>>    be a good idea to attach the new files as HTML and maybe sum up
>>    shortly what the modifications were (this will be useful for the
>>    commit message anyway).
>>
>>    --     Yanel-development mailing list Yanel-development@wyona.com
>>    
>>
>>    http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>
>>
>>
>>
>> --
>> Mehmet Birgi
>> www.wyona.com 
>>
>>
> --
> Yanel-development mailing list Yanel-development@wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>



-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032=
4/ec67e5a8/attachment.htm
From michael.wechner at wyona.com  Wed Mar 24 16:56:37 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Wed Mar 24 17:09:45 2010
Subject: [Yanel-dev] Path names in map.rc-map file
In-Reply-To: <5bf1397d1003240537l6ce3ab42h196160f8e4bad750@mail.gmail.com>
References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com>	<5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com>	<4BA93176.5020500@wyona.com>	<5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com>	<5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com>	<4BA9E997.8000001@wyona.com>	<5bf1397d1003240350w6d3de028n382c2c6f04f648f@mail.gmail.com>	<4BA9F3D9.3080005@wyona.com>
	<5bf1397d1003240537l6ce3ab42h196160f8e4bad750@mail.gmail.com>
Message-ID: <4BAA3635.9070203@wyona.com>

Mehmet Birgi wrote:
> I made some small changes to the css to improve the rendering of the 
>  and 
 tags, to be able to properly display code snippets 
> and filenames. Especially  was not defined before, which made it 
> impossible to have filenames in monospaced font within a normal text 
> paragraph, because 
 always makes a new paragraph.

ok, looks good to me.

Re the content itself. Something is wrong with one of the anchors within

http://127.0.0.1:8080/yanel/yanel-website/en/documentation/realm/realm-configuration.html

It seems to me that

http://www.yanel.org/en/documentation/resources/rc-map.html

has not much changed and that the resource map example could be a bit 
more illustrative within

http://127.0.0.1:8080/yanel/yanel-website/en/documentation/resources/rc-map.html

but every improvement is good :-), so please commit it.

Thanks

Michi
>
>
>
> On Wed, Mar 24, 2010 at 12:13 PM, Michael Wechner 
> > wrote:
>
>     from your patches I assume that you have modified the following pages:
>
>     /en/documentation/realm/realm-configuration.html
>
>     /en/documentation/resources/rc-map.html
>     /en/documentation/resources/resource_type_configuration.html
>
>     right?
>
>     Why did you change the CSS?
>
>     Thanks
>
>     Michi
>
>
>     Mehmet Birgi wrote:
>
>         Dear Guillaume
>
>         You are right, I have attached a better diff made with the
>         option "--ignore-eol-style".
>
>         All the html files have been edited only with TinyMCE, so it's
>         TinyMCE who is probably to blame for the differences in line
>         endings as well as the missing newlines at the end of the
>         files. Can anyone comment on that?
>
>         Thanks,
>
>         Memo
>
>
>         2010/3/24 Guillaume D?flache          
>                  >>
>
>
>            Mehmet Birgi schrieb:
>
>                I have updated the documentation, pls see the diff to
>         review
>                the changes, and get back with your comments.
>
>
>            Looks like some lines contained in the diff are identical,
>         maybe
>            you changed the line endings somehow?
>            Maybe fixing that will shrink the diffs a bit, but else it
>         could
>            be a good idea to attach the new files as HTML and maybe sum up
>            shortly what the modifications were (this will be useful
>         for the
>            commit message anyway).
>
>            --     Yanel-development mailing list
>         Yanel-development@wyona.com 
>                     >
>
>          
>          http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
>
>
>
>         -- 
>         Mehmet Birgi
>         www.wyona.com  
>
>
>     -- 
>     Yanel-development mailing list Yanel-development@wyona.com
>     
>     http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
>
>
>
> -- 
> Mehmet Birgi
> www.wyona.com 
>

From mehmet.birgi at wyona.com  Wed Mar 24 17:56:00 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Wed Mar 24 18:09:03 2010
Subject: [Yanel-dev] Path names in map.rc-map file
In-Reply-To: <4BAA3635.9070203@wyona.com>
References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com>
	<5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com>
	<4BA93176.5020500@wyona.com>
	<5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com>
	<5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com>
	<4BA9E997.8000001@wyona.com>
	<5bf1397d1003240350w6d3de028n382c2c6f04f648f@mail.gmail.com>
	<4BA9F3D9.3080005@wyona.com>
	<5bf1397d1003240537l6ce3ab42h196160f8e4bad750@mail.gmail.com>
	<4BAA3635.9070203@wyona.com>
Message-ID: <5bf1397d1003240956n9dfd7ack44165994ca0f8645@mail.gmail.com>

fixed the anchor and commited. re the rc-map example: do you have a better
example? or any ideas on how to improve it?


On Wed, Mar 24, 2010 at 4:56 PM, Michael Wechner
wrote:

> Mehmet Birgi wrote:
>
>> I made some small changes to the css to improve the rendering of the
>>  and 
 tags, to be able to properly display code snippets and
>> filenames. Especially  was not defined before, which made it
>> impossible to have filenames in monospaced font within a normal text
>> paragraph, because 
 always makes a new paragraph.
>>
>
> ok, looks good to me.
>
> Re the content itself. Something is wrong with one of the anchors within
>
>
> http://127.0.0.1:8080/yanel/yanel-website/en/documentation/realm/realm-co=
nfiguration.html
>
> It seems to me that
>
> http://www.yanel.org/en/documentation/resources/rc-map.html
>
> has not much changed and that the resource map example could be a bit more
> illustrative within
>
>
> http://127.0.0.1:8080/yanel/yanel-website/en/documentation/resources/rc-m=
ap.html
>
> but every improvement is good :-), so please commit it.
>
> Thanks
>
> Michi
>
>>
>>
>>
>> On Wed, Mar 24, 2010 at 12:13 PM, Michael Wechner <
>> michael.wechner@wyona.com > wrote:
>>
>>    from your patches I assume that you have modified the following pages:
>>
>>    /en/documentation/realm/realm-configuration.html
>>
>>    /en/documentation/resources/rc-map.html
>>    /en/documentation/resources/resource_type_configuration.html
>>
>>    right?
>>
>>    Why did you change the CSS?
>>
>>    Thanks
>>
>>    Michi
>>
>>
>>    Mehmet Birgi wrote:
>>
>>        Dear Guillaume
>>
>>        You are right, I have attached a better diff made with the
>>        option "--ignore-eol-style".
>>
>>        All the html files have been edited only with TinyMCE, so it's
>>        TinyMCE who is probably to blame for the differences in line
>>        endings as well as the missing newlines at the end of the
>>        files. Can anyone comment on that?
>>
>>        Thanks,
>>
>>        Memo
>>
>>
>>        2010/3/24 Guillaume D=E9flache >        
>>        >        >>
>>
>>
>>           Mehmet Birgi schrieb:
>>
>>               I have updated the documentation, pls see the diff to
>>        review
>>               the changes, and get back with your comments.
>>
>>
>>           Looks like some lines contained in the diff are identical,
>>        maybe
>>           you changed the line endings somehow?
>>           Maybe fixing that will shrink the diffs a bit, but else it
>>        could
>>           be a good idea to attach the new files as HTML and maybe sum up
>>           shortly what the modifications were (this will be useful
>>        for the
>>           commit message anyway).
>>
>>           --     Yanel-development mailing list
>>        Yanel-development@wyona.com 
>>           >        >
>>
>>
>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>
>>
>>
>>
>>        --         Mehmet Birgi
>>        www.wyona.com  
>>
>>
>>
>>    --     Yanel-development mailing list Yanel-development@wyona.com
>>    
>>    http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>
>>
>>
>>
>> --
>> Mehmet Birgi
>> www.wyona.com 
>>
>>
> --
> Yanel-development mailing list Yanel-development@wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>



-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032=
4/c1c13d8c/attachment.htm
From michael.wechner at wyona.com  Thu Mar 25 00:47:12 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Thu Mar 25 01:00:18 2010
Subject: [Yanel-dev] Path names in map.rc-map file
In-Reply-To: <5bf1397d1003240956n9dfd7ack44165994ca0f8645@mail.gmail.com>
References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com>	<5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com>	<4BA93176.5020500@wyona.com>	<5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com>	<5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com>	<4BA9E997.8000001@wyona.com>	<5bf1397d1003240350w6d3de028n382c2c6f04f648f@mail.gmail.com>	<4BA9F3D9.3080005@wyona.com>	<5bf1397d1003240537l6ce3ab42h196160f8e4bad750@mail.gmail.com>	<4BAA3635.9070203@wyona.com>
	<5bf1397d1003240956n9dfd7ack44165994ca0f8645@mail.gmail.com>
Message-ID: <4BAAA480.8030200@wyona.com>

Mehmet Birgi wrote:
> fixed the anchor and commited. re the rc-map example: do you have a 
> better example?

I don't think it needs to be a real world example, because these can be 
hard to understand sometimes, but rather
something which somebody now can relate to. You are kind of new on the 
block ;-) so what would you suggest?
> or any ideas on how to improve it?

I would definitely remove the Xopus entry, because this is not part of 
Yanel itself.

Cheers

Michi
>
>
> On Wed, Mar 24, 2010 at 4:56 PM, Michael Wechner 
> > wrote:
>
>     Mehmet Birgi wrote:
>
>         I made some small changes to the css to improve the rendering
>         of the  and 
 tags, to be able to properly display
>         code snippets and filenames. Especially  was not defined
>         before, which made it impossible to have filenames in
>         monospaced font within a normal text paragraph, because 
>         always makes a new paragraph.
>
>
>     ok, looks good to me.
>
>     Re the content itself. Something is wrong with one of the anchors
>     within
>
>     http://127.0.0.1:8080/yanel/yanel-website/en/documentation/realm/realm-configuration.html
>
>     It seems to me that
>
>     http://www.yanel.org/en/documentation/resources/rc-map.html
>
>     has not much changed and that the resource map example could be a
>     bit more illustrative within
>
>     http://127.0.0.1:8080/yanel/yanel-website/en/documentation/resources/rc-map.html
>
>     but every improvement is good :-), so please commit it.
>
>     Thanks
>
>     Michi
>
>
>
>
>         On Wed, Mar 24, 2010 at 12:13 PM, Michael Wechner
>         
>                  >> wrote:
>
>            from your patches I assume that you have modified the
>         following pages:
>
>            /en/documentation/realm/realm-configuration.html
>
>            /en/documentation/resources/rc-map.html
>            /en/documentation/resources/resource_type_configuration.html
>
>            right?
>
>            Why did you change the CSS?
>
>            Thanks
>
>            Michi
>
>
>            Mehmet Birgi wrote:
>
>                Dear Guillaume
>
>                You are right, I have attached a better diff made with the
>                option "--ignore-eol-style".
>
>                All the html files have been edited only with TinyMCE,
>         so it's
>                TinyMCE who is probably to blame for the differences in
>         line
>                endings as well as the missing newlines at the end of the
>                files. Can anyone comment on that?
>
>                Thanks,
>
>                Memo
>
>
>                2010/3/24 Guillaume D?flache
>                  
>                         >
>                         
>                         >>>
>
>
>                   Mehmet Birgi schrieb:
>
>                       I have updated the documentation, pls see the
>         diff to
>                review
>                       the changes, and get back with your comments.
>
>
>                   Looks like some lines contained in the diff are
>         identical,
>                maybe
>                   you changed the line endings somehow?
>                   Maybe fixing that will shrink the diffs a bit, but
>         else it
>                could
>                   be a good idea to attach the new files as HTML and
>         maybe sum up
>                   shortly what the modifications were (this will be useful
>                for the
>                   commit message anyway).
>
>                   --     Yanel-development mailing list
>                Yanel-development@wyona.com
>         
>                  >
>                            
>                         >>
>
>                        
>          http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
>
>
>
>                --         Mehmet Birgi
>                www.wyona.com 
>          
>
>
>
>            --     Yanel-development mailing list
>         Yanel-development@wyona.com 
>                     >
>          
>          http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
>
>
>
>         -- 
>         Mehmet Birgi
>         www.wyona.com  
>
>
>     -- 
>     Yanel-development mailing list Yanel-development@wyona.com
>     
>     http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
>
>
>
> -- 
> Mehmet Birgi
> www.wyona.com 
>

From michael.wechner at wyona.com  Thu Mar 25 00:59:42 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Thu Mar 25 01:12:43 2010
Subject: [Yanel-dev] Path names in map.rc-map file
In-Reply-To: <4BAAA480.8030200@wyona.com>
References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com>	<5bf1397d1003230901l68028e33g5a4ce0bc4f3bacc1@mail.gmail.com>	<4BA93176.5020500@wyona.com>	<5bf1397d1003240141oad9a22dj7fc581f8b7214fa2@mail.gmail.com>	<5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com>	<4BA9E997.8000001@wyona.com>	<5bf1397d1003240350w6d3de028n382c2c6f04f648f@mail.gmail.com>	<4BA9F3D9.3080005@wyona.com>	<5bf1397d1003240537l6ce3ab42h196160f8e4bad750@mail.gmail.com>	<4BAA3635.9070203@wyona.com>	<5bf1397d1003240956n9dfd7ack44165994ca0f8645@mail.gmail.com>
	<4BAAA480.8030200@wyona.com>
Message-ID: <4BAAA76E.8020607@wyona.com>

Michael Wechner wrote:
> Mehmet Birgi wrote:
>> fixed the anchor and commited. re the rc-map example: do you have a 
>> better example?
>
> I don't think it needs to be a real world example, because these can 
> be hard to understand sometimes, but rather
> something which somebody now 

I meant "new" instead "now".

Thanks

Michi
> can relate to. You are kind of new on the block ;-) so what would you 
> suggest?
>> or any ideas on how to improve it?
>
> I would definitely remove the Xopus entry, because this is not part of 
> Yanel itself.
>
> Cheers
>
> Michi
>>
>>
>> On Wed, Mar 24, 2010 at 4:56 PM, Michael Wechner 
>> > wrote:
>>
>>     Mehmet Birgi wrote:
>>
>>         I made some small changes to the css to improve the rendering
>>         of the  and 
 tags, to be able to properly display
>>         code snippets and filenames. Especially  was not defined
>>         before, which made it impossible to have filenames in
>>         monospaced font within a normal text paragraph, because 
>>         always makes a new paragraph.
>>
>>
>>     ok, looks good to me.
>>
>>     Re the content itself. Something is wrong with one of the anchors
>>     within
>>
>>     
>> http://127.0.0.1:8080/yanel/yanel-website/en/documentation/realm/realm-configuration.html 
>>
>>
>>     It seems to me that
>>
>>     http://www.yanel.org/en/documentation/resources/rc-map.html
>>
>>     has not much changed and that the resource map example could be a
>>     bit more illustrative within
>>
>>     
>> http://127.0.0.1:8080/yanel/yanel-website/en/documentation/resources/rc-map.html 
>>
>>
>>     but every improvement is good :-), so please commit it.
>>
>>     Thanks
>>
>>     Michi
>>
>>
>>
>>
>>         On Wed, Mar 24, 2010 at 12:13 PM, Michael Wechner
>>         
>>         >         >> wrote:
>>
>>            from your patches I assume that you have modified the
>>         following pages:
>>
>>            /en/documentation/realm/realm-configuration.html
>>
>>            /en/documentation/resources/rc-map.html
>>            /en/documentation/resources/resource_type_configuration.html
>>
>>            right?
>>
>>            Why did you change the CSS?
>>
>>            Thanks
>>
>>            Michi
>>
>>
>>            Mehmet Birgi wrote:
>>
>>                Dear Guillaume
>>
>>                You are right, I have attached a better diff made with 
>> the
>>                option "--ignore-eol-style".
>>
>>                All the html files have been edited only with TinyMCE,
>>         so it's
>>                TinyMCE who is probably to blame for the differences in
>>         line
>>                endings as well as the missing newlines at the end of the
>>                files. Can anyone comment on that?
>>
>>                Thanks,
>>
>>                Memo
>>
>>
>>                2010/3/24 Guillaume D?flache
>>         >         
>>                >         >
>>                >         
>>                >         >>>
>>
>>
>>                   Mehmet Birgi schrieb:
>>
>>                       I have updated the documentation, pls see the
>>         diff to
>>                review
>>                       the changes, and get back with your comments.
>>
>>
>>                   Looks like some lines contained in the diff are
>>         identical,
>>                maybe
>>                   you changed the line endings somehow?
>>                   Maybe fixing that will shrink the diffs a bit, but
>>         else it
>>                could
>>                   be a good idea to attach the new files as HTML and
>>         maybe sum up
>>                   shortly what the modifications were (this will be 
>> useful
>>                for the
>>                   commit message anyway).
>>
>>                   --     Yanel-development mailing list
>>                Yanel-development@wyona.com
>>         
>>         >         >
>>                   >         
>>                >         >>
>>
>>                                 
>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>
>>
>>
>>
>>                --         Mehmet Birgi
>>                www.wyona.com 
>>          
>>
>>
>>
>>            --     Yanel-development mailing list
>>         Yanel-development@wyona.com 
>>            >         >
>>                   
>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>
>>
>>
>>
>>         --         Mehmet Birgi
>>         www.wyona.com  
>>
>>
>>     --     Yanel-development mailing list Yanel-development@wyona.com
>>     
>>     http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>
>>
>>
>>
>> -- 
>> Mehmet Birgi
>> www.wyona.com 
>>
>

From michael.wechner at wyona.com  Thu Mar 25 01:09:23 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Thu Mar 25 01:22:23 2010
Subject: [Yanel-dev] Bug re package with multiple resource files and
 generating Yanel as binary
Message-ID: <4BAAA9B3.6030001@wyona.com>

Hi

I have noticed today a bug in the case of a resource type package 
containing multiple resource files, whereas
they do not all live within the same package, but are referenced within 
the resource type registry

/yanel/WEB-INF/classes/resource-types.xml

with only one package



which means Yanel will not be able to detect one or the other resource 
definition.

As a workaround one can still use the copy-dir-name attribute, but 
actually we would like to get rid of this attribute.

Thanks

Michi
From mehmet.birgi at wyona.com  Thu Mar 25 07:00:38 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Thu Mar 25 07:13:39 2010
Subject: [Yanel-dev] Path names in map.rc-map file
In-Reply-To: <4BAAA76E.8020607@wyona.com>
References: <5bf1397d1003230757h42881767teeb15c1bcad076ca@mail.gmail.com>
	<5bf1397d1003240315i1c8818a8w73d871bbb4242561@mail.gmail.com>
	<4BA9E997.8000001@wyona.com>
	<5bf1397d1003240350w6d3de028n382c2c6f04f648f@mail.gmail.com>
	<4BA9F3D9.3080005@wyona.com>
	<5bf1397d1003240537l6ce3ab42h196160f8e4bad750@mail.gmail.com>
	<4BAA3635.9070203@wyona.com>
	<5bf1397d1003240956n9dfd7ack44165994ca0f8645@mail.gmail.com>
	<4BAAA480.8030200@wyona.com> <4BAAA76E.8020607@wyona.com>
Message-ID: <5bf1397d1003242300n73d27db2w63f32fe26f12e4dc@mail.gmail.com>

ok, i'll try to come up with a proposal :-)


On Thu, Mar 25, 2010 at 12:59 AM, Michael Wechner  wrote:

> Michael Wechner wrote:
>
>> Mehmet Birgi wrote:
>>
>>> fixed the anchor and commited. re the rc-map example: do you have a
>>> better example?
>>>
>>
>> I don't think it needs to be a real world example, because these can be
>> hard to understand sometimes, but rather
>> something which somebody now
>>
>
> I meant "new" instead "now".
>
> Thanks
>
> Michi
>
>  can relate to. You are kind of new on the block ;-) so what would you
>> suggest?
>>
>>> or any ideas on how to improve it?
>>>
>>
>> I would definitely remove the Xopus entry, because this is not part of
>> Yanel itself.
>>
>> Cheers
>>
>> Michi
>>
>>>
>>>
>>> On Wed, Mar 24, 2010 at 4:56 PM, Michael Wechner <
>>> michael.wechner@wyona.com > wrote:
>>>
>>>    Mehmet Birgi wrote:
>>>
>>>        I made some small changes to the css to improve the rendering
>>>        of the  and 
 tags, to be able to properly display
>>>        code snippets and filenames. Especially  was not defined
>>>        before, which made it impossible to have filenames in
>>>        monospaced font within a normal text paragraph, because 
>>>        always makes a new paragraph.
>>>
>>>
>>>    ok, looks good to me.
>>>
>>>    Re the content itself. Something is wrong with one of the anchors
>>>    within
>>>
>>>
>>> http://127.0.0.1:8080/yanel/yanel-website/en/documentation/realm/realm-=
configuration.html
>>>
>>>    It seems to me that
>>>
>>>    http://www.yanel.org/en/documentation/resources/rc-map.html
>>>
>>>    has not much changed and that the resource map example could be a
>>>    bit more illustrative within
>>>
>>>
>>> http://127.0.0.1:8080/yanel/yanel-website/en/documentation/resources/rc=
-map.html
>>>
>>>    but every improvement is good :-), so please commit it.
>>>
>>>    Thanks
>>>
>>>    Michi
>>>
>>>
>>>
>>>
>>>        On Wed, Mar 24, 2010 at 12:13 PM, Michael Wechner
>>>        
>>>        >>        >> wrote:
>>>
>>>           from your patches I assume that you have modified the
>>>        following pages:
>>>
>>>           /en/documentation/realm/realm-configuration.html
>>>
>>>           /en/documentation/resources/rc-map.html
>>>           /en/documentation/resources/resource_type_configuration.html
>>>
>>>           right?
>>>
>>>           Why did you change the CSS?
>>>
>>>           Thanks
>>>
>>>           Michi
>>>
>>>
>>>           Mehmet Birgi wrote:
>>>
>>>               Dear Guillaume
>>>
>>>               You are right, I have attached a better diff made with the
>>>               option "--ignore-eol-style".
>>>
>>>               All the html files have been edited only with TinyMCE,
>>>        so it's
>>>               TinyMCE who is probably to blame for the differences in
>>>        line
>>>               endings as well as the missing newlines at the end of the
>>>               files. Can anyone comment on that?
>>>
>>>               Thanks,
>>>
>>>               Memo
>>>
>>>
>>>               2010/3/24 Guillaume D=E9flache
>>>        >>        
>>>               >>        >
>>>               >>        
>>>               >>        >>>
>>>
>>>
>>>                  Mehmet Birgi schrieb:
>>>
>>>                      I have updated the documentation, pls see the
>>>        diff to
>>>               review
>>>                      the changes, and get back with your comments.
>>>
>>>
>>>                  Looks like some lines contained in the diff are
>>>        identical,
>>>               maybe
>>>                  you changed the line endings somehow?
>>>                  Maybe fixing that will shrink the diffs a bit, but
>>>        else it
>>>               could
>>>                  be a good idea to attach the new files as HTML and
>>>        maybe sum up
>>>                  shortly what the modifications were (this will be usef=
ul
>>>               for the
>>>                  commit message anyway).
>>>
>>>                  --     Yanel-development mailing list
>>>               Yanel-development@wyona.com
>>>        
>>>        >>        >
>>>                  >>        
>>>               >>        >>
>>>
>>>
>>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>>
>>>
>>>
>>>
>>>               --         Mehmet Birgi
>>>               www.wyona.com 
>>>         
>>>
>>>
>>>
>>>           --     Yanel-development mailing list
>>>        Yanel-development@wyona.com 
>>>           >>        >
>>>
>>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>>
>>>
>>>
>>>
>>>        --         Mehmet Birgi
>>>        www.wyona.com  
>>>
>>>
>>>    --     Yanel-development mailing list Yanel-development@wyona.com
>>>    
>>>    http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>>
>>>
>>>
>>>
>>> --
>>> Mehmet Birgi
>>> www.wyona.com 
>>>
>>>
>>
> --
> Yanel-development mailing list Yanel-development@wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>



-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032=
5/5e0d21a0/attachment.htm
From michael.wechner at wyona.com  Thu Mar 25 12:12:59 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Thu Mar 25 12:26:01 2010
Subject: [Yanel-dev] permissions for policy edition and view on 'use-cases'
	realm
In-Reply-To: <4BA9F2B7.8080005@wyona.com>
References: <4BA9E59D.4000501@wyona.com>	<4BA9E7B2.2060308@wyona.com>	<4BA9EB48.10401@wyona.com>	<4BA9EF45.2070101@wyona.com>
	<4BA9F2B7.8080005@wyona.com>
Message-ID: <4BAB453B.8050403@wyona.com>

Guillaume D?flache wrote:
> Michael Wechner schrieb:
>> Guillaume D?flache wrote:
> [...]
>>> OK thanks, sorry I forgot about the .policy file.
>>>
>>> That reminds me of a remark memo made during lunch recently: this 
>>> policy file is hidden under Unix and can easily get forgotten,
>>
>> not if it is documented
>
> I'd argue one can still forget about it even then,

yes, but that is no excuse not to document it
> and it is not really "discoverable".

ls -la on UNIX
>
>
>>> maybe we should allow for an alternative name like "policy" without 
>>> the leading dot (or COLLECTION.policy so that there is still an 
>>> extension) so that it can be always visible?
>>> Ditto for .yarep files BTW.
>>
>> The problem is re conflicts. What if you have directory called 
>> COLLECTION? Or ROOT or whatever.
>
> Granted, and making that prefix configurable would complicate things 
> more and may even not be sufficient as one might need different 
> prefixes for different directory levels in case a conflict appears 
> later on.
>
> So maybe 'policy' would be the only sensible alternative?

that's not really consistent, then rather something like

_policy for "directories"

and

FILE_policy for "files"

but I really think with .policy we are fine and anyone who is interested 
how this works and read the documentation
will have no trouble with .policy

You might want to add a bugzilla entry for enhancement if you really 
care for this, such that we can later pick it up.
>
>
>> Btw, SVN and GIT use the same principle.
>
> Sure but in our case we have both a hidden file (.policy) and 
> non-hidden files (*.policy) which leads you to think you see all of 
> them when doing a simple `ls`.

that's why I am doing ls -la as pointed out above ;-)

From michael.wechner at wyona.com  Thu Mar 25 12:25:38 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Thu Mar 25 12:44:32 2010
Subject: [Yanel-dev] Introducing a refactored Policy viewer/manager
Message-ID: <4BAB4832.7020803@wyona.com>

Hi

At the moment can access the policy manager/viewer by clicking on a URL like

http://HOST:/yanel/REALM_ID/foo/bar.html?yanel.policy=read

or for example in the case of the from scratch realm

http://127.0.0.1:8080/yanel/from-scratch-realm/de/ueber/organization.html?yanel.policy=read

We are currently implementing a new version (hopefully better) of the 
policy manager/viewer.

In order to do so I would suggest to pick up Guillaume's suggestion

http://HOST:/yanel/REALM_ID/foo/bar.html?yanel.usecase=policy-read

which means we could have both versions side-by-side.

WDYT?

Thanks

Michi


From guillaume.deflache at wyona.com  Thu Mar 25 12:28:23 2010
From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=)
Date: Thu Mar 25 12:44:34 2010
Subject: [Yanel-dev] Canoo WebTest best practices: timing,
 the 'retry' steap and the 'sleep' task (and he 'timedgroup' step)
Message-ID: <4BAB48D7.6030606@wyona.com>

Hi!

In some projects we do tests on Javascript code or other kind of 
processing that takes some unpredictable amount of time.
To make sure that these tests have a chance to pass one can:
- need to either wait a bit for the long-running process to complete
- or if the check fails retry the check again immediately
- or do both


Many tests ATM only do one or the other, which is bad because:
- if the check is only tried once and the test machine is too slow at 
that time (say Hudson is compiling another project in parallel which 
hogs the CPU), then the test fails even if the correct result got 
available some time later
- if we keep checking without waiting:
   - we hog the CPU ("busy wait" loop)
   - even with many tries they may be so close from one another they may 
still all fail
   - if we do that many times the Canoo reports get huge which causes 
problems when the report needs to be transformed to HTML


For example *do not do*:

     
     

*neither do*:

     
       
     

but *rather do*:

     
       
       
     


Also please do not consider a feature test with no 'retry' and a single 
'sleep' both as a feature test and as a performance test. Better 
explicitely use the 'timedgroup' step 
() which is 
designed for that (and probably gives you better reporting WRT execution 
times) in another test, or another performance-testing tool altogether 
like JMeter.


References:
- the full test: 
http://svn.wyona.com/repos/public/yanel/trunk/src/realms/use-cases/yanel/src/test/canoo/tests/usecase-test-policy-manager.xml
- the 'retry' Canoo step (has another example of good usage): 
http://webtest.canoo.com/webtest/manual/retry.html
- the 'sleep' Ant task: http://ant.apache.org/manual/CoreTasks/sleep.html


HTH,
    Guillaume


P.S.: A further improvement to the recommended method above could be to 
make the sleep delay longer after each step, so that we only need a very 
small number of steps to get more and more slack WRT delays.
Cf. the 'decay' parameter in 
http://www.prototypejs.org/api/ajax/periodicalUpdater for a better 
explanation of what I have a mind.
I think this could be made using Canoo's "#{count}" dynamic property, 
but them it would probably be worth factoring that out in a new macro 
then to hide and avoid repeating the gory details.
From guillaume.deflache at wyona.com  Thu Mar 25 12:50:58 2010
From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=)
Date: Thu Mar 25 13:02:47 2010
Subject: [Yanel-dev] Introducing a refactored Policy viewer/manager
In-Reply-To: <4BAB4832.7020803@wyona.com>
References: <4BAB4832.7020803@wyona.com>
Message-ID: <4BAB4E22.5080106@wyona.com>

Michael Wechner schrieb:
> Hi
> 
> At the moment can access the policy manager/viewer by clicking on a URL 
> like
> 
> http://HOST:/yanel/REALM_ID/foo/bar.html?yanel.policy=read
> 
> or for example in the case of the from scratch realm
> 
> http://127.0.0.1:8080/yanel/from-scratch-realm/de/ueber/organization.html?yanel.policy=read 
> 
> 
> We are currently implementing a new version (hopefully better) of the 
> policy manager/viewer.
> 
> In order to do so I would suggest to pick up Guillaume's suggestion
> 
> http://HOST:/yanel/REALM_ID/foo/bar.html?yanel.usecase=policy-read
> 
> which means we could have both versions side-by-side.
> 
> WDYT?

FYI the original suggestion was here: 
http://lists.wyona.org/pipermail/yanel-development/2010-February/004436.html
I still agree with it! ;)
From simon at 333.ch  Thu Mar 25 23:26:55 2010
From: simon at 333.ch (simon)
Date: Thu Mar 25 23:45:43 2010
Subject: [Yanel-dev] TinyMCE resource type improvement re checkout
In-Reply-To: <4B9F6389.5060800@wyona.com>
References: <4B9F6389.5060800@wyona.com>
Message-ID: <4BABE32F.1010903@333.ch>

Michael Wechner schrieb:

Hi

sorry for the snail mail but i was on holidays :)
> Hi
>
> I have noticed when opening TinyMCE and the data is already checkout, 
> then one
> receives a note re checkout, but one does nevertheless receive the 
> input screen,
> which doesn't make sense, because one should not be able to edit.
>
> I guess the problem is that one cannot differentiate between "fatal" 
> errors (e.g. checjkout) and less "fatal" errors (e.g. well-formedness).
>
> I was thinking about checking on errors within
>
> src/resources/tinymce/htdocs/tinymce.jelly
>
> but I am not sure if this will disallow something which I don't know 
> should be possible.
>
> @Simon: Since you did most of the implementation, you might remember?
don't remember exactly. but i tried it out and it seem to work fine. 
thanks for fixing this.

cheers
simon
>
> Thanks
>
> Michi

From simon at 333.ch  Thu Mar 25 23:39:05 2010
From: simon at 333.ch (simon)
Date: Thu Mar 25 23:52:10 2010
Subject: [Yanel-dev] SitetreeDOMImpl
In-Reply-To: <4B953705.80101@wyona.com>
References: <4B952B0C.2020008@333.ch> <4B953705.80101@wyona.com>
Message-ID: <4BABE609.3020207@333.ch>

Michael Wechner schrieb:
> simon wrote:
>> hi all
>>
>> for a long time i would like to implement a sitetree editor. to start 
>> i implement the missing methods within NodeDOMImpl. when i started to 
>> write a test for it, i noticed something strange. AFAIU the 
>> SitetreeDOMImpl it expects/creates a a sitetree xml like this:
>>
>> 
>>  
>>    
>> 
>>
>> but all the sitetree.xml (yanel-website, from-scratch-realm etc.) i 
>> found within yanel looking like this:
>>
>> 
>>  
>>    Home
>>  
>> 
>>
>>
>> not sure what's the conclusion.
>
> I think it's a bug. I will have a look at it.
>> but i think the SitetreeDOMImpl doesn't make much sense at the 
>> moment. i'm wondering if this SitetreeDOMImpl has ever been used 
>> actually.
>
> definitely, but I am afraid mainly within customer projects, whereas I 
> will improve it within the public realms
thanks for this.
>>
>> i think we should create a schema for a yanel sitetree and make the 
>> SitetreeDOMImpl fits this schema.
>
> I agree that we need a schema, but we need to deduce it from the 
> SitetreeDOMImpl, because otherwise we might
> break backwards compatibility.
>
> Btw, I will soon start to implement a sitetree editor for one of our 
> customers, whereas it might not be totally generic, but
> I am happy to share as much as possible. I can send you the spec 
> offline and you might want to tell me then how much
> of it you want to re-use or how much we can develop together.
yes please send me the spec.
i can send you the untested implementations of the unimplemented  
methods of NodeDOMImpl if you haven't it already done so far.
what UI library are you planing to use?

cheers
simon
>
> Cheers
>
> Michi
>>
>> WDOT?
>>
>> cheers
>> simon
>>
>

From mehmet.birgi at wyona.com  Fri Mar 26 10:16:59 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Fri Mar 26 10:30:03 2010
Subject: [Yanel-dev] Doc update: Rapid development
Message-ID: <5bf1397d1003260216o1eaeae27rc22d868591cf7172@mail.gmail.com>

Hi

I have updated the best practices for rapid development (
http://yanel.wyona.org/en/documentation/best-practices/rapid-development-of=
-components.html)
to be - at least for me - a little clearer. Here is the new version for
reviewing:

Rapid Development of Components

When developing Yanel components, often there is no need to compile
everything. Two cases where this applies are *webapp classes* and *resource
classes*.
Efficiently building webapp classes

Webapp classes are all classes that are under
{yanel.home}/src/webapp/src/java/org/wyona/yanel/servlet. In order to build
and test these classes efficiently, one can run:

{yanel.home}/build.sh compile-webapp copy-basic-webapp-libs
copy-webapp-files-to-tomcat-cluster-node1

instead of running the whole build process. This will build only the webapp
and redeploy it, and should reduce the waiting time from a couple of minutes
to a couple of seconds.
Efficiently building resource classes

Resource classes are the classes that are found in separate directories
under {yanel.home}/src/contributions/resources. These classes all have their
own build.xml files, so to compile them efficiently, one can run the build
as

{yanel.home}/build.sh -f
src/contributions/resources/{resource.dir.name}/build.xml

instead of running the whole build process. Again, this will reduce the
building time significantly, as only the changed resource will be built.


Cheers,

Memo


-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032=
6/54dd6300/attachment.htm
From guillaume.deflache at wyona.com  Fri Mar 26 10:26:43 2010
From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=)
Date: Fri Mar 26 10:39:28 2010
Subject: [Yanel-dev] GWT HostMode/DevMode blocks Ant terminal
Message-ID: <4BAC7DD3.5040509@wyona.com>

Hi!

I noticed that the way the "gwt:hostmode" target of resource-types works 
blocks the Unix terminal on which it is run.
This is annoying, especially if you stops (^Z) the process, the GWT 
console is frozen as well as browsers that run the GWT plugin (!) (at 
least with Firefox).
Changing this should not be too confusing for the user because trying to 
open two GWT consoles always warns one is already running.

I am testing ATM if there are no problems with using on the 
corresponding 'java' task spawn='true' in addition to fork="true" to 
free the terminal. This should not make any difference WRT how the JVM 
itself is run AFAICU.
Under Windows I think this should also prevent blocking a DOS window.

Feedback is welcome, esp. WRT GWT 1.x if someone stills want to skip 
with that, Windows and OSX.

Cheers,
    Guillaume
From michael.wechner at wyona.com  Fri Mar 26 10:34:54 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Fri Mar 26 10:48:03 2010
Subject: [Yanel-dev] Doc update: Rapid development
In-Reply-To: <5bf1397d1003260216o1eaeae27rc22d868591cf7172@mail.gmail.com>
References: <5bf1397d1003260216o1eaeae27rc22d868591cf7172@mail.gmail.com>
Message-ID: <4BAC7FBE.9070409@wyona.com>

Dear Memo

Thanks for improving this, but I think you should add more examples re 
the resource, in particular a custom example and
also make it clearer that

|{yanel.home}/src/contributions/resources

is not the only directory containing resource types, but also

||{yanel.home}/src/resources

or

{yanel.home}src/realms/welcome-admin/yanel/resources/


or

{my.realm}res-types

etc.

Also you might want to add a note re realms itself, e.g.

{my.realm}build.xml


Thanks

Michi
|
Mehmet Birgi wrote:
> Hi
>
> I have updated the best practices for rapid development 
> (http://yanel.wyona.org/en/documentation/best-practices/rapid-development-of-components.html) 
> to be - at least for me - a little clearer. Here is the new version 
> for reviewing:
>
>
>   Rapid Development of Components
>
> When developing Yanel components, often there is no need to compile 
> everything. Two cases where this applies are *webapp classes* and 
> *resource classes*.
>
>
>     Efficiently building webapp classes
>
> Webapp classes are all classes that are under 
> |{yanel.home}/src/webapp/src/java/org/wyona/yanel/servlet|. In order 
> to build and test these classes efficiently, one can run:
>
> {yanel.home}/build.sh compile-webapp copy-basic-webapp-libs copy-webapp-files-to-tomcat-cluster-node1
>
> instead of running the whole build process. This will build only the 
> webapp and redeploy it, and should reduce the waiting time from a 
> couple of minutes to a couple of seconds.
>
>
>     Efficiently building resource classes
>
> Resource classes are the classes that are found in separate 
> directories under |{yanel.home}/src/contributions/resources|. These 
> classes all have their own |build.xml| files, so to compile them 
> efficiently, one can run the build as
>
> {yanel.home}/build.sh -f src/contributions/resources/{resource.dir.name }/build.xml
>
> instead of running the whole build process. Again, this will reduce 
> the building time significantly, as only the changed resource will be 
> built.
>
>
> Cheers,
>
> Memo
>
>
> -- 
> Mehmet Birgi
> www.wyona.com 
>

From mehmet.birgi at wyona.com  Fri Mar 26 11:17:59 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Fri Mar 26 11:31:17 2010
Subject: [Yanel-dev] Doc update: Rapid development
In-Reply-To: <4BAC7FBE.9070409@wyona.com>
References: <5bf1397d1003260216o1eaeae27rc22d868591cf7172@mail.gmail.com>
	<4BAC7FBE.9070409@wyona.com>
Message-ID: <5bf1397d1003260317l7b5e2ea4va23661b839f146a3@mail.gmail.com>

Thanks Michi for the suggestions. I am not sure what you meant by "custom
example", but here is the revised version so far:

Rapid Development of Components

When developing Yanel components, often there is no need to recompile
everything once a total build has been done. Components that can be built
separately are *webapp classes*, *resource classes* and *realms*.
Efficiently building webapp classes

Webapp classes are all classes that are under
{yanel.home}/src/webapp/src/java/org/wyona/yanel/servlet. In order to build
and test these classes efficiently, one can run:

{yanel.home}/build.sh compile-webapp copy-basic-webapp-libs
copy-webapp-files-to-tomcat-cluster-node1

instead of running the whole build process. This will build only the webapp
and redeploy it, and should reduce the waiting time from a couple of minutes
to a couple of seconds.
Efficiently building resource classes

Resource classes can be found in separate directories at several locations,
e.g.:

   - {yanel.home}/src/resources
   - {yanel.home}/src/contributions/resources
   - {yanel.home}src/realms/welcome-admin/yanel/resources
   - {yanel.home}src/realms/from-scratch-realm-template/res-types
   - {my.realm}res-types
   - etc...

These classes all have their own build.xml files, so to compile them
efficiently, one can run the build as

{yanel.home}/build.sh -f {path.to.resource.dir}/build.xml

instead of running the whole build process. Again, this will reduce the
building time significantly, as only the changed resource will be built.
Efficiently building single realms

In the same way as building resource classes, it is also possible to build
single realms after editing classes belonging to that realm:

{yanel.home}/build.sh -f {my.realm}/build.xml




On Fri, Mar 26, 2010 at 10:34 AM, Michael Wechner  wrote:

> Dear Memo
>
> Thanks for improving this, but I think you should add more examples re the
> resource, in particular a custom example and
> also make it clearer that
>
>
> |{yanel.home}/src/contributions/resources
>
> is not the only directory containing resource types, but also
>
> ||{yanel.home}/src/resources
>
> or
>
> {yanel.home}src/realms/welcome-admin/yanel/resources/
>
>
> or
>
> {my.realm}res-types
>
> etc.
>
> Also you might want to add a note re realms itself, e.g.
>
> {my.realm}build.xml
>
>
> Thanks
>
> Michi
> |
> Mehmet Birgi wrote:
>
>> Hi
>>
>> I have updated the best practices for rapid development (
>> http://yanel.wyona.org/en/documentation/best-practices/rapid-development=
-of-components.html)
>> to be - at least for me - a little clearer. Here is the new version for
>> reviewing:
>>
>>
>>  Rapid Development of Components
>>
>> When developing Yanel components, often there is no need to compile
>> everything. Two cases where this applies are *webapp classes* and *resou=
rce
>> classes*.
>>
>>
>>    Efficiently building webapp classes
>>
>> Webapp classes are all classes that are under
>> |{yanel.home}/src/webapp/src/java/org/wyona/yanel/servlet|. In order to
>> build and test these classes efficiently, one can run:
>>
>> {yanel.home}/build.sh compile-webapp copy-basic-webapp-libs
>> copy-webapp-files-to-tomcat-cluster-node1
>>
>> instead of running the whole build process. This will build only the
>> webapp and redeploy it, and should reduce the waiting time from a couple=
 of
>> minutes to a couple of seconds.
>>
>>
>>    Efficiently building resource classes
>>
>> Resource classes are the classes that are found in separate directories
>> under |{yanel.home}/src/contributions/resources|. These classes all have
>> their own |build.xml| files, so to compile them efficiently, one can run=
 the
>> build as
>>
>> {yanel.home}/build.sh -f src/contributions/resources/{resource.dir.name <
>> http://resource.dir.name>}/build.xml
>>
>>
>> instead of running the whole build process. Again, this will reduce the
>> building time significantly, as only the changed resource will be built.
>>
>>
>> Cheers,
>>
>> Memo
>>
>>
>> --
>> Mehmet Birgi
>> www.wyona.com 
>>
>>
> --
> Yanel-development mailing list Yanel-development@wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>



-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032=
6/f6eda4b5/attachment-0001.htm
From michael.wechner at wyona.com  Fri Mar 26 12:00:22 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Fri Mar 26 12:14:32 2010
Subject: [Yanel-dev] Doc update: Rapid development
In-Reply-To: <5bf1397d1003260317l7b5e2ea4va23661b839f146a3@mail.gmail.com>
References: <5bf1397d1003260216o1eaeae27rc22d868591cf7172@mail.gmail.com>	<4BAC7FBE.9070409@wyona.com>
	<5bf1397d1003260317l7b5e2ea4va23661b839f146a3@mail.gmail.com>
Message-ID: <4BAC93C6.4040003@wyona.com>

Mehmet Birgi wrote:
> Thanks Michi for the suggestions. I am not sure what you meant by 
> "custom example", 

an example of a third-party realm, e.g. a customer like Globus, whereas 
instead of using Globus you might want to
call it "MyInc" or whatever you think makes sense.

> but here is the revised version so far:
>
>
>   Rapid Development of Components
>
> When developing Yanel components, often there is no need to recompile 
> everything once a total build has been done. Components that can be 
> built separately are *webapp classes*, *resource classes* and *realms*.
>

these are not the only components, there is also the core, the impl 
(implementation) and the cmdl (command line)
and I think Neutron, but I am not sure either if that is it, hence you 
might rather say these are some examples.
>
>
>     Efficiently building webapp classes
>
> Webapp classes are all classes that are under 
> |{yanel.home}/src/webapp/src/java/org/wyona/yanel/servlet|. In order 
> to build and test these classes efficiently, one can run:
>
> {yanel.home}/build.sh compile-webapp copy-basic-webapp-libs copy-webapp-files-to-tomcat-cluster-node1
>
> instead of running the whole build process. This will build only the 
> webapp and redeploy it, and should reduce the waiting time from a 
> couple of minutes to a couple of seconds.
>
>
>     Efficiently building resource classes
>
> Resource classes can be found in separate directories at several 
> locations, e.g.:
>
>     * |{yanel.home}/src/resources|
>     * |{yanel.home}/src/contributions/resources|
>     * |{yanel.home}src/realms/welcome-admin/yanel/resources|
>     * |{yanel.home}src/realms/from-scratch-realm-template/res-types|
>     * |{my.realm}res-types|
>     * etc...
>

the slashes are not consistent


> These classes all have their own |build.xml| files, so to compile them 
> efficiently, one can run the build as
>
> {yanel.home}/build.sh -f {path.to.resource.dir}/build.xml
>
> instead of running the whole build process. Again, this will reduce 
> the building time significantly, as only the changed resource will be 
> built.
>
>
>     Efficiently building single realms
>
> In the same way as building resource classes, it is also possible to 
> build single realms after editing classes belonging to that realm:
>
> {yanel.home}/build.sh -f {my.realm}/build.xml


Thanks

Michi

>  
>
>
>
> On Fri, Mar 26, 2010 at 10:34 AM, Michael Wechner 
> > wrote:
>
>     Dear Memo
>
>     Thanks for improving this, but I think you should add more
>     examples re the resource, in particular a custom example and
>     also make it clearer that
>
>
>     |{yanel.home}/src/contributions/resources
>
>     is not the only directory containing resource types, but also
>
>     ||{yanel.home}/src/resources
>
>     or
>
>     {yanel.home}src/realms/welcome-admin/yanel/resources/
>
>
>     or
>
>     {my.realm}res-types
>
>     etc.
>
>     Also you might want to add a note re realms itself, e.g.
>
>     {my.realm}build.xml
>
>
>     Thanks
>
>     Michi
>     |
>     Mehmet Birgi wrote:
>
>         Hi
>
>         I have updated the best practices for rapid development
>         (http://yanel.wyona.org/en/documentation/best-practices/rapid-development-of-components.html)
>         to be - at least for me - a little clearer. Here is the new
>         version for reviewing:
>
>
>          Rapid Development of Components
>
>         When developing Yanel components, often there is no need to
>         compile everything. Two cases where this applies are *webapp
>         classes* and *resource classes*.
>
>
>            Efficiently building webapp classes
>
>         Webapp classes are all classes that are under
>         |{yanel.home}/src/webapp/src/java/org/wyona/yanel/servlet|. In
>         order to build and test these classes efficiently, one can run:
>
>         {yanel.home}/build.sh compile-webapp copy-basic-webapp-libs
>         copy-webapp-files-to-tomcat-cluster-node1
>
>         instead of running the whole build process. This will build
>         only the webapp and redeploy it, and should reduce the waiting
>         time from a couple of minutes to a couple of seconds.
>
>
>            Efficiently building resource classes
>
>         Resource classes are the classes that are found in separate
>         directories under |{yanel.home}/src/contributions/resources|.
>         These classes all have their own |build.xml| files, so to
>         compile them efficiently, one can run the build as
>
>         {yanel.home}/build.sh -f
>         src/contributions/resources/{resource.dir.name
>          }/build.xml
>
>
>         instead of running the whole build process. Again, this will
>         reduce the building time significantly, as only the changed
>         resource will be built.
>
>
>         Cheers,
>
>         Memo
>
>
>         -- 
>         Mehmet Birgi
>         www.wyona.com  
>
>
>     -- 
>     Yanel-development mailing list Yanel-development@wyona.com
>     
>     http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
>
>
>
> -- 
> Mehmet Birgi
> www.wyona.com 
>

From mehmet.birgi at wyona.com  Fri Mar 26 12:04:08 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Fri Mar 26 12:17:12 2010
Subject: [Yanel-dev] Deletable interface?
Message-ID: <5bf1397d1003260404w4e7cbb6fr77175fe92929be1c@mail.gmail.com>

Hi

I think that theoretically it may make sense to have an additional interface
"Deletable" which would include the method delete(), instead of having
delete() in the "Modifiable" interface. This would allow us to implement
resources that may be modified but not deleted, but I don't know how useful
this would really be practically and how costly it would be to implement.

Do you have any ideas/comments?

Cheers,

memo


-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032=
6/4bcdb601/attachment.htm
From mehmet.birgi at wyona.com  Fri Mar 26 12:09:12 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Fri Mar 26 12:22:17 2010
Subject: [Yanel-dev] Doc update: Rapid development
In-Reply-To: <4BAC93C6.4040003@wyona.com>
References: <5bf1397d1003260216o1eaeae27rc22d868591cf7172@mail.gmail.com>
	<4BAC7FBE.9070409@wyona.com>
	<5bf1397d1003260317l7b5e2ea4va23661b839f146a3@mail.gmail.com>
	<4BAC93C6.4040003@wyona.com>
Message-ID: <5bf1397d1003260409i527dce62hbb42001d70945639@mail.gmail.com>

On Fri, Mar 26, 2010 at 12:00 PM, Michael Wechner  wrote:

> Mehmet Birgi wrote:
>
>> Thanks Michi for the suggestions. I am not sure what you meant by "custom
>> example",
>>
>
> an example of a third-party realm, e.g. a customer like Globus, whereas
> instead of using Globus you might want to
> call it "MyInc" or whatever you think makes sense.
>

does the last part (Efficiently building single realms) not cover this? did
you mean something different?



>
>  but here is the revised version so far:
>>
>>
>>  Rapid Development of Components
>>
>> When developing Yanel components, often there is no need to recompile
>> everything once a total build has been done. Components that can be built
>> separately are *webapp classes*, *resource classes* and *realms*.
>>
>>
> these are not the only components, there is also the core, the impl
> (implementation) and the cmdl (command line)
> and I think Neutron, but I am not sure either if that is it, hence you
> might rather say these are some examples.
>
>
>>
>>    Efficiently building webapp classes
>>
>> Webapp classes are all classes that are under
>> |{yanel.home}/src/webapp/src/java/org/wyona/yanel/servlet|. In order to
>> build and test these classes efficiently, one can run:
>>
>> {yanel.home}/build.sh compile-webapp copy-basic-webapp-libs
>> copy-webapp-files-to-tomcat-cluster-node1
>>
>> instead of running the whole build process. This will build only the
>> webapp and redeploy it, and should reduce the waiting time from a couple=
 of
>> minutes to a couple of seconds.
>>
>>
>>    Efficiently building resource classes
>>
>> Resource classes can be found in separate directories at several
>> locations, e.g.:
>>
>>    * |{yanel.home}/src/resources|
>>    * |{yanel.home}/src/contributions/resources|
>>    * |{yanel.home}src/realms/welcome-admin/yanel/resources|
>>    * |{yanel.home}src/realms/from-scratch-realm-template/res-types|
>>    * |{my.realm}res-types|
>>    * etc...
>>
>>
> the slashes are not consistent


thanks for pointing out, this is corrected now.

Thanks,

Memo



>
>
>
>  These classes all have their own |build.xml| files, so to compile them
>> efficiently, one can run the build as
>>
>> {yanel.home}/build.sh -f {path.to.resource.dir}/build.xml
>>
>> instead of running the whole build process. Again, this will reduce the
>> building time significantly, as only the changed resource will be built.
>>
>>
>>    Efficiently building single realms
>>
>> In the same way as building resource classes, it is also possible to bui=
ld
>> single realms after editing classes belonging to that realm:
>>
>> {yanel.home}/build.sh -f {my.realm}/build.xml
>>
>
>
> Thanks
>
> Michi
>
>
>>
>>
>> On Fri, Mar 26, 2010 at 10:34 AM, Michael Wechner <
>> michael.wechner@wyona.com > wrote:
>>
>>    Dear Memo
>>
>>    Thanks for improving this, but I think you should add more
>>    examples re the resource, in particular a custom example and
>>    also make it clearer that
>>
>>
>>    |{yanel.home}/src/contributions/resources
>>
>>    is not the only directory containing resource types, but also
>>
>>    ||{yanel.home}/src/resources
>>
>>    or
>>
>>    {yanel.home}src/realms/welcome-admin/yanel/resources/
>>
>>
>>    or
>>
>>    {my.realm}res-types
>>
>>    etc.
>>
>>    Also you might want to add a note re realms itself, e.g.
>>
>>    {my.realm}build.xml
>>
>>
>>    Thanks
>>
>>    Michi
>>    |
>>    Mehmet Birgi wrote:
>>
>>        Hi
>>
>>        I have updated the best practices for rapid development
>>        (
>> http://yanel.wyona.org/en/documentation/best-practices/rapid-development=
-of-components.html
>> )
>>        to be - at least for me - a little clearer. Here is the new
>>        version for reviewing:
>>
>>
>>         Rapid Development of Components
>>
>>        When developing Yanel components, often there is no need to
>>        compile everything. Two cases where this applies are *webapp
>>        classes* and *resource classes*.
>>
>>
>>           Efficiently building webapp classes
>>
>>        Webapp classes are all classes that are under
>>        |{yanel.home}/src/webapp/src/java/org/wyona/yanel/servlet|. In
>>        order to build and test these classes efficiently, one can run:
>>
>>        {yanel.home}/build.sh compile-webapp copy-basic-webapp-libs
>>        copy-webapp-files-to-tomcat-cluster-node1
>>
>>        instead of running the whole build process. This will build
>>        only the webapp and redeploy it, and should reduce the waiting
>>        time from a couple of minutes to a couple of seconds.
>>
>>
>>           Efficiently building resource classes
>>
>>        Resource classes are the classes that are found in separate
>>        directories under |{yanel.home}/src/contributions/resources|.
>>        These classes all have their own |build.xml| files, so to
>>        compile them efficiently, one can run the build as
>>
>>        {yanel.home}/build.sh -f
>>        src/contributions/resources/{resource.dir.name
>>         }/build.xml
>>
>>
>>
>>        instead of running the whole build process. Again, this will
>>        reduce the building time significantly, as only the changed
>>        resource will be built.
>>
>>
>>        Cheers,
>>
>>        Memo
>>
>>
>>        --         Mehmet Birgi
>>        www.wyona.com  
>>
>>
>>
>>    --     Yanel-development mailing list Yanel-development@wyona.com
>>    
>>
>>    http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>
>>
>>
>>
>> --
>> Mehmet Birgi
>> www.wyona.com 
>>
>>
> --
> Yanel-development mailing list Yanel-development@wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>



-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032=
6/677619d3/attachment.htm
From michael.wechner at wyona.com  Fri Mar 26 12:21:49 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Fri Mar 26 12:34:53 2010
Subject: [Yanel-dev] Doc update: Rapid development
In-Reply-To: <5bf1397d1003260409i527dce62hbb42001d70945639@mail.gmail.com>
References: <5bf1397d1003260216o1eaeae27rc22d868591cf7172@mail.gmail.com>	<4BAC7FBE.9070409@wyona.com>	<5bf1397d1003260317l7b5e2ea4va23661b839f146a3@mail.gmail.com>	<4BAC93C6.4040003@wyona.com>
	<5bf1397d1003260409i527dce62hbb42001d70945639@mail.gmail.com>
Message-ID: <4BAC98CD.5090204@wyona.com>

Mehmet Birgi wrote:
>
>
> On Fri, Mar 26, 2010 at 12:00 PM, Michael Wechner 
> > wrote:
>
>     Mehmet Birgi wrote:
>
>         Thanks Michi for the suggestions. I am not sure what you meant
>         by "custom example",
>
>
>     an example of a third-party realm, e.g. a customer like Globus,
>     whereas instead of using Globus you might want to
>     call it "MyInc" or whatever you think makes sense.
>
>
> does the last part (Efficiently building single realms) not cover 
> this? did you mean something different?

no, but you were "asking" so I tried to make it clear.


Cheers

Michi

From mehmet.birgi at wyona.com  Fri Mar 26 12:25:17 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Fri Mar 26 12:38:23 2010
Subject: [Yanel-dev] Doc update: Rapid development
In-Reply-To: <4BAC98CD.5090204@wyona.com>
References: <5bf1397d1003260216o1eaeae27rc22d868591cf7172@mail.gmail.com>
	<4BAC7FBE.9070409@wyona.com>
	<5bf1397d1003260317l7b5e2ea4va23661b839f146a3@mail.gmail.com>
	<4BAC93C6.4040003@wyona.com>
	<5bf1397d1003260409i527dce62hbb42001d70945639@mail.gmail.com>
	<4BAC98CD.5090204@wyona.com>
Message-ID: <5bf1397d1003260425h2fa83db1gd09c3ac4a6ac8671@mail.gmail.com>

OK :-)

I'll commit this version then.

Thanks,

Memo



On Fri, Mar 26, 2010 at 12:21 PM, Michael Wechner  wrote:

> Mehmet Birgi wrote:
>
>
>>
>> On Fri, Mar 26, 2010 at 12:00 PM, Michael Wechner <
>> michael.wechner@wyona.com > wrote:
>>
>>    Mehmet Birgi wrote:
>>
>>        Thanks Michi for the suggestions. I am not sure what you meant
>>        by "custom example",
>>
>>
>>    an example of a third-party realm, e.g. a customer like Globus,
>>    whereas instead of using Globus you might want to
>>    call it "MyInc" or whatever you think makes sense.
>>
>>
>> does the last part (Efficiently building single realms) not cover this?
>> did you mean something different?
>>
>
> no, but you were "asking" so I tried to make it clear.
>
>
> Cheers
>
> Michi
>
>
> --
> Yanel-development mailing list Yanel-development@wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>



-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032=
6/98326ab9/attachment-0001.htm
From michael.wechner at wyona.com  Fri Mar 26 13:36:03 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Fri Mar 26 13:49:07 2010
Subject: [Yanel-dev] Doc update: Rapid development
In-Reply-To: <5bf1397d1003260425h2fa83db1gd09c3ac4a6ac8671@mail.gmail.com>
References: <5bf1397d1003260216o1eaeae27rc22d868591cf7172@mail.gmail.com>	<4BAC7FBE.9070409@wyona.com>	<5bf1397d1003260317l7b5e2ea4va23661b839f146a3@mail.gmail.com>	<4BAC93C6.4040003@wyona.com>	<5bf1397d1003260409i527dce62hbb42001d70945639@mail.gmail.com>	<4BAC98CD.5090204@wyona.com>
	<5bf1397d1003260425h2fa83db1gd09c3ac4a6ac8671@mail.gmail.com>
Message-ID: <4BACAA33.80304@wyona.com>

Mehmet Birgi wrote:
> OK :-)
>
> I'll commit this version then.

thanks

Michi
>
> Thanks,
>
> Memo
>
>
>
> On Fri, Mar 26, 2010 at 12:21 PM, Michael Wechner 
> > wrote:
>
>     Mehmet Birgi wrote:
>
>
>
>         On Fri, Mar 26, 2010 at 12:00 PM, Michael Wechner
>         
>                  >> wrote:
>
>            Mehmet Birgi wrote:
>
>                Thanks Michi for the suggestions. I am not sure what
>         you meant
>                by "custom example",
>
>
>            an example of a third-party realm, e.g. a customer like Globus,
>            whereas instead of using Globus you might want to
>            call it "MyInc" or whatever you think makes sense.
>
>
>         does the last part (Efficiently building single realms) not
>         cover this? did you mean something different?
>
>
>     no, but you were "asking" so I tried to make it clear.
>
>
>     Cheers
>
>     Michi
>
>
>     -- 
>     Yanel-development mailing list Yanel-development@wyona.com
>     
>     http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
>
>
>
> -- 
> Mehmet Birgi
> www.wyona.com 
>

From guillaume.deflache at wyona.com  Fri Mar 26 17:40:43 2010
From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=)
Date: Fri Mar 26 17:52:32 2010
Subject: [Yanel-dev] easier way to switch to GWT 2 DevMode: a bookmarket
Message-ID: <4BACE38B.6040100@wyona.com>

Hi!

Here it is (*):
javascript:(function()%7Bvar%20l=location,q=l.search,h=l.protocol+'//'+l.host+l.pathname+q+(q?'&':'?')+'gwt.codesvr='+l.hostname+':9997',n=h.replace(new%20RegExp('[%3A/.?=&-]','g'),'_'),W=open(h,n);/*alert(n);*/W.focus();%7D)()
This works in all browsers AFAICS.

To use it, simply create a new bookmark with the above URL as link and
e.g. "GWT devmode" as name.

Calling this bookmarklet will of course only do something interesting on 
a page using GWT.

This is heavily inspired by the previous "Yanel RT 'source' view" 
bookmarket and behaves mostly the same, so please refer to its 
announcement message for other details: 
http://lists.wyona.org/pipermail/yanel-development/2010-March/004490.html

HTH,
    Guillaume
From guillaume.deflache at wyona.com  Fri Mar 26 17:48:28 2010
From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=)
Date: Fri Mar 26 18:00:21 2010
Subject: [Yanel-dev] Canoo WebTest best practices: timing, the 'retry'
	steap and the 'sleep' task (and he 'timedgroup' step)
In-Reply-To: <4BAB48D7.6030606@wyona.com>
References: <4BAB48D7.6030606@wyona.com>
Message-ID: <4BACE55C.40309@wyona.com>

Hi!

Guillaume D?flache schrieb:
> [...]
> but *rather do*:
> 
>     
>        seconds="1"/>
>        text="Wyona Access Control Policy (GWT) Editor"/>
>     

This has been tested on a customer project and seems to work great (it 
may even have reduce test durations and memory usage).

It was implemented as a more compact 'retry-after-sleep' Ant macro, 
which may be brought to Yanel for general usage at some point as it is 
not project-specific at all.


> P.S.: A further improvement to the recommended method above could be to 
> make the sleep delay longer after each step, so that we only need a very 
> small number of steps to get more and more slack WRT delays.
> Cf. the 'decay' parameter in 
> http://www.prototypejs.org/api/ajax/periodicalUpdater for a better 
> explanation of what I have a mind.
> I think this could be made using Canoo's "#{count}" dynamic property, 
> but them it would probably be worth factoring that out in a new macro 
> then to hide and avoid repeating the gory details.

This might now be implemented easily an as extra optional parameter to 
that macro, or in another similar macro.

HTH,
    Guillaume
From guillaume.deflache at wyona.com  Fri Mar 26 19:55:18 2010
From: guillaume.deflache at wyona.com (=?ISO-8859-15?Q?Guillaume_D=E9flache?=)
Date: Fri Mar 26 20:07:06 2010
Subject: [Yanel-dev] running Canoo tests independently
Message-ID: <4BAD0316.70706@wyona.com>

Hi!

While fixing a lot of tests I suffered again the pain of having to run 
the full test suite of a project just to check the outcome of a single 
test because they are all interdependent.
(Fortunately on that project at least thanks to memo we have an 
automatic script to reset the application data to the initial state.)


One small inexpensive improvement could be to distinguish independent 
tests from the non-independent ones so that one would know at least when 
running the full suite is not needed.
This had been done on this project and kick-started for the 'use-cases' 
realms (which AFAICU is supposed to contain the Canoo tests that are not 
related to a particular realm or may involve several realms), cf. 
http://svn.wyona.com/repos/public/yanel/trunk/src/realms/use-cases/yanel/src/test/canoo/tests/allTests.xml


One further more expensive improvement I recently discussed offline with 
memo would be to try leverage Ant target dependency tracking (e.g. the 
'depends' attribute of targets) to make dependencies between Canoo tests 
explicit.
That would allow running a non-independent test alone by automatically 
executing its dependencies first. This may probably need new cleaning 
targets at the beginning of the dependency chain, probably more focused 
but that could still be shared by several tests as a kind of common test 
data subset.

I really the explanation is pretty cryptic, I will try to come with more 
concrete examples if there is some interest.


The underpinning idea here is that making every test fully 
self-contained is a lot of work (either lots of copy-paste or a very 
sophisticated organization of test data) and may slow down the whole 
test suite so much it will not be practically anyway.
So IMHO we have to find a middle ground if we want to keep adding more 
and more end-to-end tests.

HTH,
    Guillaume
From michael.wechner at wyona.com  Fri Mar 26 23:18:18 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Fri Mar 26 23:35:07 2010
Subject: [Yanel-dev] running Canoo tests independently
In-Reply-To: <4BAD0316.70706@wyona.com>
References: <4BAD0316.70706@wyona.com>
Message-ID: <4BAD32AA.6060401@wyona.com>

Guillaume D?flache wrote:
>
> I really the explanation is pretty cryptic, I will try to come with 
> more concrete examples if there is some interest.

I think that would be best. Make a best practice example and point to it 
from the documentation:

http://www.yanel.org/en/documentation/testing-framework.html

Thanks

Michi
>
>
> The underpinning idea here is that making every test fully 
> self-contained is a lot of work (either lots of copy-paste or a very 
> sophisticated organization of test data) and may slow down the whole 
> test suite so much it will not be practically anyway.
> So IMHO we have to find a middle ground if we want to keep adding more 
> and more end-to-end tests.
>
> HTH,
>    Guillaume

From michael.wechner at wyona.com  Fri Mar 26 23:22:50 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Fri Mar 26 23:35:58 2010
Subject: [Yanel-dev] Re: [Yanel-commits] rev 48323
	-	public/yanel/trunk/src/contributions/resources/security-api/src/java/org/wyona/yanel/impl/resources/securityapi
In-Reply-To: <201003261518.o2QFI4NC027435@cvs-extra.wyona.com>
References: <201003261518.o2QFI4NC027435@cvs-extra.wyona.com>
Message-ID: <4BAD33BA.6010606@wyona.com>

what is happening if deleting a policy fails, for example because the 
user does not have the right to delete it?

(Also see 
http://java.sun.com/j2se/1.4.2/docs/api/java/io/File.html#delete())

Thanks

Michi

guillaume@wyona.com wrote:
> Author: guillaume
> Date: 2010-03-26 16:18:04 +0100 (Fri, 26 Mar 2010)
> New Revision: 48323
>
> Modified:
>    public/yanel/trunk/src/contributions/resources/security-api/src/java/org/wyona/yanel/impl/resources/securityapi/UserManagerResource.java
> Log:
> Implemented API to delete a policy (non-recursively for now).
>
>
> Modified: public/yanel/trunk/src/contributions/resources/security-api/src/java/org/wyona/yanel/impl/resources/securityapi/UserManagerResource.java
> ===================================================================
> --- public/yanel/trunk/src/contributions/resources/security-api/src/java/org/wyona/yanel/impl/resources/securityapi/UserManagerResource.java	2010-03-26 15:14:10 UTC (rev 48322)
> +++ public/yanel/trunk/src/contributions/resources/security-api/src/java/org/wyona/yanel/impl/resources/securityapi/UserManagerResource.java	2010-03-26 15:18:04 UTC (rev 48323)
> @@ -10,6 +10,7 @@
>  import org.wyona.security.core.api.Group;
>  import org.wyona.security.core.api.GroupManager;
>  import org.wyona.security.core.api.Item;
> +import org.wyona.security.core.api.PolicyManager;
>  import org.wyona.security.core.api.User;
>  import org.wyona.security.core.api.UserManager;
>  
> @@ -29,9 +30,7 @@
>      
>      private static Logger log = Logger.getLogger(UserManagerResource.class);
>      
> -    /**
> -     *
> -     */
> +    @Override
>      protected InputStream getContentXML(String viewId) {
>          if (log.isDebugEnabled()) {
>              log.debug("requested viewId: " + viewId);
> @@ -50,6 +49,11 @@
>                  sb.append(getUserAsXML(getEnvironment().getRequest().getParameter("id")));
>              } else if (usecase.equals("getgroups")) {
>                  sb.append(getGroupsAsXML());
> +            } else if (usecase.equals("deletepolicy")) {
> +                String path = getParameterAsString("path");
> +                String recursivelyText = getParameterAsString("deep");
> +                boolean recursively = "1".equals(recursivelyText);
> +                deletePolicy(path, recursively);
>              } else {
>                  sb.append("" + usecase + "");
>              }
> @@ -65,9 +69,7 @@
>          return new ByteArrayInputStream(sb.toString().getBytes());
>      }
>  
> -    /**
> -     *
> -     */
> +    @Override
>      public boolean exists() {
>          log.warn("TODO: Implementation not finished yet!");
>          return true;
> @@ -119,6 +121,18 @@
>      }
>  
>      /**
> +     * Deletes a specific policy.
> +     * @param id the policy ID
> +     */
> +    private void deletePolicy(String path, boolean recursively) throws Exception {
> +        PolicyManager pm = getRealm().getPolicyManager();
> +        if (recursively) {
> +            log.warn("Recursively deletion of policies not yet implemented, only policy "+path+" will be deleted.");
> +        }
> +        pm.removePolicy(path);
> +    }
> +
> +    /**
>       * Get all users
>       */
>      private StringBuilder getUsersAsXML() throws Exception {
>
>   

From michael.wechner at wyona.com  Fri Mar 26 23:25:38 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Fri Mar 26 23:40:37 2010
Subject: [Yanel-dev] Canoo WebTest best practices: timing, the 'retry'
	steap and the 'sleep' task (and he 'timedgroup' step)
In-Reply-To: <4BACE55C.40309@wyona.com>
References: <4BAB48D7.6030606@wyona.com> <4BACE55C.40309@wyona.com>
Message-ID: <4BAD3462.2020007@wyona.com>

Guillaume D?flache wrote:
> Hi!
>
> Guillaume D?flache schrieb:
>> [...]
>> but *rather do*:
>>
>>     
>>       > seconds="1"/>
>>       > text="Wyona Access Control Policy (GWT) Editor"/>
>>     
>
> This has been tested on a customer project and seems to work great (it 
> may even have reduce test durations and memory usage).
>
> It was implemented as a more compact 'retry-after-sleep' Ant macro, 
> which may be brought to Yanel for general usage at some point as it is 
> not project-specific at all.

sounds  great :-)

Thanks very much for introducing this.

Michi
>
>
>> P.S.: A further improvement to the recommended method above could be 
>> to make the sleep delay longer after each step, so that we only need 
>> a very small number of steps to get more and more slack WRT delays.
>> Cf. the 'decay' parameter in 
>> http://www.prototypejs.org/api/ajax/periodicalUpdater for a better 
>> explanation of what I have a mind.
>> I think this could be made using Canoo's "#{count}" dynamic property, 
>> but them it would probably be worth factoring that out in a new macro 
>> then to hide and avoid repeating the gory details.
>
> This might now be implemented easily an as extra optional parameter to 
> that macro, or in another similar macro.
>
> HTH,
>    Guillaume

From michael.wechner at wyona.com  Mon Mar 29 09:59:00 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Mon Mar 29 10:12:08 2010
Subject: [Yanel-dev] Introducing a refactored Policy viewer/manager
In-Reply-To: <4BAB4E22.5080106@wyona.com>
References: <4BAB4832.7020803@wyona.com> <4BAB4E22.5080106@wyona.com>
Message-ID: <4BB05DC4.1040208@wyona.com>

Guillaume D?flache wrote:
> Michael Wechner schrieb:
>> Hi
>>
>> At the moment can access the policy manager/viewer by clicking on a 
>> URL like
>>
>> http://HOST:/yanel/REALM_ID/foo/bar.html?yanel.policy=read
>>
>> or for example in the case of the from scratch realm
>>
>> http://127.0.0.1:8080/yanel/from-scratch-realm/de/ueber/organization.html?yanel.policy=read 
>>
>>
>> We are currently implementing a new version (hopefully better) of the 
>> policy manager/viewer.
>>
>> In order to do so I would suggest to pick up Guillaume's suggestion
>>
>> http://HOST:/yanel/REALM_ID/foo/bar.html?yanel.usecase=policy-read
>>
>> which means we could have both versions side-by-side.
>>
>> WDYT?
>
> FYI the original suggestion was here: 
> http://lists.wyona.org/pipermail/yanel-development/2010-February/004436.html 
>
> I still agree with it! ;)

part of it is now implemented, whereas instead of

/foo/bar/yanel.usecase=read-policy

I have implemented it as

http://127.0.0.1:8080/yanel/from-scratch-realm/de/ueber.html?yanel.usecase=policy.read

because the mapping between usecase permissions is 1:1

If there is any reason not to use policy.read as value, then please let 
me know

Thanks

Michi

From michael.wechner at wyona.com  Mon Mar 29 10:17:13 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Mon Mar 29 10:34:14 2010
Subject: [Yanel-dev] Introducing a refactored Policy viewer/manager
In-Reply-To: <4BB05DC4.1040208@wyona.com>
References: <4BAB4832.7020803@wyona.com> <4BAB4E22.5080106@wyona.com>
	<4BB05DC4.1040208@wyona.com>
Message-ID: <4BB06209.2080906@wyona.com>

Michael Wechner wrote:
> Guillaume D?flache wrote:
>> Michael Wechner schrieb:
>>> Hi
>>>
>>> At the moment can access the policy manager/viewer by clicking on a 
>>> URL like
>>>
>>> http://HOST:/yanel/REALM_ID/foo/bar.html?yanel.policy=read
>>>
>>> or for example in the case of the from scratch realm
>>>
>>> http://127.0.0.1:8080/yanel/from-scratch-realm/de/ueber/organization.html?yanel.policy=read 
>>>
>>>
>>> We are currently implementing a new version (hopefully better) of 
>>> the policy manager/viewer.
>>>
>>> In order to do so I would suggest to pick up Guillaume's suggestion
>>>
>>> http://HOST:/yanel/REALM_ID/foo/bar.html?yanel.usecase=policy-read
>>>
>>> which means we could have both versions side-by-side.
>>>
>>> WDYT?
>>
>> FYI the original suggestion was here: 
>> http://lists.wyona.org/pipermail/yanel-development/2010-February/004436.html 
>>
>> I still agree with it! ;)
>
> part of it is now implemented, whereas instead of
>
> /foo/bar/yanel.usecase=read-policy
>
> I have implemented it as
>
> http://127.0.0.1:8080/yanel/from-scratch-realm/de/ueber.html?yanel.usecase=policy.read 
>

btw, this is now mapping to

src/webapp/global-resource-configs/policy-manager-v2_yanel-rc.xml

whereas it currently is a copy of the version 1, but it means we can now 
implement
the new Policy Manager version 2

Thanks

Michi
>
> because the mapping between usecase permissions is 1:1
>
> If there is any reason not to use policy.read as value, then please 
> let me know
>
> Thanks
>
> Michi
>

From mehmet.birgi at wyona.com  Mon Mar 29 11:55:47 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Mon Mar 29 12:09:40 2010
Subject: [Yanel-dev] running Canoo tests independently
In-Reply-To: <4BAD32AA.6060401@wyona.com>
References: <4BAD0316.70706@wyona.com> <4BAD32AA.6060401@wyona.com>
Message-ID: <5bf1397d1003290255i727799f6n32ba484bed6e26a5@mail.gmail.com>

Another (maybe less expensive) approach would be to group interdependent
tests together. I have just done this for testing a part of an application
for a customer project. I had to test creation, editing and deletion of a
part of a website. The cleanest way to do this is obviously to create a test
page first, then edit it, and then delete it, so that no "debris" is left
over (except automatically created meta data, of course). These tests have
to be executed in that order, or else they will fail. What I did is
basically:

1. write a separate test-XX.xml file for each test

2. write a file test-all-XXs.xml file, that calls those files as ant targets

3. integrate the test-all-XXs.xml in the test suite, and provide a target
"test-XXs" to execute that test package.

In this case, each of these tests can't be executed independently, but at
least they can be executed as a package separate from the rest.




On Fri, Mar 26, 2010 at 11:18 PM, Michael Wechner  wrote:

> Guillaume D=E9flache wrote:
>
>>
>> I really the explanation is pretty cryptic, I will try to come with more
>> concrete examples if there is some interest.
>>
>
> I think that would be best. Make a best practice example and point to it
> from the documentation:
>
> http://www.yanel.org/en/documentation/testing-framework.html
>
> Thanks
>
> Michi
>
>
>>
>> The underpinning idea here is that making every test fully self-contained
>> is a lot of work (either lots of copy-paste or a very sophisticated
>> organization of test data) and may slow down the whole test suite so muc=
h it
>> will not be practically anyway.
>> So IMHO we have to find a middle ground if we want to keep adding more a=
nd
>> more end-to-end tests.
>>
>> HTH,
>>   Guillaume
>>
>
> --
> Yanel-development mailing list Yanel-development@wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>



-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010032=
9/a8818fdc/attachment.htm
From michael.wechner at wyona.com  Tue Mar 30 16:37:53 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Tue Mar 30 16:51:02 2010
Subject: [Yanel-dev] Re: [Yanel-commits] Build failed in Hudson:
	security-trunk #1
In-Reply-To: <13947513.681269956903939.JavaMail.guillaume@wc-13.wyona.com>
References: <27291745.01269876532859.JavaMail.guillaume@wc-13.wyona.com>
	<13947513.681269956903939.JavaMail.guillaume@wc-13.wyona.com>
Message-ID: <4BB20CC1.7030400@wyona.com>

I think the problem is that Hudson cannot access the internal LDAP server.

I will try to fix this shortly.

Cheers

Michi

hudson@wyona.com wrote:
> See http://195.226.6.72:8080/job/security-trunk/1/changes
>
> Changes:
>
> [Michi] pass LDAP client implementation
>
> [Michi] notes about LDAP added
>
> [Michi] LDAP client added
>
> ------------------------------------------
> [...truncated 157 lines...]
>     [junit] 189913 2010-03-30 15:45:13,633 [main] ERROR org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers():78  - TODO: LDAP Implementation not finished yet!
>     [junit] 378906 2010-03-30 15:48:22,626 [main] ERROR org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers():89  - javax.naming.CommunicationException: 192.168.200.109:389 [Root exception is java.net.ConnectException: Connection timed out]
>     [junit] javax.naming.CommunicationException: 192.168.200.109:389 [Root exception is java.net.ConnectException: Connection timed out]
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:210)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
>     [junit] 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
>     [junit] 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
>     [junit] 	at javax.naming.InitialContext.init(InitialContext.java:223)
>     [junit] 	at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getInitialLdapContext(LDAPClientImpl.java:73)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getAllUsernames(LDAPClientImpl.java:25)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers(LDAPUserManagerImpl.java:80)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPIdentityManagerImpl.(LDAPIdentityManagerImpl.java:41)
>     [junit] 	at org.wyona.security.test.LDAPIdentityManagerImplTest.setUp(LDAPIdentityManagerImplTest.java:32)
>     [junit] 	at junit.framework.TestCase.runBare(TestCase.java:125)
>     [junit] 	at junit.framework.TestResult$1.protect(TestResult.java:106)
>     [junit] 	at junit.framework.TestResult.runProtected(TestResult.java:124)
>     [junit] 	at junit.framework.TestResult.run(TestResult.java:109)
>     [junit] 	at junit.framework.TestCase.run(TestCase.java:118)
>     [junit] 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
>     [junit] 	at junit.framework.TestSuite.run(TestSuite.java:203)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768)
>     [junit] Caused by: java.net.ConnectException: Connection timed out
>     [junit] 	at java.net.PlainSocketImpl.socketConnect(Native Method)
>     [junit] 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>     [junit] 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>     [junit] 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>     [junit] 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>     [junit] 	at java.net.Socket.connect(Socket.java:525)
>     [junit] 	at java.net.Socket.connect(Socket.java:475)
>     [junit] 	at java.net.Socket.(Socket.java:372)
>     [junit] 	at java.net.Socket.(Socket.java:186)
>     [junit] 	at com.sun.jndi.ldap.Connection.createSocket(Connection.java:352)
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:187)
>     [junit] 	... 27 more
>     [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 379.216 sec
>     [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 379.216 sec
>     [junit] ------------- Standard Output ---------------
>     [junit] 0    2010-03-30 15:42:03,720 [main] WARN  org.wyona.yarep.core.RepositoryFactory.():47  - No such resource: yarep.properties
>     [junit] 622  2010-03-30 15:42:04,342 [main] ERROR org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers():78  - TODO: LDAP Implementation not finished yet!
>     [junit] 189721 2010-03-30 15:45:13,441 [main] ERROR org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers():89  - javax.naming.CommunicationException: 192.168.200.109:389 [Root exception is java.net.ConnectException: Connection timed out]
>     [junit] javax.naming.CommunicationException: 192.168.200.109:389 [Root exception is java.net.ConnectException: Connection timed out]
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:210)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
>     [junit] 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
>     [junit] 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
>     [junit] 	at javax.naming.InitialContext.init(InitialContext.java:223)
>     [junit] 	at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getInitialLdapContext(LDAPClientImpl.java:73)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getAllUsernames(LDAPClientImpl.java:25)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers(LDAPUserManagerImpl.java:80)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPIdentityManagerImpl.(LDAPIdentityManagerImpl.java:41)
>     [junit] 	at org.wyona.security.test.LDAPIdentityManagerImplTest.setUp(LDAPIdentityManagerImplTest.java:32)
>     [junit] 	at junit.framework.TestCase.runBare(TestCase.java:125)
>     [junit] 	at junit.framework.TestResult$1.protect(TestResult.java:106)
>     [junit] 	at junit.framework.TestResult.runProtected(TestResult.java:124)
>     [junit] 	at junit.framework.TestResult.run(TestResult.java:109)
>     [junit] 	at junit.framework.TestCase.run(TestCase.java:118)
>     [junit] 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
>     [junit] 	at junit.framework.TestSuite.run(TestSuite.java:203)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768)
>     [junit] Caused by: java.net.ConnectException: Connection timed out
>     [junit] 	at java.net.PlainSocketImpl.socketConnect(Native Method)
>     [junit] 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>     [junit] 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>     [junit] 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>     [junit] 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>     [junit] 	at java.net.Socket.connect(Socket.java:525)
>     [junit] 	at java.net.Socket.connect(Socket.java:475)
>     [junit] 	at java.net.Socket.(Socket.java:372)
>     [junit] 	at java.net.Socket.(Socket.java:186)
>     [junit] 	at com.sun.jndi.ldap.Connection.createSocket(Connection.java:352)
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:187)
>     [junit] 	... 27 more
>     [junit] 189741 2010-03-30 15:45:13,461 [main] WARN  org.wyona.yarep.core.RepositoryFactory.():47  - No such resource: yarep.properties
>     [junit] 189913 2010-03-30 15:45:13,633 [main] ERROR org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers():78  - TODO: LDAP Implementation not finished yet!
>     [junit] 378906 2010-03-30 15:48:22,626 [main] ERROR org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers():89  - javax.naming.CommunicationException: 192.168.200.109:389 [Root exception is java.net.ConnectException: Connection timed out]
>     [junit] javax.naming.CommunicationException: 192.168.200.109:389 [Root exception is java.net.ConnectException: Connection timed out]
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:210)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
>     [junit] 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
>     [junit] 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
>     [junit] 	at javax.naming.InitialContext.init(InitialContext.java:223)
>     [junit] 	at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getInitialLdapContext(LDAPClientImpl.java:73)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getAllUsernames(LDAPClientImpl.java:25)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers(LDAPUserManagerImpl.java:80)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPIdentityManagerImpl.(LDAPIdentityManagerImpl.java:41)
>     [junit] 	at org.wyona.security.test.LDAPIdentityManagerImplTest.setUp(LDAPIdentityManagerImplTest.java:32)
>     [junit] 	at junit.framework.TestCase.runBare(TestCase.java:125)
>     [junit] 	at junit.framework.TestResult$1.protect(TestResult.java:106)
>     [junit] 	at junit.framework.TestResult.runProtected(TestResult.java:124)
>     [junit] 	at junit.framework.TestResult.run(TestResult.java:109)
>     [junit] 	at junit.framework.TestCase.run(TestCase.java:118)
>     [junit] 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
>     [junit] 	at junit.framework.TestSuite.run(TestSuite.java:203)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911)
>     [junit] 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768)
>     [junit] Caused by: java.net.ConnectException: Connection timed out
>     [junit] 	at java.net.PlainSocketImpl.socketConnect(Native Method)
>     [junit] 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>     [junit] 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>     [junit] 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>     [junit] 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>     [junit] 	at java.net.Socket.connect(Socket.java:525)
>     [junit] 	at java.net.Socket.connect(Socket.java:475)
>     [junit] 	at java.net.Socket.(Socket.java:372)
>     [junit] 	at java.net.Socket.(Socket.java:186)
>     [junit] 	at com.sun.jndi.ldap.Connection.createSocket(Connection.java:352)
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:187)
>     [junit] 	... 27 more
>     [junit] ------------- ---------------- ---------------
>     [junit] 
>     [junit] Testcase: testGetAllUsersFromCache took 189.739 sec
>     [junit] 	Caused an ERROR
>     [junit] 192.168.200.109:389
>     [junit] org.wyona.security.core.api.AccessManagementException: 192.168.200.109:389
>     [junit] 	at org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers(LDAPUserManagerImpl.java:90)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPIdentityManagerImpl.(LDAPIdentityManagerImpl.java:41)
>     [junit] 	at org.wyona.security.test.LDAPIdentityManagerImplTest.setUp(LDAPIdentityManagerImplTest.java:32)
>     [junit] Caused by: javax.naming.CommunicationException: 192.168.200.109:389 [Root exception is java.net.ConnectException: Connection timed out]
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:210)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
>     [junit] 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
>     [junit] 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
>     [junit] 	at javax.naming.InitialContext.init(InitialContext.java:223)
>     [junit] 	at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getInitialLdapContext(LDAPClientImpl.java:73)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getAllUsernames(LDAPClientImpl.java:25)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers(LDAPUserManagerImpl.java:80)
>     [junit] Caused by: java.net.ConnectException: Connection timed out
>     [junit] 	at java.net.PlainSocketImpl.socketConnect(Native Method)
>     [junit] 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>     [junit] 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>     [junit] 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>     [junit] 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>     [junit] 	at java.net.Socket.connect(Socket.java:525)
>     [junit] 	at java.net.Socket.connect(Socket.java:475)
>     [junit] 	at java.net.Socket.(Socket.java:372)
>     [junit] 	at java.net.Socket.(Socket.java:186)
>     [junit] 	at com.sun.jndi.ldap.Connection.createSocket(Connection.java:352)
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:187)
>     [junit] 
>     [junit] Testcase: testGetAllUsersFromLDAP took 189.166 sec
>     [junit] 	Caused an ERROR
>     [junit] 192.168.200.109:389
>     [junit] org.wyona.security.core.api.AccessManagementException: 192.168.200.109:389
>     [junit] 	at org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers(LDAPUserManagerImpl.java:90)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPIdentityManagerImpl.(LDAPIdentityManagerImpl.java:41)
>     [junit] 	at org.wyona.security.test.LDAPIdentityManagerImplTest.setUp(LDAPIdentityManagerImplTest.java:32)
>     [junit] Caused by: javax.naming.CommunicationException: 192.168.200.109:389 [Root exception is java.net.ConnectException: Connection timed out]
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:210)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)
>     [junit] 	at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
>     [junit] 	at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
>     [junit] 	at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
>     [junit] 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
>     [junit] 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
>     [junit] 	at javax.naming.InitialContext.init(InitialContext.java:223)
>     [junit] 	at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getInitialLdapContext(LDAPClientImpl.java:73)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPClientImpl.getAllUsernames(LDAPClientImpl.java:25)
>     [junit] 	at org.wyona.security.impl.ldap.LDAPUserManagerImpl.getUsers(LDAPUserManagerImpl.java:80)
>     [junit] Caused by: java.net.ConnectException: Connection timed out
>     [junit] 	at java.net.PlainSocketImpl.socketConnect(Native Method)
>     [junit] 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>     [junit] 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>     [junit] 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>     [junit] 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>     [junit] 	at java.net.Socket.connect(Socket.java:525)
>     [junit] 	at java.net.Socket.connect(Socket.java:475)
>     [junit] 	at java.net.Socket.(Socket.java:372)
>     [junit] 	at java.net.Socket.(Socket.java:186)
>     [junit] 	at com.sun.jndi.ldap.Connection.createSocket(Connection.java:352)
>     [junit] 	at com.sun.jndi.ldap.Connection.(Connection.java:187)
>     [junit] 
>     [junit] Test org.wyona.security.test.LDAPIdentityManagerImplTest FAILED
>     [junit] Running org.wyona.security.test.PolicyManagerImplTest
>     [junit] Testsuite: org.wyona.security.test.PolicyManagerImplTest
>     [junit] 0    2010-03-30 15:48:23,398 [main] WARN  org.wyona.yarep.core.RepositoryFactory.():47  - No such resource: yarep.properties
>     [junit] 85   2010-03-30 15:48:23,483 [main] WARN  org.wyona.yarep.impl.repo.vfs.VirtualFileSystemRepository.readConfiguration():180  - Use deprecated configuration version 1.0!
>     [junit] 94   2010-03-30 15:48:23,492 [main] WARN  org.wyona.yarep.impl.search.lucene.LuceneConfig.configure():111  - No search index dir () configured within: http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository-policies-version2 
>     [junit] 99   2010-03-30 15:48:23,497 [main] WARN  org.wyona.yarep.impl.search.lucene.LuceneConfig.configure():111  - No search index dir () configured within: http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository-policies-version2 
>     [junit] 117  2010-03-30 15:48:23,515 [main] WARN  org.wyona.yarep.core.RepositoryFactory.():47  - No such resource: yarep.properties
>     [junit] 125  2010-03-30 15:48:23,523 [main] WARN  org.wyona.yarep.impl.repo.vfs.VirtualFileSystemRepository.readConfiguration():180  - Use deprecated configuration version 1.0!
>     [junit] 126  2010-03-30 15:48:23,524 [main] WARN  org.wyona.yarep.impl.search.lucene.LuceneConfig.configure():111  - No search index dir () configured within: http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository-policies-version2 
>     [junit] 127  2010-03-30 15:48:23,525 [main] WARN  org.wyona.yarep.impl.search.lucene.LuceneConfig.configure():111  - No search index dir () configured within: http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository-policies-version2 
>     [junit] 129  2010-03-30 15:48:23,527 [main] WARN  org.wyona.yarep.core.RepositoryFactory.():47  - No such resource: yarep.properties
>     [junit] 134  2010-03-30 15:48:23,532 [main] WARN  org.wyona.yarep.core.RepositoryFactory.newRepository():191  - No implementation class specified within 'http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository2/repository.xml'  and hence 'org.wyona.yarep.impl.DefaultRepository' will be used!
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.563 sec
>     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.563 sec
>     [junit] ------------- Standard Output ---------------
>     [junit] 0    2010-03-30 15:48:23,398 [main] WARN  org.wyona.yarep.core.RepositoryFactory.():47  - No such resource: yarep.properties
>     [junit] 85   2010-03-30 15:48:23,483 [main] WARN  org.wyona.yarep.impl.repo.vfs.VirtualFileSystemRepository.readConfiguration():180  - Use deprecated configuration version 1.0!
>     [junit] 94   2010-03-30 15:48:23,492 [main] WARN  org.wyona.yarep.impl.search.lucene.LuceneConfig.configure():111  - No search index dir () configured within: http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository-policies-version2 
>     [junit] 99   2010-03-30 15:48:23,497 [main] WARN  org.wyona.yarep.impl.search.lucene.LuceneConfig.configure():111  - No search index dir () configured within: http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository-policies-version2 
>     [junit] 117  2010-03-30 15:48:23,515 [main] WARN  org.wyona.yarep.core.RepositoryFactory.():47  - No such resource: yarep.properties
>     [junit] 125  2010-03-30 15:48:23,523 [main] WARN  org.wyona.yarep.impl.repo.vfs.VirtualFileSystemRepository.readConfiguration():180  - Use deprecated configuration version 1.0!
>     [junit] 126  2010-03-30 15:48:23,524 [main] WARN  org.wyona.yarep.impl.search.lucene.LuceneConfig.configure():111  - No search index dir () configured within: http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository-policies-version2 
>     [junit] 127  2010-03-30 15:48:23,525 [main] WARN  org.wyona.yarep.impl.search.lucene.LuceneConfig.configure():111  - No search index dir () configured within: http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository-policies-version2 
>     [junit] 129  2010-03-30 15:48:23,527 [main] WARN  org.wyona.yarep.core.RepositoryFactory.():47  - No such resource: yarep.properties
>     [junit] 134  2010-03-30 15:48:23,532 [main] WARN  org.wyona.yarep.core.RepositoryFactory.newRepository():191  - No implementation class specified within 'http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build/repository/repository2/repository.xml'  and hence 'org.wyona.yarep.impl.DefaultRepository' will be used!
>     [junit] ------------- ---------------- ---------------
>     [junit] 
>     [junit] Testcase: testAuthorization took 0.261 sec
>
> BUILD FAILED
> http://195.226.6.72:8080/job/security-trunk/ws/security-trunk.working-copy/build.xml :299: One or more junit tests failed. Please check the log (build/log).
>
> Total time: 6 minutes 28 seconds
> Recording test results
> No test report files were found. Configuration error?
>
>   

From bugzilla at wyona.com  Wed Mar 31 09:43:10 2010
From: bugzilla at wyona.com (bugzilla@wyona.com)
Date: Wed Mar 31 09:43:12 2010
Subject: [Yanel-dev] [Bug 7541] target for debugging in Yanel build system
Message-ID: <20100331074310.5F92410CAA3@server1.example.com>

http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7541


michael.wechner@wyona.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|mehmet.birgi@wyona.com      |michael.wechner@wyona.org




-- 
Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
From guillaume.deflache at wyona.com  Wed Mar 31 10:05:45 2010
From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=)
Date: Wed Mar 31 10:22:11 2010
Subject: [Yanel-dev] running Canoo tests independently
In-Reply-To: <5bf1397d1003290255i727799f6n32ba484bed6e26a5@mail.gmail.com>
References: <4BAD0316.70706@wyona.com> <4BAD32AA.6060401@wyona.com>
	<5bf1397d1003290255i727799f6n32ba484bed6e26a5@mail.gmail.com>
Message-ID: <4BB30259.7090009@wyona.com>

Hi!

Mehmet Birgi schrieb:
> Another (maybe less expensive) approach would be to group interdependent 
> tests together. I have just done this for testing a part of an 
> application for a customer project. I had to test creation, editing and 
> deletion of a part of a website. The cleanest way to do this is 
> obviously to create a test page first, then edit it, and then delete it, 
> so that no "debris" is left over (except automatically created meta 
> data, of course). These tests have to be executed in that order, or else 

This "automatically created meta data" should in principle also be 
deleted by the page deletion (except maybe harmless empty directory 
metadata) I think.


> they will fail. What I did is basically:
> 
> 1. write a separate test-XX.xml file for each test
> 
> 2. write a file test-all-XXs.xml file, that calls those files as ant targets
> 
> 3. integrate the test-all-XXs.xml in the test suite, and provide a 
> target "test-XXs" to execute that test package.
> 
> In this case, each of these tests can't be executed independently, but 
> at least they can be executed as a package separate from the rest.

It's not clear to me if the test-XX.xml files remain at the end, or if 
you just integrated them into this one single test-all-XXs.xml file.
Because, as running them independently probably won't work well unless 
you know well what you are doing and which steps you already have run, 
it would maybe be better if they were not too visible, e.g. defined as 
Ant 'target' elements without 'description' attribute so that they do 
not show up on `ant -projecthelp`/`build -p`.

Otherwise looks like a very fine approach to me, maybe you can point me 
privately to the customer tests you are talking about, or even better 
next time we add interdependent tests to Yanel we should try to use your 
approach.


Cheers,
    Guillaume
From guillaume.deflache at wyona.com  Wed Mar 31 10:26:23 2010
From: guillaume.deflache at wyona.com (=?ISO-8859-1?Q?Guillaume_D=E9flache?=)
Date: Wed Mar 31 10:39:33 2010
Subject: [Yanel-dev] Re: [Dev] Maven repo dupes
In-Reply-To: 
References: 
Message-ID: <4BB3072F.40207@wyona.com>

[This message just came on one internal Wyona mailing-lists, answering 
it here as it is of general interest: ]

Mehmet Birgi schrieb:
 > Yesterday, while we were looking for the jakarta-commons-io lib to 
use, Guillaume noticed that this library is included twice, namely in:
 >
 > 
/Users/memo/.m2/repository/apache-jakarta-commons/apache-jakarta-commons-io/1.2/apache-jakarta-commons-io-1.2.jar
 > /Users/memo/.m2/repository/commons-io/commons-io/1.2/commons-io-1.2.jar

I previously found a statement in the jakarta-commons mailing-list about 
what is the now recommended form (I do not really remember which one so 
I won't risk a guess) and a rationale for it, I'll try to dig it up at home.


 > As they are both the same version, one of them should be enough. 
There may be other dupes, we didn't search for them. The bug 
http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7006 also 
seems to be remotely related to this. Would it be worth the effort to

It is indeed related to this. The cleanup explained below is made as 
part of http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=6896


 > try to clean out the maven repository? Or should I just enter a new P2

To sum it up is not really our or Maven's central repositories that are 
"dirty", it's rather the dependencies metadata that do not cater for 
renames of the groupId/artifactId couples during the life of a library.
Cleaning that would probably remove all "duplicate librairies", but it 
is a long term task and not a very high priority ATM I think.


 > bug and "forget about it" for now?

No need to enter another bug.
You can forget about it for now as an application developer as the only 
real way to try to fix this is to clean up the dependency tree starting 
from its "leaves".
For now only wyona-commons has been cleaned up (see r45585 on 
), next target up the tree is yarep.
I had already started on that so please coordinate with us on this list 
if you want to work on that.


HTH,
    Guillaume
From michael.wechner at wyona.com  Wed Mar 31 11:03:40 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Wed Mar 31 11:17:51 2010
Subject: [Yanel-dev] running Canoo tests independently
In-Reply-To: <4BB30819.6010705@immerda.ch>
References: <4BAD0316.70706@wyona.com>
	<4BAD32AA.6060401@wyona.com>	<5bf1397d1003290255i727799f6n32ba484bed6e26a5@mail.gmail.com>
	<4BB30259.7090009@wyona.com> <4BB30819.6010705@immerda.ch>
Message-ID: <4BB30FEC.50404@wyona.com>

kamerun@immerda.ch wrote:
>
> Good day sir,
>     wyona group Cameroon. we have written close to two mails to you 
> but we hasn't  see any reply,

I have replied to all emails (for example just last night I have sent 
another reply, did you receive that?)

I have noticed that the email address lug.limbe@gmail.com is not 
subscribed on the yanel-development mailing list

Cheers

Michael
> so we don't know what is the problem.
>                           yanel test group Limbe (Cameroon)

From michael.wechner at wyona.com  Wed Mar 31 11:05:47 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Wed Mar 31 11:19:03 2010
Subject: [Yanel-dev] running Canoo tests independently
In-Reply-To: <4BB30FEC.50404@wyona.com>
References: <4BAD0316.70706@wyona.com>	<4BAD32AA.6060401@wyona.com>	<5bf1397d1003290255i727799f6n32ba484bed6e26a5@mail.gmail.com>	<4BB30259.7090009@wyona.com>
	<4BB30819.6010705@immerda.ch> <4BB30FEC.50404@wyona.com>
Message-ID: <4BB3106B.8010400@wyona.com>

Michael Wechner wrote:
> kamerun@immerda.ch wrote:
>>
>> Good day sir,
>>     wyona group Cameroon. we have written close to two mails to you 
>> but we hasn't  see any reply,
>
> I have replied to all emails (for example just last night I have sent 
> another reply, did you receive that?)
>
> I have noticed that the email address lug.limbe@gmail.com is not 
> subscribed on the yanel-development mailing list

I have added lug.limbe@gmail.com to this mailing list.

Cheers

Michael
>
> Cheers
>
> Michael
>> so we don't know what is the problem.
>>                           yanel test group Limbe (Cameroon)
>

From mehmet.birgi at wyona.com  Wed Mar 31 14:28:01 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Wed Mar 31 14:41:15 2010
Subject: [Yanel-dev] Re: [Dev] Maven repo dupes
In-Reply-To: <4BB3072F.40207@wyona.com>
References: 
	<4BB3072F.40207@wyona.com>
Message-ID: 

Thanks for all the feedback. As this is low priority, I might get back to it
later, but I will not pursue this issue at the moment.

Cheers,

Memo



2010/3/31 Guillaume D=E9flache 

> [This message just came on one internal Wyona mailing-lists, answering it
> here as it is of general interest: ]
>
> Mehmet Birgi schrieb:
>
> > Yesterday, while we were looking for the jakarta-commons-io lib to use,
> Guillaume noticed that this library is included twice, namely in:
> >
> >
> /Users/memo/.m2/repository/apache-jakarta-commons/apache-jakarta-commons-=
io/1.2/apache-jakarta-commons-io-1.2.jar
> > /Users/memo/.m2/repository/commons-io/commons-io/1.2/commons-io-1.2.jar
>
> I previously found a statement in the jakarta-commons mailing-list about
> what is the now recommended form (I do not really remember which one so I
> won't risk a guess) and a rationale for it, I'll try to dig it up at home.
>
>
>
> > As they are both the same version, one of them should be enough. There
> may be other dupes, we didn't search for them. The bug
> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=3D7006 also se=
ems
> to be remotely related to this. Would it be worth the effort to
>
> It is indeed related to this. The cleanup explained below is made as part
> of http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=3D6896
>
>
>
> > try to clean out the maven repository? Or should I just enter a new P2
>
> To sum it up is not really our or Maven's central repositories that are
> "dirty", it's rather the dependencies metadata that do not cater for rena=
mes
> of the groupId/artifactId couples during the life of a library.
> Cleaning that would probably remove all "duplicate librairies", but it is=
 a
> long term task and not a very high priority ATM I think.
>
>
>
> > bug and "forget about it" for now?
>
> No need to enter another bug.
> You can forget about it for now as an application developer as the only
> real way to try to fix this is to clean up the dependency tree starting f=
rom
> its "leaves".
> For now only wyona-commons has been cleaned up (see r45585 on <
> http://svn.wyona.com/repos/public/>), next target up the tree is yarep.
> I had already started on that so please coordinate with us on this list if
> you want to work on that.
>
>
> HTH,
>   Guillaume
> --
> Yanel-development mailing list Yanel-development@wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>



-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010033=
1/fb391cc2/attachment.htm
From michael.wechner at wyona.com  Wed Mar 31 14:51:13 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Wed Mar 31 15:04:26 2010
Subject: [Yanel-dev] Re: [Dev] Maven repo dupes
In-Reply-To: 
References: 	<4BB3072F.40207@wyona.com>
	
Message-ID: <4BB34541.6020405@wyona.com>

Mehmet Birgi wrote:
> Thanks for all the feedback. As this is low priority, I might get back 
> to it later, but I will not pursue this issue at the moment.

I would like you to spend 15 minutes on this. Please give the debugging 
approach as I suggested a try and also please
add a bugzilla entry, because these ambiguities can lead to problems and 
hence we better get it documented it at least.

Thanks

Michi
>
> Cheers,
>
> Memo
>
>
>
> 2010/3/31 Guillaume D?flache  >
>
>     [This message just came on one internal Wyona mailing-lists,
>     answering it here as it is of general interest: ]
>
>     Mehmet Birgi schrieb:
>
>     > Yesterday, while we were looking for the jakarta-commons-io lib
>     to use, Guillaume noticed that this library is included twice,
>     namely in:
>     >
>     >
>     /Users/memo/.m2/repository/apache-jakarta-commons/apache-jakarta-commons-io/1.2/apache-jakarta-commons-io-1.2.jar
>     >
>     /Users/memo/.m2/repository/commons-io/commons-io/1.2/commons-io-1.2.jar
>
>     I previously found a statement in the jakarta-commons mailing-list
>     about what is the now recommended form (I do not really remember
>     which one so I won't risk a guess) and a rationale for it, I'll
>     try to dig it up at home.
>
>
>
>     > As they are both the same version, one of them should be enough.
>     There may be other dupes, we didn't search for them. The bug
>     http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7006
>     also seems to be remotely related to this. Would it be worth the
>     effort to
>
>     It is indeed related to this. The cleanup explained below is made
>     as part of
>     http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=6896
>
>
>
>     > try to clean out the maven repository? Or should I just enter a
>     new P2
>
>     To sum it up is not really our or Maven's central repositories
>     that are "dirty", it's rather the dependencies metadata that do
>     not cater for renames of the groupId/artifactId couples during the
>     life of a library.
>     Cleaning that would probably remove all "duplicate librairies",
>     but it is a long term task and not a very high priority ATM I think.
>
>
>
>     > bug and "forget about it" for now?
>
>     No need to enter another bug.
>     You can forget about it for now as an application developer as the
>     only real way to try to fix this is to clean up the dependency
>     tree starting from its "leaves".
>     For now only wyona-commons has been cleaned up (see r45585 on
>     ), next target up the tree is
>     yarep.
>     I had already started on that so please coordinate with us on this
>     list if you want to work on that.
>
>
>     HTH,
>       Guillaume
>     -- 
>     Yanel-development mailing list Yanel-development@wyona.com
>     
>     http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
>
>
>
> -- 
> Mehmet Birgi
> www.wyona.com 
>

From mehmet.birgi at wyona.com  Wed Mar 31 16:23:52 2010
From: mehmet.birgi at wyona.com (Mehmet Birgi)
Date: Wed Mar 31 16:37:53 2010
Subject: [Yanel-dev] Re: [Dev] Maven repo dupes
In-Reply-To: <4BB34541.6020405@wyona.com>
References: 
	<4BB3072F.40207@wyona.com>
	
	<4BB34541.6020405@wyona.com>
Message-ID: 

ok, i'll have a look at it tomorrow


On Wed, Mar 31, 2010 at 2:51 PM, Michael Wechner
wrote:

> Mehmet Birgi wrote:
>
>> Thanks for all the feedback. As this is low priority, I might get back to
>> it later, but I will not pursue this issue at the moment.
>>
>
> I would like you to spend 15 minutes on this. Please give the debugging
> approach as I suggested a try and also please
> add a bugzilla entry, because these ambiguities can lead to problems and
> hence we better get it documented it at least.
>
> Thanks
>
> Michi
>
>>
>> Cheers,
>>
>> Memo
>>
>>
>>
>> 2010/3/31 Guillaume D=E9flache > guillaume.deflache@wyona.com>>
>>
>>
>>    [This message just came on one internal Wyona mailing-lists,
>>    answering it here as it is of general interest: ]
>>
>>    Mehmet Birgi schrieb:
>>
>>    > Yesterday, while we were looking for the jakarta-commons-io lib
>>    to use, Guillaume noticed that this library is included twice,
>>    namely in:
>>    >
>>    >
>>
>>  /Users/memo/.m2/repository/apache-jakarta-commons/apache-jakarta-common=
s-io/1.2/apache-jakarta-commons-io-1.2.jar
>>    >
>>    /Users/memo/.m2/repository/commons-io/commons-io/1.2/commons-io-1.2.j=
ar
>>
>>    I previously found a statement in the jakarta-commons mailing-list
>>    about what is the now recommended form (I do not really remember
>>    which one so I won't risk a guess) and a rationale for it, I'll
>>    try to dig it up at home.
>>
>>
>>
>>    > As they are both the same version, one of them should be enough.
>>    There may be other dupes, we didn't search for them. The bug
>>    http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=3D7006
>>    also seems to be remotely related to this. Would it be worth the
>>    effort to
>>
>>    It is indeed related to this. The cleanup explained below is made
>>    as part of
>>    http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=3D6896
>>
>>
>>
>>    > try to clean out the maven repository? Or should I just enter a
>>    new P2
>>
>>    To sum it up is not really our or Maven's central repositories
>>    that are "dirty", it's rather the dependencies metadata that do
>>    not cater for renames of the groupId/artifactId couples during the
>>    life of a library.
>>    Cleaning that would probably remove all "duplicate librairies",
>>    but it is a long term task and not a very high priority ATM I think.
>>
>>
>>
>>    > bug and "forget about it" for now?
>>
>>    No need to enter another bug.
>>    You can forget about it for now as an application developer as the
>>    only real way to try to fix this is to clean up the dependency
>>    tree starting from its "leaves".
>>    For now only wyona-commons has been cleaned up (see r45585 on
>>    ), next target up the tree is
>>    yarep.
>>    I had already started on that so please coordinate with us on this
>>    list if you want to work on that.
>>
>>
>>    HTH,
>>      Guillaume
>>    --     Yanel-development mailing list Yanel-development@wyona.com
>>    
>>
>>    http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>
>>
>>
>>
>> --
>> Mehmet Birgi
>> www.wyona.com 
>>
>>
> --
> Yanel-development mailing list Yanel-development@wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>



-- =

Mehmet Birgi
www.wyona.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010033=
1/ea9dfc6d/attachment.htm
From michael.wechner at wyona.com  Wed Mar 31 20:59:08 2010
From: michael.wechner at wyona.com (Michael Wechner)
Date: Wed Mar 31 21:15:01 2010
Subject: [Yanel-dev] Generic LDAP implementation
Message-ID: <4BB39B7C.9060809@wyona.com>

Hi

I have started a generic LDAP implementation, see for example

src/realms/from-scratch-realm-template/realm.xml 

 
    
      config/ac-identities-repository.xml
      
org.wyona.security.impl.ldap.LDAPClientImpl
      ldap://192.168.200.109:389
      simple

    
  

whereas the custom LDAP access is hidden within the custom LDAP client 
implementation. This means in order to use
LDAP together with Yanel one needs to implement a LDAP client, but which 
is rather straightforward. In a second phase
I might develop a generic configurable LDAP client implementation.

Please let me know if you have any questions.

Cheers

Michi