From ashley.moran at patchspace.co.uk  Thu Mar  5 10:33:11 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Thu, 5 Mar 2009 15:33:11 +0000
Subject: [Celerity-users] New version
Message-ID: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>

Hi

Any plans to release a new Celerity gem?  There's been a lot of good  
features since the last gem build and that was AGES ago!

Thanks
Ashley

-- 
http://www.patchspace.co.uk/
http://aviewfromafar.net/
http://twitter.com/ashleymoran




From ashley.moran at patchspace.co.uk  Thu Mar  5 10:54:32 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Thu, 5 Mar 2009 15:54:32 +0000
Subject: [Celerity-users] New version
In-Reply-To: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>
References: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>
Message-ID: <3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>

On 5 Mar 2009, at 15:33, Ashley Moran wrote:
> Any plans to release a new Celerity gem?  There's been a lot of good  
> features since the last gem build and that was AGES ago!

Hi Jari

Just noticed that your Github account is building more up to date  
gems, but they are not on RubyForge.  Do you plan to maintain the  
RubyForge gems or should we all be using Github now?

Ashley

-- 
http://www.patchspace.co.uk/
http://aviewfromafar.net/
http://twitter.com/ashleymoran




From joahking at gmail.com  Thu Mar  5 11:21:23 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Thu, 5 Mar 2009 17:21:23 +0100
Subject: [Celerity-users] New version
In-Reply-To: <8277b7f40903050812p1af2041fn627a192b3ea01a3e@mail.gmail.com>
References: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>
	<3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>
	<8277b7f40903050812p1af2041fn627a192b3ea01a3e@mail.gmail.com>
Message-ID: <8277b7f40903050821y10594973i37409facd53fc2f0@mail.gmail.com>

well I am actually noticing the browser differs between versions:

in 0.0.4:

$ b = Celerity::Browser.new :log_level => :all

=> #<Celerity::Browser:0xaa77d9
@webclient=#<Java::ComGargoylesoftwareHtmlunit::WebClient:0x1a271f5
@java_object=com.gargoylesoftware.htmlunit.WebClient at 1e7a755>, @page=nil,
@last_url=nil, @error_checkers=[], @viewer=nil,
@page_container=#<Celerity::Browser:0xaa77d9 ...>, @opts={:log_level=>:all}>

in jarib-celerity (0.0.5.8):

$ b = Celerity::Browser.new :log_level => :all

=> #<Celerity::Browser:0xe7eec9 @page=nil @charset="UTF-8" @last_url=nil
@error_checkers=[] @render_type=:html @viewer=Celerity::DefaultViewer>

any ideas?

thanks
joaquin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090305/2fdba87e/attachment.html>

From joahking at gmail.com  Thu Mar  5 11:12:00 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Thu, 5 Mar 2009 17:12:00 +0100
Subject: [Celerity-users] New version
In-Reply-To: <3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>
References: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>
	<3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>
Message-ID: <8277b7f40903050812p1af2041fn627a192b3ea01a3e@mail.gmail.com>

speaking about that,
something gets broken when I use the github gem (jarib-celerity-0.0.5.8)

NativeException: java.lang.IllegalAccessError: tried to access method
org.mozilla.javascript.Context.<init>(Lorg/mozilla/javascript/ContextFactory;)V
from class

the following works ok with 0.0.4:

$ jruby -v
jruby 1.1.6RC1 (ruby 1.8.6 patchlevel 114) (2009-02-23 rev 6586) [i386-java]

$ jirb
irb(main):001:0> require 'celerity'
=> true

irb(main):002:0> b = Celerity::Browser.new :log_level => :all

=> #<Celerity::Browser:0xe7eec9 @page=nil @charset="UTF-8" @last_url=nil
@error_checkers=[] @render_type=:html @viewer=Celerity::DefaultViewer>

irb(main):003:0> b.goto 'localhost:4000/flying_sites'

NativeException: java.lang.IllegalAccessError: tried to access method
org.mozilla.javascript.Context.<init>(Lorg/mozilla/javascript/ContextFactory;)V
from class
com.gargoylesoftware.htmlunit.javascript.HtmlUnitContextFactory$TimeoutContext
    from
com/gargoylesoftware/htmlunit/javascript/HtmlUnitContextFactory.java:116:in
`<init>'
    from
com/gargoylesoftware/htmlunit/javascript/HtmlUnitContextFactory.java:138:in
`makeContext'
    from org/mozilla/javascript/Context.java:401:in `enter'
    from org/mozilla/javascript/Context.java:497:in `call'
    from org/mozilla/javascript/ContextFactory.java:511:in `call'
    from
com/gargoylesoftware/htmlunit/javascript/JavaScriptEngine.java:137:in
`initialize'
    from com/gargoylesoftware/htmlunit/WebClient.java:1104:in `initialize'
    from com/gargoylesoftware/htmlunit/WebWindowImpl.java:97:in
`setEnclosedPage'
    from com/gargoylesoftware/htmlunit/html/HTMLParser.java:272:in `parse'
    from com/gargoylesoftware/htmlunit/DefaultPageCreator.java:127:in
`createHtmlPage'
    from com/gargoylesoftware/htmlunit/DefaultPageCreator.java:101:in
`createPage'
    from com/gargoylesoftware/htmlunit/WebClient.java:441:in
`loadWebResponseInto'
    from com/gargoylesoftware/htmlunit/WebClient.java:329:in `getPage'
    from com/gargoylesoftware/htmlunit/WebClient.java:402:in `getPage'
    from sun/reflect/NativeMethodAccessorImpl.java:-2:in `invoke0'
    from sun/reflect/NativeMethodAccessorImpl.java:57:in `invoke'
