Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: <= 3.x
-
Labels:None
-
Sub-Committee:RNE
Description
https://test.kuali.org/confluence/display/KULRNE/Ajax+Refactoring+Recommendation
i already did the basic of step 1-4 in the configuration section, since most folks don't have access to add libs or modify the web.xml file. specific methods need to be added to dwr.xml. i am not concerned with breaking dwr.xml into separate files by module now. that wouldn't really make a dent in the modularization issues that we have, e.g. spring refs, ojb refs, struts, etc. and will be easy enough to do later. i also like the idea of exposing methods in individual services, rather than creating a wrapper service layer. and, corresponding imports need to be done in appropriate tags/jsps - i actually kind of like the idea of putting these in page.tag with the engine and utils imports i added to keep it all together.
recommend global error handling strategy to rne team via mailing list.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is relied upon by
-
KFSOLD-6245 CG AJAX
-
- Closed
-
Activity
it appears that we are already using json for one piece of chart functionality. there are some concerns about the license, and it has been suggested that we rewrite the spec rather than use it. i assume the current usage will be automatically eliminated when we do this work (and therefore the json stuff in objectInfoUtils.js can juts be removed for now, rather than increase the scope of this task?
we will work on this the week of our F2F at Davis (2/12) if you don't get to it first
jonathan - can you comment on the erroe handling strategy and the json issue? thanks
reopening to flag for follow up on error handling and json
jonathan is using dwr error handler to blank out fields when an error happens. displays a user-friendly message in red - like "User not found". json stuff has been removed, so the licensing concern is gone
i am attaching the licensing checklist to this issue rather than a config management issue, because i already did the config management work. this chage was approved by the tech council