Wiki source code of IRC Archive for channel #xwiki

Last modified by Vincent Massol on 2012/10/18 18:38

Show last authors
1 DSpair - (00:48): Quick question, I'm looking at the query guide, and I see how to write the query, but how do I iterate the results?
2 CalebJamesDeLisl - (00:51): It returns a list. You can use a for loop like: for (String name : results) {
3 DSpair - (00:52): OK, thanks!
4 DSpair - (00:55): OK, I tried to run my first query and I got "Failed to locate Script Service [query]"
5 DSpair - (00:55): Back to the docs.
6 CalebJamesDeLisl - (01:29): What was the command? Ping me when you have questions because I'm not always looking at irc.
7 lucaa left at 01:37 (Ping timeout: 240 seconds
8 abusenius left at 01:53 (Ping timeout: 260 seconds
9 DragosRusu left at 04:09 (*.net *.split
10 DragosRusu joined #xwiki at 04:10
11 DSpair left at 04:32 (Quit: Leaving
12 lucaa joined #xwiki at 05:31
13 SvenDowideit left at 05:47 (Ping timeout: 260 seconds
14 SvenDowideit joined #xwiki at 05:47
15 tmortagne joined #xwiki at 07:47
16 vmassol joined #xwiki at 07:53
17 sburjan joined #xwiki at 08:39
18 johan_ joined #xwiki at 08:40
19 silviar joined #xwiki at 08:48
20 johan_ is now known as nuvolari ([email protected]
21 nuvolari left at 08:50 (Changing host
22 nuvolari joined #xwiki at 08:50
23 Denis joined #xwiki at 09:01
24 silviar left at 09:08 (Read error: Connection reset by peer
25 kibahop joined #xwiki at 09:10
26 CalebJamesDeLisl - (09:13): I had a crazy idea, maybe all code should start out messy. If code starts out as one big method, then as it grows it gets broken off into other methods, then they become inner classes and finally the classes are promoted to .java files, no code ends up in production without multiple revisions and having been used, revised and used again.
27 CalebJamesDeLisl - (09:15): Code which has seen real use and been revised is less likely to have extension points which later on prove useless.
28 CalebJamesDeLisl - (09:17): Also if a coder doesn't think about extensibility and cleanliness until after the first prototype runs, the space of time between the eureka moment and running code is shorter.
29 vmassol - (09:20): I wouldn't like that…. :)
30 vmassol - (09:21): But
31 vmassol - (09:21): components are there to hide implementation details
32 vmassol - (09:21): and anything in the internal package is internal
33 vmassol - (09:21): so you're just talking about putting stuff internally first before exposing it
34 vmassol - (09:21): and this I agree
35 CalebJamesDeLisl - (09:22): I write a lot of messy code, it never leaves my computer.
36 vmassol - (09:22): it's surely safer to open apis on need basis rather than too early
37 vmassol - (09:22): CalebJamesDeLisl: you can commit it in the sandbox :)
38 vmassol - (09:22): if you want to see messy code look at xwiki-core
39 CalebJamesDeLisl - (09:22): I did :)
40 vmassol - (09:22): and look at how hard it is to maintain/evolve it
41 CalebJamesDeLisl - (09:23): Something I noticed in xwiki-core was there were extension points which were never used so it's clear that the developer _tried_ to do it right.
42 vmassol - (09:24): there are ad-hoc extensions points everywhere
43 vmassol - (09:24): with hacks over hacks
44 vmassol - (09:24): to provide extensibility
45 vmassol - (09:24): and to take care of all use cases
46 vmassol - (09:24): but *without* having done any refactoring
47 CalebJamesDeLisl - (09:24): I agree with you about apis, they are difficult to deal with.
48 vmassol - (09:24): as a consequence it's a big ball of mud
49 CalebJamesDeLisl - (09:24): Yes, refactoring is key.
50 vmassol - (09:25): the key is the refactoring
51 vmassol - (09:25): yep
52 CalebJamesDeLisl - (09:25): I am partial to the concept of spiral development I guess.
53 vmassol - (09:25): I also like iterative dev
54 vmassol - (09:26): but I don't see it as the opposite of clean dev
55 CalebJamesDeLisl - (09:27): Well I see the problem with clean from the start development is that you don't know what you will need later so the developer tries to guess where extension points will be needed.
56 CalebJamesDeLisl - (09:28): My whole concept breaks down when multiple developers are working on the same piece of code (xwiki-core) because they are all afraid of breaking something.
57 CalebJamesDeLisl - (09:31): Something I find neat is how community development leads to modularity if for no other reason because nobody wants to break other people's code.
58 vmassol - (09:31): it's never clean from the start
59 vmassol - (09:31): but it can be thought out at a minimum level
60 vmassol - (09:31): you'll make mistakes anyway
61 vmassol - (09:32): but having cleaniness at heart will lead to better solution when you refactor the second time
62 vmassol - (09:32): and more importantly
63 vmassol - (09:32): it allows others to participate
64 CalebJamesDeLisl - (09:33): Others are pretty well locked out until the code has undergone a few iterations.
65 CalebJamesDeLisl - (09:33): (in my model)
66 sburjan - (09:39): hello vmassol
67 silviar joined #xwiki at 09:39
68 CalebJamesDeLisl - (09:49): Now that Dirtree has some semblance of stability, I'm doing stuff that I was putting off because it was a pain before. This is great. Now all I have to do is shorten the build time for XE.
69 jvdrean joined #xwiki at 09:49
70 vmassol - (09:58): CalebJamesDeLisl: once you have something stable and you're happy with it, you could send a mail explaining it to others and see where to take it from there, maybe?
71 vmassol - (09:59): got to disconnect for 1 mn, brb
72 vmassol left at 09:59 (Quit: Leaving.
73 vmassol joined #xwiki at 10:01
74 silviar - (10:02): Hi! I have an issue if someone has a bit of time to look at it. I've added an application icon to the new invitation page http://code.xwiki.org/xwiki/bin/view/Applications/InvitationApplication; The issue is the icon will not show up in the bundled applications list on the Enterprise Features page http://enterprise.xwiki.org/xwiki/bin/view/Main/Features
75 silviar - (10:02): I think this has something to do with the fact that the new app page is in 2.0 Syntax
76 silviar - (10:02): as opposed to the other pages which are still in 1.0
77 CalebJamesDeLisl - (10:03): Hmm. let me take a look. I wrote it.
78 CalebJamesDeLisl - (10:03): Nice icon.
79 silviar - (10:03): thanks
80 vmassol - (10:04): the image is missing the url for some reason
81 vmassol - (10:04): silviar: you have invitation.png
82 vmassol - (10:04): instead of the full url
83 vmassol - (10:04): let me check the other pages
84 vmassol - (10:05): yes that's why
85 vmassol - (10:05): you need a URL
86 vmassol - (10:05): I don't know if it's supported but it should be computed with velocity ideally
87 vmassol - (10:05): let me check if it works
88 CalebJamesDeLisl - (10:06): Ahh yes, when I wrote the 2.0 version I was making it "so easy" by appending the content to "attack:"
89 CalebJamesDeLisl - (10:06): s/attack:/attach:
90 silviar - (10:06): i've added the url, but the problem persists
91 silviar - (10:07): last time i fixed this by changing the page to 1.0 syntax for the annotations app page
92 vmassol - (10:07): silviar: nope
93 vmassol - (10:07): :)
94 vmassol - (10:07): it's fixed
95 vmassol - (10:07): it's just that this page has a cache
96 silviar - (10:07): ok :)
97 silviar - (10:07): so that was it
98 vmassol - (10:07): to refresh pages with a cache you need to suffix the url with ?refresh=1
99 silviar - (10:07): thanks
100 vmassol - (10:08): CalebJamesDeLisl: hmmm not much we can do to prevent having to put a full URL right now
101 vmassol - (10:08): since attach will only support absolute URL FTM
102 vmassol - (10:08): so using $xwiki.getDocument(…).getURL(…) will not work
103 CalebJamesDeLisl - (10:09): I think the fix is going to break the other page until someone changes the classSheet
104 vmassol - (10:09): silviar: don't change pages to 1.0 syntax!
105 vmassol - (10:10): we want the opposite :)
106 CalebJamesDeLisl - (10:10): Ok, I used "image:" so it still works with the full URL. Good.
107 silviar - (10:11): yes, i know :)
108 sburjan - (10:12): Does anybody have any Idea when the multilanguage problem will be fixed ? the one that shows all available languages even if the user enabled 3
109 CalebJamesDeLisl - (10:13): hah, I capitalize Idea too.
110 vmassol - (10:13): sburjan: nobody expressed interest so far in fixing this AFAIK
111 vmassol - (10:15): CalebJamesDeLisl: some failing tests for you: http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/com.xpn.xwiki.products$xwiki-enterprise-test-ui/990/testReport/
112 vmassol - (10:15): hmm sergiu hasn't fixed the object editor yet
113 vmassol - (10:15): :(
114 vmassol - (10:16): another day lost for the release
115 CalebJamesDeLisl - (10:16): That looks like the flicker we were talking about. Seems to be disrupting the state.
116 abusenius joined #xwiki at 10:16
117 tmortagne - (10:16): vmassol: yep i can't see him connected since he said he would fix them
118 CalebJamesDeLisl - (10:17): Maybe I can try to detect a page load.
119 CalebJamesDeLisl - (10:17): Broken fiber strikes at the worst moments...
120 vmassol - (10:18): broken fiber is better than no fiber at all! :)
121 CalebJamesDeLisl - (10:18): I don't have any fiber but I live in the woods and when a fiber breaks nobody reports it for a week.
122 CalebJamesDeLisl - (10:18): (the backhaul fiber for the town)
123 tmortagne - (10:19): vmassol: i reduced the validity test to only inline style related failures that will can't be easily fixed without some refactoring but are very minor so that would be ok for the release
124 vmassol - (10:20): tmortagne: ok, what's the plan after the release? We enable them again? We'll need to decide who fixes them
125 sburjan - (10:20): how can a fiber break ?
126 vmassol - (10:20): sburjan: put an elephant on it
127 vmassol - (10:20): :)
128 CalebJamesDeLisl - (10:21): or a tree branch. Or an incompetent backhoe operator.
129 tmortagne - (10:21): vmassol: i don't plan to disable them, they should be blocker for the RC
130 sburjan - (10:21): i know optic-fiber is buried
131 vmassol - (10:21): tmortagne: oh ok, I understood wrongly your message
132 CalebJamesDeLisl - (10:21): Not in my town, it runs along the phone lines.
133 sburjan - (10:22): i understand
134 tmortagne - (10:22): vmassol: i said it's ok to release a milestone with them because they are minor but i don't need to disable anything to release
135 CalebJamesDeLisl - (10:22): In my town you can't dig 6 inches without hitting a rock.
136 sburjan - (10:23): where do you live ?
137 tmortagne - (10:23): there is only one that will probably impossible to fix and that we will disable i guess: that's the incitation one that needs to be inline because of mails
138 CalebJamesDeLisl - (10:23): woods
139 sburjan - (10:28): vmassol : when you have 5 minutes to finish the yesterday's topic please tell me :)
140 vmassol - (10:29): sburjan: don't wait for me
141 vmassol - (10:29): just ask your questions
142 vmassol - (10:29): but don't ask them to me
143 vmassol - (10:29): ask them to the community
144 vmassol - (10:29): whoever is free and has the answer will answer
145 sburjan - (10:29): ok. i'll try to be as short as possible. This is a question for everybody anyway.
146 vmassol - (10:30): just to be clear, there's nobody in charge of xwiki.org
147 vmassol - (10:30): I'm not in charge for ex
148 sburjan - (10:30): We have some portion of documentation that aren;t accessible from nowhere. There are certain pages that only accessible if you know the URL, but from the interface they are inaccessible.
149 sburjan - (10:31): i know, but you're one of the few who actually respond to my dilemmas
150 sburjan - (10:31): *isn't
151 vmassol - (10:31): sure but I'd like others to answer too
152 sburjan - (10:31): me too
153 vmassol - (10:31): so if you ping me nobody else will answer
154 vmassol - (10:31): :)
155 sburjan - (10:31): :)
156 vmassol - (10:32): what page? can you give an ex?
157 sburjan - (10:32): now
158 sburjan - (10:32): http://code.xwiki.org/xwiki/bin/view/Applications/WatchlistApplication
159 sburjan - (10:32): go to : Viewing the elements in your watchlist
160 sburjan - (10:32): on the bottom
161 sburjan - (10:32): you'll see there a screenshot with Remove from watchlist
162 sburjan - (10:33): that screen isn;t accessible from nowhere, but only if you know the URL
163 vmassol - (10:33): I think that screenshot is old now
164 vmassol - (10:33): since the watchlist is now in the user's profile
165 vmassol - (10:33): no?
166 sburjan - (10:33): but the "interface" is still there
167 sburjan - (10:33): yes
168 tmortagne - (10:33): sburjan: are you sure ? wathlist is supposed to be accessible in user profile
169 sburjan - (10:33): it is accessible from user profile
170 sburjan - (10:34): but you can.t delete nothing from there
171 vmassol - (10:34): sburjan: the UI is different now so the image will need to be updated
172 sburjan - (10:34): onlyUNwatch
173 vmassol - (10:34): sburjan: indeed it's a bug
174 vmassol - (10:34): jvdrean: any idea?
175 vmassol - (10:34): (jvdrean is the one who did it)
176 sburjan - (10:34): it's not a bug.. we changed the UI in thea meantime.. but forgot to actually delete the old functionality
177 vmassol - (10:34): entering call now, bbl
178 sburjan - (10:34): okay
179 sburjan - (10:35): so as far as I see, nowdays we don't telede the watch on a space, page, wiki, we click on the unwatch button
180 tmortagne - (10:35): sburjan: something that should not be here is a bug ;)
181 sburjan - (10:35): and this oldscreen + still existingfunctionality has remained
182 sburjan - (10:39): I mean... it's like we have multiple UI's .. but only one of them is viewable, the others are like hidden easter eggs :)
183 sburjan - (10:40): the problem would be that is they will coexist .. maybe they could break functionality and become some sort of exploits
184 sburjan - (10:40): and can't be found when testing
185 tmortagne - (10:41): sburjan: again this does not looks like something done on purpose and everyone agree that it's bad to have old lost UIs duplicating new UIs
186 tmortagne - (10:43): sburjan: jvdrean is looking at it (can't answer right now)
187 jvdrean - (10:44): looking at it, indeed there's a page that should have been removed a while ago
188 vmassol left at 10:44 (Read error: Connection reset by peer
189 vmassol joined #xwiki at 10:44
190 jvdrean - (10:48): lucaa: looks like the annotations menu entry doesn't like the use of the watch entry next to it
191 lucaa - (10:48): hi jvdrean
192 lucaa - (10:49): it's the other way around :) watch menu is refreshing the whole menu when it's changed
193 sburjan - (10:49): okay, so I should issue a Major bug on JIRA ?
194 jvdrean - (10:49): is there a jira about this ?
195 jvdrean - (10:49): sburjan: I'll handle it
196 lucaa - (10:49): what bug are you referring?
197 sburjan - (10:49): okay jvdrean
198 vmassol1 joined #xwiki at 10:50
199 sburjan - (10:52): okay. so I have a go to remove the documentation that reffers to the lost UI ?
200 jvdrean - (10:53): sburjan: yes please, the 'Viewing the elements in your watchlist' paragraph must be removed
201 sburjan - (10:54): ps: this is present also on xwiki.org
202 vmassol left at 10:54 (Ping timeout: 276 seconds
203 vmassol joined #xwiki at 10:59
204 vmassol1 left at 11:01 (Ping timeout: 252 seconds
205 CalebJamesDeLisl - (11:05): So are there any opinions on whether the invitation app should be linked from other places and if so where?
206 CalebJamesDeLisl - (11:05): On the one hand, if it's not set up then linking it to the user pages or some place will confuse users when it doesn't work.
207 silviar - (11:06): jvdrean: I actually found the watchlist hidden page while fixing the notifications page on xwiki.org, otherwise we may not have noticed it; for the watch & annotations issue i filed this bug some time ago XAANNOTATIONS-9 ; feel free to move it to watchlist app if you think that's where it should go
208 CalebJamesDeLisl - (11:07): On the other hand, that's the way the watchlist app works and it's linked from the user pages even if it doesn't work.
209 vmassol left at 11:09 (Ping timeout: 258 seconds
210 jvdrean - (11:09): CalebJamesDeLisl: wdym?
211 CalebJamesDeLisl - (11:09): If no mail relay is set up, users can still access the watchlist.
212 CalebJamesDeLisl - (11:10): Asking is that how invitation should be (see post before Silvia's)
213 jvdrean - (11:10): (computer slow has hell, I didn't see your previous messages at first)
214 CalebJamesDeLisl - (11:12): I could put it in the user dropdown menu under profile, preferences, watchlist.
215 sburjan - (11:13): CalebJamesDeLisl, : have you separeted failed messages from the other ?
216 CalebJamesDeLisl - (11:13): Nah, getting there...
217 CalebJamesDeLisl - (11:14): Seems logical to separate accepted messages, and declined messages etc. So it will be a redesign of the page.
218 vmassol joined #xwiki at 11:15
219 florinciu joined #xwiki at 11:17
220 CalebJamesDeLisl - (11:22): How did saving ram in the velocity macros go? Were any changes made to the cache?
221 tmortagne - (11:29): CalebJamesDeLisl: vmassol fixed it, the change is that the cache is cleaned at the end of the page rendering process now
222 CalebJamesDeLisl - (11:30): So it doesn't clean when #includeForm is called?
223 abusenius left at 11:31 (Quit: Konversation terminated!
224 abusenius joined #xwiki at 11:31
225 tmortagne - (11:32): no
226 tmortagne - (11:32): (no it does not)
227 sburjan - (11:42): who created the ColorTheme App ?
228 sburjan - (11:43): I have a question. I am able to change the ColorTheme from the Administration Panel, but I can;t change the ColorTheme from AdministerSpace. The field isn't there anymore. Is this normal behaviour ?
229 sburjan - (11:45): I can change the skin for a space (eg. put Toucan) .. so I should be able to change ColorThemes in Colibri too
230 tmortagne - (11:47): sburjan: i think it's not supported at space level or something
231 sburjan - (11:47): so only skin change is supported at space level ?
232 sburjan - (11:48): okay
233 sburjan - (11:49): another issue is .. does XWiki support user level skin change ? I found a document that states this, but I am unable to do ti
234 tmortagne - (11:49): (not 100% sure, sdumitriu would know better)
235 sburjan - (11:49): *i
236 sburjan - (11:49): okay
237 tmortagne - (11:49): user level skin change is not supported no AFAIK
238 sburjan - (11:50): thanks. I'll correct the docs
239 tmortagne - (11:50): (but again not the expert, simply never heard of that)
240 kibahop left #xwiki at 12:10
241 CalebJamesDeLisl - (12:20): What can you do with XWQL that you can't to with hibernate?
242 tmortagne - (12:46): CalebJamesDeLisl: most important thing is that you write query supposedly independent from the storage
243 tmortagne - (12:47): now i doubt you can do things with XWQL impossible with hibernate, since the query is converted to hibernate query
244 CalebJamesDeLisl - (12:47): Been playing with it a little, I can write most of the hql language into the xwql parser so I'm not sure if that's a realistic expectation.
245 tmortagne - (12:47): CalebJamesDeLisl: artem tested XWQL with JCR
246 tmortagne - (12:48): which is completely different
247 CalebJamesDeLisl - (12:48): I would be +1 for it if there was a nice way to (for instance) get an object property value.
248 tmortagne - (12:48): CalebJamesDeLisl: i don't know XWQL very well but it's supposed to be easier to write than hql
249 tmortagne - (12:49): things you probably can't do with XWQL are join i guess
250 vmassol - (12:49): tmortagne: really?
251 CalebJamesDeLisl - (12:49): The problem with JCR testing is proving that you can't craft an xql query which will not work on jcr.
252 vmassol - (12:49): why not?
253 CalebJamesDeLisl - (12:50): No I just did a join.
254 vmassol - (12:50): XWQL is a superset of JPQL
255 vmassol - (12:50): so all JPQL stuffare supported
256 tmortagne - (12:50): vmassol: no idea, it's just that it's generally the last thing supported and i don't think JCR support that
257 vmassol - (12:50): it's not JCR
258 vmassol - (12:50): this is not JCR
259 tmortagne - (12:50): vmassol: i know
260 tmortagne - (12:50): it's not what i said
261 vmassol - (12:50): "things you probably can't do with XWQL are join i guess"
262 vmassol - (12:50): was just answerng to that
263 tmortagne - (12:50): there is an JCR based imprementation
264 tmortagne - (12:50): which is supposed to support XWQL
265 vmassol - (12:51): really?
266 vmassol - (12:51): I didn't know that
267 tmortagne - (12:51): yes and you did not understand what i said
268 tmortagne - (12:51): that was one of the main goal
269 tmortagne - (12:51): having a common language for several implementations
270 tmortagne - (12:52): now i don't know how far artem could go on JCR implementation
271 CalebJamesDeLisl - (12:52): What happens if users write queries (say for instance with joins) and then we switch to jcr and those queries break because fundamentally they are HQL?
272 tmortagne - (12:52): CalebJamesDeLisl: i'm not even sure it's not supported by JCR but i think i remember something about that
273 tmortagne - (12:53): but i gues if we have time and workforce for it in that case we would have to emulate
274 CalebJamesDeLisl - (12:54): I see no way of proving that every XWQL->HQL query will work with XWQL->JCR.
275 vmassol - (12:54): JCR has its own query API
276 vmassol - (12:54): and JCR implementation have to support some query languages
277 vmassol - (12:54): xpath, sql in jcr 2.0
278 vmassol - (12:55): now some JCR implementation should allow you to plug your own language implementation
279 vmassol - (12:55): but this remains to be seen
280 vmassol - (12:55): I couldn't find out how to do that easily with jackrabit for ex
281 mariusbutuc joined #xwiki at 12:55
282 vmassol - (12:55): (I didn't look too long though, was just looking for a way to replace the jackrabbit query engine with ours)
283 CalebJamesDeLisl - (12:56): Another complaint about XWQL is the error messages. "expecting from, id"
284 tmortagne - (12:57): AFAICS we only have XWQLtoHQLTranslator for now
285 CalebJamesDeLisl - (12:58): So it's not even proven that XWQL _can_ be translated to JCR.
286 tmortagne - (12:58): so no JCR support
287 tmortagne - (12:59): i think that's why i remember something about Artem waiting for JCR2
288 CalebJamesDeLisl - (12:59): I like the idea of an XWiki query manager.
289 CalebJamesDeLisl - (13:01): IMO the perfect query manager would take the place of hibernate or jcr and interface with jdbc.
290 vmassol - (13:01): CalebJamesDeLisl: you mean a XWIKI JCR query manager?
291 vmassol - (13:02): (because otherwise we already have a xwiki query manager)
292 CalebJamesDeLisl - (13:03): I am worried that jcr would not perform well. Everything in one table, sounds like bad news.
293 vmassol - (13:03): JCR doesn't say that.It depends on implementations
294 vmassol - (13:03): the pb with a xwiki jcr query manager is that the JCR specs doesn't say anything about plugging your own implementation
295 vmassol - (13:04): CalebJamesDeLisl: there are 2 differents things to understand
296 vmassol - (13:04): 1) using the JCR API
297 vmassol - (13:04): 2) using an existing JCR implementation
298 CalebJamesDeLisl - (13:04): What are the advantages of JCR?
299 vmassol - (13:04): your code is independent of the underlying storage and standard
300 vmassol - (13:04): standard = you can change the underlying engine
301 CalebJamesDeLisl - (13:05): Well actually it's dependent on JCR standard.
302 vmassol - (13:05): JCR is a standard and it's generic for any content app
303 tmortagne - (13:05): I guess that's the mail that made me remember something about JCR 2/query manager: http://markmail.org/message/o77ki3skmmpvpjgs
304 CalebJamesDeLisl - (13:06): And some vendors will add optional features which we must avoid in order to be compatable, just like SQL.
305 vmassol - (13:06): CalebJamesDeLisl: you really need to have a look at what JCR
306 vmassol - (13:06): provides
307 vmassol - (13:06): it's 100 times better than what we ahve
308 vmassol - (13:07): I started listed the advantages for us on the new model design page
309 vmassol - (13:07): and I'm only talking about standard jcr
310 vmassol - (13:07): not anything optional
311 CalebJamesDeLisl - (13:07): I read up on it a bit. The text was talking about the choice between jcr and subversion which is not very encouraging from a performance perspective.
312 vmassol - (13:07): JCR is like JDBC if you prefer
313 vmassol - (13:08): before JDBC you could still DB queries
314 vmassol - (13:08): s/Still/still do/
315 vmassol - (13:08): I think I put some links in the deisng page
316 CalebJamesDeLisl - (13:08): Without jdbc each db would need a different driver api correct?
317 vmassol - (13:09): yes
318 vmassol - (13:09): lunch time!
319 CalebJamesDeLisl - (13:09): coffee time.
320 venkatesh joined #xwiki at 13:12
321 lucaa left at 13:23 (Ping timeout: 265 seconds
322 mariusbutuc left at 13:27 (Read error: Connection reset by peer
323 vmassol - (13:31): still no sergiu….
324 vmassol - (13:37): guys seems there's a new version of selenium2
325 vmassol - (13:37): http://repo2.maven.org/maven2/org/seleniumhq/selenium/selenium/2.0a4/
326 vmassol - (13:38): I'm proposing to upgrade
327 vmassol - (13:38): ok?
328 tmortagne - (13:38): +1
329 vmassol - (13:38): I'll run some tests locally with it first
330 lucaa joined #xwiki at 13:45
331 vmassol - (13:45): I still get errors…. our tests are really bad I think since I always get lots of errors when I execute them locally
332 vmassol - (13:45): several are missing setting up preconditions
333 vmassol - (13:47): + even more important the flickering
334 vmassol - (13:48): I think this is not correct:
335 vmassol - (13:48): public void clickSaveAndContinue()
336 vmassol - (13:48): {
337 vmassol - (13:48): saveandcontinue.click();
338 vmassol - (13:48): }
339 vmassol - (13:48): we need to wait for the save to have been done I think
340 vmassol - (13:48): this is one causing flickering
341 vmassol - (13:48): I'll try to fix it
342 DSpair joined #xwiki at 13:54
343 DSpair - (13:54): Good morning all.
344 DSpair - (13:55): Quick question. I created a new class called "Circuit". I added several object of that class type to a document. I then added a livetable to that document and got the following message and only one row of results : The environment prevents the table to load data.
345 DSpair - (13:56): Wait one, I found a mailing list post about this error.
346 DSpair - (14:00): OK, I imported the updated version of LiveTable application and now I don't get an error, but I also don't get any data displayed.
347 vmassol - (14:13): js guys, any idea why the following doesn't work for save&continue:
348 vmassol - (14:13): waitUntilElementIsVisible(By.xpath("//div[@class='xnotification-done' and text()='Saved'"));
349 vmassol - (14:13): I also tried with:
350 vmassol - (14:13): waitUntilElementIsVisible(By.xpath("//div[@class='xnotification-done']"));
351 vmassol - (14:17): this one seems to work though:
352 vmassol - (14:17): waitUntilElementIsVisible(By.className("xnotification-done"));
353 CalebJamesDeLisl - (14:19): you can do that in an xpath?
354 vmassol - (14:19): CalebJamesDeLisl: what part?
355 CalebJamesDeLisl - (14:20): and text()... looks wrong
356 vmassol - (14:20): yes that one might not work
357 vmassol - (14:20): I wasn't sure of myself
358 vmassol - (14:20): but the other one should have worked
359 vmassol - (14:20): no?
360 vmassol - (14:20): unless it's not a div
361 vmassol - (14:20): but the js source seems to suggest it is
362 vmassol - (14:20): this.element = new Element("div", {"class" : "xnotification xnotification-" + this.type}).update(this.text);
363 CalebJamesDeLisl - (14:21): Also if it's multiple class names.
364 vmassol - (14:21): hmm right
365 CalebJamesDeLisl - (14:21): class="class1 class2"
366 vmassol - (14:21): that might be it
367 vmassol - (14:21): trying
368 vmassol - (14:22): indeed
369 vmassol - (14:22): waitUntilElementIsVisible(By.xpath("//div[contains(@class,'xnotification-done')]"));
370 vmassol - (14:22): works
371 CalebJamesDeLisl - (14:22): hmm, didn't know about that one.
372 vmassol - (14:22): btw
373 vmassol - (14:23): this works too now
374 vmassol - (14:23): waitUntilElementIsVisible(By.xpath("//div[contains(@class,'xnotification-done') and text()='Saved']"));
375 CalebJamesDeLisl - (14:23): Interesting. I must have missed the lower half of the xpath spec.
376 CalebJamesDeLisl - (14:25): I read your page about JCR. Versioning is very nice. Still no language integration of queries, unfortunately.
377 vmassol - (14:26): regarding xpath
378 vmassol - (14:26): I was told to avoid it as much as possible in selenium2
379 vmassol - (14:26): because the xpath engine on IE is awfully slow
380 vmassol - (14:26): at some point we might want to replace them with other chained By
381 CalebJamesDeLisl - (14:27): I have been avoiding xpath because it just seems like it would be slow. Are we planning IE testing?
382 vmassol - (14:27): re IE yes
383 CalebJamesDeLisl - (14:28): Good. Releasing with IE bugs was not cool.
384 vmassol - (14:28): CalebJamesDeLisl: is that what you mean: http://www.day.com/specs/jcr/2.0/6_Query.html ?
385 vmassol - (14:28): JCR-JQOM
386 CalebJamesDeLisl - (14:29): Query createQuery(java.lang.String statement, java.lang.String language)
387 CalebJamesDeLisl - (14:30): Same old query method = same old "select something where this = '" + sqlInjection + "'";
388 vmassol - (14:30): I don't read it this way
389 vmassol - (14:30): "JCR-JQOM (JCR Java Query Object Model), which expresses a query as a tree of Java objects."
390 vmassol - (14:32): ah here's an ex:
391 vmassol - (14:32): http://dev.day.com/discussion-groups/content/lists/cq-google/2010-03/2010-03-24__day_communique_CQ5_3_how_to_create_queries_with_JQOM_Thomas_Amsler.html/4?sort=date&q=jcr
392 vmassol - (14:33): hmm not very good ex
393 CalebJamesDeLisl - (14:35): This looks promising: http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/index.html
394 CalebJamesDeLisl - (14:36): No this http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/javax/jcr/query/qom/package-summary.html
395 vmassol - (14:36): yes
396 CalebJamesDeLisl - (14:37): I still want to see a real query. Linq is ok but not that intuitive.
397 CalebJamesDeLisl - (14:38): Seen more broken websites looking for this than in the past week.
398 vmassol - (14:41): ok 9 more false positives tests to fix….
399 vmassol - (14:41): CalebJamesDeLisl: are you fixing this one:
400 vmassol - (14:41): java.lang.AssertionError: LiveValidation did not show a failure message but clicking on the register button did.
401 vmassol - (14:41): ?
402 CalebJamesDeLisl - (14:41): I'm not sure what to do with that.
403 CalebJamesDeLisl - (14:42): Stop testing liveValidation?
404 vmassol - (14:42): make it work?
405 DSpair - (14:42): LOL
406 CalebJamesDeLisl - (14:42): return true; ;)
407 vmassol - (14:42): these are failing locally for me: http://tinycoke.com/_6rsuAVrtncELU/screen_shot_2010-06-24_at_2.41.55_pm.png
408 CalebJamesDeLisl - (14:43): I havn't seen that many fail on my machine.
409 CalebJamesDeLisl - (14:44): running...
410 vmassol - (14:44): I have a build from yesterday morning I think
411 DSpair - (14:46): Wanted to let you know, in the next few days I will have completed my new application for XWiki. It's called InfrastructureBackup and it allows you to add a list of Cisco/HP/Nortel/etc... devices which it will then automatically log into via telnet/SSH and capture the running configuration and back it up as an attachment.
412 DSpair - (14:46): I'll submit it for public use to wherever you would like me to put it.
413 sburjan - (14:46): guys, who crafted the PhotoAlbum App ?
414 DSpair - (14:46): I should say "I'll have finished the first version"
415 florinciu - (14:47): sburjan: JV and Jerome I think
416 DSpair - (14:48): Right now it uses ExpectJ and calls to "exec()" to run local copies of ssh/telnet. The next version I will integrate Jsch for SSH and use sockets for Telnet.
417 CalebJamesDeLisl - (14:48): That's great! Applications go on code.xwiki.org
418 tmortagne - (14:50): CalebJamesDeLisl: you can close XAADMINISTRATION-140 since there is no XHTML validity issues in admin app anymore
419 CalebJamesDeLisl - (14:51): Yes, thanks for pointing that out. Should I assign you?
420 CalebJamesDeLisl - (14:52): Actually we all put some work into that one.
421 tmortagne - (14:52): CalebJamesDeLisl: your are the only one having done commit associated to this issue ;)
422 tmortagne - (14:52): assign to you
423 CalebJamesDeLisl - (14:52): Ok, credit I can take.
424 mariusbutuc joined #xwiki at 14:54
425 tmortagne - (14:56): CalebJamesDeLisl: same for http://jira.xwiki.org/jira/browse/XAADMINISTRATION-139
426 DSpair - (14:59): I just downloaded XEclipse and it won't run. Is the Linux version only good on 32bit?
427 CalebJamesDeLisl - (15:00): Hmm I still see a few failures.
428 tmortagne - (15:00): CalebJamesDeLisl: not on admin app
429 tmortagne - (15:00): let me re-check
430 tmortagne - (15:00): CalebJamesDeLisl: there is annotation, invitation and editors
431 tmortagne - (15:01): so nothing related to xwiki-application-administration project
432 CalebJamesDeLisl - (15:01): I see so that's because you changed the rules?
433 tmortagne - (15:02): what rules are you talking about ?
434 tmortagne - (15:02): i fixed lots of test (and remove PanelWyzard test) but i did not changed anything
435 CalebJamesDeLisl - (15:02): Ok.
436 tmortagne - (15:03): s/fixed lots of test/fixed lots of failure/
437 CalebJamesDeLisl - (15:06): Did you commit on any issue when you fixed the tests?
438 tmortagne - (15:07): CalebJamesDeLisl: was generally "[misc] Fix Dutch Web Guidelines validity issues" i was a bit lazy on that but i mostly fixed templates if i remember well, if i fixed admin app page it was a very few
439 tmortagne - (15:08): (and "[misc] Fix XHTML validity issues")
440 CalebJamesDeLisl - (15:08): Hmm, no commits on that issue and it's fixed.
441 tmortagne - (15:08): checking
442 tmortagne - (15:09): CalebJamesDeLisl: maybe you fixed them in some other committs
443 tmortagne - (15:10): i don't see any commit from me on admin app since the previous release
444 venkatesh left at 15:10 (Ping timeout: 260 seconds
445 CalebJamesDeLisl - (15:10): I guess I'll call it a dupe of the XHTML issue.
446 tmortagne - (15:11): yep maybe you fixed theses issue with the XHTML issues yes
447 tmortagne - (15:11): CalebJamesDeLisl: XAADMINISTRATION-149
448 tmortagne - (15:12): that was a XHTML issue too
449 tmortagne - (15:12): so you probably committed in theses one
450 CalebJamesDeLisl - (15:12): Ahh, thanks.
451 tmortagne - (15:12): anyway, if there was anything you fixed it ;)
452 KermitTheFragger joined #xwiki at 15:25
453 sburjan - (16:08): I get this warning in the console when running the latest snapshot
454 sburjan - (16:08): 2010-06-24 17:03:22,814 [http://localhost:8080/xwiki/bin/edit/UNREGISTEREDuserSPACE/WebHome?parent=&template=&title=UNREGISTEREDuserSPACE] WARN internal.DefaultVelocityEngine - Deprecated usage of getter [com.xpn.xwiki.api.Document.getSyntaxId] in /templates/macros.vm@2341,54
455 sburjan - (16:08): I only created a new space
456 vmassol - (16:08): sburjan: we're fixing those, this is a just a warning so don't worry
457 sburjan - (16:09): I;m worried about everything that looks a bit suspicious
458 vmassol - (16:09): sburjan: yes that's good
459 sburjan - (16:10): so these warns will be fixed in M2 ?
460 vmassol - (16:10): yes
461 sburjan - (16:10): okay
462 sburjan - (16:11): also I get A LOT of these when logging off/in
463 sburjan - (16:11): 2010-06-24 17:10:41.045::WARN: java.lang.IllegalArgumentException: Cookie name "XWiki.Admin_Panels.Recently Modified" is a reserved token
464 vmassol - (16:11): that one isn't normal
465 vmassol - (16:11): never seen it
466 sburjan - (16:12): these aren't logged in xwiki.log
467 sburjan - (16:12): they are spat directly in the terminal
468 vmassol - (16:13): whatever goes on the terminal also go in xwiki.log
469 vmassol - (16:14): (unless you've modified the default logging config but I doubt that)
470 vmassol - (16:14): ah maybe they're not coming from xwiki
471 sburjan - (16:14): oddly, these aren't in my xwiki.log . running latest snapshot, default all
472 vmassol - (16:14): in which case they'll go in other log files
473 vmassol - (16:15): hmm
474 vmassol - (16:15): another option is that whoever sends those don't use the xwiki log system
475 vmassol - (16:15): you don't have more details?
476 sburjan - (16:16): well .. in order to reproduce
477 sburjan - (16:16): I start either start_xwiki.sh or start_xwiki_debug.sh ...
478 sburjan - (16:17): click on Run In Terminal
479 sburjan - (16:17): so I get a terminal windows opened as long as xwikis erver is running
480 sburjan - (16:17): and this is the place where I get these
481 vmassol - (16:17): anyway that's not the issue
482 vmassol - (16:17): how do I reproduce?
483 sburjan - (16:18): how I said above
484 sburjan - (16:18): i get a few when logging in, a few when logging out
485 vmassol - (16:18): so you get those at startup even when you don't touch the xwiki app?
486 sburjan - (16:18): let me try
487 vmassol - (16:18): ahah
488 vmassol - (16:18): so you log in
489 vmassol - (16:18): you didn't say that before
490 sburjan - (16:18): i log in
491 vmassol - (16:19): can you verify?
492 vmassol - (16:19): that you get them all the time
493 sburjan - (16:19): when starting xwiki clean.. without touching nothing, not even a refresh I don't get it
494 vmassol - (16:19): I don't get why we're putting the name of a page in a cookie though
495 sburjan - (16:19): I get it when simply refreshing the page
496 sburjan - (16:20): again when hitting the log In button
497 sburjan - (16:20): again when hitting the Log out button
498 sburjan - (16:20): i have a clue why we do that
499 vmassol - (16:20): to redirect back to the page after logging?
500 sburjan - (16:21): because when you log off, i saw that xwiki has the tendency to leavy you on the same page you were on when you hit logoff, instead ofredirecting to the main page
501 sburjan - (16:21): yes
502 sburjan - (16:21): exactly
503 sburjan - (16:21): but i'm not a tech guy yet, so I don;t know what happens before
504 vmassol - (16:21): what servlet container are you using, jetty?
505 sburjan - (16:21): yes, standard jetty, latest snapshot take from mave.xwiki.org ...
506 sburjan - (16:21): *taken
507 sburjan - (16:22): these lines aren'tsaved in xwiki.log
508 sburjan - (16:22): i triple checked
509 sburjan - (16:23): what could I do more in order to help figure it out ?
510 vmassol - (16:23): nothing FTM
511 vmassol - (16:23): except report it
512 vmassol - (16:23): in jira
513 vmassol - (16:25): it's possible sergiu introduced the pb in rev 28709
514 sburjan - (16:25): wait till silviar confirms too
515 vmassol - (16:25): when fixing "XWIKI-5156: Session cookies are not marked as HttpOnly"
516 vmassol - (16:26): maybe response.addCookie was escaping chars
517 vmassol - (16:26): while the new method he's used odesn't
518 sburjan - (16:27): maybe my browser or cache or cookies have something
519 sburjan - (16:27): let me cleamall
520 sburjan - (16:30): it was my browser's cookies
521 sburjan - (16:30): something messed them up. I officially apologize
522 vmassol - (16:31): yes sergiu's code does use quoted string:
523 vmassol - (16:32):  cookieValue.append("\"" + cookie.getValue() + "\"");
524 vmassol - (16:32): so special chars hsould be ok
525 vmassol - (16:32): I still odn't understand how you could have such invalid cookies
526 sburjan - (16:32): i'm special :)
527 vmassol - (16:32): seems the pb is witht he cookie name, not the value....
528 sburjan - (16:32): I cleared all the cookies .. andnow it perfectly works
529 vmassol - (16:33): sure but that doesn't prove there isn't a pb
530 sburjan - (16:33): i used around 7 snapshots without clearing nothing in the browser
531 sburjan - (16:33): what's the expiration time of the cookie ?
532 sburjan - (16:34): well.. I'll try to reproduce that error .. maybe 2 different versions of xwiki using a cookie created by another version
533 mariusbutuc left #xwiki at 16:34
534 vmassol - (16:39): ok
535 vmassol - (16:39): I couldn't find a pb after a cursory look at the code
536 sburjan - (16:41): i'm failing to reproduce
537 sburjan - (16:41): (the problem)
538 evalica joined #xwiki at 16:41
539 tmortagne1 joined #xwiki at 16:46
540 tmortagne left at 16:46 (Read error: Connection reset by peer
541 sburjan left at 17:03 (Quit: Ex-Chat
542 jvdrean left at 17:18 (Quit: Leaving.
543 jvdrean joined #xwiki at 17:19
544 silviar left at 17:38 (Quit: Leaving.
545 KermitTheFragger left at 18:11 (Quit: Leaving
546 abusenius left at 18:34 (Ping timeout: 276 seconds
547 vmassol - (18:43): …. as your name suggests....
548 vmassol - (18:43): :)
549 vmassol - (18:43): (I hope it's not your real name :))
550 vmassol - (18:44): ah no it's not…. pfeww…. almost made a blunder
551 vmassol - (18:47): anyone good in threading here? I don't understand something…..
552 vmassol - (18:48): tmortagne1: you busy?
553 tmortagne1 - (18:48): vmassol: always :)
554 vmassol - (18:48): (I see you're doing your 20% time while waiting for sergiu to wake up…..)
555 tmortagne1 - (18:48): :)
556 tmortagne1 - (18:48): shoot
557 vmassol - (18:48): tmortagne1: in case you can spare a few minutes, you could connect on skype
558 vmassol - (18:48): might be easier
559 tmortagne1 - (18:48): sine i'm discovered
560 vmassol - (18:48): :)
561 tmortagne1 - (18:48): ha i'm not on skype ?
562 tmortagne1 - (18:49): indeed it crashed
563 abusenius joined #xwiki at 19:09
564 jvdrean left at 19:18 (Quit: Leaving.
565 lucaa left at 19:20 (Quit: Leaving.
566 vmassol1 joined #xwiki at 19:29
567 vmassol1 left at 19:29 (Client Quit
568 vmassol left at 19:29 (Read error: Connection reset by peer
569 vmassol joined #xwiki at 19:32
570 nickless joined #xwiki at 20:54
571 abusenius left at 20:55 (Ping timeout: 264 seconds
572 tmortagne1 left #xwiki at 20:56
573 nickless is now known as abusenius ([email protected]
574 DSpair - (21:05): Uhhhggg. . . AT&T had a card go bad in one of their backbone switches and it has taken down our entire North America WAN.... Our company is losing about $200k every 10 minutes right now.
575 nickless joined #xwiki at 21:08
576 abusenius left at 21:08 (Read error: Connection reset by peer
577 nickless left at 21:09 (Read error: Connection reset by peer
578 nickless joined #xwiki at 21:09
579 nickless is now known as abusenius ([email protected]
580 vmassol left at 22:20 (Quit: Leaving.
581 lucaa joined #xwiki at 22:30
582 npm left at 22:53 (Quit: Leaving.
583 npm joined #xwiki at 23:03
584 florinciu left at 23:09 (Read error: Connection reset by peer
585 evalica left at 23:59 (Quit: Leaving.

Get Connected