[EMAIL PROTECTED] a écrit :
>> Hi Nicholas,
>>
>> 1) AJAX use a lot of Javascript, so HtmlUnit is the solution, 
>> even if I still have problem with onclick event (it works 
>> with HtmlUnit alone, but not with jWebUnit+HtmlUnit).
>>     
>
> Great.  I'll try it out....
>
>   
>> It is possible to package a jar with full dependencies 
>> inside. If you are interested, just ask.
>>
>>     
>
> No, not right now.
>
>   
>> Concerning Jacobie, plugin is currently totally broken, as I 
>> made some change in jWebUnit Interface, and jacob.dll is not 
>> on the right place. 
>> However, Selenium is a better solution, as it works with all browser. 
>> I'm currently working on SeleniumDialog, and I hope it will 
>> pass most of the tests soon.
>>     
>
> You can move the jacob.dll into a new location....whereever....it should
> Be somewhere.  Don't worry about this engine for now.....  I haven't had
> any
> Time to even touch it in the last 6 months.  Is it not compiling or
> something...I noticed
> You segmented everything into its own project....good call.  Is this a
> Maven 2 thing?  To make
> Packaging easier?
>   
In fact, because of Maven 2 transitive dependencies, the old 
architecture was needing all dependencies to use JWebUnit. For example, 
you needed HttpUnit dependencies even with HtmlUnit. It brought many 
conflict, so I decided to split in different modules. The core should 
only contains user API, helper methods, and the interface plugins should 
implement.
As every plugins use the same test cases, so I created a module for 
tests (moreover, final users don't need to download test cases).

Now, packaging is easy thanks to Maven.
> About selenium....I see a lot of people using it....is it javascript
> based, thus allows
> Javascript to be plugged into each browser....  I thought you had to
> setup a proxy
> Of somesort to get it to work.  It sounds like it may be a bit to
> setup....I may be totally wrong....but hey
> That is the beauty of the jwebunit arch.  If one doesn't work (engine)
> try another....
>
> It would be nice to do for jwebunit just like springs concept of
> packaging or distros... They release
> Two distro's.  One that is lightweight that is basically the compiled
> "spring" jars....and a
> Second distro that bundles "ALL depenencies" within one *.zip file.  I
> don't know if you know
> Spring but it includes about, at least, 50 dependant jar files.  These
> jars are sometimes hard
> To find.
>   
OK, but I suggest one .zip by plugin, as peoples using HtmlUnit don't 
want to download Jacobie stuff.
> See Ya,
>
> Nick Neuberger
>
>
> _______________________________________________
> Jwebunit-development mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jwebunit-development
>
>   

-- 

_________________________________________________________________________

Julien HENRY | **Capgemini Sud **| Nice

www.fr.capgemini.com <http://www.capgemini.com/>

Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice

**Join the Collaborative Business Experience**** **
_________________________________________________________________________


This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.



_______________________________________________
Jwebunit-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-development

Reply via email to