Hello, I know this is a difficult one. I hope it can be coped somehow and my problem is understandable.
We have a JSP based framework. Our value is contained in JSP custom tags. So what our customers did is they created HTML and put in some of our value adding JSP custom tags. What those do is not that much of interest, they do alot, some do rendering some do calculation etc. Now we see the cool features wicket has to offer. It is a great architecture. But we have to ensure backwards compatibility (bc). On the first sight it looked a bit impossible but on the second sight it does not. Lets take the JSP as main page template. the only difference is that a there is no <div wicket:id> but <my:tag .../> Could we teach the page parser to recognize our tags, and invoke them somehow (we are totally free to do what happens behind the scene, e.g. we could have written a wicket component for that tag and create it dynamically) we even could invoke some standard JSP methods on our old code and put in the result to the wicket output. But in those cases we would loose the wicket type actions. Take a more concrete example and imagine that we have a form tag that sets the value a user inters into a form field to a session variable. Another tag from us reads it from there and prints it. So we could create a MyWicketForm, which overwrites the setModelValue (or any other appropriate method) that additionally puts the value to someother container (some hash emulating the session scope) the form-template used to render is inherited from the wicket one. Our outputting tag would then be an enhanced Label that instead of taking getModelObjectAsString() it would read from our own scope hash. How does it sound, Any opinions on how feasible this would be? Any designed hooks we could use to hook into the lifecycle? Any non-designed hooks we could try to hack? The point is the only thing the customer creates is the JSP. If it is not possible to keep this JSP as some kind of API (no matter what processing we run in the background) a second option i saw before, which i do not like anymore that much is to do a two pass rendering, first run some kind of JSP->wicket template conversion. so basically replace the jsp custom tags with <div wicket:id> and clean unneeded stuff (jsp page directes etc) also prepare the instances of the wicket components (as wicked:id has to contain a id that is working, in that case the component is created on beforehand with a unique id) but that approach looks a bit too decoupled for me. Any other opinions? Ideas? Solutions? Anything is appreciated. I am writing this kind of anonymous. If some more found user or even better wicket developer finds this use case appealing, feel free to contact me directly. If there is a solution possible, there might be the opportunity to earn some money :) .: Fabian _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
