Re: [OS-webwork] New version of XWork editor posted

[Jon Lipsky]

Title: Message

Thanks for pointing out the default parameter name for the result types...  The editor definately doesn't handle this right now...  I'll have to see if I can come up with a way to work with that, otherwise I might have to preprocess (transform) the xwork.xml file insert the parameter.   If I did that, then it would change:   <result type="dispatch">foo.jsp</result>   into   <result type="dispatch">     <param name="location">foo.jsp</param> </result> ----- Original Message ----- From: Jason Carreira To: [EMAIL PROTECTED] Sent: Tuesday, September 09, 2003 7:09 PM Subject: RE: [OS-webwork] New version of XWork editor posted That sounds useful.. also, I don't know if you pick up the default parameter name for each of the result types... this is a static constant field in each result class (optional) which lets the framework know what name it should give unnamed params.   i.e.   <result type="dispatch">foo.jsp</result>   uses "location = foo.jsp" -----Original Message----- From: Jon Lipsky (Mailing Lists) [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 09, 2003 11:39 AM To: '[EMAIL PROTECTED]' Subject: [OS-webwork] New version of XWork editor posted Hi All,   I just updated a the webstartable versions of the xwork editor.  It fixes the two problems that have been found until now:   1) Adding a parameter to an interceptor did not work. 2) You could not enter the class name of a new interceptor.   Jon...   PS - If any one has any ideas for additional "usage" type panels to add, let me know, and I'll see if I can get them added.  One example that I can think of off the top of my head that might be useful is a new tab to show the "locations" referenced by actions.  That way, you could easily figure out which actions let you to which specific JSP pages...  Does that sound useful to anyone? Any other ideas?