Diff PortletJava1En

Line 1:
- article of '''MassimilianoDessi''' + article of '''MassimilianoDessi'''
- translated by Nelly Cannas ( nellycannas[#at*]yahoo[*dot#]it ) +
- [<html>] + translated by Nelly Cannas ( nellycannas[#at*]yahoo[*dot#]it )
- + [<html>]
- + 
- Portlet I + 
- + Portlet I 
- Introduction + 
- The Jakarta-Jetspeed project permits the construction of enterprise portals + Introduction 
- by means of portlets. + The Jakarta-Jetspeed project permits the construction of enterprise portals
- Portlets are web components that can be used as plug-in and managed by a container + by means of portlets. 
- (Jetspeed). + Portlets are web components that can be used as plug-in and managed by a container
- The pages are created assembling portlets, which are pieces of pages and their + (Jetspeed). 
- role is giving information from sources. + The pages are created assembling portlets, which are pieces of pages and their
- The use of this technology allows users to construct their own portal, simply + role is giving information from sources. 
- choosing where + The use of this technology allows users to construct their own portal, simply
- , how and in which page put the portlets with the different contents. + choosing where 
- Portlets can be java applications of several kinds, for example based on Â“actionsÂ” + , how and in which page put the portlets with the different contents. 
- ( of Turbine, Velocity or Struts), contents from other sites through RSS [1], + Portlets can be java applications of several kinds, for example based on Â“actionsÂ”
- xslt, or publications made with Cocoon [2]. + ( of Turbine, Velocity or Struts), contents from other sites through RSS [1],
- Another application allowed by portlets is the connection with content management + xslt, or publications made with Cocoon [2]. 
- systems , thanks to the fact that portlets are components. + Another application allowed by portlets is the connection with content management
- Jetspeed shows the content adapting the language to the userÂ’s browser + systems , thanks to the fact that portlets are components. 
- ; which can be an http client or a wap phone. + Jetspeed shows the content adapting the language to the userÂ’s browser
- In order to consent the portability between commercial portlet containers, the + ; which can be an http client or a wap phone. 
- java community process has been asked to create a standard for portlets (jsr + In order to consent the portability between commercial portlet containers, the
- 168*) . + java community process has been asked to create a standard for portlets (jsr
- The comitee is composed by ASF, Oracle, IBM, Sun, SAP, Borland, Novell, and + 168*) . 
- many others. + The comitee is composed by ASF, Oracle, IBM, Sun, SAP, Borland, Novell, and
- Framework and components used in Jetspeed + many others. 
- LetÂ’s start to see in a logical-functional way how pages are assembled. + Framework and components used in Jetspeed 
- The assembling of portlets in a page is made by Turbine. + LetÂ’s start to see in a logical-functional way how pages are assembled. 
- Turbine is a Jakarta framework for the creation of web application according + The assembling of portlets in a page is made by Turbine. 
- to the paradigm MVC[3]. + Turbine is a Jakarta framework for the creation of web application according
- Turbine gives services and functionalities, particularly by means of the actions + to the paradigm MVC[3]. 
- , services in background and template. + Turbine gives services and functionalities, particularly by means of the actions
- For template Turbine uses Velocity[4] or the Jsp. + , services in background and template. 
- Velocity is a Jakarta template engine, with his template (.vm Velocity macro) + For template Turbine uses Velocity[4] or the Jsp. 
- it is possibile to have access to java objects in his context. + Velocity is a Jakarta template engine, with his template (.vm Velocity macro)
- Velocity represents the view of Turbine. + it is possibile to have access to java objects in his context. 
- Creation of the pages + Velocity represents the view of Turbine. 
- The calls to Jetspeed are like this: + Creation of the pages
- http://wwwÂ…/portal/user/userName/page/default.psml?params + The calls to Jetspeed are like this: 
- The url contains the name of the user who is asking the page and refers to a + http://wwwÂ…/portal/user/userName/page/default.psml?params 
- psml file , even followed by possible params . + The url contains the name of the user who is asking the page and refers to a
- The psml file (Portal structure markup language) is an xml file which contains + psml file , even followed by possible params . 
- the site structure with the portlet entries for the different pages (but it + The psml file (Portal structure markup language) is an xml file which contains
- is also possible to have separated files, for each page, that refer to each + the site structure with the portlet entries for the different pages (but it
- other to compose a psml file). + is also possible to have separated files, for each page, that refer to each
- In the psml file it is shown what layout controller must be used to dispose + other to compose a psml file). 
- the components that form the page (es.tab-controller, card- controller) . + In the psml file it is shown what layout controller must be used to dispose
- At this point Jetspeed has all the information to compose the page. + the components that form the page (es.tab-controller, card- controller) . 
- Turbine, starting from the file default.vm of Velocity, that contains the general + At this point Jetspeed has all the information to compose the page. 
- layoutof pages, creates the portlets according to the scheme imposed by the + Turbine, starting from the file default.vm of Velocity, that contains the general
- controller written in the psml. + layoutof pages, creates the portlets according to the scheme imposed by the
- [</html>] + controller written in the psml. 
- attach:portlet-1_fig1.jpg +
- + [</html>]
- [<html>] +
- Fig 1. JetspeedÂ’s architecture + attach:portlet-1_fig1.jpg
- +
- Velocity macro + [<html>]
- Velocity macro files (vm) are VelocityÂ’s templates, they are html files +
- with variables that are substituted by Velocity + Fig 1. JetspeedÂ’s architecture 
- An example of the vm file is this default.vm : + 
- <html> + Velocity macro 
- <head> + Velocity macro files (vm) are VelocityÂ’s templates, they are html files
- Â…$jnavigation.setTemplate("top.vm") + with variables that are substituted by Velocity 
- Â….. + An example of the vm file is this default.vm :
- $jnavigation.setTemplate("left.vm") + <html> 
- Â… + <head> 
- $screen_placeholder + Â…$jnavigation.setTemplate("top.vm") 
- Â…. + Â….. 
- $jnavigation.setTemplate("bottom.vm") + $jnavigation.setTemplate("left.vm") 
- Â… + Â… 
- </body> + $screen_placeholder 
- </html> + Â…. 
- + $jnavigation.setTemplate("bottom.vm") 
- In this file Velocity is asked to compose the layout of the page with a top, + Â… 
- a left and a bottom and a piece that is called $screen placeholder and that + </body> 
- we will see later. + </html> 
- The result will be a page like fig 2 + 
- + In this file Velocity is asked to compose the layout of the page with a top,
- [</html>] + a left and a bottom and a piece that is called $screen placeholder and that
- + we will see later. 
- attach:portlet-1_fig2.jpg + The result will be a page like fig 2
- [<html>] +
- + [</html>]
- Fig. 2 Jetspeed Layout +
- + attach:portlet-1_fig2.jpg
- LetÂ’s see what is $screen placeholder. +
- As we have said, the psml file contains the portlets that must be visualized + [<html>]
- for the corresponding pages , and they are inserted for that page in the part +
- called $screen placeholder, according to the modalities given by the controller. + 
- + Fig. 2 Jetspeed Layout
- So we will have the page like in fig3 and 4, that is the structure of the pages + 
- constructed by Turbine using VelocityÂ’s templates. + LetÂ’s see what is $screen placeholder. 
- + As we have said, the psml file contains the portlets that must be visualized
- [</html>] + for the corresponding pages , and they are inserted for that page in the part
- attach:portlet-1_fig3.jpg + called $screen placeholder, according to the modalities given by the controller.
- [<html>] + 
- Fig 3 Turbine Layout + So we will have the page like in fig3 and 4, that is the structure of the pages
- [</html>] + constructed by Turbine using VelocityÂ’s templates. 
- attach:portlet-1_fig4.jpg +
- [<html>] + [</html>]
- Fig 4 Layout Screen +
- + attach:portlet-1_fig3.jpg
- Other functionalities +
- After the explanation of the most common use, with http calls, letÂ’s see + [<html>]
- other functionalities of Jetspeed. +
- In the folder WEB-INF\templates we have two subdirectories, Jsp and Velocity, + Fig 3 Turbine Layout
- as Turbine can use both templates. + [</html>]
- In the subdirectories we have the folder html and wml: in the first are contained +
- the template for browser http, in the second that for wap device. + attach:portlet-1_fig4.jpg
- [</html>] +
- attach:portlet-1_fig5.jpg + [<html>]
- [<html>] + Fig 4 Layout Screen
- Fig 5 Jetspeed on http :http://www.anglonaweb.it + 
- [</html>] + Other functionalities 
- attach:portlet-1_fig6.jpg + After the explanation of the most common use, with http calls, letÂ’s see
- [<html>] + other functionalities of Jetspeed. 
- Fig 6 Jetspeed on wap + In the folder WEB-INF\templates we have two subdirectories, Jsp and Velocity,
- With these template is managed the supplying of the contents on several canals. + as Turbine can use both templates. 
- The localization is managed by a service from turbine that is used by Velocity + In the subdirectories we have the folder html and wml: in the first are contained
- (l10n). + the template for browser http, in the second that for wap device. 
- Jetspeed exposes even some web-services. + [</html>]
- Configurating properly Velocity templates, it is possibile to have even different +
- layouts for the portal pages, the only limit is the fantasy of the graphic who + attach:portlet-1_fig5.jpg
- will choose the layout of the site, that will be translated in the VelocityÂ’s +
- template. + [<html>]
- + Fig 5 Jetspeed on http :http://www.anglonaweb.it
- + [</html>]
- Structure and content of psml file (Portal structure markup language) +
- + attach:portlet-1_fig6.jpg
- It contains the structure of the userÂ’s portal, the portlets that will +
- composed the pages and the controllers for the pages and even the portletsÂ’ + [<html>]
- skins. + Fig 6 Jetspeed on wap
- [</html>] + With these template is managed the supplying of the contents on several canals. 
- @@@@ + The localization is managed by a service from turbine that is used by Velocity
- <?xml version="1.0" encoding="iso-8859-1"?> + (l10n). 
- <portlets xmlns="http://xml.apache.org/jetspeed/2000/psml"> + Jetspeed exposes even some web-services. 
- <metainfo> + Configurating properly Velocity templates, it is possibile to have even different
- <title>Default Jetspeed Page</title> + layouts for the portal pages, the only limit is the fantasy of the graphic who
- </metainfo> + will choose the layout of the site, that will be translated in the VelocityÂ’s
- <control name="TabControl"/> + template.
- <controller name="CardPortletController"> + 
- <parameter name="parameter" value="pane"/> + 
- </controller> + Structure and content of psml file (Portal structure markup language)
- <skin name="orange-grey"/> + 
- Â… + It contains the structure of the userÂ’s portal, the portlets that will
- <portlets> + composed the pages and the controllers for the pages and even the portletsÂ’
- <entry parent="HelloVelocity"/> + skins. 
- <layout> + [</html>]
- <property name="row" value="0"/> + @@@@
- <property name="column" value="1"/> + <?xml version="1.0" encoding="iso-8859-1"?>
- </layout> + <portlets xmlns="http://xml.apache.org/jetspeed/2000/psml">
- </portlets> + <metainfo>
- <portlets> + <title>Default Jetspeed Page</title>
- <entry parent="HelloJSP"/> + </metainfo>
- <layout> + <control name="TabControl"/>
- <property name="row" value="1"/> + <controller name="CardPortletController">
- <property name="column" value="0"/> + <parameter name="parameter" value="pane"/>
- </layout> + </controller>
- </portlets> + <skin name="orange-grey"/>
- </portlets> + Â…
- '''Conclusions''' + <portlets>
- In this first artiche we have seen what Jetspeed and the portlets provide: + <entry parent="HelloVelocity"/> 
- *The possibility for the users to create their own portals, according to the language and the device used + <layout> 
- *The connection with Content Management System thanks to the fact that the portlets are components, an example of Jetspeed with a cms: http://www.anglonaweb.it/. + <property name="row" value="0"/> 
- The complete list of the sites created with Jetspeed are available on: + <property name="column" value="1"/> 
- http://jakarta.apache.org/jetspeed/site/usejetspeed.html + </layout> 
- For the developer, as Jetspeed is a portal framework that exposes information, applications and services, it is possibile to find in it the application of the lates innovations, of standards, trends and methodologies of java programming, and even the use of other projects that are not of common use from who isnÂ’t a mailing list open-source haunter, but are used in commercial projects. + </portlets>
- In the next article we will see in a more technical and detailed way the portletsÂ’ hierarchies, how they really work , which and how many are the base kinds, and how to deploy in a container portlet. + <portlets>
- '''Bibliography and references''' + <entry parent="HelloJSP"/>
- Jetspeed : Enterprise Information Portal: http://jakarta.apache.org/jetspeed + <layout>
- Turbine : Web Application framework: http://jakarta.apache.org/turbine + <property name="row" value="1"/>
- Velocity: Java Template Engine: http://jakarta.apache.org/velocity + <property name="column" value="0"/>
- Cocoon: http://xml.apache.org/cocoon + </layout>
- jsr168: http://www.jcp.org/en/jsr/detail?id=168 + </portlets>
- #Rss (Rich Site Summary) McLaughlin, Â“Java e XmlÂ“, ed. OÂ’Reilly 2001 + </portlets>
- #Cocoon McLaughlin, Â“Java e XmlÂ“, ed. OÂ’Reilly 2001 +
- #http://jakarta.apache.org/turbine/turbine-2.3/model2+1.html + '''Conclusions'''
- #Velocity e WebMacro Hunter-Crawford, Â“Java Servlet Programming II ed.Â“, ed. OÂ’Reilly 2001 + In this first artiche we have seen what Jetspeed and the portlets provide:
- ---- + *The possibility for the users to create their own portals, according to the language and the device used
- '''MassimilianoDessì''' (desmax74[*](\)@(/)[*]yahoo[*](/).(\)[*]it) + *The connection with Content Management System thanks to the fact that the portlets are components, an example of Jetspeed with a cms: http://www.anglonaweb.it/.
- He has started working at the Sistemi Informativi S.p.A (IBM) (http://www.sistinf.it) as a Java programmer. Since 2001 he has been working at the Atlantis S.p.A. (http://www.gruppoatlantis.com/), where he uses agile methodologies as the eXtreme programming (Xp), he develops enterprise Web-based applications with J2EE technology, like portals and content management system for territorial promotion. +
- In his free time he co- operates to the open-source Jakarta Â–Jetspeed project, and he takes care of the Italian version of Jetspeed. He studies electronic engineering at the University of Cagliari. + The complete list of the sites created with Jetspeed are available on:
+ http://jakarta.apache.org/jetspeed/site/usejetspeed.html
+
+ For the developer, as Jetspeed is a portal framework that exposes information, applications and services, it is possibile to find in it the application of the lates innovations, of standards, trends and methodologies of java programming, and even the use of other projects that are not of common use from who isnÂ’t a mailing list open-source haunter, but are used in commercial projects.
+
+ In the next article we will see in a more technical and detailed way the portletsÂ’ hierarchies, how they really work , which and how many are the base kinds, and how to deploy in a container portlet.
+
+ '''Bibliography and references'''
+ Jetspeed : Enterprise Information Portal: http://jakarta.apache.org/jetspeed
+ Turbine : Web Application framework: http://jakarta.apache.org/turbine
+ Velocity: Java Template Engine: http://jakarta.apache.org/velocity
+ Cocoon: http://xml.apache.org/cocoon
+ jsr168: http://www.jcp.org/en/jsr/detail?id=168
+ #Rss (Rich Site Summary) McLaughlin, Â“Java e XmlÂ“, ed. OÂ’Reilly 2001
+ #Cocoon McLaughlin, Â“Java e XmlÂ“, ed. OÂ’Reilly 2001
+ #http://jakarta.apache.org/turbine/turbine-2.3/model2+1.html
+ #Velocity e WebMacro Hunter-Crawford, Â“Java Servlet Programming II ed.Â“, ed. OÂ’Reilly 2001
+ ----
+ '''MassimilianoDessì''' (desmax74[*](\)@(/)[*]yahoo[*](/).(\)[*]it)
+ He has started working at the Sistemi Informativi S.p.A (IBM) (http://www.sistinf.it) as a Java programmer. Since 2001 he has been working at the Atlantis S.p.A. (http://www.gruppoatlantis.com/), where he uses agile methodologies as the eXtreme programming (Xp), he develops enterprise Web-based applications with J2EE technology, like portals and content management system for territorial promotion.
+ In his free time he co- operates to the open-source Jakarta Â–Jetspeed project, and he takes care of the Italian version of Jetspeed. He studies electronic engineering at the University of Cagliari.