Feature SO_WHAT

[Wadael]

As incredible as it seems, unknown commands ordered to advanced robots
did not have any consequence until today.
It means that if the user made a typo, it wouldn't execute and would
not warn about it.

This is available in the SVN.

Update your local WadRobotFramework project, rebuild the JAR, update
the wadrobotframework.jar used in your application (redeploy). And
that's it, you benefit of this new feature.

Thanks to Romin (@iRomin) for warning me about this.

Jérôme

[Romin Irani]

Thanks for the quick turnaround.

Romin

[Romin Irani]

Jerome,

I understand that you have developed the SO_WHAT feature. Is it
possible to update your Downloads list page, so that one can pull the
JAR from there itself instead of building it themselves.

Thanks
Romin

[Wadaël]

Hi Romin,

I'm considering removing the JAR from the downloads. Because a user that takes only the .jar misses the generator :(

What's your opinion on this ?


Jérôme

2010/2/10 Romin Irani <romin....@gmail.com>

--
Wadaël
http://www.wadael.org  _  http://blog.wadael.org _  http://contrepeteries.free.fr _ http://code.google.com/p/wadrobotframework/

[Romin Irani]

I feel we should provide flexibility. For e.g. if I already have an existing Eclipse Project that needs to be enhanced with a Robot, then I need only the JAR.

Also -- consider my existing project, where you have added the SO_WHAT and really all I need is to add the JAR, build my project and deploy. But now, I will need to build things myself ? 

What do you think? I do not want to increase your work load :-)

Cheers

Romin

[Wadael]

Romin,

I agree to update the JAR at each iteration of the project. It's
better for existing "customers" :)

It would be good to be able to rename the previous .jar (with an
increment), so that the latest is always wadrobotframework.jar
I haven't seem how to do this so far through the web UI

You certainly have downloaded WRF by SVN, so to get updates easily
(that's the method I recommend) so it just takes the default task to
run to get the latest jar.

My recommandation for users who already have a webapp and want to add
a robot in it is to generate a skeleton anyway.
And then, just copy files that do not exist in their app yet
(capabilities.xml for example) and be precise when updating existing
files (web.xml) with the generated content.

HIH

Jérôme / Wadaël