Sorry, you caught us in the middle of a remodeling :-) 

The UI tags have just been refactored and we haven't fixed up all of the examples. 
We're waiting on Ognl 2.6.4 for the beta2, not the final. Especially after this UI tag 
refactoring, it's going to be important to shake things out a bit before releasing. 

> -----Original Message-----
> From: Ke Ops [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, November 02, 2003 9:09 AM
> To: [EMAIL PROTECTED]
> Subject: [OS-webwork] webwork-example.war
> 
> 
> Hi!
> 
> I'm currently using Struts, but am considering wether
> to use WebWork2 for a new project - having read
> positive things about it. 
> 
> To vent this first: 
> I actually spent several -hours- searching through
> different homepages, documentation fragments and
> mailing lists and cvs repositories before finally
> getting my hands on working example application. If
> I'd been just a little less stubborn I would have
> decided to ditch WebWork2 once and for all, and settle
> with "good old Struts". At least with Struts there is
> an acceptable level of new-user friendliness, with one
> defined homepage, coherent documentation and downloads
> that actually work. The only webwork2 examplewar
> publicly available does not work. I eventually had to
> register with java.net and wait until the next day for 
> approval, then check out the whole project source from cvs, 
> and then build the webwork-example.war myself. If you guys 
> try to build your own Ivory Tower, you're succeeding very 
> well - it surely is not a very good way to encurage newbies. 
> Phew - now that I've got that out of my system... :-)
> 
> Now for the example web application:
> 
> This (I suppose) will be the first contact a new user
> has with the framework. Therefore it should work. And
> it should demonstrate some essential features of the
> framework. And I should not be forced to read the
> comments in the source code to understand what is
> going on. The example should be simple and self
> explanatory.
> 
> I think I read somewhere in the documentation or
> mailing list that the only thing remaining before
> removing the "beta" is that you're waiting for a new
> release of OGNL. Right? Unless you're planning on a
> few rounds with RC before releasing, I would suggest
> fixing up the example application a bit more first. If
> you really want to challenge Struts as the prefered
> framework you need too convert former Struts users,
> and  to effectively doing that you need a more
> newbie-friendly entrypoint (examples+documentation).
> 
> These are my comments after going through
> webwork-example.war. As mentioned I had to build it
> myself from cvs, using "ant example-war". These
> comments are only ment to help you polish the
> examples, so dumb-ass newbies like myself don't decide
> to run home to Struts... :-)
> 
> 
> 
> Starting example webapp, Tomcat log shows :
> 
> SEVERE: Could not find test.properties. Skipping
> 02.nov.2003 13:45:33 
> com.opensymphony.webwork.config.DefaultConfiguration
> <init>
> 
> SEVERE: Could not find com/opensymphony/webwork/othertest.properties.
> Skipping
> 02.nov.2003 13:45:33 
> com.opensymphony.webwork.views.velocity.VelocityManager
> loadConfiguration
> 
> 
> 
> Example webapp :
> 
> 
> Click here for a stupid little counter
> 
> Getting this exception:
> 
> org.apache.jasper.JasperException: Unable to find
> value for name VelocityCounter
> 
> 
> 
> 
> Click here for an example of the Form Tag and the
> Token Tag for hidden transaction tokens
> 
> Result looks exactly the same wether I use the form
> with token or no token. 
> Is the HTML source supposed to be like this (with $)?
> :
> 
> <input type="hidden" name="webwork.token.name" 
> value="$parameters.name"/> <input type="hidden" 
> name="$parameters.name" value="HLA8C0Q8RK3HYQQGQO4I4PC5CRZMI0SL"/><br>
> 
> 
> 
> Click here for a basic validation example
> 
> I was expecting some kind of validation messages when
> I entered illegal data.
> But no matter what I type (legal/illegal), the form
> just seems to be reset when I submit..? 
> 
> 
> 
> Click here for a visitor validation example
> 
> Same as basic validation. In addition Tomcat log shows 
> exception on first run (not on subsequent) :
> 
> INFO: Starting execution stack for action
> visitorValidation
> java.text.ParseException: Unparseable date:
> "01/01/1970"
>         at
> java.text.DateFormat.parse(DateFormat.java:334)
> 
> 
> 
> Click here for a visitor validation example with
> expression validation
> 
> Same as basic validation.
> 
> 
> 
> Click here to view the FormTag example using a
> location resolved via ognl
> 
> Result looks exactly the same wether I use the form
> with token or no token. 
> 
> 
> 
> Is it supposed to be this way?
> Any comments appreciated.
> 
> I believe the WebWork2 developers are doing a great
> job. But I think you need someone to boost up the
> documentation side of the product, in order to gain
> more users. 
> 
> Regards. :-)
> 
> - Keops
> 
> 
> ______________________________________________________
> Få den nye Yahoo! Messenger på http://no.messenger.yahoo.com/ 
> Nye ikoner og bakgrunner, webkamera med superkvalitet og 
> dobbelt så morsom
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program. 
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/ 
> _______________________________________________
> Opensymphony-webwork mailing list 
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> 


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to