Re: Struts and Portlets
I am glad to see the interest in supporting Struts applications in a Portal Server. I worked on adding support for Struts in WebSphere Portal, which added the ability to create Struts applications that can be deployed in WebSphere Portal. We encountered some relatively minor changes that could be made to the framework to help support Struts in a Portal Server, but there were other issues as well. It was not clear how receptive the Struts community would be to some of these suggestions at the time but it sounds like the co-existence of Struts and JSR 168 may be an important one for the future. Some of the issues have already been raised like ForwardAction and the chaining of request processors. We had to package an implementation of a request processor, so that meant we also had to ship a Tiles request processor that inherited from ours. There were some general problems that we encountered in a Portal environment. The first was Struts depends on the servlet container to distinguish Struts actions from other requests, as it should. In a Portal server, the URLs use the servlet context of the configured Portal. The URL will have some additional information that the Portal server can use to determine which portlet the user is interacting with, and then some attributes for the portlet. We had to modify the tags that created URLs, like Form and Link, to create URLs to the Portal Server and then we added the Struts action, href, forward, etc as a request parameter. The portlet would then look at the parameter and determine whether to call the request processor because it was an action or include a jsp, for example. It would be a real convenience to create a hook in the tags to allow creating these custom URLs. We were able to subclass the link tags implementations and modify the tlds to use our version. That is fine, but I think Struts developers will want to create Struts applications that can be deployed in both a servlet and a portlet environment. Other changes that we needed dealt with the fact that in a Portal Server it is very easy to add a portlet to a page more than once. This could also be an issue when using Tiles as well. The problem that we encountered is the Struts form tag uses the name of the form bean as the form name. This name will not be unique if the same Struts application is added to the Portal page more than once. We had to namescope the name so it was unique, but that forced us to change the dynamic validation tags to also create unique names for the validation function. We also ran into issues with the response object. In Portal, the response object is committed by the time a portlet gets it, so we had to include instead of forward. The forward was convenient for many applications because you could forward to an action or a dynamic/static page. We recursively call the appropriate request processor for actions as needed and use an include if the URI was for a page. This also meant that pageContext.forward in a JSP would not function correctly, but that turned out not to be a big issue because of the logic forward tag which we could modify. This detail may be specific to my Portal Server. Portal also has two phase processing, as opposed to the servlet's one phase service method. There are some interesting design decisions that need to be made with how to map Struts processing with Portal's two phase processing. This is a feature in the JSR 168. The module support in Struts was very helpful to support the different modes in Portal. The portal mode could be used when selecting modules so the developer can create a Struts module for each of the portlet's mode, like view and edit. It was a nice application for Struts modules. Portlet modes are also part of the JSR. That's just an brief overview of some of the things we encountered, I don't want to bore this mailing list with all the details. - Original Message - From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, February 26, 2003 1:32 PM Subject: RE: Struts and Portlets > > > On Wed, 26 Feb 2003, PILGRIM, Peter, FM wrote: > > > > > > > Does anyone have a copy of the JSR 168 as a PDF or MS WORD document? > > > If you do, could you save > > > > I meant could you send me a copy of the draft specification document > > off list. Actually the last thing I do have on my work drive is a > > Power Point presentation from JavaOne 2002 on JSR 168. > > > > MTIA == many thanks in advance > > JSR168 has not yet gone to community draft, so the only folks who would > have such a document are EG members. You can get the current status of > the JSR at: > > http://jcp.org/en/jsr/detail?id=168 > > Craig > > - > To unsubscribe, e-mail: [EMAIL PRO
RE: Struts and Portlets
On Wed, 26 Feb 2003, Mete Kural wrote: > Date: Wed, 26 Feb 2003 11:08:59 -0800 (PST) > From: Mete Kural <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: RE: Struts and Portlets > > > JSR168 has not yet gone to community draft, so the > > only folks who would > > have such a document are EG members. You can get > > the current status of > > the JSR at: > > http://jcp.org/en/jsr/detail?id=168 > > On this page, it says that the public draft is > scheduled for March 2003 and the final draft is > scheduled for May 2003. Is this still the case or have > the deadlines changed? I thought they did and maybe > they forgot the update the status page accordingly. > I'm not on the 168 expert group, so can't answer that one for you -- best bet would be to send mail to the feedback address and ask. > > Craig > > -Mete Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts and Portlets
> JSR168 has not yet gone to community draft, so the > only folks who would > have such a document are EG members. You can get > the current status of > the JSR at: > http://jcp.org/en/jsr/detail?id=168 On this page, it says that the public draft is scheduled for March 2003 and the final draft is scheduled for May 2003. Is this still the case or have the deadlines changed? I thought they did and maybe they forgot the update the status page accordingly. > Craig -Mete > > - > 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]
RE: Struts and Portlets
On Wed, 26 Feb 2003, PILGRIM, Peter, FM wrote: > > > > Does anyone have a copy of the JSR 168 as a PDF or MS WORD document? > > If you do, could you save > > I meant could you send me a copy of the draft specification document > off list. Actually the last thing I do have on my work drive is a > Power Point presentation from JavaOne 2002 on JSR 168. > > MTIA == many thanks in advance JSR168 has not yet gone to community draft, so the only folks who would have such a document are EG members. You can get the current status of the JSR at: http://jcp.org/en/jsr/detail?id=168 Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Portlets
Hi Vic, > Sounds good to me. Good. You are welcome to start analyzing Liferay's source code then. You can either download the source zip archive available here http://sourceforge.net/project/showfiles.php?group_id=49260 or log in to the sourceforge cvs with this command: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/lportal login I prefer logging into the CVS with an IDE. When you have questions about the source, please ask them in the mailing list for which you can subscribe at http://lists.sourceforge.net/lists/listinfo/lportal-development Thank you, Mete > > Mete Kural wrote: > > Hi Vic, > > > > I read your proposal. As you say, I think it would > be > > great to provide Struts-based verticals under a > portal > > platform. In your proposal you have mentioned that > one > > of BasicPortal's goals is to provide a UI that is > > similar to my.netscape.com. I think that Liferay > has > > accomplished this and it also has pretty extensive > > personalization and administration features. > Please > > surf through the demo at my.liferay.com Log in as > the > > administrator so you can check out the > administration > > features as well: > > Login: [EMAIL PROTECTED] Pass: test > > > > Since now I am somewhat involved in both Liferay > and > > BasicPortal (although I have not yet contributed a > > single line of code to either of them) I can > clearly > > see that there is a common goal in both of these > > projects: providing an open-source "Struts-based" > > portal server. Both projects have their strengths. > > While BasicPortal has a good lightweight > persistence > > framework, Liferay has an extensive UI for > > personalization and administration. I suggest that > the > > best of both projects can be combined under a > brand > > new Jakarta subproject that would aim to provide a > > Struts-based alternative to JetSpeed. What do you > > think? > > > > -Mete > > > > --- Vic Cekvenich <[EMAIL PROTECTED]> wrote: > > > > > http://nagoya.apache.org/wiki/apachewiki.cgi?PortalProposal > > > >>Mete Kural wrote: > >> > >>>--- "Craig R. McClanahan" <[EMAIL PROTECTED]> > >> > >>wrote: > >> > There are certainly people in the > world who have done this sort of thing already > (Liferay, BasicPortal, etc.) for non-JSR-168 > portlet APIs, so it's clearly feasible, and it's > a > pretty good idea. But, from my perspective, > this > sort of thing is actually a Struts-based > application, rather than part of the framework > itself. > >>> > >>> > >>>Thanks for the insight. Now I understand what the > >> > >>role > >> > >>>of Struts would be regarding the Portlet API. In > >> > >>this > >> > >>>case I have another question to follow. If Struts > >> > >>will > >> > >>>hopefully provide a "framework for building > >>>Struts-based portlets", how do you find the idea > >> > >>of > >> > >>>cultivating interest for open-source programmers > >> > >>to > >> > >>>work on a Struts-based portal server under the > >> > >>Jakarta > >> > >>>umbrella? As you say, there are already people > who > >>>have implemented Struts-based non-JSR-168 portal > >>>servers such as Liferay and BasicPortal. I think > >> > >>that > >> > >>>it would be wonderful if there could be a joint > >> > >>effort > >> > >>>to create an open-source Struts-based portal > >> > >>server > >> > >>>under Jakarta, as an alternative to JetSpeed. > What > >> > >>do > >> > >>>you think? > >>> > >>>Thanks, > >>>Mete > >> > >> > >> > >> > > > - > > > >>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]
RE: Struts and Portlets
> -Original Message- > From: PILGRIM, Peter, FM ---- > > servlet container and a Servlet. As such, I think the best role for > > Struts is to answer the "how do you program a portlet" rather > > than "how do > > I build a portal server". > > > > ---- > > Does anyone have a copy of the JSR 168 as a PDF or MS WORD document? > If you do, could you save I meant could you send me a copy of the draft specification document off list. Actually the last thing I do have on my work drive is a Power Point presentation from JavaOne 2002 on JSR 168. MTIA == many thanks in advance -- Peter Pilgrim, Struts/J2EE Consultant, RBoS FM, Risk IT Tel: +44 (0)207-375-4923 *** Visit our Internet site at http://www.rbsmarkets.com This e-mail is intended only for the addressee named above. As this e-mail may contain confidential or privileged information, if you are not the named addressee, you are not authorised to retain, read, copy or disseminate this message or any part of it. The Royal Bank of Scotland plc is registered in Scotland No 90312 Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB Regulated by the Financial Services Authority *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts and Portlets
> -Original Message- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] > > > On Tue, 25 Feb 2003, Mete Kural wrote: > > > From: Mete Kural <[EMAIL PROTECTED]> ---- > > > > --- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > > > I'm definitely interested in making it possible to > > > reuse Struts-based > > > webapp things (actions, form beans, pages, business > > > logic) in a portlet. > > > That's going to take some refactoring and > > > abstraction of the fundamental > > > APIs -- but it's definitely going to be worth doing. > > > > Craig, what would be the scope of implementing the > > Portlet API in Struts? Would it encompass implementing > > some features of a portal server? Do you think it is > > practical to provide a portal server platform within > > Struts? > > > > The result of JSR 168 is going to be an API contract between a portal > server and a portlet -- much like the Servlet API contract between a > servlet container and a Servlet. As such, I think the best role for > Struts is to answer the "how do you program a portlet" rather > than "how do > I build a portal server". > ---- Does anyone have a copy of the JSR 168 as a PDF or MS WORD document? If you do, could you save -- Peter Pilgrim, Struts/J2EE Consultant, RBoS FM, Risk IT Tel: +44 (0)207-375-4923 *** Visit our Internet site at http://www.rbsmarkets.com This e-mail is intended only for the addressee named above. As this e-mail may contain confidential or privileged information, if you are not the named addressee, you are not authorised to retain, read, copy or disseminate this message or any part of it. The Royal Bank of Scotland plc is registered in Scotland No 90312 Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB Regulated by the Financial Services Authority *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts and Portlets
Hi John, Actually Liferay does not force you to use Orion. The intention was to make Liferay both application server and database agnostic. Since Liferay developers themselves use Orion as the development application server the directory structure in the CVS may have given you the wrong impression. The source for Liferay is available in a zip file in the Sourceforge download page. But it is true that the modification and compilation of source can be made more convenient. This could be one of the goals in a joint Jakarta subproject. Of course if the Apache people admit the project to Jakarta. I think that the persistence layer of Liferay could be vastly improved. It should be made much easier to customize, i.e. change the underlying tables, database system, or even use a J2EE resource adaptor instead of the JDBC API. This is one of the things you guys working on BasicPortal are good at: persistence. So you could help improve the persistence layer. -Mete --- John Menke <[EMAIL PROTECTED]> wrote: > I tried to use Liferay the other day and they force > you to use Orion and get > the CVS if you want the code. otherwise all you get > is the compiled stuff. > We would have to get them to change that but I would > be interesting in > seeing what could be done to integrate the two > projects > > > -Original Message- > > From: Vic Cekvenich [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, February 25, 2003 4:56 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Struts and Portlets > > > > > > Sounds good to me. > > > > Mete Kural wrote: > > > Hi Vic, > > > > > > I read your proposal. As you say, I think it > would be > > > great to provide Struts-based verticals under a > portal > > > platform. In your proposal you have mentioned > that one > > > of BasicPortal's goals is to provide a UI that > is > > > similar to my.netscape.com. I think that Liferay > has > > > accomplished this and it also has pretty > extensive > > > personalization and administration features. > Please > > > surf through the demo at my.liferay.com Log in > as the > > > administrator so you can check out the > administration > > > features as well: > > > Login: [EMAIL PROTECTED] Pass: test > > > > > > Since now I am somewhat involved in both Liferay > and > > > BasicPortal (although I have not yet contributed > a > > > single line of code to either of them) I can > clearly > > > see that there is a common goal in both of these > > > projects: providing an open-source > "Struts-based" > > > portal server. Both projects have their > strengths. > > > While BasicPortal has a good lightweight > persistence > > > framework, Liferay has an extensive UI for > > > personalization and administration. I suggest > that the > > > best of both projects can be combined under a > brand > > > new Jakarta subproject that would aim to provide > a > > > Struts-based alternative to JetSpeed. What do > you > > > think? > > > > > > -Mete > > > > > > --- Vic Cekvenich <[EMAIL PROTECTED]> wrote: > > > > > > > http://nagoya.apache.org/wiki/apachewiki.cgi?PortalProposal > > > > > >>Mete Kural wrote: > > >> > > >>>--- "Craig R. McClanahan" <[EMAIL PROTECTED]> > > >> > > >>wrote: > > >> > > >>>>There are certainly people in the > > >>>>world who have done this sort of thing already > > >>>>(Liferay, BasicPortal, etc.) for non-JSR-168 > > >>>>portlet APIs, so it's clearly feasible, and > it's a > > >>>>pretty good idea. But, from my perspective, > this > > >>>>sort of thing is actually a Struts-based > > >>>>application, rather than part of the framework > > >>>>itself. > > >>> > > >>> > > >>>Thanks for the insight. Now I understand what > the > > >> > > >>role > > >> > > >>>of Struts would be regarding the Portlet API. > In > > >> > > >>this > > >> > > >>>case I have another question to follow. If > Struts > > >> > > >>will > > >> > > >>>hopefully provide a "framework for building > > >>>Struts-based portlets", how do you find the > idea > > >> > > >>of > > >> > > >>&
RE: Struts and Portlets
I tried to use Liferay the other day and they force you to use Orion and get the CVS if you want the code. otherwise all you get is the compiled stuff. We would have to get them to change that but I would be interesting in seeing what could be done to integrate the two projects > -Original Message- > From: Vic Cekvenich [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 25, 2003 4:56 PM > To: [EMAIL PROTECTED] > Subject: Re: Struts and Portlets > > > Sounds good to me. > > Mete Kural wrote: > > Hi Vic, > > > > I read your proposal. As you say, I think it would be > > great to provide Struts-based verticals under a portal > > platform. In your proposal you have mentioned that one > > of BasicPortal's goals is to provide a UI that is > > similar to my.netscape.com. I think that Liferay has > > accomplished this and it also has pretty extensive > > personalization and administration features. Please > > surf through the demo at my.liferay.com Log in as the > > administrator so you can check out the administration > > features as well: > > Login: [EMAIL PROTECTED] Pass: test > > > > Since now I am somewhat involved in both Liferay and > > BasicPortal (although I have not yet contributed a > > single line of code to either of them) I can clearly > > see that there is a common goal in both of these > > projects: providing an open-source "Struts-based" > > portal server. Both projects have their strengths. > > While BasicPortal has a good lightweight persistence > > framework, Liferay has an extensive UI for > > personalization and administration. I suggest that the > > best of both projects can be combined under a brand > > new Jakarta subproject that would aim to provide a > > Struts-based alternative to JetSpeed. What do you > > think? > > > > -Mete > > > > --- Vic Cekvenich <[EMAIL PROTECTED]> wrote: > > > > http://nagoya.apache.org/wiki/apachewiki.cgi?PortalProposal > > > >>Mete Kural wrote: > >> > >>>--- "Craig R. McClanahan" <[EMAIL PROTECTED]> > >> > >>wrote: > >> > >>>>There are certainly people in the > >>>>world who have done this sort of thing already > >>>>(Liferay, BasicPortal, etc.) for non-JSR-168 > >>>>portlet APIs, so it's clearly feasible, and it's a > >>>>pretty good idea. But, from my perspective, this > >>>>sort of thing is actually a Struts-based > >>>>application, rather than part of the framework > >>>>itself. > >>> > >>> > >>>Thanks for the insight. Now I understand what the > >> > >>role > >> > >>>of Struts would be regarding the Portlet API. In > >> > >>this > >> > >>>case I have another question to follow. If Struts > >> > >>will > >> > >>>hopefully provide a "framework for building > >>>Struts-based portlets", how do you find the idea > >> > >>of > >> > >>>cultivating interest for open-source programmers > >> > >>to > >> > >>>work on a Struts-based portal server under the > >> > >>Jakarta > >> > >>>umbrella? As you say, there are already people who > >>>have implemented Struts-based non-JSR-168 portal > >>>servers such as Liferay and BasicPortal. I think > >> > >>that > >> > >>>it would be wonderful if there could be a joint > >> > >>effort > >> > >>>to create an open-source Struts-based portal > >> > >>server > >> > >>>under Jakarta, as an alternative to JetSpeed. What > >> > >>do > >> > >>>you think? > >>> > >>>Thanks, > >>>Mete > >> > >> > >> > >> > > - > > > >>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]
Re: Struts and Portlets
Sounds good to me. Mete Kural wrote: Hi Vic, I read your proposal. As you say, I think it would be great to provide Struts-based verticals under a portal platform. In your proposal you have mentioned that one of BasicPortal's goals is to provide a UI that is similar to my.netscape.com. I think that Liferay has accomplished this and it also has pretty extensive personalization and administration features. Please surf through the demo at my.liferay.com Log in as the administrator so you can check out the administration features as well: Login: [EMAIL PROTECTED] Pass: test Since now I am somewhat involved in both Liferay and BasicPortal (although I have not yet contributed a single line of code to either of them) I can clearly see that there is a common goal in both of these projects: providing an open-source "Struts-based" portal server. Both projects have their strengths. While BasicPortal has a good lightweight persistence framework, Liferay has an extensive UI for personalization and administration. I suggest that the best of both projects can be combined under a brand new Jakarta subproject that would aim to provide a Struts-based alternative to JetSpeed. What do you think? -Mete --- Vic Cekvenich <[EMAIL PROTECTED]> wrote: http://nagoya.apache.org/wiki/apachewiki.cgi?PortalProposal Mete Kural wrote: --- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: There are certainly people in the world who have done this sort of thing already (Liferay, BasicPortal, etc.) for non-JSR-168 portlet APIs, so it's clearly feasible, and it's a pretty good idea. But, from my perspective, this sort of thing is actually a Struts-based application, rather than part of the framework itself. Thanks for the insight. Now I understand what the role of Struts would be regarding the Portlet API. In this case I have another question to follow. If Struts will hopefully provide a "framework for building Struts-based portlets", how do you find the idea of cultivating interest for open-source programmers to work on a Struts-based portal server under the Jakarta umbrella? As you say, there are already people who have implemented Struts-based non-JSR-168 portal servers such as Liferay and BasicPortal. I think that it would be wonderful if there could be a joint effort to create an open-source Struts-based portal server under Jakarta, as an alternative to JetSpeed. What do you think? Thanks, Mete - 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]
Re: Struts and Portlets
Hi Vic, I read your proposal. As you say, I think it would be great to provide Struts-based verticals under a portal platform. In your proposal you have mentioned that one of BasicPortal's goals is to provide a UI that is similar to my.netscape.com. I think that Liferay has accomplished this and it also has pretty extensive personalization and administration features. Please surf through the demo at my.liferay.com Log in as the administrator so you can check out the administration features as well: Login: [EMAIL PROTECTED] Pass: test Since now I am somewhat involved in both Liferay and BasicPortal (although I have not yet contributed a single line of code to either of them) I can clearly see that there is a common goal in both of these projects: providing an open-source "Struts-based" portal server. Both projects have their strengths. While BasicPortal has a good lightweight persistence framework, Liferay has an extensive UI for personalization and administration. I suggest that the best of both projects can be combined under a brand new Jakarta subproject that would aim to provide a Struts-based alternative to JetSpeed. What do you think? -Mete --- Vic Cekvenich <[EMAIL PROTECTED]> wrote: > http://nagoya.apache.org/wiki/apachewiki.cgi?PortalProposal > > Mete Kural wrote: > > --- "Craig R. McClanahan" <[EMAIL PROTECTED]> > wrote: > > > >>There are certainly people in the > >>world who have done this sort of thing already > >>(Liferay, BasicPortal, etc.) for non-JSR-168 > >>portlet APIs, so it's clearly feasible, and it's a > >>pretty good idea. But, from my perspective, this > >>sort of thing is actually a Struts-based > >>application, rather than part of the framework > >>itself. > > > > > > Thanks for the insight. Now I understand what the > role > > of Struts would be regarding the Portlet API. In > this > > case I have another question to follow. If Struts > will > > hopefully provide a "framework for building > > Struts-based portlets", how do you find the idea > of > > cultivating interest for open-source programmers > to > > work on a Struts-based portal server under the > Jakarta > > umbrella? As you say, there are already people who > > have implemented Struts-based non-JSR-168 portal > > servers such as Liferay and BasicPortal. I think > that > > it would be wonderful if there could be a joint > effort > > to create an open-source Struts-based portal > server > > under Jakarta, as an alternative to JetSpeed. What > do > > you think? > > > > Thanks, > > Mete > > > > - > 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]
Re: Struts and Portlets
http://nagoya.apache.org/wiki/apachewiki.cgi?PortalProposal Mete Kural wrote: --- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: There are certainly people in the world who have done this sort of thing already (Liferay, BasicPortal, etc.) for non-JSR-168 portlet APIs, so it's clearly feasible, and it's a pretty good idea. But, from my perspective, this sort of thing is actually a Struts-based application, rather than part of the framework itself. Thanks for the insight. Now I understand what the role of Struts would be regarding the Portlet API. In this case I have another question to follow. If Struts will hopefully provide a "framework for building Struts-based portlets", how do you find the idea of cultivating interest for open-source programmers to work on a Struts-based portal server under the Jakarta umbrella? As you say, there are already people who have implemented Struts-based non-JSR-168 portal servers such as Liferay and BasicPortal. I think that it would be wonderful if there could be a joint effort to create an open-source Struts-based portal server under Jakarta, as an alternative to JetSpeed. What do you think? Thanks, Mete - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Portlets
--- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > There are certainly people in the > world who have done this sort of thing already > (Liferay, BasicPortal, etc.) for non-JSR-168 > portlet APIs, so it's clearly feasible, and it's a > pretty good idea. But, from my perspective, this > sort of thing is actually a Struts-based > application, rather than part of the framework > itself. Thanks for the insight. Now I understand what the role of Struts would be regarding the Portlet API. In this case I have another question to follow. If Struts will hopefully provide a "framework for building Struts-based portlets", how do you find the idea of cultivating interest for open-source programmers to work on a Struts-based portal server under the Jakarta umbrella? As you say, there are already people who have implemented Struts-based non-JSR-168 portal servers such as Liferay and BasicPortal. I think that it would be wonderful if there could be a joint effort to create an open-source Struts-based portal server under Jakarta, as an alternative to JetSpeed. What do you think? Thanks, Mete - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Portlets
On Tue, 25 Feb 2003, Mete Kural wrote: > Date: Tue, 25 Feb 2003 09:31:36 -0800 (PST) > From: Mete Kural <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: Re: Struts and Portlets > > --- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > > I'm definitely interested in making it possible to > > reuse Struts-based > > webapp things (actions, form beans, pages, business > > logic) in a portlet. > > That's going to take some refactoring and > > abstraction of the fundamental > > APIs -- but it's definitely going to be worth doing. > > Craig, what would be the scope of implementing the > Portlet API in Struts? Would it encompass implementing > some features of a portal server? Do you think it is > practical to provide a portal server platform within > Struts? > The result of JSR 168 is going to be an API contract between a portal server and a portlet -- much like the Servlet API contract between a servlet container and a Servlet. As such, I think the best role for Struts is to answer the "how do you program a portlet" rather than "how do I build a portal server". The analogy in the servlet space is that there's no need for Struts to implement the servlet API, since lots of containers (including Tomcat) do that for you. Instead, I want to make it possible to write Struts-based portlets that can run on *anyone's* portal server that supports JSR-168. That doesn't mean we have to write the portal server itself -- it means we need to implement the portlet API analog of what ActionServlet does for servlet requests. Now, another interesting question is "can I build a portal server based on Struts that can then incorporate JSR-168 portlets?" The thinking is that you could use Tiles and other Struts based features to manage the aggregation that portal servers do. There are certainly people in the world who have done this sort of thing already (Liferay, BasicPortal, etc.) for non-JSR-168 portlet APIs, so it's clearly feasible, and it's a pretty good idea. But, from my perspective, this sort of thing is actually a Struts-based application, rather than part of the framework itself. > Thanks, > Mete Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Portlets
--- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > I'm definitely interested in making it possible to > reuse Struts-based > webapp things (actions, form beans, pages, business > logic) in a portlet. > That's going to take some refactoring and > abstraction of the fundamental > APIs -- but it's definitely going to be worth doing. Craig, what would be the scope of implementing the Portlet API in Struts? Would it encompass implementing some features of a portal server? Do you think it is practical to provide a portal server platform within Struts? Thanks, Mete - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Portlets
On Tue, 25 Feb 2003 [EMAIL PROTECTED] wrote: > Date: Tue, 25 Feb 2003 07:52:38 +0100 > From: [EMAIL PROTECTED] > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Struts and Portlets > > Hi, > > is there an intention to implement the JSR-168 (Portlet API) into > struts? > I'm definitely interested in making it possible to reuse Struts-based webapp things (actions, form beans, pages, business logic) in a portlet. That's going to take some refactoring and abstraction of the fundamental APIs -- but it's definitely going to be worth doing. Craig McClanahan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE: Struts and Portlets
Liferay has not yet implemented JSR-168 completely. This is because the specs keep on changing still. Once the specs become fairly stabilized, a.k.a. once JSR-168 hits the community, the Portlet API is intended to be implemented fully. As our friend said, Liferay is an implementation of an enterprise portal server, similar to Plumtree and Epicentric. -Mete --- [EMAIL PROTECTED] wrote: > My fault, I guess I needed a couple more cups of > coffee before typing up my response. Liferay has > implemented an enterprise portal, which uses Struts > 1.b2. As for their adherence to the fore mentioned > spec, JSR-168, I am not sure. > > Sorry for the misinformation. > > Todd > > > > > From: "Mitchell Morris" <[EMAIL PROTECTED]> > > Date: 2003/02/25 Tue AM 11:11:55 EST > > To: "'Struts Users Mailing List'" > <[EMAIL PROTECTED]> > > Subject: RE: Struts and Portlets > > > > Ummm ... JSR-168 is still being held under NDA. > Their page > > (http://www.jcp.org/en/jsr/detail?id=168) says > that they'll expose the spec > > in March sometime. How did you get a copy of the > spec in advance, and aren't > > you concerned about violating the NDA? Also, can > we look at the spec too? > > I'm exceedingly curious to see what's in it. > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, February 25, 2003 7:02 AM > > > To: Struts Users Mailing List > > > Subject: Re: Struts and Portlets > > > > > > > > > You could take a look at www.liferay.com, there > latest > > > implementation (1.8) follows the Porlet Spec, > JSR-168, and is > > > using Struts 1.1b2. > > > > > > Regards, > > > Todd G. Nist > > > > > > > > > > > From: [EMAIL PROTECTED] > > > > Date: 2003/02/25 Tue AM 01:52:38 EST > > > > To: [EMAIL PROTECTED] > > > > Subject: Struts and Portlets > > > > > > > > Hi, > > > > > > > > is there an intention to implement the JSR-168 > (Portlet > > > API) into struts? > > > > > > > > In my opinion three important features like > multiple output > > > formats with XSLT, workflows and the support of > portlets > > > would be very important for the future. > > > > > > > > The ability to create standardised portlets > with struts > > > would be very interesting. I think the the > actions and jsp > > > are not much mightful for the future. The > development of the > > > jsp/action with tiles a.s.o. is fine but too > slow and theres > > > still a limited reuse. In my opinion there > should/could be > > > more abstraction for project comprehensive > reuse. Such > > > portlets could create configurable components > with > > > jsp/actions and beans. I dont have access to the > portlets > > > specification, but I am sure that this aspects > are included there. > > > > > > > > Any comments? > > > > > > > > Juraj > > > > > > > > > > > > > > > > > > > > > > > > - > > > > 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] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE: Struts and Portlets
My fault, I guess I needed a couple more cups of coffee before typing up my response. Liferay has implemented an enterprise portal, which uses Struts 1.b2. As for their adherence to the fore mentioned spec, JSR-168, I am not sure. Sorry for the misinformation. Todd > > From: "Mitchell Morris" <[EMAIL PROTECTED]> > Date: 2003/02/25 Tue AM 11:11:55 EST > To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> > Subject: RE: Struts and Portlets > > Ummm ... JSR-168 is still being held under NDA. Their page > (http://www.jcp.org/en/jsr/detail?id=168) says that they'll expose the spec > in March sometime. How did you get a copy of the spec in advance, and aren't > you concerned about violating the NDA? Also, can we look at the spec too? > I'm exceedingly curious to see what's in it. > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, February 25, 2003 7:02 AM > > To: Struts Users Mailing List > > Subject: Re: Struts and Portlets > > > > > > You could take a look at www.liferay.com, there latest > > implementation (1.8) follows the Porlet Spec, JSR-168, and is > > using Struts 1.1b2. > > > > Regards, > > Todd G. Nist > > > > > > > > From: [EMAIL PROTECTED] > > > Date: 2003/02/25 Tue AM 01:52:38 EST > > > To: [EMAIL PROTECTED] > > > Subject: Struts and Portlets > > > > > > Hi, > > > > > > is there an intention to implement the JSR-168 (Portlet > > API) into struts? > > > > > > In my opinion three important features like multiple output > > formats with XSLT, workflows and the support of portlets > > would be very important for the future. > > > > > > The ability to create standardised portlets with struts > > would be very interesting. I think the the actions and jsp > > are not much mightful for the future. The development of the > > jsp/action with tiles a.s.o. is fine but too slow and theres > > still a limited reuse. In my opinion there should/could be > > more abstraction for project comprehensive reuse. Such > > portlets could create configurable components with > > jsp/actions and beans. I dont have access to the portlets > > specification, but I am sure that this aspects are included there. > > > > > > Any comments? > > > > > > Juraj > > > > > > > > > > > > > > > > > - > > > 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]
RE: Struts and Portlets
We believe that Struts together with other best-of-breed loosely connected components without hard connections to any engines such as the ones in JetSpeed will be best to implement JSR-168. Obviously, we have to wait for Reference Implementation of JSR-168. This topic will be hot. BaTien === -Original Message- From: Mitchell Morris [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 25, 2003 9:12 AM To: 'Struts Users Mailing List' Subject: RE: Struts and Portlets Ummm ... JSR-168 is still being held under NDA. Their page (http://www.jcp.org/en/jsr/detail?id=168) says that they'll expose the spec in March sometime. How did you get a copy of the spec in advance, and aren't you concerned about violating the NDA? Also, can we look at the spec too? I'm exceedingly curious to see what's in it. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 25, 2003 7:02 AM > To: Struts Users Mailing List > Subject: Re: Struts and Portlets > > > You could take a look at www.liferay.com, there latest > implementation (1.8) follows the Porlet Spec, JSR-168, and is > using Struts 1.1b2. > > Regards, > Todd G. Nist > > > > > From: [EMAIL PROTECTED] > > Date: 2003/02/25 Tue AM 01:52:38 EST > > To: [EMAIL PROTECTED] > > Subject: Struts and Portlets > > > > Hi, > > > > is there an intention to implement the JSR-168 (Portlet > API) into struts? > > > > In my opinion three important features like multiple output > formats with XSLT, workflows and the support of portlets > would be very important for the future. > > > > The ability to create standardised portlets with struts > would be very interesting. I think the the actions and jsp > are not much mightful for the future. The development of the > jsp/action with tiles a.s.o. is fine but too slow and theres > still a limited reuse. In my opinion there should/could be > more abstraction for project comprehensive reuse. Such > portlets could create configurable components with > jsp/actions and beans. I dont have access to the portlets > specification, but I am sure that this aspects are included there. > > > > Any comments? > > > > Juraj > > > > > > > > > > > - > > 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]
AW: Struts and Portlets
Hi Mitchell, I dont have it. I expect that some features are included. Juraj -Ursprüngliche Nachricht- Von: Mitchell Morris [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 25. Februar 2003 17:12 An: 'Struts Users Mailing List' Betreff: RE: Struts and Portlets Ummm ... JSR-168 is still being held under NDA. Their page (http://www.jcp.org/en/jsr/detail?id=168) says that they'll expose the spec in March sometime. How did you get a copy of the spec in advance, and aren't you concerned about violating the NDA? Also, can we look at the spec too? I'm exceedingly curious to see what's in it. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 25, 2003 7:02 AM > To: Struts Users Mailing List > Subject: Re: Struts and Portlets > > > You could take a look at www.liferay.com, there latest > implementation (1.8) follows the Porlet Spec, JSR-168, and is > using Struts 1.1b2. > > Regards, > Todd G. Nist > > > > > From: [EMAIL PROTECTED] > > Date: 2003/02/25 Tue AM 01:52:38 EST > > To: [EMAIL PROTECTED] > > Subject: Struts and Portlets > > > > Hi, > > > > is there an intention to implement the JSR-168 (Portlet > API) into struts? > > > > In my opinion three important features like multiple output > formats with XSLT, workflows and the support of portlets > would be very important for the future. > > > > The ability to create standardised portlets with struts > would be very interesting. I think the the actions and jsp > are not much mightful for the future. The development of the > jsp/action with tiles a.s.o. is fine but too slow and theres > still a limited reuse. In my opinion there should/could be > more abstraction for project comprehensive reuse. Such > portlets could create configurable components with > jsp/actions and beans. I dont have access to the portlets > specification, but I am sure that this aspects are included there. > > > > Any comments? > > > > Juraj > > > > > > > > > > > - > > 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]
RE: Struts and Portlets
Ummm ... JSR-168 is still being held under NDA. Their page (http://www.jcp.org/en/jsr/detail?id=168) says that they'll expose the spec in March sometime. How did you get a copy of the spec in advance, and aren't you concerned about violating the NDA? Also, can we look at the spec too? I'm exceedingly curious to see what's in it. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 25, 2003 7:02 AM > To: Struts Users Mailing List > Subject: Re: Struts and Portlets > > > You could take a look at www.liferay.com, there latest > implementation (1.8) follows the Porlet Spec, JSR-168, and is > using Struts 1.1b2. > > Regards, > Todd G. Nist > > > > > From: [EMAIL PROTECTED] > > Date: 2003/02/25 Tue AM 01:52:38 EST > > To: [EMAIL PROTECTED] > > Subject: Struts and Portlets > > > > Hi, > > > > is there an intention to implement the JSR-168 (Portlet > API) into struts? > > > > In my opinion three important features like multiple output > formats with XSLT, workflows and the support of portlets > would be very important for the future. > > > > The ability to create standardised portlets with struts > would be very interesting. I think the the actions and jsp > are not much mightful for the future. The development of the > jsp/action with tiles a.s.o. is fine but too slow and theres > still a limited reuse. In my opinion there should/could be > more abstraction for project comprehensive reuse. Such > portlets could create configurable components with > jsp/actions and beans. I dont have access to the portlets > specification, but I am sure that this aspects are included there. > > > > Any comments? > > > > Juraj > > > > > > > > > > > - > > 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]
Re: Struts and Portlets
You could take a look at www.liferay.com, there latest implementation (1.8) follows the Porlet Spec, JSR-168, and is using Struts 1.1b2. Regards, Todd G. Nist > > From: [EMAIL PROTECTED] > Date: 2003/02/25 Tue AM 01:52:38 EST > To: [EMAIL PROTECTED] > Subject: Struts and Portlets > > Hi, > > is there an intention to implement the JSR-168 (Portlet API) into struts? > > In my opinion three important features like multiple output formats with XSLT, > workflows and the support of portlets would be very important for the future. > > The ability to create standardised portlets with struts would be very interesting. I > think the the actions and jsp are not much mightful for the future. The development > of the jsp/action with tiles a.s.o. is fine but too slow and theres still a limited > reuse. In my opinion there should/could be more abstraction for project > comprehensive reuse. Such portlets could create configurable components with > jsp/actions and beans. I dont have access to the portlets specification, but I am > sure that this aspects are included there. > > Any comments? > > Juraj > > > > > - > 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]
Re: Struts and Portlets
I found JSR-168 lacking. I have been using "Tile 201" like things for a long time to give me a lite and fast version of "Portlets" features. http://blogs.browsermedia.com/patrick/index.do?date=20030211#130200 .V [EMAIL PROTECTED] wrote: Hi, is there an intention to implement the JSR-168 (Portlet API) into struts? In my opinion three important features like multiple output formats with XSLT, workflows and the support of portlets would be very important for the future. The ability to create standardised portlets with struts would be very interesting. I think the the actions and jsp are not much mightful for the future. The development of the jsp/action with tiles a.s.o. is fine but too slow and theres still a limited reuse. In my opinion there should/could be more abstraction for project comprehensive reuse. Such portlets could create configurable components with jsp/actions and beans. I dont have access to the portlets specification, but I am sure that this aspects are included there. Any comments? Juraj - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Struts and Portlets
Hi, is there an intention to implement the JSR-168 (Portlet API) into struts? In my opinion three important features like multiple output formats with XSLT, workflows and the support of portlets would be very important for the future. The ability to create standardised portlets with struts would be very interesting. I think the the actions and jsp are not much mightful for the future. The development of the jsp/action with tiles a.s.o. is fine but too slow and theres still a limited reuse. In my opinion there should/could be more abstraction for project comprehensive reuse. Such portlets could create configurable components with jsp/actions and beans. I dont have access to the portlets specification, but I am sure that this aspects are included there. Any comments? Juraj - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Struts and Portlets
Hi There, Do you know if Struts and Portlets are compatible concepts? I don´t know enough about Portlets, but I know it´s a framework responsable for mounting a unified view from distinct applications (the portlets are the views for these applications). IBM has a framework for portals, and I would like to know if I can use struts with it. Thanks for any information, Rodrigo. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
