Jason, 1 - On the ClientDispatcher, if you give me pointers I'll get on it right away. Can't promess 'flash' speed, but will get it done. 2 - On the XML/XSL view: Having either Velocity or JSP render the XML is an option. The drawback of that is introducing another layer when the rendering could be done on the dispatcher itself or not done at all and left for the requestor (in the case where the requestor is not a browser but a client through HTTP or through a ClientDispatcher). In the latter case, all that would be needed is the ability to not have a view at all and respond with the result of a method call on the bean (just an idea) that would return a string representation of the bean (in this case XML). If the actions are able to respond with a standard XML interface it would be a snap to provide Web Services interfaces to Webwork2 (more power to it). Thanks. Let me know. Sergio Infante
----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 15, 2003 1:43 PM Subject: Opensymphony-webwork digest, Vol 1 #1352 - 2 msgs > Message: 1 > Subject: RE: [OS-webwork] Re: Opensymphony-webwork digest, Vol 1 #1348 - 2 msgs > Date: Mon, 15 Dec 2003 12:35:09 -0600 > From: "Jason Carreira" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > > I don't really know much about the XML/XSL view stuff... If it were me, > I guess I'd use a Velocity template to generate XML, but maybe I'm > missing something there. > > The ClientDispatcher shouldn't be too hard to get working... I > personally don't have time to do it, but I'd be willing to share ideas > and pointers with anyone who wanted to work on it. > > Jason > > > -----Original Message----- > > From: Sergio Infante [mailto:[EMAIL PROTECTED] > > Sent: Monday, December 15, 2003 1:32 PM > > To: [EMAIL PROTECTED] > > Subject: [OS-webwork] Re: Opensymphony-webwork digest, Vol 1 > > #1348 - 2 msgs > > > > > > Jason, > > > > Thanks for your reply. These two features are key for our > > articulated architecture of which Webwork2 is the central > > piece. The idea being that no matter how you view (not just > > about templating but also about portals vs. web-apps vs. > > swing clients vs. altio clients) the results of business > > 'actions' the logic remains the same. > > > > XML/XSL provide us with the articulation we need in terms of > > connection points and for inter-operability; remote clients > > (ClientDispatcher) guarantee scalability on the business > > layer vs. presentation layer. For example, to make sure we > > can run the portal in a server cluster remotely (in a > > different context and possibly server cluster) from the > > central Webwork2 piece. In order of priorities for the > > project, XML/XSL is rather crucial and Remote invocation will > > become important in a few weeks. Ideally (IMHO) implementors > > should be able to switch from local to remote dispatchers > > based on the XML configuration on the client without changing > > anything in the client code or the server action. That > > provides real scalability. I have been looking at serveral > > frameworks in the past months and have to say that with these > > two features there is no framework out there that can touch > > Webwork2 (not that they're close). I say this because as much > > as I hope these features are included as quickly as possible, > > I realize the amount of work that has been done already. > > Please let me know if you have any ETA on these. Thanks again, > > > > Sergio Infante > > > > > > > > > I'm not sure if Patrick ported the XSL view to WW2... The > > > ClientDispatcher has not been added to WW2 yet because > > no-one's really > > > been asking for it yet. If you need it and want to get it > > working, let > > > us know and we can look at adding it in. > > > > > From: Sergio Infante [mailto:[EMAIL PROTECTED] > > > Sent: Monday, December 15, 2003 12:41 PM > > > To: [EMAIL PROTECTED] > > > Subject: [OS-webwork] Lost in Docs maze: Please help: XSL View and > > > ClientDispatcher > > > > > > > > > > > > Hello, > > > I was hoping somebody could help me figure out my way. I am a > > > converted user of Maverick to Webwork2 but having some difficulties > > > trying to follow documentation and figuring out which are > > Webwork and > > > which are Webwork2 features. > > > > > > Right now I am interested in implementing two features: (1) XSL > > > presentation as a View type and (2) the use of a remote client > > > dispatcher (which I found somewhat documented in Webwork > > 1). These are > > > key to the architecture I am defining to serve local and remote > > > portals and web applications within the institution > > (education). Are > > > these still present in Webwork2? If so, are they part of > > the current > > > release? Is there any documentation showing how they work? > > > > > > Thanks so much for your time. > > > Sergio ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
