Considering that much of the desire to write an application in Struts (or merge a pre-existing one) is probably because of the explicit action mapping or possibly the benefits of tiles, a different design approach to web applications might be the best route. These benefits can, at least to a small extent, be realized in different ways inside of Jetspeed, most notably that the need for tiles diminishes since the portal itself handles layouts et al so in effect you need only write the content 'view' which is what you would be most likely doing in tiles anyway...
In short, try developing or using applications that have well defined business logic in seperate classes that are not framework related, and running all of this in the same container (or set). Then, you could embark on merely implementing the workflow and adapting the view to whatever platform you want to deploy things to by implementing the appropriate action/view paradigm in the framework. The idea here is that things like authentication and other things that end up being framework related are adapted instead of hardcoded... I am testing these theories now, and while they are certainly idealist, if it results in code to help migrate/cross-deploy apps from [webwork|struts| turbine| jetspeed| <insert framework of the week here>] then it was worth the try.... a lot of applications that I would love to 'portalize' for instance have their own ideas about how the world should work. In part, the J2EE webapp design didn't accomodate well for a portal mentality - 'one app to rule them all' :)
Cheers, Jeremy
Jason Trust wrote:
Would it make sense to develop your web application as separate from the JetSpeed portal. Use the WebBrowserPortlet or others and provide URL links to your specific portlets?
If this is the route you were trying to head down, my suggestion would be to identify the type of portlet you will be using to display your web applications, and make sure it will work for all the portlets you are going to build. You may also need to identify how you might pass authentication information or other parameters that your web applications may need to function or display properly.
As far as how you would configure you web applications - excluding JetSpeed, we are in the midst of that right now. The WebBrowserPortlet is what we are looking at, but we are having issues with certain tags and javascript mutilation, but that could be the way we have our pages written, etc. In any case, we are trying to determine a developer guideline for web applications that use the WebBrowserPortlet, as well as the IFrame, etc.
HTH
Jason Trust
-----Original Message-----
From: Debora Galante [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 19, 2004 9:12 AM
To: Jetspeed Users List
Subject: R: Struts & Jetspeed 1.5
Any news about Struts & Jetspeed 1.5? I have the same problem...do you know Liferay??
-----Messaggio originale----- Da: J. L. [mailto:[EMAIL PROTECTED] Inviato: mercoled� 12 maggio 2004 18.30 A: [EMAIL PROTECTED] Oggetto: Struts & Jetspeed 1.5
Hi,
I'm a brand new user of Jetspeed. I just finished the tutorial, and still ask myself a lot of questions. I didn't find answers neither in the FAQ nor in the mailing list archive. I want to develop a web-application based on Struts and I was wondering how I could develop this web-app in collaboration with Jetspeed.
How can I make Struts and Jetspeed work together ? I don't know how to 'merge' Struts Action, ActionForm ... with Jetspeed HTMLPortlet, JSPPortlet, ...
I'll have several portlets (web-app) therefore : How should I structure my classes, JSP, config files ... ?
What are the best practices ?
Thanks in advance for your advices.
Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! Cr�ez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/
Dialoguez en direct avec vos amis gr�ce � Yahoo! Messenger !T�l�chargez Yahoo! Messenger sur http://fr.messenger.yahoo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
