a question that i would ask myself if i was in your shoes:
does a portal meet the long term needs of the client. in a simple way do they need to publish portlet? Or do they need a light wieght web app? chris On 3/28/07, citynomad <[EMAIL PROTECTED]> wrote:
Thanks a lot for your quick response. Sounds like it may be quite an effort. So now I have a dilemma of what to drop - AppFuse or the portal. I just might rethink that whole portal idea, after all. ;-) Eugene mraible wrote: > > On 3/28/07, citynomad <[EMAIL PROTECTED]> wrote: >> >> Hi all, >> >> I am starting work on a project that will probably include a portal >> solution >> (using Liferay or JetSpeed or something similar.) >> >> I am curious if anyone has tried running AppFuse 2 in a portlet >> container, >> and if so: >> 1. What's involved in setting it up? Is it more trouble than it's worth? > > I got Equinox working in Jetspeed a few years ago using some of the > "bridges" that are available. > > Here's what I had to do with the Struts 1.x version to make it work: > > http://raibledesigns.com/wiki/Wiki.jsp?page=StrutsPortlet > > That being said, there's a lot of problems with deploying a > traditional WAR in a portlet environment. For example, it's unlikely > you'll be able to use SiteMesh, or any of the CSS and JavaScript from > your WAR (AFAIK). > >> 2. Which archetype, if any, is more suitable for such scenario? (I am >> thinking of using the Spring MVC version, but not sure if the basic or >> the >> modular archetype is a better fit for what I need.) > > It depends. If you can get a bridge working, then it'll likely depend > on the maturity of the bridge. > >> 3. Which portlet container would you recommend? (slick UI is of utmost >> importance to the client, so having an AJAXified interface would be nice. >> :) > > I've heard good and bad things about Liferay. I've spent quite a few > hours installing Jetspeed on different containers over the years and > haven't had much luck outside of Tomcat. The last time I tried was a > year ago, so it's likely much better now. > >> >> Also, are there any plans to have a specifically portlet aware version of >> AppFuse (using Spring Portlet MVC or Spring Web Flow, perhaps?) > > Nope. There's not enough demand at this point. > > Matt > >> >> Thanks. >> >> Eugene >> -- >> View this message in context: >> http://www.nabble.com/AppFuse-2.0-in-a-portlet-container-tf3481744s2369.html#a9718400 >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > http://raibledesigns.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/AppFuse-2.0-in-a-portlet-container-tf3481744s2369.html#a9721755 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Chris Love ph. 303 929.8509 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
