webwork-devel Mailing List for WebWork (Page 51)
Brought to you by:
baldree,
rickardoberg
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(316) |
Dec
(117) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(197) |
Feb
(229) |
Mar
(293) |
Apr
(177) |
May
(84) |
Jun
(40) |
Jul
(43) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Rickard O. <ri...@xp...> - 2001-11-21 06:58:14
|
Mike Cannon-Brookes wrote: > I just upgraded an application to the latest webwork jar and of course > it broke - ApplicationFormSupport is gone! Correct :-) > I don't have a huge problem with this, here's how I solved it (is this > the correct way now?) > > All my 'form actions' now implement CommandDriven, and to get the input > form up (without validating and generating errors on data that hasn't > been submitted yet) I link to FormAction!default.action rather than > FormAction.action ? That is indeed the correct way, although I'd probably use an alias for it instead of doing the above, i.e. alias "FormAction!Default" with either "formaction.default" or only the action as "formaction!default". > If this is true - it should be doc'ed for people upgrading from previous > versions! It has been discussed on the user list with a "!IMPORTANT!" note attached to it. I can do it again though. /Rickard -- Rickard Öberg |
|
From: Mike Cannon-B. <mi...@at...> - 2001-11-21 02:12:25
|
Idea: why not have success as the default view? (it may already be so) <action name=3D"FooBar"> <view>/onlyview.jsp</view> </action> ? -mike On Wed, 2001-11-21 at 04:15, Rickard =D6berg wrote: > I just committed the XML action configuration stuff to CVS, as outlined=20 > earlier. I don't have time to explain how it works right now, but look=20 > at these files: > webwork.config.XMLActionConfiguration > /WEB-INF/classes/actions.xml >=20 > and try running /webwork/actions.action to get a listing of actions=20 > defined in actions.xml. >=20 > have fun, > Rickard >=20 > --=20 > Rickard =D6berg >=20 >=20 > _______________________________________________ > Webwork-devel mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-devel |
|
From: Mike Cannon-B. <mi...@at...> - 2001-11-21 02:01:39
|
I just upgraded an application to the latest webwork jar and of course it broke - ApplicationFormSupport is gone! I don't have a huge problem with this, here's how I solved it (is this the correct way now?) All my 'form actions' now implement CommandDriven, and to get the input form up (without validating and generating errors on data that hasn't been submitted yet) I link to FormAction!default.action rather than FormAction.action ? If this is true - it should be doc'ed for people upgrading from previous versions! -mike |
|
From: Markus H. <ma...@ac...> - 2001-11-20 18:54:04
|
Rickard =D6berg <ri...@xp...> writes: > Examples: > foo.jsp -> foo.jsp (no change) > /foo.jsp -> /webwork/foo.jsp (prefix with context) > http://mycomp.com/foo.jsp -> http://mycomp.com/foo.jsp (no change) >=20 > Are these rules always true? Do you have any cases where the link is > absolute and you don't want the context added, and vice versa? AFAIK, these rules are always true. I can't think of one single legitimate reason to not add the context path to absolute path links (unless you are doing some very obscure). Markus --=20 Markus Holmberg ma...@ac... |
|
From: Victor S. <sa...@us...> - 2001-11-20 18:11:46
|
Update of /cvsroot/webwork/webwork/src/build In directory usw-pr-cvs1:/tmp/cvs-serv10388 Modified Files: build.xml Log Message: Made it so action.xml was not included in the jar, because otherwise that's the one it would always find :) |
|
From: Rickard <ri...@xp...> - 2001-11-20 17:15:17
|
I just committed the XML action configuration stuff to CVS, as outlined earlier. I don't have time to explain how it works right now, but look at these files: webwork.config.XMLActionConfiguration /WEB-INF/classes/actions.xml and try running /webwork/actions.action to get a listing of actions defined in actions.xml. have fun, Rickard -- Rickard Öberg |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:12:56
|
Update of /cvsroot/webwork/webwork/src/resources/web/WEB-INF/classes In directory usw-pr-cvs1:/tmp/cvs-serv25589/src/resources/web/WEB-INF/classes Modified Files: views.properties webwork.properties Added Files: actions.xml Log Message: Added XML action examples and defaults |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:12:55
|
Update of /cvsroot/webwork/webwork/src/main/webwork/dispatcher In directory usw-pr-cvs1:/tmp/cvs-serv25589/src/main/webwork/dispatcher Modified Files: ServletDispatcher.java Log Message: Added XML action examples and defaults |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:12:55
|
Update of /cvsroot/webwork/webwork/src/resources/web In directory usw-pr-cvs1:/tmp/cvs-serv25589/src/resources/web Added Files: actions.jsp Log Message: Added XML action examples and defaults |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:12:55
|
Update of /cvsroot/webwork/webwork/src/main/webwork/taglib In directory usw-pr-cvs1:/tmp/cvs-serv25589/src/main/webwork/taglib Modified Files: ActionTag.java Log Message: Added XML action examples and defaults |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:12:55
|
Update of /cvsroot/webwork/webwork/src/main/webwork/action/factory In directory usw-pr-cvs1:/tmp/cvs-serv25589/src/main/webwork/action/factory Modified Files: ActionFactory.java Log Message: Added XML action examples and defaults |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:12:55
|
Update of /cvsroot/webwork/webwork/src/main/webwork In directory usw-pr-cvs1:/tmp/cvs-serv25589/src/main/webwork Modified Files: default.properties Log Message: Added XML action examples and defaults |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:12:55
|
Update of /cvsroot/webwork/webwork In directory usw-pr-cvs1:/tmp/cvs-serv25589 Modified Files: WebWork.ipr Log Message: Added XML action examples and defaults |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:10:29
|
Update of /cvsroot/webwork/webwork/src/main/webwork/config In directory usw-pr-cvs1:/tmp/cvs-serv24614 Modified Files: Configuration.java DefaultConfiguration.java PropertiesConfiguration.java Added Files: XMLActionConfiguration.java Log Message: Added XML action configuration support |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:09:30
|
Update of /cvsroot/webwork/webwork/src/main/webwork/action/test In directory usw-pr-cvs1:/tmp/cvs-serv24122 Added Files: ActionListing.java Log Message: Added ActionListing |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:08:09
|
Update of /cvsroot/webwork/webwork/src/main/webwork/velocity In directory usw-pr-cvs1:/tmp/cvs-serv23661 Modified Files: URLBean.java WebWorkUtil.java WebWorkVelocityServlet.java Log Message: Better creation of contexts in the servlet Better handling of various input types in util methods URLBean now prefixes URL's only if they are absolute |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:06:56
|
Update of /cvsroot/webwork/webwork/src/resources/web/velocity In directory usw-pr-cvs1:/tmp/cvs-serv23193 Added Files: macros.vm test.vm Log Message: Added Velocity macros test |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 17:06:38
|
Update of /cvsroot/webwork/webwork/src/resources/web In directory usw-pr-cvs1:/tmp/cvs-serv23075 Modified Files: index.jsp Log Message: Added Velocity macros test |
|
From: Rickard <ri...@xp...> - 2001-11-20 16:26:11
|
About URL tag and context path prefixing. I was wondering what the different cases are, and when you want it to be prefixed with the context and, when you want to leave it alone. It seems like it's most interesting when it's an absolute path without a hostname. Examples: foo.jsp -> foo.jsp (no change) /foo.jsp -> /webwork/foo.jsp (prefix with context) http://mycomp.com/foo.jsp -> http://mycomp.com/foo.jsp (no change) Are these rules always true? Do you have any cases where the link is absolute and you don't want the context added, and vice versa? /Rickard -- Rickard Öberg |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 15:25:35
|
Update of /cvsroot/webwork/webwork/src/resources/web/WEB-INF/classes In directory usw-pr-cvs1:/tmp/cvs-serv19577 Modified Files: webwork.vm Log Message: Added #url macro (thanks to Dave Bryson for this contribution!) |
|
From: Rickard ?b. <ric...@us...> - 2001-11-20 15:25:07
|
Update of /cvsroot/webwork/webwork/src/main/webwork/velocity In directory usw-pr-cvs1:/tmp/cvs-serv19391 Added Files: URLBean.java Log Message: Added URL-bean (thanks to Dave Bryson for this contribution!) |
|
From: Rickard <ri...@xp...> - 2001-11-20 13:48:14
|
Mike Cannon-Brookes wrote: > Ditto - I love it - I've realised why it's much more readable - you see > what all the parts are from the XML tags. > > ie <action name="Test"> is actually more readable than Test.success > (despite being more verbose ;)). Hehe, interesting that your example is wrong. "Test.success" defines the success view for Test, whereas your XML example is the definition of an action... ah well... point taken... > PS Can I now outlaw all Apache like voting for changes such that it > might inhibit the quality of the software produced? ;) Can you show an example where voring would inhibit the QoS? /Rickard -- Rickard Öberg |
|
From: Mike Cannon-B. <mi...@at...> - 2001-11-20 13:40:53
|
Ditto - I love it - I've realised why it's much more readable - you see what all the parts are from the XML tags.=20 ie <action name=3D"Test"> is actually more readable than Test.success (despite being more verbose ;)). +1 -mike PS Can I now outlaw all Apache like voting for changes such that it might inhibit the quality of the software produced? ;)=20 PPS +1 to outlaw voting ;)) On Wed, 2001-11-21 at 00:00, Victor Salaman wrote: > Seems good to me! >=20 >=20 > >Hey > > > >I have now implemented an XML-based Action configuration module. It can > >load XML in the following format, which is used both for action > >instatiation and view mappings. Example: > ><actions> > > <action name=3D"Test" alias=3D"test"> > > <view name=3D"success">test.jsp</view> > > <command name=3D"foo" alias=3D"test.foo"> > > <view name=3D"success">test.jsp</view> > > </command> > > <command name=3D"default"> > > <view name=3D"success">test.jsp</view> > > </command> > > </action> > ></actions> > > > >So, basically it's a list of actions. Actions may or may not have > >aliases. Actions may have a number of commands defined, each of which > >may in turn have aliases or not. If a command alias has not been > >defined, it may be invoked using the actions name/alias followed by "!" > >followed by the commands name. For example, the above XML would allow > >the two Test commands to be invoked using: > >test.foo > >test!default > > > >That's all there's to it. No changes were needed in the view mapping or > >action factory, since they both use the above using the Configuration > >interface. > > > >Any thoughts on this? I have not yet added it to CVS, since I wanted > >feedback first. > > > >regards, > > Rickard > > > >-- > >Rickard =D6berg > > > > > >_______________________________________________ > >Webwork-devel mailing list > >Web...@li... > >https://lists.sourceforge.net/lists/listinfo/webwork-devel >=20 >=20 > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.as= p >=20 >=20 > _______________________________________________ > Webwork-devel mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-devel |
|
From: Rickard <ri...@xp...> - 2001-11-20 13:36:17
|
Philipp Meier wrote: > Is it be possible with your current implementation to make the mappings > changeable at runtime? I have the idea to store the mappings in a > database. It makes sense in my case because it want to build a system > where actions etc. can be plugged-in at runtime. Currently the mapping *implementation* may not be changed at runtime. However, the used may be implemented in a way that allows runtime updates. The current view mapping simply delegates to the Configuration, so you have two options: 1) Implement your own view mapping implementation that looks in a database. 2) Implement your own Configuration implementation that looks in a database, and set the view mapping implementation to the ConfigurationViewMapping (since the DefaultViewMapping does caching). I would recommend 2) since then you don't have to reimplement the logic that allow you to not set all views. /Rickard -- Rickard Öberg |
|
From: Philipp M. <me...@o-...> - 2001-11-20 13:35:57
|
On Tue, Nov 20, 2001 at 01:49:05PM +0100, Rickard =D6berg wrote: > Hey >=20 > Billy, it would very cool if you could update the XSLT support to=20 > include JDOM walkers. Right now JDOM trees don't output very nicely=20 > using showtree.xslt. Haven't had a look at JDOM yet but will do so. > Also, in my editor (IntelliJ/W2K) the newlines are all screwed up. There= =20 > are one empty line between each line of code. I suppose this is a=20 > *nix/Windows problem. Can you see if you can fix this up. Currently it's= =20 > a bit unreadable. I will fix that but it may take some days before I have the time to do it. Should be perl / sed onliner to fix it. ;-)) Unix rules. -billy. --=20 Philipp Meier o-matic GmbH Gesch=E4ftsf=FChrer Pfarrer-Wei=DF-Weg 16-18 Tel.: +49-(0)700-66284236 89077 Ulm |