... 118 levels...
    from org/jruby/ast/BlockNode.java:68:in `interpret'
    from org/jruby/internal/runtime/methods/DefaultMethod.java:156:in
`interpretedCall'
    from org/jruby/internal/runtime/methods/DefaultMethod.java:133:in `call'
    from org/jruby/internal/runtime/methods/DefaultMethod.java:246:in `call'
    from org/jruby/runtime/callsite/CachingCallSite.java:280:in
`cacheAndCall'
    from org/jruby/runtime/callsite/CachingCallSite.java:116:in `call'
    from home/joahking/java/jruby_minus_1_dot_1_dot_6RC1/bin/jirb:19:in
`__file__'
    from home/joahking/java/jruby_minus_1_dot_1_dot_6RC1/bin/jirb:-1:in
`__file__'
    from home/joahking/java/jruby_minus_1_dot_1_dot_6RC1/bin/jirb:-1:in
`load'
    from org/jruby/Ruby.java:564:in `runScript'
    from org/jruby/Ruby.java:467:in `runNormally'
    from org/jruby/Ruby.java:340:in `runFromMain'
    from org/jruby/Main.java:214:in `run'
    from org/jruby/Main.java:100:in `run'
    from org/jruby/Main.java:84:in `main'

are you seeing this also, or is it just me?

cheers
joaquin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090305/44dd0c29/attachment-0001.html>

From joahking at gmail.com  Thu Mar  5 11:55:35 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Thu, 5 Mar 2009 17:55:35 +0100
Subject: [Celerity-users] which page should I end with after committing a
	form?
Message-ID: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>

hey there,
I have a form that after submit everything goes ok, only I end up with the
incorrect page. example:
> b = Celerity::Browser.new :log_level => :all
> b.goto "http://localhost:4000/world"
> b.text_field(:id, 'address').set('habana, cuba')
> p = b.button(:text, 'Search around').click
=> #<Java::ComGargoylesoftwareHtmlunitHtml::HtmlPage:0x6c2ea3
@java_object=HtmlPage(http://localhost:4000/world)@30552785>

the form submits to: /around, and looking at the test server log I see
everything was ok:
.......
Completed in 739ms (View: 586, DB: 25) | 200 OK [
http://localhost/around?lat=23.1333333&lng=-82.3666667&address=habana%2C+cuba]
(pid:14520)

but my browser instance and the returned page are the original one and not
the last one:
> b.url
=> "http://localhost:4000/world"
> p.inspect
=> "#<Java::ComGargoylesoftwareHtmlunitHtml::HtmlPage:0x6c2ea3
@java_object=HtmlPage(http://localhost:4000/world)@30552785>"

I am looking into celerity/lib/celerity/htmlunit.rb, also at HtmlUnit itself
(I will try the jirb example directly in java to see if it's a HtmlUnit
thing). I have no problem with contributing some code, but some help would
be great

any ideas? is this the expected behaviour?

thanks in advance
joaquin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090305/9d1276a0/attachment.html>

From jari.bakken at gmail.com  Thu Mar  5 14:44:22 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Thu, 5 Mar 2009 20:44:22 +0100
Subject: [Celerity-users] New version
In-Reply-To: <3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>
References: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>
	<3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>
Message-ID: <8E77CCF7-A648-4135-B2C1-C679CB3961BA@gmail.com>


On 5. mars. 2009, at 16.54, Ashley Moran wrote:

> On 5 Mar 2009, at 15:33, Ashley Moran wrote:
>> Any plans to release a new Celerity gem?  There's been a lot of  
>> good features since the last gem build and that was AGES ago!
>

Yes - it's been too long since the last Rubyforge release. I'm waiting  
for JRuby 1.2 (because of http://jira.codehaus.org/browse/JRUBY-3226),  
but will do a release as soon as it's out.

  

From jari.bakken at gmail.com  Thu Mar  5 14:48:16 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Thu, 5 Mar 2009 20:48:16 +0100
Subject: [Celerity-users] New version
In-Reply-To: <8277b7f40903050821y10594973i37409facd53fc2f0@mail.gmail.com>
References: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>
	<3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>
	<8277b7f40903050812p1af2041fn627a192b3ea01a3e@mail.gmail.com>
	<8277b7f40903050821y10594973i37409facd53fc2f0@mail.gmail.com>
Message-ID: <683FE381-6F90-40C2-A4CD-77C93CA25AAF@gmail.com>

>
> $ b = Celerity::Browser.new :log_level => :all
>
> => #<Celerity::Browser:0xe7eec9 @page=nil @charset="UTF-8"  
> @last_url=nil @error_checkers=[] @render_type=:html  
> @viewer=Celerity::DefaultViewer>
>
> any ideas?

This is because I trimmed down Browser#inspect to not include all the  
instance variables - looks nicer IMO.

http://github.com/jarib/celerity/commit/dadd32724dba8853e43b2abf0f6702e6a078e830


From jari.bakken at gmail.com  Thu Mar  5 14:49:01 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Thu, 5 Mar 2009 20:49:01 +0100
Subject: [Celerity-users] New version
In-Reply-To: <8277b7f40903050812p1af2041fn627a192b3ea01a3e@mail.gmail.com>
References: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>
	<3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>
	<8277b7f40903050812p1af2041fn627a192b3ea01a3e@mail.gmail.com>
Message-ID: <EA6E0800-039E-49A0-BC34-C2D29FB06BEB@gmail.com>

> NativeException: java.lang.IllegalAccessError: tried to access  
> method org.mozilla.javascript.Context.<init>(Lorg/mozilla/javascript/ 
> ContextFactory;)V from class  
> com.gargoylesoftware.htmlunit.javascript.HtmlUnitContextFactory 
> $TimeoutContext
>
> are you seeing this also, or is it just me?

I've never seen that error before - looks like something goes wrong  
with execution of the JavaScript on your site. Could you create a  
reduced case that will reproduce the problem?





From jari.bakken at gmail.com  Thu Mar  5 15:17:42 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Thu, 5 Mar 2009 21:17:42 +0100
Subject: [Celerity-users] which page should I end with after committing
	a form?
In-Reply-To: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
References: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
Message-ID: <D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>

> > p = b.button(:text, 'Search around').click
> => #<Java::ComGargoylesoftwareHtmlunitHtml::HtmlPage:0x6c2ea3  
> @java_object=HtmlPage(http://localhost:4000/world)@30552785>

If the page returned from ClickableElement#click is wrong, it's most  
likely a bug in HtmlUnit. I would try to create a reduced case and  
submit to them. See http://htmlunit.sourceforge.net/submittingBugs.html.

Also make sure you're using the latest version from GitHub (0.0.5.9) -  
they just fixed a similar issue I had (#2624738) in the latest  
snapshot. I've just pushed a new gemspec, so it should be available  
soon.




From joahking at gmail.com  Thu Mar  5 15:31:28 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Thu, 5 Mar 2009 21:31:28 +0100
Subject: [Celerity-users] which page should I end with after committing
	a form?
In-Reply-To: <D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>
References: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
	<D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>
Message-ID: <8277b7f40903051231s28f90862x4e9fa0f074f00a2a@mail.gmail.com>

thanks, I'll check it out


2009/3/5, Jari Bakken <jari.bakken at gmail.com>:
>> > p = b.button(:text, 'Search around').click
>> => #<Java::ComGargoylesoftwareHtmlunitHtml::HtmlPage:0x6c2ea3
>> @java_object=HtmlPage(http://localhost:4000/world)@30552785>
>
> If the page returned from ClickableElement#click is wrong, it's most
> likely a bug in HtmlUnit. I would try to create a reduced case and
> submit to them. See http://htmlunit.sourceforge.net/submittingBugs.html.
>
> Also make sure you're using the latest version from GitHub (0.0.5.9) -
> they just fixed a similar issue I had (#2624738) in the latest
> snapshot. I've just pushed a new gemspec, so it should be available
> soon.
>
>
>
> _______________________________________________
> Celerity-users mailing list
> Celerity-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/celerity-users
>


-- 
www.least-significant-bit.com

From joahking at gmail.com  Thu Mar  5 15:32:41 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Thu, 5 Mar 2009 21:32:41 +0100
Subject: [Celerity-users] New version
In-Reply-To: <683FE381-6F90-40C2-A4CD-77C93CA25AAF@gmail.com>
References: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>
	<3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>
	<8277b7f40903050812p1af2041fn627a192b3ea01a3e@mail.gmail.com>
	<8277b7f40903050821y10594973i37409facd53fc2f0@mail.gmail.com>
	<683FE381-6F90-40C2-A4CD-77C93CA25AAF@gmail.com>
Message-ID: <8277b7f40903051232x605a2932x29ed955640168070@mail.gmail.com>

I'll get into that reduced case soon,
thanks



2009/3/5, Jari Bakken <jari.bakken at gmail.com>:
>>
>> $ b = Celerity::Browser.new :log_level => :all
>>
>> => #<Celerity::Browser:0xe7eec9 @page=nil @charset="UTF-8"
>> @last_url=nil @error_checkers=[] @render_type=:html
>> @viewer=Celerity::DefaultViewer>
>>
>> any ideas?
>
> This is because I trimmed down Browser#inspect to not include all the
> instance variables - looks nicer IMO.
>
> http://github.com/jarib/celerity/commit/dadd32724dba8853e43b2abf0f6702e6a078e830
>
> _______________________________________________
> Celerity-users mailing list
> Celerity-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/celerity-users
>


-- 
www.least-significant-bit.com

From ashley.moran at patchspace.co.uk  Thu Mar  5 15:53:22 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Thu, 5 Mar 2009 20:53:22 +0000
Subject: [Celerity-users] New version
In-Reply-To: <8E77CCF7-A648-4135-B2C1-C679CB3961BA@gmail.com>
References: <811AB62B-4A86-48DF-B7E7-ED51808D5FD4@patchspace.co.uk>
	<3E1069B9-B452-42A2-AB22-E557CA1CFA5F@patchspace.co.uk>
	<8E77CCF7-A648-4135-B2C1-C679CB3961BA@gmail.com>
Message-ID: <EA79C919-51FA-478C-813D-81FF6EAB2FCE@patchspace.co.uk>


On Mar 05, 2009, at 7:44 pm, Jari Bakken wrote:

> Yes - it's been too long since the last Rubyforge release. I'm  
> waiting for JRuby 1.2 (because ofhttp://jira.codehaus.org/browse/JRUBY-3226) 
> , but will do a release as soon as it's out.


Cool - I'm happy with that!  Thanks Jari.


-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran


From joahking at gmail.com  Fri Mar  6 06:33:18 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Fri, 6 Mar 2009 12:33:18 +0100
Subject: [Celerity-users] which page should I end with after committing
	a form?
In-Reply-To: <8277b7f40903051231s28f90862x4e9fa0f074f00a2a@mail.gmail.com>
References: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
	<D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>
	<8277b7f40903051231s28f90862x4e9fa0f074f00a2a@mail.gmail.com>
Message-ID: <8277b7f40903060333t51f011cbrca0ba34d91effe61@mail.gmail.com>

hey there,
only to report my ongoing tests, I've set up 4 forms, and from jirb:

1. form with no js and submit button: submits OK, the result is the new page

2. form with button that before submitting have erroneous js: OK, the js
error is caught and nothing gets submitted

3. form with button that before submitting alerts a "text": OK, here the
result is the new page,
still there's a warning:
Mar 6, 2009 11:47:34 AM com.gargoylesoftware.htmlunit.javascript.host.Window
jsxFunction_alert
WARNING: window.alert("blah") no alert handler installed

4. form that before submitting geolocates to GMap API the text_field value
and set lat and lng hidden fields. NOK, this is the problematic case:

the form gets submitted, the log in test server shows the request and
correct processing, still the browser remains with the initial page

the thing seems to be a javascript issue like you pointed, are there any
known issues with GMap js that you know?

I'll keep on searching,

thanks in advance,
joaquin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090306/9d9cdc4a/attachment-0001.html>

From joahking at gmail.com  Fri Mar  6 07:19:40 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Fri, 6 Mar 2009 13:19:40 +0100
Subject: [Celerity-users] which page should I end with after committing
	a form?
In-Reply-To: <8277b7f40903060333t51f011cbrca0ba34d91effe61@mail.gmail.com>
References: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
	<D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>
	<8277b7f40903051231s28f90862x4e9fa0f074f00a2a@mail.gmail.com>
	<8277b7f40903060333t51f011cbrca0ba34d91effe61@mail.gmail.com>
Message-ID: <8277b7f40903060419r5845611dof8ec30f41727ced1@mail.gmail.com>

hey,
I might be missing something from HtmlUnit, I am now giving
http://wiki.github.com/jarib/celerity/creating-jar-files a try to see if
that solve the thiing

cheers,
joaquin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090306/c7eb41f1/attachment.html>

From jari.bakken at gmail.com  Fri Mar  6 21:25:41 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Sat, 7 Mar 2009 03:25:41 +0100
Subject: [Celerity-users] which page should I end with after committing
	a form?
In-Reply-To: <8277b7f40903060419r5845611dof8ec30f41727ced1@mail.gmail.com>
References: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
	<D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>
	<8277b7f40903051231s28f90862x4e9fa0f074f00a2a@mail.gmail.com>
	<8277b7f40903060333t51f011cbrca0ba34d91effe61@mail.gmail.com>
	<8277b7f40903060419r5845611dof8ec30f41727ced1@mail.gmail.com>
Message-ID: <97ED56E8-5BD3-49D9-A722-699C4074951B@gmail.com>

On 6. mars. 2009, at 13.19, Joaquin Rivera Padron wrote:

> hey,
> I might be missing something from HtmlUnit, I am now giving http://wiki.github.com/jarib/celerity/creating-jar-files 
>  a try to see if that solve the thiing
>

The Celerity jar shouldn't be different from using the gem directly.

From joahking at gmail.com  Sun Mar  8 12:04:17 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Sun, 8 Mar 2009 17:04:17 +0100
Subject: [Celerity-users] which page should I end with after committing
	a form?
In-Reply-To: <97ED56E8-5BD3-49D9-A722-699C4074951B@gmail.com>
References: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
	<D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>
	<8277b7f40903051231s28f90862x4e9fa0f074f00a2a@mail.gmail.com>
	<8277b7f40903060333t51f011cbrca0ba34d91effe61@mail.gmail.com>
	<8277b7f40903060419r5845611dof8ec30f41727ced1@mail.gmail.com>
	<97ED56E8-5BD3-49D9-A722-699C4074951B@gmail.com>
Message-ID: <8277b7f40903080904n6bd6703bs70ec0cfd95b9675a@mail.gmail.com>

hey there,
I've set up a reduced case with a form and 3 buttons, a submit one, one with
an onclick to normal js and then submits, and a third one with a onclick
that geolocates to GMap and then submits the form.

then I spec-ed:
- the form gets submitted with submit button: OK it passes
- the form gets submitted after some js: OK it passes
- the form gets submitted after GMap call: it does not pass!

the results are the same for firefox and IE. I've also set up the specs with
resynchronized browser and there shows a stacktrace that something goes on
inside GMap js...

I've put a gist for you here: http://gist.github.com/75816, there are a rack
app and a spec file to be run in jruby. I attached also my specs run
stacktrace

would someone please run it and see if you get same results?

thanks in advance,
joaquin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090308/b8e9133f/attachment.html>

From jari.bakken at gmail.com  Sun Mar  8 14:47:38 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Sun, 8 Mar 2009 19:47:38 +0100
Subject: [Celerity-users] which page should I end with after committing
	a form?
In-Reply-To: <8277b7f40903080904n6bd6703bs70ec0cfd95b9675a@mail.gmail.com>
References: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
	<D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>
	<8277b7f40903051231s28f90862x4e9fa0f074f00a2a@mail.gmail.com>
	<8277b7f40903060333t51f011cbrca0ba34d91effe61@mail.gmail.com>
	<8277b7f40903060419r5845611dof8ec30f41727ced1@mail.gmail.com>
	<97ED56E8-5BD3-49D9-A722-699C4074951B@gmail.com>
	<8277b7f40903080904n6bd6703bs70ec0cfd95b9675a@mail.gmail.com>
Message-ID: <4677B3A8-268B-42B9-88E4-042754EE8EBF@gmail.com>

Hello Joaquin,

> I've put a gist for you here: http://gist.github.com/75816, there  
> are a rack app and a spec file to be run in jruby. I attached also  
> my specs run stacktrace
>
> would someone please run it and see if you get same results?


I forked your gist and fixed some minor issues in the specs

http://gist.github.com/75833

I do not see the Javascript exception using the latest gem (0.0.5.9) -  
so that issue might be fixed (I added the output on my machine to the  
gist). The specs are still failing though. Unfortunately the GMap  
issue is very likely in HtmlUnit and not in Celerity - so you'll want  
to file a bug with them to see this fixed.

PS. While playing with the test page I noticed the gmap button doesn't  
work in Safari 4 public beta either - works fine in Firefox 3 and  
Opera 10 though.




From joahking at gmail.com  Mon Mar  9 12:52:35 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Mon, 9 Mar 2009 17:52:35 +0100
Subject: [Celerity-users] which page should I end with after committing
	a form?
In-Reply-To: <4677B3A8-268B-42B9-88E4-042754EE8EBF@gmail.com>
References: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
	<D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>
	<8277b7f40903051231s28f90862x4e9fa0f074f00a2a@mail.gmail.com>
	<8277b7f40903060333t51f011cbrca0ba34d91effe61@mail.gmail.com>
	<8277b7f40903060419r5845611dof8ec30f41727ced1@mail.gmail.com>
	<97ED56E8-5BD3-49D9-A722-699C4074951B@gmail.com>
	<8277b7f40903080904n6bd6703bs70ec0cfd95b9675a@mail.gmail.com>
	<4677B3A8-268B-42B9-88E4-042754EE8EBF@gmail.com>
Message-ID: <8277b7f40903090952j149fcf4eo52c61f68a37b2a39@mail.gmail.com>

>
>  <http://gist.github.com/75833> I do not see the Javascript exception
> using the latest gem (0.0.5.9) - so that issue might be fixed (I added the
> output on my machine to the gist). The specs are still failing though.
> Unfortunately the GMap issue is very likely in HtmlUnit and not in Celerity
> - so you'll want to file a bug with them to see this fixed.


I'll look into that

thanks for your time
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090309/87a942ad/attachment.html>

From joahking at gmail.com  Wed Mar 11 10:16:55 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Wed, 11 Mar 2009 15:16:55 +0100
Subject: [Celerity-users] which page should I end with after committing
	a form?
In-Reply-To: <8277b7f40903090952j149fcf4eo52c61f68a37b2a39@mail.gmail.com>
References: <8277b7f40903050855x7b889b71ue474b2dc5e2a9cb@mail.gmail.com>
	<D983373F-B9C5-4475-83E9-609EE081AFD0@gmail.com>
	<8277b7f40903051231s28f90862x4e9fa0f074f00a2a@mail.gmail.com>
	<8277b7f40903060333t51f011cbrca0ba34d91effe61@mail.gmail.com>
	<8277b7f40903060419r5845611dof8ec30f41727ced1@mail.gmail.com>
	<97ED56E8-5BD3-49D9-A722-699C4074951B@gmail.com>
	<8277b7f40903080904n6bd6703bs70ec0cfd95b9675a@mail.gmail.com>
	<4677B3A8-268B-42B9-88E4-042754EE8EBF@gmail.com>
	<8277b7f40903090952j149fcf4eo52c61f68a37b2a39@mail.gmail.com>
Message-ID: <8277b7f40903110716u310b3828sd26bd1f942dededd@mail.gmail.com>

as an aside info, I only get my features to pass with selenium (do not
confuse with selenium-on-rails)

I've tried watir with my app also and it does not pass... showing the same
not refreshing issue as htmlunit

luckily for me Selenium filled the bill, so for the moment I'll be sticking
with it (don't get me wrong, I really need to keep going with my features,
I'm dealing with this for 3 weeks now)...

I'll update the gist specs for watir and selenium to test against the rack
example there, and submit the bug to htmlunit in short

thanks for your time,
joaquin

2009/3/9 Joaquin Rivera Padron <joahking at gmail.com>

>  <http://gist.github.com/75833> I do not see the Javascript exception
>> using the latest gem (0.0.5.9) - so that issue might be fixed (I added the
>> output on my machine to the gist). The specs are still failing though.
>> Unfortunately the GMap issue is very likely in HtmlUnit and not in Celerity
>> - so you'll want to file a bug with them to see this fixed.
>
>
> I'll look into that
>
> thanks for your time
>
>


-- 
www.least-significant-bit.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090311/2ee92e06/attachment.html>

From jari.bakken at gmail.com  Thu Mar 19 10:15:04 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Thu, 19 Mar 2009 15:15:04 +0100
Subject: [Celerity-users] [ANN] celerity 0.0.6 Released
Message-ID: <eae5f6f90903190715w70f4d62dgf0903cec4640bb1b@mail.gmail.com>

celerity version 0.0.6 has been released!

* *http://github.com/jarib/celerity/tree
** *http://celerity.rubyforge.org
*
Celerity is a JRuby wrapper around HtmlUnit ? a headless Java browser with
JavaScript support. It provides a simple API for programmatic navigation
through web applications. Celerity aims at being API compatible with Watir.

Changes:

## 0.0.6 2009-03-19
* Support for meta, strong, dl, dt, dd, and em HTML elements.
* Update to HtmlUnit 2.5-SNAPSHOT.
* New options for Browser#new: :proxy, :charset, :render, :log_level
* Methods added:
  - Browser#add_cookie
  - Browser#asynchronized
  - Browser#add_listener
  - Browser#content_type
  - Browser#cookies
  - Browser#debug_web_connection
  - Browser#focused_element
  - Browser#io
  - Browser#remove_cookie
  - Browser#response_headers
  - Browser#wait
  - Browser#xml
  - Browser#{element,elements}_by_xpath
  - ClickableElement#{double,right}_click
  - ElementCollection#{first,last}
* Methods removed:
  - Browser#show_*
* Methods renamed:
  - SelectList#get_all_contents   => SelectList#options
  - SelectList#get_selected_items => SelectList#selected_options
  - SelectList#clear_selection    => SelectList#clear
* Add support for finding elements by their corresponding <label>.
* Recognize buttons of type image, reset, submit.
* Proxy support (see Browser.new)
* Lots of refactorings, bug fixes and minor enhancements.

Thanks to Hirobumi Hama, Kamal Fariz Mahyuddin and Thomas Marek for
contributions in this release.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090319/00c0ba95/attachment-0001.html>

From ashley.moran at patchspace.co.uk  Thu Mar 19 16:44:26 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Thu, 19 Mar 2009 20:44:26 +0000
Subject: [Celerity-users] [ANN] celerity 0.0.6 Released
In-Reply-To: <eae5f6f90903190715w70f4d62dgf0903cec4640bb1b@mail.gmail.com>
References: <eae5f6f90903190715w70f4d62dgf0903cec4640bb1b@mail.gmail.com>
Message-ID: <D89F62D6-AC6C-4162-9397-35DFFAF48382@patchspace.co.uk>


On 19 Mar 2009, at 14:15, Jari Bakken wrote:

> * Add support for finding elements by their corresponding <label>.

Haha, I spent a few hours doing that myself the other day... had no  
idea it was going into Celerity!

Thanks for the new release.  XPath support is a an especially great  
addition.

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From ashley.moran at patchspace.co.uk  Tue Mar 24 15:54:12 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Tue, 24 Mar 2009 19:54:12 +0000
Subject: [Celerity-users] Suggestion: do not treat status 401 as an error
Message-ID: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>

Hi

Just switched on status code exceptions:

@browser = Celerity::Browser.new(:browser =>  
"firefox", :status_code_exceptions => true)

However, this causes Celerity to throw an exception on status code 401  
(unauthorised).  401 is a normal part of accessing a (partially)  
protected site - so it should not be considered an error (unlike, say,  
403).  Maybe it should be excluded from the list of codes that throw  
exceptions.

I consider the current behaviour a bug.  WDYT?

Thanks
Ashley

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From jari.bakken at gmail.com  Tue Mar 24 16:23:42 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Tue, 24 Mar 2009 21:23:42 +0100
Subject: [Celerity-users] Suggestion: do not treat status 401 as an error
In-Reply-To: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>
References: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>
Message-ID: <8E5ED7EC-507A-4E6D-9363-AF8D1E72A356@gmail.com>


On 24. mars. 2009, at 20.54, Ashley Moran wrote:
>
> However, this causes Celerity to throw an exception on status code  
> 401 (unauthorised).  401 is a normal part of accessing a (partially)  
> protected site - so it should not be considered an error (unlike,  
> say, 403).  Maybe it should be excluded from the list of codes that  
> throw exceptions.

That sounds reasonable, but you'll have to take it to the HtmlUnit  
list, since we don't control this in Celerity. We simply set:

@webclient.throwExceptionOnFailingStatusCode = true

Perhaps we should add a method to turn this on/off also after the  
Browser is created.


From joahking at gmail.com  Tue Mar 24 16:37:05 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Tue, 24 Mar 2009 21:37:05 +0100
Subject: [Celerity-users] Suggestion: do not treat status 401 as an error
In-Reply-To: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>
References: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>
Message-ID: <8277b7f40903241337n420bea34yecb988ac50aef8da@mail.gmail.com>

I agree with you, 401 should not raise

cheers,
joaquin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/celerity-users/attachments/20090324/fbe7707b/attachment.html>

From ashley.moran at patchspace.co.uk  Tue Mar 24 20:33:19 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Wed, 25 Mar 2009 00:33:19 +0000
Subject: [Celerity-users] Suggestion: do not treat status 401 as an error
In-Reply-To: <8E5ED7EC-507A-4E6D-9363-AF8D1E72A356@gmail.com>
References: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>
	<8E5ED7EC-507A-4E6D-9363-AF8D1E72A356@gmail.com>
Message-ID: <2591DAEB-D315-4617-B6EA-3CFA206B23B7@patchspace.co.uk>


On 24 Mar 2009, at 20:23, Jari Bakken wrote:

> That sounds reasonable, but you'll have to take it to the HtmlUnit  
> list, since we don't control this in Celerity. We simply set:
>
> @webclient.throwExceptionOnFailingStatusCode = true
>
> Perhaps we should add a method to turn this on/off also after the  
> Browser is created.

That's exactly what I was about to try :)  And indeed, it would be  
generally useful, as it would let you inspect custom 404, 500 error  
pages etc without exploding, while raising errors during normal runs.

The consensus seems to be that the new 401 behaviour would be a good  
thing.  So there are two issues:

* passing that along to the HtmlUnit team
* implementing a setter method on Celerity::Browser

Should I raise tickets for either?  Let me know if you'd like me to  
take further action (if so, where), or if you can handle these.

Thanks!

Ashley


-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From ashley.moran at patchspace.co.uk  Tue Mar 24 22:02:19 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Wed, 25 Mar 2009 02:02:19 +0000
Subject: [Celerity-users] Suggestion: generic element finder
Message-ID: <2D9A7BA4-EBBC-4264-B836-9F05CFF428C4@patchspace.co.uk>

Hi

As far is I can tell, all input elements respond to #set in a sensible  
way.  So you can use Celerity::SelectList#set the same as  
Celerity::TextField.  The problem is, you can't *find* an element of  
any type with one method.  This causes problems if, as I've had to do  
recently, you want to sumbit a form without caring what type of  
elements you are filling out.

Currently, I'm doing this (selected parts of my the Cucumber steps  
code):

   def set_form_attribute_to_value(label_text, value)
     label_element = label_by_text(label_text)
     form_element = element_by_id(label_element.for)
     form_element.set(format_value_for_form_element(value,  
form_element))
   end

   def element_by_id(id)
     element_by_attribute(:id, id)
   end

   def element_by_attribute(html_attribute, value)
     element_by_xpath("//*[@#{html_attribute.to_s}='#{value}']")
   end

   def element_by_xpath(xpath)
     element = @browser.element_by_xpath(xpath)
     raise RuntimeError.new("XPath found no elements: #{xpath}")  
unless element.exists?
     element
   end

(I think I copied everything you need to understand what I mean.)

This problem could be simplified if you could instead write:

   @browser.element(:id => "or :name => whatever").set("blah")

WDYT?

Ashley

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From kamal.fariz at gmail.com  Tue Mar 24 22:26:51 2009
From: kamal.fariz at gmail.com (Kamal Fariz Mahyuddin)
Date: Wed, 25 Mar 2009 10:26:51 +0800
Subject: [Celerity-users] Suggestion: generic element finder
In-Reply-To: <2D9A7BA4-EBBC-4264-B836-9F05CFF428C4@patchspace.co.uk>
References: <2D9A7BA4-EBBC-4264-B836-9F05CFF428C4@patchspace.co.uk>
Message-ID: <13d1fccd0903241926t32f7591fte60f057c9486e88f@mail.gmail.com>

I use Webrat's semantics of always searching by multiple ways in order
of priority.

Form elements: search by id, then by name attribute, then by label
Buttons: search by value, then by id, then by inner text, then by alt attribute
Link: search by inner text, then by title attribute, then by id

For form elements, I created a custom Element called GenericField
which is a union of TextField, Hidden, Radio, Checkbox, and
SelectList. This is more for ease of locating. Setting though is
different for each actual field, which is a separate post.

I've implemented what I describe above in my webrat fork
http://github.com/kamal/webrat/tree/1543bc64ecf85054f9a033e1fc7670806886b41e/lib/webrat/celerity

On Wed, Mar 25, 2009 at 10:02 AM, Ashley Moran
<ashley.moran at patchspace.co.uk> wrote:
> Hi
>
> As far is I can tell, all input elements respond to #set in a sensible way.
> ?So you can use Celerity::SelectList#set the same as Celerity::TextField.
> ?The problem is, you can't *find* an element of any type with one method.
> ?This causes problems if, as I've had to do recently, you want to sumbit a
> form without caring what type of elements you are filling out.
>
> Currently, I'm doing this (selected parts of my the Cucumber steps code):
>
> ?def set_form_attribute_to_value(label_text, value)
> ? ?label_element = label_by_text(label_text)
> ? ?form_element = element_by_id(label_element.for)
> ? ?form_element.set(format_value_for_form_element(value, form_element))
> ?end
>
> ?def element_by_id(id)
> ? ?element_by_attribute(:id, id)
> ?end
>
> ?def element_by_attribute(html_attribute, value)
> ? ?element_by_xpath("//*[@#{html_attribute.to_s}='#{value}']")
> ?end
>
> ?def element_by_xpath(xpath)
> ? ?element = @browser.element_by_xpath(xpath)
> ? ?raise RuntimeError.new("XPath found no elements: #{xpath}") unless
> element.exists?
> ? ?element
> ?end
>
> (I think I copied everything you need to understand what I mean.)
>
> This problem could be simplified if you could instead write:
>
> ?@browser.element(:id => "or :name => whatever").set("blah")
>
> WDYT?
>
> Ashley
>
> --
> http://www.patchspace.co.uk/
> http://www.linkedin.com/in/ashleymoran
> http://aviewfromafar.net/
> http://twitter.com/ashleymoran
>
>
>
>
>
>
> _______________________________________________
> Celerity-users mailing list
> Celerity-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/celerity-users
>

From jari.bakken at gmail.com  Wed Mar 25 06:18:07 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Wed, 25 Mar 2009 11:18:07 +0100
Subject: [Celerity-users] Suggestion: do not treat status 401 as an error
In-Reply-To: <2591DAEB-D315-4617-B6EA-3CFA206B23B7@patchspace.co.uk>
References: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>
	<8E5ED7EC-507A-4E6D-9363-AF8D1E72A356@gmail.com>
	<2591DAEB-D315-4617-B6EA-3CFA206B23B7@patchspace.co.uk>
Message-ID: <73779DD6-3EB6-41EE-B4F0-4D7291E0C3AC@gmail.com>


>
> * passing that along to the HtmlUnit team
> * implementing a setter method on Celerity::Browser
>
> Should I raise tickets for either?  Let me know if you'd like me to  
> take further action (if so, where), or if you can handle these.

I think you should post this as a feature request to the htmlunit-user  
list.

http://sourceforge.net/mail/?group_id=47038

I can implement the setter - I added Browser#status_code yesterday,  
which also could be useful in this context.






From ashley.moran at patchspace.co.uk  Wed Mar 25 19:38:55 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Wed, 25 Mar 2009 23:38:55 +0000
Subject: [Celerity-users] Suggestion: do not treat status 401 as an error
In-Reply-To: <73779DD6-3EB6-41EE-B4F0-4D7291E0C3AC@gmail.com>
References: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>
	<8E5ED7EC-507A-4E6D-9363-AF8D1E72A356@gmail.com>
	<2591DAEB-D315-4617-B6EA-3CFA206B23B7@patchspace.co.uk>
	<73779DD6-3EB6-41EE-B4F0-4D7291E0C3AC@gmail.com>
Message-ID: <ACE73E69-50B9-4052-8E72-7B2ED74FA210@patchspace.co.uk>


On 25 Mar 2009, at 10:18, Jari Bakken wrote:

> I think you should post this as a feature request to the htmlunit- 
> user list.
>
> http://sourceforge.net/mail/?group_id=47038

I've made an action to do just this.

> I can implement the setter - I added Browser#status_code yesterday,  
> which also could be useful in this context.

Thanks!  I think it will be a generally useful thing.

Cheers
Ashley

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From ashley.moran at patchspace.co.uk  Thu Mar 26 16:19:10 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Thu, 26 Mar 2009 20:19:10 +0000
Subject: [Celerity-users] Suggestion: do not treat status 401 as an error
In-Reply-To: <73779DD6-3EB6-41EE-B4F0-4D7291E0C3AC@gmail.com>
References: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>
	<8E5ED7EC-507A-4E6D-9363-AF8D1E72A356@gmail.com>
	<2591DAEB-D315-4617-B6EA-3CFA206B23B7@patchspace.co.uk>
	<73779DD6-3EB6-41EE-B4F0-4D7291E0C3AC@gmail.com>
Message-ID: <EAC7E5AA-B383-4D5C-A0A4-287B32353058@patchspace.co.uk>


On 25 Mar 2009, at 10:18, Jari Bakken wrote:

> I think you should post this as a feature request to the htmlunit- 
> user list.

Done:

https://sourceforge.net/tracker/?func=detail&aid=2715327&group_id=47038&atid=448266

Ashley

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From ashley.moran at patchspace.co.uk  Thu Mar 26 16:22:23 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Thu, 26 Mar 2009 20:22:23 +0000
Subject: [Celerity-users] Suggestion: truncate Java stack trace
Message-ID: <0DE8D97A-D5B4-41C6-A90B-FF1A0508EEB3@patchspace.co.uk>

Hi

I'm finding the `:status_code_exceptions => true` error reporting  
extremely useful, *but* it spams the terminal with Java method calls  
which take ages to scroll through.  It might be better to return just  
the first line (which says what error code was thrown).

WDYT?

Ashley

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From jari.bakken at gmail.com  Thu Mar 26 20:37:07 2009
From: jari.bakken at gmail.com (Jari Bakken)
Date: Fri, 27 Mar 2009 01:37:07 +0100
Subject: [Celerity-users] Suggestion: truncate Java stack trace
In-Reply-To: <0DE8D97A-D5B4-41C6-A90B-FF1A0508EEB3@patchspace.co.uk>
References: <0DE8D97A-D5B4-41C6-A90B-FF1A0508EEB3@patchspace.co.uk>
Message-ID: <6795F72A-4880-43A6-B9A1-746131F78257@gmail.com>


On 26. mars. 2009, at 21.22, Ashley Moran wrote:
> I'm finding the `:status_code_exceptions => true` error reporting  
> extremely useful, *but* it spams the terminal with Java method calls  
> which take ages to scroll through.  It might be better to return  
> just the first line (which says what error code was thrown).
>
> WDYT?

Hmm, we could need to rescue HtmlUnit::FailingHttpStatusCodeException  
and re-raise with a modified backtrace. Only problem is that there's  
no central place in Celerity to do this - new HTTP requests can be  
initiated from a number of places. I guess Browser#goto and all the  
methods in the ClickableElement module are the most likely ones, but  
others could possibly go unrescued. I'll look into it.

From ashley.moran at patchspace.co.uk  Thu Mar 26 20:41:43 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Fri, 27 Mar 2009 00:41:43 +0000
Subject: [Celerity-users] Suggestion: do not treat status 401 as an error
In-Reply-To: <73779DD6-3EB6-41EE-B4F0-4D7291E0C3AC@gmail.com>
References: <C623A23F-A90D-4F5C-BA78-68C4B6F3136A@patchspace.co.uk>
	<8E5ED7EC-507A-4E6D-9363-AF8D1E72A356@gmail.com>
	<2591DAEB-D315-4617-B6EA-3CFA206B23B7@patchspace.co.uk>
	<73779DD6-3EB6-41EE-B4F0-4D7291E0C3AC@gmail.com>
Message-ID: <B35E7946-1513-421A-83BF-565EB8EEE2A8@patchspace.co.uk>


On 25 Mar 2009, at 10:18, Jari Bakken wrote:

> I think you should post this as a feature request to the htmlunit- 
> user list.
>
> http://sourceforge.net/mail/?group_id=47038


I posted[1] but Daniel Gredler disagreed about 401s not being errors.   
Feel free to back me up ;)

Cheers
Ashley

[1] https://sourceforge.net/tracker/?func=detail&atid=448266&aid=2715327&group_id=47038

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From ashley.moran at patchspace.co.uk  Fri Mar 27 12:58:36 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Fri, 27 Mar 2009 16:58:36 +0000
Subject: [Celerity-users] Suggestion: truncate Java stack trace
In-Reply-To: <6795F72A-4880-43A6-B9A1-746131F78257@gmail.com>
References: <0DE8D97A-D5B4-41C6-A90B-FF1A0508EEB3@patchspace.co.uk>
	<6795F72A-4880-43A6-B9A1-746131F78257@gmail.com>
Message-ID: <848C79F9-8084-451C-B773-DF88B58ADCA6@patchspace.co.uk>


On 27 Mar 2009, at 00:37, Jari Bakken wrote:

> Hmm, we could need to rescue  
> HtmlUnit::FailingHttpStatusCodeException and re-raise with a  
> modified backtrace. Only problem is that there's no central place in  
> Celerity to do this - new HTTP requests can be initiated from a  
> number of places. I guess Browser#goto and all the methods in the  
> ClickableElement module are the most likely ones, but others could  
> possibly go unrescued. I'll look into it.

Hmmm, I hadn't looked at the code, but I had a feeling it might be  
hard to do.  I guess it would be useful if you could make all HTTP  
requests go through one point?  (I really need to look at the source  
to know if that's feasible...)

Thanks
Ashley

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran