Re: Struts and Jetspeed
BaTien Duong wrote: Craig R. McClanahan wrote: SNIP There is also an implicit non-goal that I should state explicitly -- I'm totally uninterested in building in (to Struts) support for non-JSR 168 based portal servers -- be they open source ones like Jetspeed or commercial ones (BEA, IBM, Oracle, Sun, whatever). This is for the same reason that I'm not interested in supporting any non-Servlet-API variant on servlets -- that's not where the market is. Providers of non-168 portal servers are welcome to provide their own adaptations of they want to, and several of them already do. Fortunately, all of the servers portal mentioned above (including Jetspeed) are planning to provide JSR-168 compatible support, so implementing 168 support into Struts is instantly useful on all of them. That's the power of common standards. SNIP many Struts developers (i know at least a number of Portals based on Struts-Tiles, all except basic portal, stating to support JSR-168) (i am one of them) will seriously put some time in this refactoring process. Yep ... JSR-168 is going to be a very popular API, quite likely rivalling servlet in the number of server choices people will have. And supporting it gracefully in Struts means you'll be able to deploy a Struts based app using either servlet or portlet based servers, depending on your needs, with minimal changes. Thanks for this forcefull statement that indicates the right leadership. I totally agree with this. That is why i think Struts with the best design and least burden of past technologies is the best candidate to realize the importance of JSR-168 Portal/Portlet container and WSRP for later stage. Hope many developers / designers will join in to realize the benefits of industry standards. BaTien DBGROUPS SNIP (Funny how we talk past each other). If people want to market JetSlow w/ JSF (and add on EJB even ) against bP OK, more competition means better sofware. I market to companies that also have non Java, and want some code to execute in a browser (like Struts Menu, Validator and now Calendar tag do) and like high scalability, and easy to build. I kind of look at PHP forums, Nukes, Zope, Plone, MS Sharepoint etc. Non of them will support Portlet API either. JCP 168 and 127 are Sun standards and might not become a popular standard. ( http://finance.yahoo.com/q?s=SUNWd=ck=c2a=vp=e5,m20,m100,m200,e200t=2yl=offz=lq=l ) To say that you could take Portlet writen in BEA to IBM... when this can't be done for EJB (if your resume says IBM EJB, you can't get a BEA EJB gig) and who would want to go from IBM to BEA... mostly people go from Java to C# or Javascript. That IS cross platform: http://www.xmlrpc.com/directory/1568/implementations (but... if you like JetSpeed and the JCP Portlet API, I would think you would/should use it w/JSF and not (simpler) Struts). By some definition, Struts is not a JCP standard, but it is a *defacto standard*. So JSF + Portlet are JCP Sun stanadrds (and Struts is not JCP, neither is iBaits or Hibrenate people still use them a lot in production ... not like some API that do not make it to production) So what vendors think is cross plafrom and standard is not what clients I work with consider standard or cross platform. I like KISS architecture, so as long as I am able to sell that, it works for me. bP (aka best Practice) example forums writen in Struts with display tag pagination, (and TilesAction, not JetSlow) WIP: http://basicportal.com/do/articleLstPg?ID=1 (bP is free for open source and free for small start ups... and VERY cheap for others, Struts training available. It is all Struts examples, so you can write your own standard modules quick like) wishing you best of everything, -- Vic Cekvenich, Struts Instructor, 1-215-312-9146 Advanced a href =baseBeans.comStruts Training/a, mentoring and project recovery in North East. Struts conversion and a href =baseBeans.com fixed bid development/a. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Jetspeed
Vic: I like your practical approaches as well, and share part of it. Keep express yourself freely. We need many *frank* discussions to keep things moving in a proper perspective. Best regards BaTien DBGROUPS Vic Cekvenich wrote: BaTien Duong wrote: Craig R. McClanahan wrote: SNIP There is also an implicit non-goal that I should state explicitly -- I'm totally uninterested in building in (to Struts) support for non-JSR 168 based portal servers -- be they open source ones like Jetspeed or commercial ones (BEA, IBM, Oracle, Sun, whatever). This is for the same reason that I'm not interested in supporting any non-Servlet-API variant on servlets -- that's not where the market is. Providers of non-168 portal servers are welcome to provide their own adaptations of they want to, and several of them already do. Fortunately, all of the servers portal mentioned above (including Jetspeed) are planning to provide JSR-168 compatible support, so implementing 168 support into Struts is instantly useful on all of them. That's the power of common standards. SNIP many Struts developers (i know at least a number of Portals based on Struts-Tiles, all except basic portal, stating to support JSR-168) (i am one of them) will seriously put some time in this refactoring process. Yep ... JSR-168 is going to be a very popular API, quite likely rivalling servlet in the number of server choices people will have. And supporting it gracefully in Struts means you'll be able to deploy a Struts based app using either servlet or portlet based servers, depending on your needs, with minimal changes. Thanks for this forcefull statement that indicates the right leadership. I totally agree with this. That is why i think Struts with the best design and least burden of past technologies is the best candidate to realize the importance of JSR-168 Portal/Portlet container and WSRP for later stage. Hope many developers / designers will join in to realize the benefits of industry standards. BaTien DBGROUPS SNIP (Funny how we talk past each other). If people want to market JetSlow w/ JSF (and add on EJB even ) against bP OK, more competition means better sofware. I market to companies that also have non Java, and want some code to execute in a browser (like Struts Menu, Validator and now Calendar tag do) and like high scalability, and easy to build. I kind of look at PHP forums, Nukes, Zope, Plone, MS Sharepoint etc. Non of them will support Portlet API either. JCP 168 and 127 are Sun standards and might not become a popular standard. ( http://finance.yahoo.com/q?s=SUNWd=ck=c2a=vp=e5,m20,m100,m200,e200t=2yl=offz=lq=l ) To say that you could take Portlet writen in BEA to IBM... when this can't be done for EJB (if your resume says IBM EJB, you can't get a BEA EJB gig) and who would want to go from IBM to BEA... mostly people go from Java to C# or Javascript. That IS cross platform: http://www.xmlrpc.com/directory/1568/implementations (but... if you like JetSpeed and the JCP Portlet API, I would think you would/should use it w/JSF and not (simpler) Struts). By some definition, Struts is not a JCP standard, but it is a *defacto standard*. So JSF + Portlet are JCP Sun stanadrds (and Struts is not JCP, neither is iBaits or Hibrenate people still use them a lot in production ... not like some API that do not make it to production) So what vendors think is cross plafrom and standard is not what clients I work with consider standard or cross platform. I like KISS architecture, so as long as I am able to sell that, it works for me. bP (aka best Practice) example forums writen in Struts with display tag pagination, (and TilesAction, not JetSlow) WIP: http://basicportal.com/do/articleLstPg?ID=1 (bP is free for open source and free for small start ups... and VERY cheap for others, Struts training available. It is all Struts examples, so you can write your own standard modules quick like) wishing you best of everything, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Jetspeed
Craig R. McClanahan wrote: On Wed, 20 Aug 2003, BaTien Duong wrote: Date: Wed, 20 Aug 2003 13:31:17 -0600 From: BaTien Duong [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Subject: Re: Struts and Jetspeed Emerson Cargnin wrote: any advice in choosing tiles vs jetspeedy? I suppose tiles integrates better, but at the other side jettyspeed follows the portlets specification. Any other comments? It is still too early to tell. I believe in simplicity and the right design that up to now Struts-Tiles give us elegant controller-templating engine. Craig has stated his ideal goal for developing Struts to work with JSR-168. The challenge is to have something like tiles as a template engine according to JSR-168 specifications for Portal / Portlet container(s). There is also an implicit non-goal that I should state explicitly -- I'm totally uninterested in building in (to Struts) support for non-JSR 168 based portal servers -- be they open source ones like Jetspeed or commercial ones (BEA, IBM, Oracle, Sun, whatever). This is for the same reason that I'm not interested in supporting any non-Servlet-API variant on servlets -- that's not where the market is. Providers of non-168 portal servers are welcome to provide their own adaptations of they want to, and several of them already do. Fortunately, all of the servers portal mentioned above (including Jetspeed) are planning to provide JSR-168 compatible support, so implementing 168 support into Struts is instantly useful on all of them. That's the power of common standards. I think after the release of JSR-168 Reference Inplementation, which has been proposed to become an Apache project, by the way; see the 'jakarta-jetspeed-2' CVS repository ... many Struts developers (i know at least a number of Portals based on Struts-Tiles, all except basic portal, stating to support JSR-168) (i am one of them) will seriously put some time in this refactoring process. Yep ... JSR-168 is going to be a very popular API, quite likely rivalling servlet in the number of server choices people will have. And supporting it gracefully in Struts means you'll be able to deploy a Struts based app using either servlet or portlet based servers, depending on your needs, with minimal changes. Thanks for this forcefull statement that indicates the right leadership. I totally agree with this. That is why i think Struts with the best design and least burden of past technologies is the best candidate to realize the importance of JSR-168 Portal/Portlet container and WSRP for later stage. Hope many developers / designers will join in to realize the benefits of industry standards. BaTien DBGROUPS BaTien DBGROUPS Craig McClanahan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] .
Re: Struts and Jetspeed
Vic Cekvenich wrote: BaTien Duong wrote: Emerson Cargnin wrote: any advice in choosing tiles vs jetspeedy? I suppose tiles integrates better, but at the other side jettyspeed follows the portlets specification. Any other comments? It is still too early to tell. I believe in simplicity and the right design that up to now Struts-Tiles give us elegant controller-templating engine. Craig has stated his ideal goal for developing Struts to work with JSR-168. The challenge is to have something like tiles as a template engine according to JSR-168 specifications for Portal / Portlet container(s). I think after the release of JSR-168 Reference Inplementation, many Struts developers (i know at least a number of Portals based on Struts-Tiles, all except basicPortal.com FIX, stating to support JSR-168) (i am one of them) will seriously put some time in this refactoring process. Just FYI, this is the reason bP will bypass 168: http://marc.theaimsgroup.com/?l=jetspeed-userm=105850057414235w=2 bP action event context actually handles the potlet api and servlet api (as it was built to handle more the servlets... SOAP for example), but instead will focus on WS, SOA, XML-RPC and other things that address a heterogeneous environment, organizations that have C# and Java. If anyone wants to jump of the bridge... I will have even more clients. :-) I plan to implent something better than dataGridGirl.com, Ex: http://www.tufat.com/datagrid/datagrid2.html So we just have different goals. What is the url to the portal you are building, if it is avialable? .V The discussion of pro and con of server-side and client-side technologies have been partly explored in Jetspeed Mailing list. I generally agree with the view that given current status, the JSR-168 authors have done a good job to balance what can be best to deliver at this time. The client side state maintenance still needs to be addressed by Java developer community. My portal development actually takes the similar approach as you are planning to do to get our portlets and personalization engine working with standard Portal / Portlet containers, and gradually move into our Portal/Portlet container built from open technologies such as Struts. The site is http://www.dbgroups.com BaTien DBGROUPS
Re: Struts and Jetspeed
any advice in choosing tiles vs jetspeedy? I suppose tiles integrates better, but at the other side jettyspeed follows the portlets specification. Any other comments? Alex wrote: Mike, Is there specific portlet available for wrapping existing Struts application in Jetspeed framework? HTML portlet, WebPagePortlet, ServletProxyPortlet, WebBrowserPortlet or any other suggestions? Session information is missing after porting existing Struts application to JetSpeed portlet. Thanks, Alex Mainguy, Mike wrote: I'll agree, if you're already using Turbine, then struts is really a waste of time and effort. Just use the turbine framework (it's more complete anyway IMHO). If you really want to use struts for portlets, I'd recommend using struts in a different servlet context and then wrapping it in a portlet so you don't end up with a confused mish-mash of technologies. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:49 AM To: Struts Users Mailing List Subject: Re: Struts and Jetspeed At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Jetspeed
At 2:21 PM -0300 8/20/03, Emerson Cargnin wrote: any advice in choosing tiles vs jetspeedy? I suppose tiles integrates better, but at the other side jettyspeed follows the portlets specification. Any other comments? It's a little early to say that anything follows the portlet specification since it's just barely in public review! I can also tell you that on the Struts developer list there seems to be decent awareness of Portlets and a general commitment to making Struts work equally well in either a portlet or servlet context -- but no one is in a hurry to start before the spec is final, it seems. If all you want is a portlet container, Jetspeed is one already, regardless of JSR-168. Struts isn't a portlet container, and besides tiles, you'd have to build up user authentication and preference support which Jetspeed has out of the box. Joe Alex wrote: Mike, Is there specific portlet available for wrapping existing Struts application in Jetspeed framework? HTML portlet, WebPagePortlet, ServletProxyPortlet, WebBrowserPortlet or any other suggestions? Session information is missing after porting existing Struts application to JetSpeed portlet. Thanks, Alex Mainguy, Mike wrote: I'll agree, if you're already using Turbine, then struts is really a waste of time and effort. Just use the turbine framework (it's more complete anyway IMHO). If you really want to use struts for portlets, I'd recommend using struts in a different servlet context and then wrapping it in a portlet so you don't end up with a confused mish-mash of technologies. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:49 AM To: Struts Users Mailing List Subject: Re: Struts and Jetspeed At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com If nature worked that way, the universe would crash all the time. --Jaron Lanier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Jetspeed
Or peek at basicPortal.com, a portal built on Struts, that also ignores the 168. It has a lot out of the box. .V Joe Germuska wrote: At 2:21 PM -0300 8/20/03, Emerson Cargnin wrote: any advice in choosing tiles vs jetspeedy? I suppose tiles integrates better, but at the other side jettyspeed follows the portlets specification. Any other comments? It's a little early to say that anything follows the portlet specification since it's just barely in public review! I can also tell you that on the Struts developer list there seems to be decent awareness of Portlets and a general commitment to making Struts work equally well in either a portlet or servlet context -- but no one is in a hurry to start before the spec is final, it seems. If all you want is a portlet container, Jetspeed is one already, regardless of JSR-168. Struts isn't a portlet container, and besides tiles, you'd have to build up user authentication and preference support which Jetspeed has out of the box. Joe Alex wrote: Mike, Is there specific portlet available for wrapping existing Struts application in Jetspeed framework? HTML portlet, WebPagePortlet, ServletProxyPortlet, WebBrowserPortlet or any other suggestions? Session information is missing after porting existing Struts application to JetSpeed portlet. Thanks, Alex Mainguy, Mike wrote: I'll agree, if you're already using Turbine, then struts is really a waste of time and effort. Just use the turbine framework (it's more complete anyway IMHO). If you really want to use struts for portlets, I'd recommend using struts in a different servlet context and then wrapping it in a portlet so you don't end up with a confused mish-mash of technologies. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:49 AM To: Struts Users Mailing List Subject: Re: Struts and Jetspeed At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Vic Cekvenich, Struts Instructor, 1-800-917-JAVA Advanced a href =baseBeans.comStruts Training/a, mentoring and project recovery in North East. Struts conversion and a href =baseBeans.com fixed bid development/a. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Jetspeed
Emerson Cargnin wrote: any advice in choosing tiles vs jetspeedy? I suppose tiles integrates better, but at the other side jettyspeed follows the portlets specification. Any other comments? It is still too early to tell. I believe in simplicity and the right design that up to now Struts-Tiles give us elegant controller-templating engine. Craig has stated his ideal goal for developing Struts to work with JSR-168. The challenge is to have something like tiles as a template engine according to JSR-168 specifications for Portal / Portlet container(s). I think after the release of JSR-168 Reference Inplementation, many Struts developers (i know at least a number of Portals based on Struts-Tiles, all except basic portal, stating to support JSR-168) (i am one of them) will seriously put some time in this refactoring process. BaTien DBGROUPS Alex wrote: Mike, Is there specific portlet available for wrapping existing Struts application in Jetspeed framework? HTML portlet, WebPagePortlet, ServletProxyPortlet, WebBrowserPortlet or any other suggestions? Session information is missing after porting existing Struts application to JetSpeed portlet. Thanks, Alex Mainguy, Mike wrote: I'll agree, if you're already using Turbine, then struts is really a waste of time and effort. Just use the turbine framework (it's more complete anyway IMHO). If you really want to use struts for portlets, I'd recommend using struts in a different servlet context and then wrapping it in a portlet so you don't end up with a confused mish-mash of technologies. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:49 AM To: Struts Users Mailing List Subject: Re: Struts and Jetspeed At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe - 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 Jetspeed
BaTien Duong wrote: Emerson Cargnin wrote: any advice in choosing tiles vs jetspeedy? I suppose tiles integrates better, but at the other side jettyspeed follows the portlets specification. Any other comments? It is still too early to tell. I believe in simplicity and the right design that up to now Struts-Tiles give us elegant controller-templating engine. Craig has stated his ideal goal for developing Struts to work with JSR-168. The challenge is to have something like tiles as a template engine according to JSR-168 specifications for Portal / Portlet container(s). I think after the release of JSR-168 Reference Inplementation, many Struts developers (i know at least a number of Portals based on Struts-Tiles, all except basicPortal.com FIX, stating to support JSR-168) (i am one of them) will seriously put some time in this refactoring process. Just FYI, this is the reason bP will bypass 168: http://marc.theaimsgroup.com/?l=jetspeed-userm=105850057414235w=2 bP action event context actually handles the potlet api and servlet api (as it was built to handle more the servlets... SOAP for example), but instead will focus on WS, SOA, XML-RPC and other things that address a heterogeneous environment, organizations that have C# and Java. If anyone wants to jump of the bridge... I will have even more clients. :-) I plan to implent something better than dataGridGirl.com, Ex: http://www.tufat.com/datagrid/datagrid2.html So we just have different goals. What is the url to the portal you are building, if it is avialable? .V BaTien DBGROUPS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Jetspeed
On Wed, 20 Aug 2003, BaTien Duong wrote: Date: Wed, 20 Aug 2003 13:31:17 -0600 From: BaTien Duong [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Subject: Re: Struts and Jetspeed Emerson Cargnin wrote: any advice in choosing tiles vs jetspeedy? I suppose tiles integrates better, but at the other side jettyspeed follows the portlets specification. Any other comments? It is still too early to tell. I believe in simplicity and the right design that up to now Struts-Tiles give us elegant controller-templating engine. Craig has stated his ideal goal for developing Struts to work with JSR-168. The challenge is to have something like tiles as a template engine according to JSR-168 specifications for Portal / Portlet container(s). There is also an implicit non-goal that I should state explicitly -- I'm totally uninterested in building in (to Struts) support for non-JSR 168 based portal servers -- be they open source ones like Jetspeed or commercial ones (BEA, IBM, Oracle, Sun, whatever). This is for the same reason that I'm not interested in supporting any non-Servlet-API variant on servlets -- that's not where the market is. Providers of non-168 portal servers are welcome to provide their own adaptations of they want to, and several of them already do. Fortunately, all of the servers portal mentioned above (including Jetspeed) are planning to provide JSR-168 compatible support, so implementing 168 support into Struts is instantly useful on all of them. That's the power of common standards. I think after the release of JSR-168 Reference Inplementation, which has been proposed to become an Apache project, by the way; see the 'jakarta-jetspeed-2' CVS repository ... many Struts developers (i know at least a number of Portals based on Struts-Tiles, all except basic portal, stating to support JSR-168) (i am one of them) will seriously put some time in this refactoring process. Yep ... JSR-168 is going to be a very popular API, quite likely rivalling servlet in the number of server choices people will have. And supporting it gracefully in Struts means you'll be able to deploy a Struts based app using either servlet or portlet based servers, depending on your needs, with minimal changes. BaTien DBGROUPS Craig McClanahan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Jetspeed
Mike, Is there specific portlet available for wrapping existing Struts application in Jetspeed framework? HTML portlet, WebPagePortlet, ServletProxyPortlet, WebBrowserPortlet or any other suggestions? Session information is missing after porting existing Struts application to JetSpeed portlet. Thanks, Alex Mainguy, Mike wrote: I'll agree, if you're already using Turbine, then struts is really a waste of time and effort. Just use the turbine framework (it's more complete anyway IMHO). If you really want to use struts for portlets, I'd recommend using struts in a different servlet context and then wrapping it in a portlet so you don't end up with a confused mish-mash of technologies. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:49 AM To: Struts Users Mailing List Subject: Re: Struts and Jetspeed At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Jetspeed
At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe -- -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com If nature worked that way, the universe would crash all the time. --Jaron Lanier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts and Jetspeed
I'll agree, if you're already using Turbine, then struts is really a waste of time and effort. Just use the turbine framework (it's more complete anyway IMHO). If you really want to use struts for portlets, I'd recommend using struts in a different servlet context and then wrapping it in a portlet so you don't end up with a confused mish-mash of technologies. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:49 AM To: Struts Users Mailing List Subject: Re: Struts and Jetspeed At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe -- -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com If nature worked that way, the universe would crash all the time. --Jaron Lanier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message and its contents (to include attachments) are the property of Kmart Corporation (Kmart) and may contain confidential and proprietary information. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on information contained herein is strictly prohibited. Unauthorized use of information contained herein may subject you to civil and criminal prosecution and penalties. If you are not the intended recipient, you should delete this message immediately. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts and Jetspeed
Also, be sure to read up on Tiles for creating your layout. On the other hand, I am a big fan of Jetspeed as a service aggregator. Jahia (also a portal product with content management) allows you to drop-deploy struts applications which is very useful. IOW, If you are just trying to create a layout and login, I agree with previous posts that you may be mis-matching frameworks; but, if you are trying to aggregate a struts service with other content providers, struts in a portlet is a worthy goal. Steve B. - Original Message - From: Mainguy, Mike [EMAIL PROTECTED] To: 'Struts Users Mailing List' [EMAIL PROTECTED] Sent: Thursday, July 31, 2003 10:12 AM Subject: RE: Struts and Jetspeed I'll agree, if you're already using Turbine, then struts is really a waste of time and effort. Just use the turbine framework (it's more complete anyway IMHO). If you really want to use struts for portlets, I'd recommend using struts in a different servlet context and then wrapping it in a portlet so you don't end up with a confused mish-mash of technologies. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:49 AM To: Struts Users Mailing List Subject: Re: Struts and Jetspeed At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe -- -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com If nature worked that way, the universe would crash all the time. --Jaron Lanier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message and its contents (to include attachments) are the property of Kmart Corporation (Kmart) and may contain confidential and proprietary information. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on information contained herein is strictly prohibited. Unauthorized use of information contained herein may subject you to civil and criminal prosecution and penalties. If you are not the intended recipient, you should delete this message immediately. - 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 Jetspeed
Joe Germuska wrote: At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. Struts has a much better control, while JetSpeed has established portlets and facilities to connect devices to portlets. The problem with Jetspeed is that it is binding to Turbine, while Struts allows complete separation of controller framework and presentation layer. Struts-Tiles enable 1 single web-page view rather than portal view and portlet view. With the release of JSR-168 specification of portal/portlet container based on standard Servlet container, it makes a lot of sense to refactor Struts framework to work with standard Servlet / Portal /Portlet container. Then an effort to refactor Jetspeed portlets into this framework. I wonder if any developer has playing with this idea? I heard Craig and Cedric have something under their desks, and not ready to share yet? Am I right? It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe BaTien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts and Jetspeed
Have you looked at http://www.liferay.com/products/index.jsp which is built open source technologies like Hibernate, Lucene, and Struts. -Original Message- From: BaTien Duong [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 12:13 PM To: Struts Users Mailing List Subject: Re: Struts and Jetspeed Joe Germuska wrote: At 22:22 -0600 7/30/03, jakarta-lists wrote: Has anyone successfully use Struts with Jetspeed? I'm looking into the possiblilty of having jetspeed do the authentication, templating and layout.. while struts will handle the control of the app. It sounds like a good idea to me, but I haven't worked with struts enough yet to know for sure and I would like to know about pitfalls if any. Struts has a much better control, while JetSpeed has established portlets and facilities to connect devices to portlets. The problem with Jetspeed is that it is binding to Turbine, while Struts allows complete separation of controller framework and presentation layer. Struts-Tiles enable 1 single web-page view rather than portal view and portlet view. With the release of JSR-168 specification of portal/portlet container based on standard Servlet container, it makes a lot of sense to refactor Struts framework to work with standard Servlet / Portal /Portlet container. Then an effort to refactor Jetspeed portlets into this framework. I wonder if any developer has playing with this idea? I heard Craig and Cedric have something under their desks, and not ready to share yet? Am I right? It doesn't sound like there's much left for Struts to do once you use Jetspeed (or Turbine, its underlying framework) for authentication, templating, and layout. Once you're talking about providing content to individual portlets in your Jetspeed installation, you can do it with much less work than adding Struts in to the mix. Joe BaTien - 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 JetSpeed
From http://jakarta.apache.org/jetspeed/site/resources.html, JetSpeed relies on these Xerces Xalan Turbine Cocoon Castor ECS Hypersonic-SQL Velocity Working Dogs (Village) Tomcat CVS, WinCvs I don't think you can use both Turbine and Struts for the same application. -Original Message- From: Ryan Cuprak [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 09, 2002 12:36 PM To: Struts Users Mailing List Subject: Struts and JetSpeed I was just curious as to whether one can use both struts and jetspeed (integrated). I have gotten a pretty good handle on Struts but recently discovered jetspeed and liked what I saw. Thanks, Ryan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts and JetSpeed
On Tue, 9 Jul 2002, Dan Cancro wrote: Date: Tue, 9 Jul 2002 13:22:22 -0700 From: Dan Cancro [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: 'Struts Users Mailing List' [EMAIL PROTECTED] Subject: RE: Struts and JetSpeed From http://jakarta.apache.org/jetspeed/site/resources.html, JetSpeed relies on these Xerces Xalan Turbine Cocoon Castor ECS Hypersonic-SQL Velocity Working Dogs (Village) Tomcat CVS, WinCvs I don't think you can use both Turbine and Struts for the same application. I don't see why that would be the case, as long as you don't have conflicts over the servlet mappings. Craig -Original Message- From: Ryan Cuprak [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 09, 2002 12:36 PM To: Struts Users Mailing List Subject: Struts and JetSpeed I was just curious as to whether one can use both struts and jetspeed (integrated). I have gotten a pretty good handle on Struts but recently discovered jetspeed and liked what I saw. Thanks, Ryan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
