Morning All-

Following the literature guidelines listed at
http://wiki.apache.org/struts/MigrationTools
I am hoping to deliver a (hopefully) comprehensive Struts.1 to Struts.2 
migration strategy
Keeping in mind that Spring is being used for IOC of required objects (e.g. 
BeanFactories) and such

My question is the majority of migration suggestions is to use ActionWrapper to 
point backwards to Action 1.x classes using the Struts 1.x plugin defined in 
init method where there are 3 conversion steps
0)MessageResources
Action 2.0 TextProvider that retrieves messages from the Action 1.x 
MessageResources instance in the servlet context 
(understood as this exists in majority of localisation converters)

1)Struts 1 Action -> Struts 2 Interceptor -> Interceptor introduced to some 
manner of commons chain
Looking for clarification on where in the chain would this new Interceptor 
introduced and how is this determination made?

2)
ValidationInterceptor
LookUp the action in (existing) commons-validation objects loaded by an 
existing Action 1.x application
If there is validation logic in any method of a (non) commons-validation object 
how could one introduce this validation as a new 
commons-validation class and object (If handcoding is the only way then thats 
ok)

Many Thanks
Martin --
--------------------------------------------------------------------------- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--------------------------------------------------------------------------- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.

Reply via email to