[J2] Major new version of the Struts Bridge: version 0.2 now available
I'm happy to bring the news of a major upgrade of the Struts Bridge. A short summary of its new features: - Based on the latest Struts-1.2.4 - Provides new struts-1.2.4-portlet-html.tld and struts-1.2.4-portlet-html-el.tld, as well as a new struts-portlet-el.tld. The first two tld files are full replacements for the struts-html and struts-html-el tlds. By using these tlds instead of the struts-portlet and struts-portlet-el tlds, migrating existing Struts applications becomes much easier (just change the taglib definition). Furthermore, there is now full struts-el support Bridge for all the tags (including the new onces). - New Portlet supporting extended Struts tags ImgTag and ImageTag and largely extended LinkTag and RewriteTag. These tags now support relative image src paths and href link paths (including ../ elements). - Provides transparent (non-code based) definition of request attribute values to be saved during ActionRequest handling which will be restored in the subsequent RenderRequest(s). - Provides transparent (non-code based) definition of url (prefixes) which must be rendered as Action or Render PortletURL. This removes the need to specify the renderURL attribute for link and rewrite tags (its still supported though, and then will override). - xml based configuration of above two features loaded at Portlet initialization. Default configuration file name: WEB-INF/struts-portlet-config.xml, but this is configurable itself as well. Example configuration (from the new JPetstore demo Portlet): ?xml version=1.0 encoding=UTF-8? config render-context attribute name=errors/ attribute name=message/ /render-context portlet-url-type default=render action path=/shop/add/ action path=/shop/switch/ action path=/shop/remove/ action path=/shop/signoff/ action path=/shop/viewCategory/ action path=/shop/viewItem/ action path=/shop/viewProduct/ action path=/shop/viewCart/ action path=/shop/newOrder/ render path=/shop/newOrderForm/ action path=/shop/listOrders/ /portlet-url-type /config - IMPORTANT: Default PorletURL created by link and rewrite tag changed from ActionURL to RenderURL. This change is made because in the most cases this turned out to be RenderURLs. For migrating of existing Struts Bridge based Portlets to the new version there is an very simple configuration option to revert this to the old style: Define a WEB-INF/struts-portlet-config.xml containing (at least): ?xml version=1.0 encoding=UTF-8? config portlet-url-type default=action/ /config That'll switch the default back to the old style. For the old Struts MailReader Demo Portlet also provided with Jetspeed-2, I've put in a configuration file just like that. - New demo portlet application: JPetstore Portlet. This very know example web application from iBatis (www.ibatis.com) is now also available as Portlet and is automatically deployed in Jetspeed-2 as demo portlet: check it out. - Deploy as Portlet or as web application! The Struts Bridge can now be used in a non-Portlet context, and then will simply fall back to the basic Struts functionality. This allows the deployment of the same Portlet Application war as web application and as portlet application. You can thus also test the application in a web server only (as long as you don't use Portlet features specifically). Try out the JPetstore Portlet demo and access it as Portlet from within Jetspeed-2 or directly from the webserver (e.g. http://localhost:8080/jpetstore). - Abstracted the access to the ServletContextProvider with protected methods in StrutsPortlet allowing Portal Vendor specific extensions to be used (like VAP). - Still no real documentation ;-) I'm working on it and plan to deliver real usage documentation, as well as a tutorial and instructions for migrating existing Struts applications, within a week. Regards, Ate Douma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [J2] Major new version of the Struts Bridge: version 0.2 now available
Wow, this is great Ate! These are many of the features that I was hoping for! I will try this out first thing tomorrow morning. Do you know if it handles the EditPage better than the last version? I'm hoping it fixes a problem that I was having. Thanks again! -- Jeff Sheets On Thu, 20 Jan 2005 03:49:32 +0100, Ate Douma [EMAIL PROTECTED] wrote: I'm happy to bring the news of a major upgrade of the Struts Bridge. A short summary of its new features: - Based on the latest Struts-1.2.4 - Provides new struts-1.2.4-portlet-html.tld and struts-1.2.4-portlet-html-el.tld, as well as a new struts-portlet-el.tld. The first two tld files are full replacements for the struts-html and struts-html-el tlds. By using these tlds instead of the struts-portlet and struts-portlet-el tlds, migrating existing Struts applications becomes much easier (just change the taglib definition). Furthermore, there is now full struts-el support Bridge for all the tags (including the new onces). - New Portlet supporting extended Struts tags ImgTag and ImageTag and largely extended LinkTag and RewriteTag. These tags now support relative image src paths and href link paths (including ../ elements). - Provides transparent (non-code based) definition of request attribute values to be saved during ActionRequest handling which will be restored in the subsequent RenderRequest(s). - Provides transparent (non-code based) definition of url (prefixes) which must be rendered as Action or Render PortletURL. This removes the need to specify the renderURL attribute for link and rewrite tags (its still supported though, and then will override). - xml based configuration of above two features loaded at Portlet initialization. Default configuration file name: WEB-INF/struts-portlet-config.xml, but this is configurable itself as well. Example configuration (from the new JPetstore demo Portlet): ?xml version=1.0 encoding=UTF-8? config render-context attribute name=errors/ attribute name=message/ /render-context portlet-url-type default=render action path=/shop/add/ action path=/shop/switch/ action path=/shop/remove/ action path=/shop/signoff/ action path=/shop/viewCategory/ action path=/shop/viewItem/ action path=/shop/viewProduct/ action path=/shop/viewCart/ action path=/shop/newOrder/ render path=/shop/newOrderForm/ action path=/shop/listOrders/ /portlet-url-type /config - IMPORTANT: Default PorletURL created by link and rewrite tag changed from ActionURL to RenderURL. This change is made because in the most cases this turned out to be RenderURLs. For migrating of existing Struts Bridge based Portlets to the new version there is an very simple configuration option to revert this to the old style: Define a WEB-INF/struts-portlet-config.xml containing (at least): ?xml version=1.0 encoding=UTF-8? config portlet-url-type default=action/ /config That'll switch the default back to the old style. For the old Struts MailReader Demo Portlet also provided with Jetspeed-2, I've put in a configuration file just like that. - New demo portlet application: JPetstore Portlet. This very know example web application from iBatis (www.ibatis.com) is now also available as Portlet and is automatically deployed in Jetspeed-2 as demo portlet: check it out. - Deploy as Portlet or as web application! The Struts Bridge can now be used in a non-Portlet context, and then will simply fall back to the basic Struts functionality. This allows the deployment of the same Portlet Application war as web application and as portlet application. You can thus also test the application in a web server only (as long as you don't use Portlet features specifically). Try out the JPetstore Portlet demo and access it as Portlet from within Jetspeed-2 or directly from the webserver (e.g. http://localhost:8080/jpetstore). - Abstracted the access to the ServletContextProvider with protected methods in StrutsPortlet allowing Portal Vendor specific extensions to be used (like VAP). - Still no real documentation ;-) I'm working on it and plan to deliver real usage documentation, as well as a tutorial and instructions for migrating existing Struts applications, within a week. Regards, Ate Douma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
Re: [J2] Major new version of the Struts Bridge: version 0.2 now available
Jeff Sheets wrote: Wow, this is great Ate! These are many of the features that I was hoping for! I will try this out first thing tomorrow morning. Do you know if it handles the EditPage better than the last version? I'm hoping it fixes a problem that I was having. Actually, I don't know to which problem you are referring. I don't think I fixed anything in that area, but if you can give me more details, I'll be more than happy to so. Ate Thanks again! -- Jeff Sheets On Thu, 20 Jan 2005 03:49:32 +0100, Ate Douma [EMAIL PROTECTED] wrote: I'm happy to bring the news of a major upgrade of the Struts Bridge. A short summary of its new features: - Based on the latest Struts-1.2.4 - Provides new struts-1.2.4-portlet-html.tld and struts-1.2.4-portlet-html-el.tld, as well as a new struts-portlet-el.tld. The first two tld files are full replacements for the struts-html and struts-html-el tlds. By using these tlds instead of the struts-portlet and struts-portlet-el tlds, migrating existing Struts applications becomes much easier (just change the taglib definition). Furthermore, there is now full struts-el support Bridge for all the tags (including the new onces). - New Portlet supporting extended Struts tags ImgTag and ImageTag and largely extended LinkTag and RewriteTag. These tags now support relative image src paths and href link paths (including ../ elements). - Provides transparent (non-code based) definition of request attribute values to be saved during ActionRequest handling which will be restored in the subsequent RenderRequest(s). - Provides transparent (non-code based) definition of url (prefixes) which must be rendered as Action or Render PortletURL. This removes the need to specify the renderURL attribute for link and rewrite tags (its still supported though, and then will override). - xml based configuration of above two features loaded at Portlet initialization. Default configuration file name: WEB-INF/struts-portlet-config.xml, but this is configurable itself as well. Example configuration (from the new JPetstore demo Portlet): ?xml version=1.0 encoding=UTF-8? config render-context attribute name=errors/ attribute name=message/ /render-context portlet-url-type default=render action path=/shop/add/ action path=/shop/switch/ action path=/shop/remove/ action path=/shop/signoff/ action path=/shop/viewCategory/ action path=/shop/viewItem/ action path=/shop/viewProduct/ action path=/shop/viewCart/ action path=/shop/newOrder/ render path=/shop/newOrderForm/ action path=/shop/listOrders/ /portlet-url-type /config - IMPORTANT: Default PorletURL created by link and rewrite tag changed from ActionURL to RenderURL. This change is made because in the most cases this turned out to be RenderURLs. For migrating of existing Struts Bridge based Portlets to the new version there is an very simple configuration option to revert this to the old style: Define a WEB-INF/struts-portlet-config.xml containing (at least): ?xml version=1.0 encoding=UTF-8? config portlet-url-type default=action/ /config That'll switch the default back to the old style. For the old Struts MailReader Demo Portlet also provided with Jetspeed-2, I've put in a configuration file just like that. - New demo portlet application: JPetstore Portlet. This very know example web application from iBatis (www.ibatis.com) is now also available as Portlet and is automatically deployed in Jetspeed-2 as demo portlet: check it out. - Deploy as Portlet or as web application! The Struts Bridge can now be used in a non-Portlet context, and then will simply fall back to the basic Struts functionality. This allows the deployment of the same Portlet Application war as web application and as portlet application. You can thus also test the application in a web server only (as long as you don't use Portlet features specifically). Try out the JPetstore Portlet demo and access it as Portlet from within Jetspeed-2 or directly from the webserver (e.g. http://localhost:8080/jpetstore). - Abstracted the access to the ServletContextProvider with protected methods in StrutsPortlet allowing Portal Vendor specific extensions to be used (like VAP). - Still no real documentation ;-) I'm working on it and plan to deliver real usage documentation, as well as a tutorial and instructions for migrating existing Struts applications, within a week. Regards, Ate Douma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
Re: [J2] Major new version of the Struts Bridge: version 0.2 now available
Thanks for the quick reply. Our problem is with the EditPage when using Fusion. The problem might be unique to fusion, but I've been assuming it is due to a bug in the struts bridge. The old struts-demo didn't use an EditPage, so maybe you never saw the issue. When you have an EditPage, you can get to it from the first screen in your app from the pencil icon. After saving from the EditPage and telling the PortletRequest to return to the View Mode, you are returned to the correct page. But now every refresh of the page takes you to the EditPage instead of the ViewPage. Also, if you navigate between pages in the View Mode then the pencil icon no longer takes you to the ViewPage. Also, I updated from cvs yesterday and the bug still seems to exist using Jetspeed1 from HEAD and Jetspeed2 tagged M1. Good work, and we really like the bridge so far. We've gotten around our issue by leaving all portlets in the View Mode at all times, but I'd really like to use the Edit Mode. On Thu, 20 Jan 2005 04:40:56 +0100, Ate Douma [EMAIL PROTECTED] wrote: Jeff Sheets wrote: Wow, this is great Ate! These are many of the features that I was hoping for! I will try this out first thing tomorrow morning. Do you know if it handles the EditPage better than the last version? I'm hoping it fixes a problem that I was having. Actually, I don't know to which problem you are referring. I don't think I fixed anything in that area, but if you can give me more details, I'll be more than happy to so. Ate Thanks again! -- Jeff Sheets On Thu, 20 Jan 2005 03:49:32 +0100, Ate Douma [EMAIL PROTECTED] wrote: I'm happy to bring the news of a major upgrade of the Struts Bridge. A short summary of its new features: - Based on the latest Struts-1.2.4 - Provides new struts-1.2.4-portlet-html.tld and struts-1.2.4-portlet-html-el.tld, as well as a new struts-portlet-el.tld. The first two tld files are full replacements for the struts-html and struts-html-el tlds. By using these tlds instead of the struts-portlet and struts-portlet-el tlds, migrating existing Struts applications becomes much easier (just change the taglib definition). Furthermore, there is now full struts-el support Bridge for all the tags (including the new onces). - New Portlet supporting extended Struts tags ImgTag and ImageTag and largely extended LinkTag and RewriteTag. These tags now support relative image src paths and href link paths (including ../ elements). - Provides transparent (non-code based) definition of request attribute values to be saved during ActionRequest handling which will be restored in the subsequent RenderRequest(s). - Provides transparent (non-code based) definition of url (prefixes) which must be rendered as Action or Render PortletURL. This removes the need to specify the renderURL attribute for link and rewrite tags (its still supported though, and then will override). - xml based configuration of above two features loaded at Portlet initialization. Default configuration file name: WEB-INF/struts-portlet-config.xml, but this is configurable itself as well. Example configuration (from the new JPetstore demo Portlet): ?xml version=1.0 encoding=UTF-8? config render-context attribute name=errors/ attribute name=message/ /render-context portlet-url-type default=render action path=/shop/add/ action path=/shop/switch/ action path=/shop/remove/ action path=/shop/signoff/ action path=/shop/viewCategory/ action path=/shop/viewItem/ action path=/shop/viewProduct/ action path=/shop/viewCart/ action path=/shop/newOrder/ render path=/shop/newOrderForm/ action path=/shop/listOrders/ /portlet-url-type /config - IMPORTANT: Default PorletURL created by link and rewrite tag changed from ActionURL to RenderURL. This change is made because in the most cases this turned out to be RenderURLs. For migrating of existing Struts Bridge based Portlets to the new version there is an very simple configuration option to revert this to the old style: Define a WEB-INF/struts-portlet-config.xml containing (at least): ?xml version=1.0 encoding=UTF-8? config portlet-url-type default=action/ /config That'll switch the default back to the old style. For the old Struts MailReader Demo Portlet also provided with Jetspeed-2, I've put in a configuration file just like that. - New demo portlet application: JPetstore Portlet. This very know example web application from iBatis (www.ibatis.com) is now also available as Portlet and is automatically deployed in Jetspeed-2 as demo portlet: check it
Re: [J2] Major new version of the Struts Bridge: version 0.2 now available
Jeff, if this problem still exists in the new Bridge could you create a JIRA issue for this problem? I'll pick it up then from there. Ate Jeff Sheets wrote: Thanks for the quick reply. Our problem is with the EditPage when using Fusion. The problem might be unique to fusion, but I've been assuming it is due to a bug in the struts bridge. The old struts-demo didn't use an EditPage, so maybe you never saw the issue. When you have an EditPage, you can get to it from the first screen in your app from the pencil icon. After saving from the EditPage and telling the PortletRequest to return to the View Mode, you are returned to the correct page. But now every refresh of the page takes you to the EditPage instead of the ViewPage. Also, if you navigate between pages in the View Mode then the pencil icon no longer takes you to the ViewPage. Also, I updated from cvs yesterday and the bug still seems to exist using Jetspeed1 from HEAD and Jetspeed2 tagged M1. Good work, and we really like the bridge so far. We've gotten around our issue by leaving all portlets in the View Mode at all times, but I'd really like to use the Edit Mode. On Thu, 20 Jan 2005 04:40:56 +0100, Ate Douma [EMAIL PROTECTED] wrote: Jeff Sheets wrote: Wow, this is great Ate! These are many of the features that I was hoping for! I will try this out first thing tomorrow morning. Do you know if it handles the EditPage better than the last version? I'm hoping it fixes a problem that I was having. Actually, I don't know to which problem you are referring. I don't think I fixed anything in that area, but if you can give me more details, I'll be more than happy to so. Ate Thanks again! -- Jeff Sheets On Thu, 20 Jan 2005 03:49:32 +0100, Ate Douma [EMAIL PROTECTED] wrote: I'm happy to bring the news of a major upgrade of the Struts Bridge. A short summary of its new features: - Based on the latest Struts-1.2.4 - Provides new struts-1.2.4-portlet-html.tld and struts-1.2.4-portlet-html-el.tld, as well as a new struts-portlet-el.tld. The first two tld files are full replacements for the struts-html and struts-html-el tlds. By using these tlds instead of the struts-portlet and struts-portlet-el tlds, migrating existing Struts applications becomes much easier (just change the taglib definition). Furthermore, there is now full struts-el support Bridge for all the tags (including the new onces). - New Portlet supporting extended Struts tags ImgTag and ImageTag and largely extended LinkTag and RewriteTag. These tags now support relative image src paths and href link paths (including ../ elements). - Provides transparent (non-code based) definition of request attribute values to be saved during ActionRequest handling which will be restored in the subsequent RenderRequest(s). - Provides transparent (non-code based) definition of url (prefixes) which must be rendered as Action or Render PortletURL. This removes the need to specify the renderURL attribute for link and rewrite tags (its still supported though, and then will override). - xml based configuration of above two features loaded at Portlet initialization. Default configuration file name: WEB-INF/struts-portlet-config.xml, but this is configurable itself as well. Example configuration (from the new JPetstore demo Portlet): ?xml version=1.0 encoding=UTF-8? config render-context attribute name=errors/ attribute name=message/ /render-context portlet-url-type default=render action path=/shop/add/ action path=/shop/switch/ action path=/shop/remove/ action path=/shop/signoff/ action path=/shop/viewCategory/ action path=/shop/viewItem/ action path=/shop/viewProduct/ action path=/shop/viewCart/ action path=/shop/newOrder/ render path=/shop/newOrderForm/ action path=/shop/listOrders/ /portlet-url-type /config - IMPORTANT: Default PorletURL created by link and rewrite tag changed from ActionURL to RenderURL. This change is made because in the most cases this turned out to be RenderURLs. For migrating of existing Struts Bridge based Portlets to the new version there is an very simple configuration option to revert this to the old style: Define a WEB-INF/struts-portlet-config.xml containing (at least): ?xml version=1.0 encoding=UTF-8? config portlet-url-type default=action/ /config That'll switch the default back to the old style. For the old Struts MailReader Demo Portlet also provided with Jetspeed-2, I've put in a configuration file just like that. - New demo portlet application: JPetstore Portlet. This very know example web application from iBatis (www.ibatis.com) is now also available as Portlet and is automatically deployed in Jetspeed-2 as demo portlet: check it out. - Deploy as Portlet or as web application! The Struts Bridge can now be used in a non-Portlet
