[Shale Wiki] Update of LogoContest by paksegu
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by paksegu: http://wiki.apache.org/shale/LogoContest -- || Dennis Byrne || [EMAIL PROTECTED] || attachment:shale_dennisbyrne.jpg || TODO || || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_pyramid.jpg || attachment:shale_pyramid_pow.jpg|| || Jacob Hookom || [EMAIL PROTECTED] || attachment:shale02_lg_jhook.gif || attachment:shale02_sm_jhook.gif || - || Ransford Segu-Baffoe || [EMAIL PROTECTED] || attachment:shale_paksegu || + || Ransford Segu-Baffoe || [EMAIL PROTECTED] || attachment:shalePaksegu.gif ||
[Shale Wiki] Update of LogoContest by stephanopitz
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by stephanopitz: http://wiki.apache.org/shale/LogoContest -- || Jacob Hookom || [EMAIL PROTECTED] || attachment:shale01_lg_jhook.gif || attachment:shale01_sm_jhook.gif || || Dennis Byrne || [EMAIL PROTECTED] || attachment:shale_dennisbyrne.jpg || TODO || || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_pyramid.jpg || attachment:shale_pyramid_pow.jpg|| + || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_nature.jpg || attachment:shale_nature_pow.jpg|| || Jacob Hookom || [EMAIL PROTECTED] || attachment:shale02_lg_jhook.gif || attachment:shale02_sm_jhook.gif || || Ransford Segu-Baffoe || [EMAIL PROTECTED] || attachment:shalepaksegu.gif ||
[Shale Wiki] Update of LogoContest by jacobhookom
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by jacobhookom: http://wiki.apache.org/shale/LogoContest -- || Joey Jones || [EMAIL PROTECTED] || attachment:shale-logo-example-jmitchell.jpg || attachment:shale-logo-powered-example-jmitchell.jpg || || Dennis Byrne || [EMAIL PROTECTED] || attachment:shale_dennisbyrne.jpg || TODO || || Jacob Hookom || [EMAIL PROTECTED] || attachment:shale01_lg_jhook.gif || attachment:shale01_sm_jhook.gif || - || Jacob Hookom || [EMAIL PROTECTED] || attachment:shale02_lg_jhook.gif || attachment:shale02_sm_jhook.gif || + || Jacob Hookom || [EMAIL PROTECTED] || attachment:shale03_lg_jhook.gif || attachment:shale03_sm_jhook.gif || || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_pyramid.gif || attachment:shale_pyramid_pow.gif|| || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_nature.gif || attachment:shale_nature_pow.gif|| || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_nature_2.gif || attachment:shale_nature_pow_2.gif||
[Shale Wiki] Update of LogoContest by ugodiggi
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by ugodiggi: http://wiki.apache.org/shale/LogoContest -- || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_nature.gif || attachment:shale_nature_pow.gif|| || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_nature_2.gif || attachment:shale_nature_pow_2.gif|| || Ransford Segu-Baffoe || [EMAIL PROTECTED] || attachment:shalepaksegu.gif || + || ugodiggi || [EMAIL PROTECTED] || attachment:Shale_large_udg.png || attachment:Shale_power_udg.png ||
[Shale Wiki] Update of FrontPage by WendySmoak
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/shale/FrontPage -- === Shale Framework Components === * ShaleRemoting + * ShaleTest
[Shale Wiki] Update of FrontPage by WendySmoak
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/shale/FrontPage -- * ShaleRemoting * ShaleTest + === Project Maintenance === + + * MavenBuild + * MavenConfig + * SubversionConfig +
[Shale Wiki] Trivial Update of MavenBuild by WendySmoak
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by WendySmoak:
http://wiki.apache.org/shale/MavenBuild
The comment on the change is:
svn repo reorg
--
=== Examples ===
- From the 'top level' directory of the Shale source code:
+ From the 'framework' directory of the Shale source code:
|| $ '''{{{mvn}}}''' || Default build. Includes the framework jars. ||
|| $ '''{{{mvn clean -P apps,dist,designtime}}}''' || Deletes the 'target'
directory from every module ||
[Shale Wiki] Update of FrontPage by schof
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by schof: http://wiki.apache.org/shale/FrontPage -- * MavenConfig * SubversionRepo * SubversionConfig + * Continuum Setup
[Shale Wiki] Update of FrontPage by schof
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by schof: http://wiki.apache.org/shale/FrontPage -- * MavenConfig * SubversionRepo * SubversionConfig - * Continuum Setup + * ContinuumSetup
[Shale Wiki] Update of ViewControllerMapper by ReneZanner
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by ReneZanner:
http://wiki.apache.org/shale/ViewControllerMapper
The comment on the change is:
added more information on purpose and providing a custom implementation
--
- === Default ===
+ == Purpose ==
- * !DefaultViewControllerMapper
[http://shale.apache.org/shale-core/apidocs/org/apache/shale/view/impl/DefaultViewControllerMapper.html
Javadoc]
+ To support the !ViewController pattern Shale provides a mechanism for
automatic 1:1 association of managed beans with JSF views. The
[http://shale.apache.org/shale-core/apidocs/org/apache/shale/view/ViewControllerMapper.html
ViewControllerMapper] interface provides the mapping between a given JSF view
id and managed bean name in your faces-config.xml (maybe you've already seen
those warnings No !ViewController found for view id ...). (For details on the
!ViewController pattern look into the
[http://shale.apache.org/shale-core/apidocs/org/apache/shale/view/ViewController.html
Javadoc]!)
- === Custom ===
+ == Default Implementation ==
- * http://www.mail-archive.com/user%40shale.apache.org/msg00158.html
+ The !DefaultViewControllerMapper maps view ids to managed bean names as
documented in it's
[http://shale.apache.org/shale-core/apidocs/org/apache/shale/view/impl/DefaultViewControllerMapper.html
Javadoc].
+ '''ATTENTION:''' When your view ids have dots in it's name (e.g.
tiles.like.file.name.jsp), the resulting managed bean name is illegal from
JSF's point of view. The resulting managed bean name will be
tiles.like.file.name. It can be used without problems for defining the
corresponding managed bean in your faces-config.xml. The problem is: it can
never be used as a value binding expression.
+ The reason: JSFs default !VariableResolver interprets the first '.' in a
value binding expression as separator between the scoped object (e.g. a managed
bean) and the referenced property or method. So in this small example the
!VariableResolver would look for a managed bean called tiles which is not
defined - booom!
+
+ == Custom Implementation ==
+
+ To modify the mapping between view ids and managed bean names you can replace
the !DefaultViewControllerMapper with an own implementation. As I stated in my
message [http://www.mail-archive.com/user%40shale.apache.org/msg00158.html
here], you have to provide the following context parameter entry in your
web.xml:{{{
+ context-param
+ param-nameorg.apache.shale.view.VIEW_CONTROLLER_MAPPER/param-name
+ param-valuefoo.MyVerySpecialViewControllerMapper/param-value
+ /context-param}}}
+
[Shale Wiki] Update of ReleasePlan102 by CraigMcClanahan
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/ReleasePlan102 -- - = ReleasePlan102 = - (Up to ReleasePlans) - == Shale 1.0.2 Release Plan == + = Shale 1.0.2 Release Plan = (This page was copied from the Struts Wiki, where the actual planning effort took place.)
[Shale Wiki] Update of LogoContest by schof
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by schof: http://wiki.apache.org/shale/LogoContest -- || Arun Sreedharan || [EMAIL PROTECTED] || attachment:aksSHALE_mst.gif || attachment:aksSHALE_pb.gif || || Andrei Dragomir || [EMAIL PROTECTED] || attachment:apacheshale_ro_buc.jpg || attachment:poweredbyapacheshale_ro_buc.jpg || || Mihai Copae || [EMAIL PROTECTED] || attachment:mihai_copae_logo.jpg || attachment:mihai_copae_powered.jpg || + || Michael Ameduri || [EMAIL PROTECTED] || attachment:6balls.jpg || attachment:powered6balls.jpg || + || Michael Ameduri || [EMAIL PROTECTED] || attachment:bic.jpg || attachment:poweredbic.jpg || + || Michael Ameduri || [EMAIL PROTECTED] || attachment:rocky.jpg || attachment:poweredrocky.jpg || + || Michael Ameduri || [EMAIL PROTECTED] || attachment:star.jpg || attachment:poweredstar.jpg || + || Michael Ameduri || [EMAIL PROTECTED] || attachment:wolf.jpg || attachment:poweredwolf.jpg ||
[Shale Wiki] Update of ReleasePlan102 by CraigMcClanahan
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/ReleasePlan102 -- (This page was copied from the Struts Wiki, where the actual planning effort took place.) + == Info == + + 1. Struts [http://struts.apache.org/releases.html#Releases Release Guidelines] + + 2. [http://wiki.apache.org/incubator/SigningReleases Signing Releases] + + 3. Apache [http://apache.org/dev/mirrors.html Mirroring Guidelines] + + == Release Manager == + + The release manager is '''Wendy Smoak''' + + == Special Issues == + + This release is likely to be an interim '''test build''' release of Shale technology. As such, you should assume that the APIs are still evolving and subject to change. For a stability rating on each API, see http://struts.apache.org/struts-shale/api-stability.html for more information. + + == Outstanding Bug Review == + + || '''ID''' || '''Summary''' || '''Component''' || '''Status''' || + || [http://issues.apache.org/bugzilla/show_bug.cgi?id=35066 35066] || Serious issue with dialog state || dialog || LATER[1] || + || [http://issues.apache.org/bugzilla/show_bug.cgi?id=35839 35839] || Clay processes components inside HTML comments || clay || LATER[2] || + || [http://issues.apache.org/bugzilla/show_bug.cgi?id=37024 37024] || No clay component configuration for MyFaces Tomahawk || clay || LATER[3] || + || [http://issues.apache.org/bugzilla/show_bug.cgi?id=37120 37120] || IFrame does not work properly inside Shale dialog || dialog || LATER[4] || + || [http://issues.apache.org/bugzilla/show_bug.cgi?id=37643 37643] || Add documentation for tiles and remoting features || docs || RFE[5] || + + + [1] The dialog facility is in need of improved functionality for handling multiple simulteously active dialogs, and dealing with back buttons. This issue is deferred to Shale 1.0.3 or later. + + [2] The proposed solution to this issue is to cut-n-paste the HTML parser that Tapestry uses for reading templates. Before going that way, it would be appropriate to see if the Tapestry developers were interested in abstracting out this code (perhaps to a commons project) so that it could be shared more easily. + + [3] The Shale contribution to addressing this issue is to ensure that META-INF/clay-config.jar resources in JAR files loaded as part of the application are automatically loaded. The actual configuration resources for a given component library such as Tomahawk, however, should be provided by the component library itself rather than by Shale. + + [4] Will be addressed as part of the overall support for multiple simultaneously active dialogs. + + [5] RFE to be reviewed for a subsequent release. + + + == Remaining Development Tasks == + + || '''Description''' || '''Status''' || + || Dialog - support multiple in-progress dialogs || LATER || + || (New) - optional layer of annotation support if running on JavaSE 5 || (./) || + || Documentation - finish basic feature descriptions || LATER || + + == Preparation Checklist == + + || '''#''' || '''Description''' || '''Status''' || + || 1. || Announce plan to dev@ list || (./) || + || 2. || Review/Complete Remaining Development Tasks || (./) || + || 3. || Review/Resolve Outstanding Bugs || (./) || + || 4. || Update Release Notes || (./) || + || 5. || Check Dependencies || (./) || + || 6. || Update to version 1.0.2 default.properties, project.xml, build/maven2/*.pom || (./) || + + The Commons [http://jakarta.apache.org/commons/releases/prepare.html Preparation Guide] is a helpful preparation backgrounder, but Commons + uses the beta/release-candidate/final process. + + Likewise, the [http://httpd.apache.org/dev/release.html HTTPD Release Guidelines] is a helpful overall process backgrounder, + but HTTPD does not use a test-build stage. + + Dependency versions for this release: + + || '''Dependency''' || '''Version''' || '''Status''' ||'''Used In''' || + || Commons !BeanUtils || 1.7.0 || Released || core, clay || + || Commons Chain || 1.0.0 || Released || core, clay || + || Commons Digester || 1.7.0 || Released || core, clay || + || Commons Logging || 1.0.4 || Released || core, clay, test, usecases || + || Commons Validator || 1.2.0 || Released || core || + || JavaServer Faces || 1.1 || Released || core, clay, test, usecases || + || Spring Framework (Optional) || 1.2.2 || Released || core || + || Struts Tiles Standalone || --- || Struts Sandbox || core || + || HtmlUnit (Optional) || 1.6 or 1.7 || Released || test, usecases || + + Because this is a test build release, a dependency on an unreleased component is acceptable. + + == Testing Checklist == + + === Testing Summary === + + || '''#''' || '''Description''' || '''Completed''' || + || 1. || Run Unit Test targets against JSF RI || (./) || + || 2. ||
[Shale Wiki] Update of ViewController by ReneZanner
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by ReneZanner: http://wiki.apache.org/shale/ViewController New page: == View Controller == === When to use init(), preprocess() and prerender() === In [http://www.nabble.com/Re%3A-Shale-AbstractViewController-for-Dummies-p4073019.html this thread], Craig suggests asking yourself the following questions: 1. Do I need the results of this computation in order to process a form submit? 1. Do I need the results of this computation in order to render the page? Then, based on your answers, * Use init() for ''(1) and (2)'' * Use preprocess() for ''(1) only'' * Use prerender() for ''(2) only''
[Shale Wiki] Update of ShaleCore by ReneZanner
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by ReneZanner: http://wiki.apache.org/shale/ShaleCore -- == Tutorials and Guides == - * ViewController + * ViewController (Several minor questions, e.g. When to use `init()`, `preprocess()` and `prerender()`) * ViewControllerMapper (Explains the default view controller mapper and how to use a custom one)
[Shale Wiki] Update of UsingMyFacesWithShaleClay by ReneZanner
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by ReneZanner: http://wiki.apache.org/shale/UsingMyFacesWithShaleClay The comment on the change is: content moced from Struts Wiki New page: * UsingPopupComponent
[Shale Wiki] Trivial Update of ShaleValidation by ReneZanner
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by ReneZanner: http://wiki.apache.org/shale/ShaleValidation -- ##language:en #pragma section-numbers off + + (original version in Struts Wiki from 2006-03-17 18:20:27 by NiallPemberton) + ||rowbgcolor=#E0[http://struts.apache.org/struts-shale/index.html Shale Home]||[:Shale:Wiki Home]||[:Shale/UserDocs:User Docs]||[:Shale/SiteMap:Index]||[:Shale/WikiGuidelines:Guidelines]||[:../:Go Up]|| -
[Shale Wiki] Update of UserDoc by ReneZanner
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by ReneZanner: http://wiki.apache.org/shale/UserDoc -- === Shale Features === * [:ShaleRemoting:Remoting] + * [:ShaleAndSpring:Spring Integration] * [:ShaleValidation:Validation]
[Shale Wiki] Update of LogoContest by JamesMitchell
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by JamesMitchell: http://wiki.apache.org/shale/LogoContest The comment on the change is: Some people need hand holding -- To submit your design, simply create a logo image and a powered-by image and add it to this wiki page along with your name and email address. Follow the existing format using double piping symbols || to create table cells. - To upload and display your images, Choose attachments from the More actions select list, upload your files (give them a unique name) and then edit this page and follow the example below. + To upload and display your images, you must login (create a new account if you don't already have one), then choose attachments from the More actions select list, upload your files (give them a unique name) and then edit this page and follow the example below. === The deadline for submissions is August 31, 2006. ===
[Shale Wiki] Update of LogoContest by DKolarova
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by DKolarova: http://wiki.apache.org/shale/LogoContest -- || Gulam Patel (Mikael) || [EMAIL PROTECTED] || attachment:shale_D.jpg || attachment:shale_D_1.jpg || || J. Klouda || [EMAIL PROTECTED] || attachment:jk_sh_hex.jpg || attachment:jk_sh_hex_pbcut.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleSilver.jpg || attachment:ShaleSilverPoweredBy.jpg || + || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg ||
[Shale Wiki] Update of LogoContest by tarawakefield
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by tarawakefield: http://wiki.apache.org/shale/LogoContest -- || Gulam Patel (Mikael) || [EMAIL PROTECTED] || attachment:shale_D.jpg || attachment:shale_D_1.jpg || || J. Klouda || [EMAIL PROTECTED] || attachment:jk_sh_hex.jpg || attachment:jk_sh_hex_pbcut.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleSilver.jpg || attachment:ShaleSilverPoweredBy.jpg || - || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || + || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || t. wakefield || [EMAIL PROTECTED] || attachment:shalie.jpg || attachment:shaliepower.jpg
[Shale Wiki] Update of LogoContest by tarawakefield
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by tarawakefield: http://wiki.apache.org/shale/LogoContest -- || J. Klouda || [EMAIL PROTECTED] || attachment:jk_sh_hex.jpg || attachment:jk_sh_hex_pbcut.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleSilver.jpg || attachment:ShaleSilverPoweredBy.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || - || t. wakefield || [EMAIL PROTECTED] || attachment:shalie.jpg || attachment:shaliepower.jpg || + || t. wakefield || [EMAIL PROTECTED] || attachment:shalebird.jpg || attachment:shalebirdpower.jpg ||
[Shale Wiki] Update of LogoContest by ConnorGarvey
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by ConnorGarvey: http://wiki.apache.org/shale/LogoContest -- || J. Klouda || [EMAIL PROTECTED] || attachment:jk_sh_hex.jpg || attachment:jk_sh_hex_pbcut.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleSilver.jpg || attachment:ShaleSilverPoweredBy.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || - || t. wakefield || [EMAIL PROTECTED] || attachment:shalebird.jpg || attachment:shalebirdpower.jpg || + || t. wakefield || [EMAIL PROTECTED] || attachment:shalebird.jpg || attachment:shalebirdpower.jpg || || Connor Garvey || [EMAIL PROTECTED] || attachment:Simple-2.png || attachment:Simple-2-Powered.png ||
[Shale Wiki] Update of LogoContest by AndrewSmith
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by AndrewSmith: http://wiki.apache.org/shale/LogoContest -- || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || || t. wakefield || [EMAIL PROTECTED] || attachment:shalebird.jpg || attachment:shalebirdpower.jpg || || Connor Garvey || [EMAIL PROTECTED] || attachment:Simple-2.png || attachment:Simple-2-Powered.png || + || Andrew Smith || [EMAIL PROTECTED] || attachment:shale-basic.png || attachment:shale-basic-poweredby.png ||
[Shale Wiki] Update of LogoContest by AndrewSmith
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by AndrewSmith: http://wiki.apache.org/shale/LogoContest -- || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || || t. wakefield || [EMAIL PROTECTED] || attachment:shalebird.jpg || attachment:shalebirdpower.jpg || || Connor Garvey || [EMAIL PROTECTED] || attachment:Simple-2.png || attachment:Simple-2-Powered.png || - || Andrew Smith || [EMAIL PROTECTED] || attachment:shale-basic.png || attachment:shale-basic-poweredby.png ||
[Shale Wiki] Update of LogoContest by DKolarova
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by DKolarova: http://wiki.apache.org/shale/LogoContest -- || J. Klouda || [EMAIL PROTECTED] || attachment:jk_sh_hex.jpg || attachment:jk_sh_hex_pbcut.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleSilver.jpg || attachment:ShaleSilverPoweredBy.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || + || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleTextSpheres.jpg || attachment:ShaleTextSpheresPoweredBy.jpg|| || t. wakefield || [EMAIL PROTECTED] || attachment:shalebird.jpg || attachment:shalebirdpower.jpg || || Connor Garvey || [EMAIL PROTECTED] || attachment:Simple-2.png || attachment:Simple-2-Powered.png || || Andrew Smith || [EMAIL PROTECTED] || attachment:shale-basic.png || attachment:shale-basic-poweredby.png ||
[Shale Wiki] Update of LogoContest by Karolina Gorska
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Karolina Gorska: http://wiki.apache.org/shale/LogoContest -- || Michael Ameduri || [EMAIL PROTECTED] || attachment:blackglossy.jpg || attachment:blackglossy-power.jpg || || Michael Ameduri || [EMAIL PROTECTED] || attachment:steel-bar.jpg || attachment:steel-bar-power.jpg || || Michael Ameduri || [EMAIL PROTECTED] || attachment:purple-star.jpg || attachment:purple-star-powered.jpg || + || Karolina Gorska || [EMAIL PROTECTED] || attachment:Shale_eye.jpg || attachment:Shale_eye_power.jpg ||
[Shale Wiki] Update of LogoContest by Karolina Gorska
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Karolina Gorska: http://wiki.apache.org/shale/LogoContest -- || Michael Ameduri || [EMAIL PROTECTED] || attachment:steel-bar.jpg || attachment:steel-bar-power.jpg || || Michael Ameduri || [EMAIL PROTECTED] || attachment:purple-star.jpg || attachment:purple-star-powered.jpg || || Karolina Gorska || [EMAIL PROTECTED] || attachment:Shale_eye.jpg || attachment:Shale_eye_power.jpg || + || Karolina Gorska || [EMAIL PROTECTED] || attachment:Shale_point.jpg || attachment:Shale_point_power.jpg ||
[Shale Wiki] Update of LogoContest by gemmyfang
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by gemmyfang: http://wiki.apache.org/shale/LogoContest -- || Karolina Gorska || [EMAIL PROTECTED] || attachment:Shale_eye.jpg || attachment:Shale_eye_power.jpg || || Karolina Gorska || [EMAIL PROTECTED] || attachment:Shale_point.jpg || attachment:Shale_point_power.jpg || || Pakcik Kantin || [EMAIL PROTECTED] || attachment:pakcik-shale-big-1.gif || attachment:pakcik-shale-small-1.gif || - || Pakcik Kantin || [EMAIL PROTECTED] || attachment:pakcik-shale-big-2.gif || attachment:pakcik-shale-small-2.gif || + || Gemmy Fang || [EMAIL PROTECTED] || attachment:shale_logo.gif || attachment:power_by_shale.gif ||
[Shale Wiki] Update of 维基沙盘演练 b y CraigMcClanahan
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by CraigMcClanahan:
http://wiki.apache.org/shale/%e7%bb%b4%e5%9f%ba%e6%b2%99%e7%9b%98%e6%bc%94%e7%bb%83
--
+ deleted
- ## Please edit system and help pages ONLY in the moinmaster wiki! For more
- ## information, please see MoinMaster:MoinPagesEditorGroup.
- ##master-page:WikiSandBox
- ##master-date:2004-10-06 09:33:07
- #format wiki
- #language zh
- == 请注æ ==
-
- å¨ä¸é¢çå个ç横åé¢æ¨å¯ä»¥éæç¼è¾ç»ä¹ ...
ä½è¯·'''ä¸è¦'''ä»
ä»
为äºè¯ä¸ä¸ï¼å°±å¨æ²¡ææä»·å¼å
容çæ
åµä¸å建æ°çç½é¡µï¼
-
- '''æå·§:'''
Shift-ç¹å»[帮å©-ç¼è¾]å¨å¦å¤ä¸ä¸ªçªå£ä¸é
读帮å©ç½é¡µã
-
-
- hello
- == æç ==
-
-
- ''æä½'' '''ç²ä½''' {{{æåæºåä½}}}
-
- `ç¨åå¼å·æ¬èµ·çæåæºåä½` (å¯è½éè¦è®¾ç½®)
-
- ~+ 大ä¸ç¹ +~ ~- å°ä¸äº -~
-
- {{{
- é¢å
æ好ç
- }}}
-
- {{{#!python
- def syntax(highlight):
- print on
- return None
- }}}
-
- == é¾æ¥ ==
-
- HelpOnEditing MoinMoin:InterWiki
-
- [帮å©-ç¼è¾]
-
- http://purl.net/wiki/moin/ [http://www.python.org/ Python]
-
- [EMAIL PROTECTED]
-
-
- === å¾çé¾æ¥ ===
- [http://c2.com/cgi/wiki http://c2.com/sig/wiki.gif]
-
- == å表 ==
-
- === åç¹ ===
- * ä¸
-1. åµå¥å¹¶ç¼å·
-1. ç¼å·çå表æ»æ¯éæ°ç¼å·ç
- * äº
- * ä¸
-é£ä¹ãé£ä¹
- 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨
大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨
大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨
大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨
大åå¼ç¨
-æ´å¤ç¼©è¿
-
- === è¯æ±è¡¨===
- æ¯è¯:: å®ä¹
-
- === å¾ç» ===
- drawing:mytest
-
- = æ é¢ 1 =
- == æ é¢ 2 ==
- === æ é¢ 3 ===
- æ é¢ 4
- = æ é¢ 5=
-
- å
容
-
- = IRCæ¥å¿æµè¯ =
-
- {{{#!irc
- (23:18) jroes ah
- (23:19) jroes hm, i like the way {{{ works, but i was hoping the lines
would wrap
- (23:21) -!- gpciceri [EMAIL PROTECTED] has quit [Read error: 110 (Connection
timed out)]
- (23:36) ThomasWal you could also write a parser or processor
- (23:38) jroes i could?
- (23:38) jroes would that require modification on the moin end though?
- (23:38) jroes i cant change the wiki myself :x
- (23:39) ThomasWal parsers and processors are plugable
- (23:39) ThomasWal so you dont need to change the core code
- (23:40) ThomasWal you need to copy it to the wiki data directory though
- (23:40) jroes well, what i meant to say was that i dont have access to
the box running the wiki
- (23:40) ThomasWal then this is no option awdsd asdasd sa asdasd sad
asdadasds adasd asd asd asd asd asd a dadad ad adad ad asd asd adad asdasd asd
adad as d
- (23:40) jroes yeah :/
- }}}
-
- æ¤é¡µçè±æçæ¬ï¼WikiSandBox
-
[Shale Wiki] Update of LogoContest by Chris Schaer
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Chris Schaer: http://wiki.apache.org/shale/LogoContest -- || Karolina Gorska || [EMAIL PROTECTED] || attachment:Shale_point.jpg || attachment:Shale_point_power.jpg || || Pakcik Kantin || [EMAIL PROTECTED] || attachment:pakcik-shale-big-1.gif || attachment:pakcik-shale-small-1.gif || || Gemmy Fang || [EMAIL PROTECTED] || attachment:gemmyfang_shale_logo.gif || attachment:gemmyfang_power_by_shale.gif || + || Chris Schaer || [EMAIL PROTECTED] || attachment:webdevil_shale.gif || attachment:webdevil_powered.gif ||
[Shale Wiki] Update of LogoContest by Chris Schaer
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Chris Schaer: http://wiki.apache.org/shale/LogoContest -- || Karolina Gorska || [EMAIL PROTECTED] || attachment:Shale_point.jpg || attachment:Shale_point_power.jpg || || Pakcik Kantin || [EMAIL PROTECTED] || attachment:pakcik-shale-big-1.gif || attachment:pakcik-shale-small-1.gif || || Gemmy Fang || [EMAIL PROTECTED] || attachment:gemmyfang_shale_logo.gif || attachment:gemmyfang_power_by_shale.gif || - || Chris Schaer || [EMAIL PROTECTED] || attachment:webdevil_shale.gif || attachment:webdevil_powered.gif ||
[Shale Wiki] Update of FrontPage by WendySmoak
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/shale/FrontPage -- * ReleaseGuidelines * ReleasePlans + * ReleaseProcess
[Shale Wiki] Update of ReleaseProcess by WendySmoak
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/shale/ReleaseProcess The comment on the change is: Capture Sean's JIRA instructions. New page: === Archive the SNAPSHOT version in JIRA === 1.) Create a new JIRA version for the release (ex. 1.0.3) 2.) Search and then bulk change unresolved issues with a fix for of the old snapshot version (ex. 1.0.3-SNAPSHOT) and change to Unknown. At this point in the process, there shouldn't be any issues left on the roadmap but do a search (and bulk change) if necessary. For all bulk changes be sure to uncheck the Send mail for this update option on Step 3. 3.) Search and then bulk change resolved issues with a fix for of the old snapshot version (ex. 1.0.3-SNAPSHOT) and change to the new version (ex. 1.0.3). For all bulk changes be sure to uncheck the Send mail for this update option on Step 3. 4.) Archive the old version. This allows you to still search on issues that were *reported* against a SNAPSHOT version yet it prevents you from reporting new issues against the SNAPSHOT.
[Shale Wiki] Update of ReleaseGuidelines by CraigMcClanahan
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/ReleaseGuidelines The comment on the change is: Initial draft for doing releases with both Maven and release artifacts New page: = Shale Release Guidelines = == Document Status == This document is currently being updated to note the steps required to perform a Shale release based on our new Maven 2 based build infrastructure. After refinement, it will likely be voted on as a ''normative'' process document. Until then, it should be considered to be ''informative'' only. == Steady State Conditions == Between releases, it is assumed that the following conditions hold: * Version number in all of the POMs is '''x.y.z-SNAPSHOT''' (for instance, 1.0.3-SNAPSHOT) * JIRA contains a version labelled '''x.y.z-SNAPSHOT''' used to tag issues to be fixed in this release * Developers complete an issue by setting status to '''Resolved''' with an appropriate ''Resolution'' FIXME - maybe need note about developers testing against both MyFaces and the JSF RI? And running integration tests as well as unit tests? Or maybe this should all go on a page about stuff to do before you check code in. Occasionally, it may be necessary to update the Shale Master POM (maven/master-pom/pom.xml). If this becomes necessary, it must be released separately, before a Shale release that depends upon it can be performed. See ShaleReleaseMasterPom for more information. == Begin Release Planning == Appoint a release manager for the upcoming release. He or she will manage the remainder of the process described in this document. Release manager should set a target date for the release, and set up a Release Plan page on the wiki, using ReleasePlanTemplate (FIXME - this document is not ready to use yet) as a page template. The new release plan page should be linked from ReleasePlans also. Review outstanding unresolved JIRA issues, to determine whether to target setting the ''Fix Version'' for each issue to '''x.y.z-SNAPSHOT''' or not. This will likely involve discussions on the dev list to come to consensus on what is in and what is not. == Work Off The Road Map == From this point forward the JIRA Road Map for release '''x.y.z-SNAPSHOT''' will be an invaluable resource in seeing what is left to be accomplished. Encourage developers to focus on the road map issues. After the initial review, no new issues should be set with a fix version of '''x.y.z-SNAPSHOT''' without the explicit agreement of the release manager, and the consent (implied by silence or explicit) of the other developers. == Final Snapshot Review == After all road map issues have been resolved, release manager should coordinate an in depth review of the latest snapshot, in preparation for switching to the real '''x.y.z''' version number and publishing the release. This involves preparing both Maven artifacts to be published into a repository, and release artifacts to be published on the Apache distributions server and mirror network. To prepare and validate the Maven artifacts: * Turn off any automated deployment or artifact publishing from continuous build or nightly build scripts * Check out and locally build the entire trunk (see FIXME for details) * Deploy all artifacts that will be deployed in the official release (see FIXME for details) into the snapshot repository * Digitally sign each of the release artifacts (both POMs and JARs) (see FIXME for details) and manually upload the .asc signature files to be sitting next to the artifacts they have signed * Ask on the dev list for people to examine the individual artifacts and report back: * Appropriate ontents of each JAR file * Correct META-INF/MANIFEST.MF values * Correct POM settings, such as dependencies and versions * Validity of checksums and digital signatures To prepare and validate the release artifacts: * Check out and locally build the entire trunk (see FIXME for details) * Build the release artifacts using appropriate assembly steps (see FIXME for details) * Create .md5 and .sha1 checksums for each release artifact * Digitally sign each release artifact (see FIXME for details) * Upload the snapshot release artifacts, checksums, and digital signatures to a convenient place (such as a subdirectory of the release manager's public_html directory) * Ask on the dev list for people to examine the individual release artifacts and report back: * Appropriate contents of each artifact * Can each artifact be rebuilt from itself with Maven? * For sample apps, can the apps be succesfully dropped into a servlet container and run? * Validity of checksums and digital signatures Iterate over these review processes until the release manager is satisfied that it is time to actually cut a test release and post it. == Cut An Actual Release ==
[Shale Wiki] Update of FrontPage by CraigMcClanahan
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/FrontPage The comment on the change is: Add link to a new whiteboard page for dialog -- * ReleasePlans * ReleaseProcess + === Features Whiteboard Pages === + + * DialogFeature +
[Shale Wiki] Update of FrontPage by CraigMcClanahan
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/FrontPage The comment on the change is: Correct name for new page -- === Features Whiteboard Pages === - * DialogFeature + * DialogManagerFeature
[Shale Wiki] Update of DialogManagerFeature by CraigMcClanahan
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/DialogManagerFeature The comment on the change is: First crack at a requirements list for the dialog feature -- = Dialog Manager Feature = + + == Introduction == The [http://shale.apache.org/features-dialog-manager.html Dialog Manager] feature of Shale shows promise in helping application developers organize large scale applications into conversations with the user, maintaining local state solely for the duration of that conversation (instead of letting it accumulate in session scope until the user logs off). Unfortunately, the current implementation is the subject of several outstanding bug reports: * [https://issues.apache.org/struts/browse/SHALE-10 SHALE-10] IFrame does not work properly inside Shale dialog @@ -9, +11 @@ To address these issues, it seems likely that some rearchitecture will be required. In that case, it also makes sense to go back and articulate the set of requirements that the revised functionality should support, to ensure that they all get met satisfactorily. + == Requirements == + + For an appropriate prioritization, the requirements below are separated into MANDATORY, DESIREABLE, and NICE TO HAVE buckets. Within each bucket, requirements are numbered - so any new requirements added to a bucket later should go to the end. Original requirements that we decide to remove from the list should be visually labelled in some way, to maintain the identity of the requirement numbers. + + === Mandatory Requirements === + + 1. Make implementation decisions that minimize the amount of new learning for a developer that is already familiar with JSF. + * Also, leverage existing JSF concepts such as managed beans and programmatic expression evaluation where it is useful. + 1. Support modelling of a dialog as a UML state diagram, with states embodying various kinds of processing activity and transitions between states being driven by logical outcomes from these activities. + 1. Support configuration of zero or more uniquely named dialogs within the scope of a single web application. + * An XML based configuration mechanism is required, with support for one or more configuration resources, a default resource name if none is specified, and automatic recognition of configuration resources in the META-INF section of a JAR file. + 1. Support the concept of an ''action'' state that represents a call to an arbitrary method of some arbitrary bean, which returns a logical outcome. + * Support configuration of the method to be called with a JSF method binding expression + * Logical outcome returned by this method is used to select the appropriate transition + 1. Support the concept of a ''view'' state that represents the rendering of a particular JSF view, following by a subsequent postback, up to and including Invoke Application phase. + * Logical outcome returned by the invoked action method is used to select the appropriate transition + 1. Support the concept of an ''exit'' state that causes the current dialog to be completed (throwing away any stored state information). + * Requires some mechanism for an exit state to provide a logical outcome, in order to drive transitions in a parent dialog + 1. Support the concept of a ''subdialog'' state that allows reuse of a different dialog definition as a black box subroutine. + * Logical outcome returned by the exit state of the invoked subdialog is used to select the appropriate transition. + 1. Context data for a currently executing dialog must be maintained while a dialog is in progress, and must be automatically thrown away when the dialog is exited. + * Must be accessible programmatically in JSF event handlers + 1. Support for multiple active dialog instances within a single page. + * Includes support for multiple instances of the same dialog name. + 1. Support for multiple active dialog instances across multiple frames or windows, including popup windows. + * Includes support for multiple instances of the same dialog name. + 1. State synchronization must deal appropriately with use of browser navigation buttons. + 1. Implementation must not modify standard JSF semantics like return null from an action method means redisplay the current view. + 1. Must be possible to enter a dialog as a result of a JSF navigation rule. + + === Desireable Requirements === + + 1. Context information for a currently active dialog instance is accessible via a custom VariableResolver so that it can be referenced with value binding expressions. (May be difficult to disambiguate a single variable name if there are multiple active dialog instances going on.) + 1. Use of a particular JSF view
[Shale Wiki] Update of LogoContest by WangJianbin
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WangJianbin: http://wiki.apache.org/shale/LogoContest -- || Chris Schaer || [EMAIL PROTECTED] || attachment:webdevil_shale.gif || attachment:webdevil_powered.gif || || M.J. DeSantis || [EMAIL PROTECTED] || attachment:shale_wave.gif || attachment:shale_wave_powered.gif || || M.J. DeSantis || [EMAIL PROTECTED] || attachment:shale_wave2.gif || attachment:shale_wave_powered.gif || + || Wang Jianbin || [EMAIL PROTECTED] || attachment:shale_james.jpg || attachment:power_shale_james.jpg ||
[Shale Wiki] Update of LogoContest by WangJianbin
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WangJianbin: http://wiki.apache.org/shale/LogoContest -- || Chris Schaer || [EMAIL PROTECTED] || attachment:webdevil_shale.gif || attachment:webdevil_powered.gif || || M.J. DeSantis || [EMAIL PROTECTED] || attachment:shale_wave.gif || attachment:shale_wave_powered.gif || || M.J. DeSantis || [EMAIL PROTECTED] || attachment:shale_wave2.gif || attachment:shale_wave_powered.gif || - || Wang Jianbin || [EMAIL PROTECTED] || attachment:shale_james.jpg || attachment:power_shale_james.jpg || + || Wang Jianbin || [EMAIL PROTECTED] || attachment:F__document_PhotoShop_shale_james.jpg || attachment:F__document_PhotoShop_power_shale_james.jpg ||
[Shale Wiki] Update of LogoContest by WesleyHales
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WesleyHales: http://wiki.apache.org/shale/LogoContest -- || Pakcik Kantin || [EMAIL PROTECTED] || attachment:apache-shale3.gif || attachment:apache-shale3-small.gif || || Wesley Hales || [EMAIL PROTECTED] || attachment:shale1.jpg || attachment:PBshale1.jpg || || Wesley Hales || [EMAIL PROTECTED] || attachment:WH_shale2.jpg || attachment:WH_PBshale2.jpg || + || Wesley Hales || [EMAIL PROTECTED] || attachment:WH_shale3.jpg || attachment:WH_PBshale3.jpg ||
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Wesley Hales || [EMAIL PROTECTED] || attachment:WH_shale4.jpg || attachment:WH_PBshale4.jpg || || Nik Wahlberg || [EMAIL PROTECTED] || attachment:nw_shale_logo.gif || attachment:nw_shale_logo_pb.gif || || JSchmidt || [EMAIL PROTECTED] || attachment:jSchmidt_shale_logo.jpg || attachment:jSchmidt_shale_powered.jpg || - || iD || [EMAIL PROTECTED] || attachment:shale_deposits.jpg || + || iD || [EMAIL PROTECTED] || attachment:shale_deposits.jpg || attachment:shale_depositsPW.jpg || - attachment:shale_depositsPW.jpg || + || iD || [EMAIL PROTECTED] || attachment:shale_framework.jpg || attachment:shale_frameworkPW.jpg
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Wesley Hales || [EMAIL PROTECTED] || attachment:WH_shale4.jpg || attachment:WH_PBshale4.jpg || || Nik Wahlberg || [EMAIL PROTECTED] || attachment:nw_shale_logo.gif || attachment:nw_shale_logo_pb.gif || || JSchmidt || [EMAIL PROTECTED] || attachment:jSchmidt_shale_logo.jpg || attachment:jSchmidt_shale_powered.jpg || - || iD || [EMAIL PROTECTED] || attachment:shale_deposits.jpg || attachment:shale_depositsPW.jpg || + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_deposits.jpg || attachment:shale_depositsPW.jpg || - || iD || [EMAIL PROTECTED] || attachment:shale_framework.jpg || attachment:shale_frameworkPW.jpg || + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_framework.jpg || attachment:shale_frameworkPW.jpg || - || iD || [EMAIL PROTECTED] || attachment:shale_underground.jpg || attachment:shale_undergroundPW.jpg || + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_underground.jpg || attachment:shale_undergroundPW.jpg || - || iD || [EMAIL PROTECTED] || attachment:shale_struts_shale.jpg || attachment:shale_struts_shalePW.jpg || + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_struts_shale.jpg || attachment:shale_struts_shalePW.jpg || + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_overground.jpg || attachment:shale_overgroundPW.jpg ||
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Wesley Hales || [EMAIL PROTECTED] || attachment:WH_shale4.jpg || attachment:WH_PBshale4.jpg || || Nik Wahlberg || [EMAIL PROTECTED] || attachment:nw_shale_logo.gif || attachment:nw_shale_logo_pb.gif || || JSchmidt || [EMAIL PROTECTED] || attachment:jSchmidt_shale_logo.jpg || attachment:jSchmidt_shale_powered.jpg || + + /!\ '''Edit conflict - other version:''' || Aide Chang || [EMAIL PROTECTED] || attachment:shale_deposits.jpg || attachment:shale_depositsPW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_framework.jpg || attachment:shale_frameworkPW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_underground.jpg || attachment:shale_undergroundPW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_struts_shale.jpg || attachment:shale_struts_shalePW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_overground.jpg || attachment:shale_overgroundPW.jpg || + /!\ '''Edit conflict - your version:''' + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_deposits.jpg || attachment:shale_depositsPW.jpg || + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_framework.jpg || attachment:shale_frameworkPW.jpg || + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_underground.jpg || attachment:shale_undergroundPW.jpg || + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_struts_shale.jpg || attachment:shale_struts_shalePW.jpg || + || Aide Chang || [EMAIL PROTECTED] || attachment:shale_overground.jpg || attachment:shale_overgroundPW.jpg || +
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Wesley Hales || [EMAIL PROTECTED] || attachment:WH_shale4.jpg || attachment:WH_PBshale4.jpg || || Nik Wahlberg || [EMAIL PROTECTED] || attachment:nw_shale_logo.gif || attachment:nw_shale_logo_pb.gif || || JSchmidt || [EMAIL PROTECTED] || attachment:jSchmidt_shale_logo.jpg || attachment:jSchmidt_shale_powered.jpg || - - /!\ '''Edit conflict - other version:''' || Aide Chang || [EMAIL PROTECTED] || attachment:shale_deposits.jpg || attachment:shale_depositsPW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_framework.jpg || attachment:shale_frameworkPW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_underground.jpg || attachment:shale_undergroundPW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_struts_shale.jpg || attachment:shale_struts_shalePW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_overground.jpg || attachment:shale_overgroundPW.jpg || - /!\ '''Edit conflict - your version:''' - || Aide Chang || [EMAIL PROTECTED] || attachment:shale_deposits.jpg || attachment:shale_depositsPW.jpg || - || Aide Chang || [EMAIL PROTECTED] || attachment:shale_framework.jpg || attachment:shale_frameworkPW.jpg || - || Aide Chang || [EMAIL PROTECTED] || attachment:shale_underground.jpg || attachment:shale_undergroundPW.jpg || - || Aide Chang || [EMAIL PROTECTED] || attachment:shale_struts_shale.jpg || attachment:shale_struts_shalePW.jpg || - || Aide Chang || [EMAIL PROTECTED] || attachment:shale_overground.jpg || attachment:shale_overgroundPW.jpg || -
[Shale Wiki] Update of LogoContest by coco
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by coco: http://wiki.apache.org/shale/LogoContest The comment on the change is: add my design -- || Aide Chang || [EMAIL PROTECTED] || attachment:shale_underground.jpg || attachment:shale_undergroundPW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_struts_shale.jpg || attachment:shale_struts_shalePW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_overground.jpg || attachment:shale_overgroundPW.jpg || + || Coco || [EMAIL PROTECTED] || attachment:coco1.gif || attachment:coco11.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco2.gif || attachment:coco21.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco3.gif || attachment:coco31.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco4.gif || attachment:coco41.gif ||
[Shale Wiki] Update of LogoContest by coco
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by coco: http://wiki.apache.org/shale/LogoContest -- || Aide Chang || [EMAIL PROTECTED] || attachment:shale_underground.jpg || attachment:shale_undergroundPW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_struts_shale.jpg || attachment:shale_struts_shalePW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_overground.jpg || attachment:shale_overgroundPW.jpg || - || Coco || [EMAIL PROTECTED] || attachment:coco1.gif || attachment:coco11.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco1.gif || attachment:coco1.gif || - || Coco || [EMAIL PROTECTED] || attachment:coco2.gif || attachment:coco21.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco2.gif || attachment:coco2.gif || - || Coco || [EMAIL PROTECTED] || attachment:coco3.gif || attachment:coco31.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco3.gif || attachment:coco3.gif || - || Coco || [EMAIL PROTECTED] || attachment:coco4.gif || attachment:coco41.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco4.gif || attachment:coco4.gif ||
[Shale Wiki] Update of LogoContest by coco
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by coco: http://wiki.apache.org/shale/LogoContest -- || Aide Chang || [EMAIL PROTECTED] || attachment:shale_underground.jpg || attachment:shale_undergroundPW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_struts_shale.jpg || attachment:shale_struts_shalePW.jpg || || Aide Chang || [EMAIL PROTECTED] || attachment:shale_overground.jpg || attachment:shale_overgroundPW.jpg || - || Coco || [EMAIL PROTECTED] || attachment:coco1.gif || attachment:coco1.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco1.gif || attachment:coco11.gif || - || Coco || [EMAIL PROTECTED] || attachment:coco2.gif || attachment:coco2.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco2.gif || attachment:coco21.gif || - || Coco || [EMAIL PROTECTED] || attachment:coco3.gif || attachment:coco3.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco3.gif || attachment:coco31.gif || - || Coco || [EMAIL PROTECTED] || attachment:coco4.gif || attachment:coco4.gif || + || Coco || [EMAIL PROTECTED] || attachment:coco4.gif || attachment:coco41.gif ||
[Shale Wiki] Update of LogoContest by TriSeprian
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by TriSeprian: http://wiki.apache.org/shale/LogoContest -- || Coco || [EMAIL PROTECTED] || attachment:coco4.gif || attachment:coco41.gif || || Santy || [EMAIL PROTECTED] || attachment:santy_shalelogo1.jpg || attachment:santy_shalelogopowered1.jpg || || Binfel || [EMAIL PROTECTED] || attachment:logo-shale2.gif || attachment:logo-shale-powered.gif || + || TriSeprian || [EMAIL PROTECTED] || attachment:seprian_shale1.jpg || attachment:seprian_shale1_pow.jpg
[Shale Wiki] Update of LogoContest by TriSeprian
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by TriSeprian: http://wiki.apache.org/shale/LogoContest -- || Coco || [EMAIL PROTECTED] || attachment:coco4.gif || attachment:coco41.gif || || Santy || [EMAIL PROTECTED] || attachment:santy_shalelogo1.jpg || attachment:santy_shalelogopowered1.jpg || || Binfel || [EMAIL PROTECTED] || attachment:logo-shale2.gif || attachment:logo-shale-powered.gif || - || TriSeprian || [EMAIL PROTECTED] || attachment:seprian_shale1.jpg || attachment:seprian_shale1_pow.jpg + || TriSeprian || [EMAIL PROTECTED] || attachment:seprian_shale1.jpg || attachment:seprian_shale1_pow.jpg ||
[Shale Wiki] Update of DialogManagerFeature by CraigMcClanahan
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/DialogManagerFeature The comment on the change is: Add some really good ideas from Paul Spencer on the dev list -- 1. State synchronization must deal appropriately with use of browser navigation buttons. 1. Implementation must not modify standard JSF semantics like return null from an action method means redisplay the current view. 1. Must be possible to enter a dialog as a result of a JSF navigation rule. + 1. It must be possible to use the dialog management features without relying on any state save/restore facilities of the dialog functionality, as long as the application is managing its own state in this scenario. (Credit for this idea to Paul Spencer paulsp AT apache.org.) + 1. The framework must provide a configurable mechanism to deal with application exceptions that does not disable dialog functionality. (Credit for this idea to Paul Spencer paulsp AT apache.org.) === Desireable Requirements === @@ -58, +60 @@ 1. Support of either a custom dialog-defined JavaBean with properties for individual state data, or a generic Map, as the holder of state data. 1. Programmatic entry into, and exit from, a dialog instance (in addition to navigation based entry and exit state based exit). 1. A stable public API to access the static configuration of a dialog (as opposed to the dynamic state and context of an executing dialog instance). + 1. The framework should recognize updated configuration files and reload them, without requiring an application restart. (Credit for this idea to Paul Spencer paulsp AT apache.org.) === Nice To Have Requirements ===
[Shale Wiki] Update of LogoContest by PRathore
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by PRathore: http://wiki.apache.org/shale/LogoContest -- || Santy || [EMAIL PROTECTED] || attachment:santy_shalelogo1.jpg || attachment:santy_shalelogopowered1.jpg || || Binfel || [EMAIL PROTECTED] || attachment:logo-shale2.gif || attachment:logo-shale-powered.gif || || TriSeprian || [EMAIL PROTECTED] || attachment:seprian_shale1.jpg || attachment:seprian_shale1_pow.jpg || + || PRathore || [EMAIL PROTECTED] || attachment:logo_p || attachment:powered_logo_p||
[Shale Wiki] Update of LogoContest by PRathore
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by PRathore: http://wiki.apache.org/shale/LogoContest -- || Santy || [EMAIL PROTECTED] || attachment:santy_shalelogo1.jpg || attachment:santy_shalelogopowered1.jpg || || Binfel || [EMAIL PROTECTED] || attachment:logo-shale2.gif || attachment:logo-shale-powered.gif || || TriSeprian || [EMAIL PROTECTED] || attachment:seprian_shale1.jpg || attachment:seprian_shale1_pow.jpg || - || PRathore || [EMAIL PROTECTED] || attachment:logo_p || attachment:powered_logo_p||
[Shale Wiki] Update of LogoContest by PRathore
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by PRathore: http://wiki.apache.org/shale/LogoContest -- || Santy || [EMAIL PROTECTED] || attachment:santy_shalelogo1.jpg || attachment:santy_shalelogopowered1.jpg || || Binfel || [EMAIL PROTECTED] || attachment:logo-shale2.gif || attachment:logo-shale-powered.gif || || TriSeprian || [EMAIL PROTECTED] || attachment:seprian_shale1.jpg || attachment:seprian_shale1_pow.jpg || + || TriSeprian || [EMAIL PROTECTED] || attachment:seprian_shale1.jpg || attachment:seprian_shale1_pow.jpg || + || PRathore || [EMAIL PROTECTED] || attachment:logo_p.jpg || attachment:powered_logo_p.jpg ||
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Walied Amer || [EMAIL PROTECTED] || attachment:walied02.jpg || attachment:walied02_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied03.jpg || attachment:walied03_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied04.jpg || attachment:walied04_powered.jpg || + || Daniel Yang || [EMAIL PROTECTED] || attachment:individual.jpg || attachment:individualPW.jpg ||
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Walied Amer || [EMAIL PROTECTED] || attachment:walied03.jpg || attachment:walied03_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied04.jpg || attachment:walied04_powered.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:individual.jpg || attachment:individualPW.jpg || + || Daniel Yang || [EMAIL PROTECTED] || attachment:individual_2.jpg || attachment:individual_2PW.jpg || + || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS.jpg || attachment:LogoS_PW.jpg || + || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS_2.jpg || attachment:LogoS_2PW.jpg || + || Daniel Yang || [EMAIL PROTECTED] || attachment:underground_2.jpg || attachment:underground_2PW.jpg ||
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Walied Amer || [EMAIL PROTECTED] || attachment:walied02.jpg || attachment:walied02_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied03.jpg || attachment:walied03_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied04.jpg || attachment:walied04_powered.jpg || - || Daniel Yang || [EMAIL PROTECTED] || attachment:individual.jpg || attachment:individualPW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:individual_2.jpg || attachment:individual_2PW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS.jpg || attachment:LogoS_PW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS_2.jpg || attachment:LogoS_2PW.jpg ||
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Walied Amer || [EMAIL PROTECTED] || attachment:walied02.jpg || attachment:walied02_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied03.jpg || attachment:walied03_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied04.jpg || attachment:walied04_powered.jpg || + || Daniel Yang || [EMAIL PROTECTED] || attachment:individual.jpg || attachment:individualPW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:individual_2.jpg || attachment:individual_2PW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS.jpg || attachment:LogoS_PW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS_2.jpg || attachment:LogoS_2PW.jpg ||
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Walied Amer || [EMAIL PROTECTED] || attachment:walied02.jpg || attachment:walied02_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied03.jpg || attachment:walied03_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied04.jpg || attachment:walied04_powered.jpg || - || Daniel Yang || [EMAIL PROTECTED] || attachment:individual.jpg || attachment:individualPW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:individual_2.jpg || attachment:individual_2PW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS.jpg || attachment:LogoS_PW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS_2.jpg || attachment:LogoS_2PW.jpg ||
[Shale Wiki] Update of LogoContest by iD
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by iD: http://wiki.apache.org/shale/LogoContest -- || Walied Amer || [EMAIL PROTECTED] || attachment:walied03.jpg || attachment:walied03_powered.jpg || || Walied Amer || [EMAIL PROTECTED] || attachment:walied04.jpg || attachment:walied04_powered.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:individual_2.jpg || attachment:individual_2PW.jpg || + || Daniel Yang || [EMAIL PROTECTED] || attachment:individual.jpg || attachment:individualPW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS.jpg || attachment:LogoS_PW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS_2.jpg || attachment:LogoS_2PW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:underground_2.jpg || attachment:underground_2PW.jpg ||
[Shale Wiki] Update of LogoContest by igoutham
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by igoutham: http://wiki.apache.org/shale/LogoContest The comment on the change is: [EMAIL PROTECTED] Uploaded Shale Logo -- || Daniel Yang || [EMAIL PROTECTED] || attachment:LogoS_2.jpg || attachment:LogoS_2PW.jpg || || Daniel Yang || [EMAIL PROTECTED] || attachment:underground_2.jpg || attachment:underground_2PW.jpg || || Norbert Busch || [EMAIL PROTECTED] || attachment:shale_logo_bschwck_2.gif || attachment:shale_poweredby_bschwrck2.gif || + || Gouthaman Ilangovan || [EMAIL PROTECTED] || attachment:Goutham-Apache-Shale-V1.jpg || attachment:Goutham-Apache-Shale-V1-PoweredBy.jpg ||
[Shale Wiki] Update of LogoContest by Santy
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Santy: http://wiki.apache.org/shale/LogoContest -- || Coco || [EMAIL PROTECTED] || attachment:coco2.gif || attachment:coco21.gif || || Coco || [EMAIL PROTECTED] || attachment:coco3.gif || attachment:coco31.gif || || Coco || [EMAIL PROTECTED] || attachment:coco4.gif || attachment:coco41.gif || - || Santy || [EMAIL PROTECTED] || attachment:santy_shalelogo1.jpg || attachment:santy_shalelogopowered1.jpg || + || Santy || [EMAIL PROTECTED] || attachment:santy_shalelogo1.jpg || attachment:santy_shalelogopowered1.jpg || || Binfel || [EMAIL PROTECTED] || attachment:logo-shale2.gif || attachment:logo-shale-powered.gif || || TriSeprian || [EMAIL PROTECTED] || attachment:seprian_shale1.jpg || attachment:seprian_shale1_pow.jpg || || PRathore || [EMAIL PROTECTED] || attachment:logo_p.jpg || attachment:powered_logo_p.jpg ||
[Shale Wiki] Update of LogoContest by DKolarova
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by DKolarova: http://wiki.apache.org/shale/LogoContest -- || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleSilver.jpg || attachment:ShaleSilverPoweredBy.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleTextSpheres.jpg || attachment:ShaleTextSpheresPoweredBy.jpg|| + || D. Kolarova || [EMAIL PROTECTED] || attachment:shale_faces.jpg || attachment:shale_faces_poweredby.jpg|| || t. wakefield || [EMAIL PROTECTED] || attachment:shalebird.jpg || attachment:shalebirdpower.jpg || || Connor Garvey || [EMAIL PROTECTED] || attachment:Simple-2.png || attachment:Simple-2-Powered.png || || Andrew Smith || [EMAIL PROTECTED] || attachment:shale-basic.png || attachment:shale-basic-poweredby.png ||
[Shale Wiki] Update of LogoContest by DKolarova
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by DKolarova: http://wiki.apache.org/shale/LogoContest -- || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleSilver.jpg || attachment:ShaleSilverPoweredBy.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleTextSpheres.jpg || attachment:ShaleTextSpheresPoweredBy.jpg|| - || D. Kolarova || [EMAIL PROTECTED] || attachment:shale_faces.jpg || attachment:shale_faces_poweredby.jpg|| || t. wakefield || [EMAIL PROTECTED] || attachment:shalebird.jpg || attachment:shalebirdpower.jpg || || Connor Garvey || [EMAIL PROTECTED] || attachment:Simple-2.png || attachment:Simple-2-Powered.png || || Andrew Smith || [EMAIL PROTECTED] || attachment:shale-basic.png || attachment:shale-basic-poweredby.png ||
[Shale Wiki] Update of LogoContest by DKolarova
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by DKolarova: http://wiki.apache.org/shale/LogoContest -- || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleSilver.jpg || attachment:ShaleSilverPoweredBy.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleWhite.jpg || attachment:ShaleWhitePoweredBy.jpg || || D. Kolarova || [EMAIL PROTECTED] || attachment:ShaleTextSpheres.jpg || attachment:ShaleTextSpheresPoweredBy.jpg|| + || D. Kolarova || [EMAIL PROTECTED] || attachment:shale_faces.jpg || attachment:shale_faces_poweredby.jpg|| || t. wakefield || [EMAIL PROTECTED] || attachment:shalebird.jpg || attachment:shalebirdpower.jpg || || Connor Garvey || [EMAIL PROTECTED] || attachment:Simple-2.png || attachment:Simple-2-Powered.png || || Andrew Smith || [EMAIL PROTECTED] || attachment:shale-basic.png || attachment:shale-basic-poweredby.png ||
[Shale Wiki] Update of LogoContest by schof
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by schof: http://wiki.apache.org/shale/LogoContest -- || Norbert Busch || [EMAIL PROTECTED] || attachment:shale_logo_bschwck_2.gif || attachment:shale_poweredby_bschwrck2.gif || || Gouthaman Ilangovan || [EMAIL PROTECTED] || attachment:Goutham-Apache-Shale-V1.jpg || attachment:Goutham-Apache-Shale-V1-PoweredBy.jpg || || Youssef Elhafyani || [EMAIL PROTECTED] || attachment:golden_apache.jpg || attachment:golden_apache_powered.jpg || + || Michael Ameduri || [EMAIL PROTECTED] || attachment:s_wire_ball.jpg || attachment:s_wire_ball_power.jpg || + || Michael Ameduri || [EMAIL PROTECTED] || attachment:s_logo.jpg || attachment:s_logo.jpg ||
[Shale Wiki] Update of ExceptionHandling by WendySmoak
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by WendySmoak:
http://wiki.apache.org/shale/ExceptionHandling
The comment on the change is:
Another post from Craig that we need to save. :)
New page:
If you use the 1.0.3 release (or a very recent daily build), the behavior of
handling exceptions thrown by an action event is now programmable, in several
different ways.
By default, exceptions thrown from lifecycle callback methods (init, destroy,
etc.), or from the action method connected to a command link or command button,
will still be accumulated.
You can change this by defining a class that implements
org.apache.shale.view.!ExceptionHandler and storing it in application scope
under the key defined by !FacesConstants.EXCEPTION_HANDLER (the literal value
is org$apache$shale$view$EXCEPTION_HANDLER).
During a phase listener that is invokved after the Invoke Application phase
(i.e. just after your command action has returned a logical outcome), it is
checked whether there have been any exceptions accumulated by the default
handler above.
If so, it can optionally do a !RequestDispatcher.forward() call to the context
relative path of an error display page for your application. You can configure
such a path in web.xml with a context init parameter like this:
{{{
context-param
param-nameorg.apache.shale.view.EXCEPTION_DISPATCH_PATH/param-name
param-value/exception-viewer.faces/param-value
/context-param
}}}
This page will be displayed instead of the one that would normally be selected
by your navigation rules.
In addition, it will receive request attributes containing interesting facts
about the error that occurred, just like an error page you provide
to your servlet container as an exception handler. The most interesting one
is an attribute named javax.servlet.error.exception, which will receive a
Shale !ApplicationException that lists all the exceptions that have occurred
for this request.
=== References ===
* http://mail-archives.apache.org/mod_mbox/shale-user/200609.mbox/[EMAIL
PROTECTED]
[Shale Wiki] Update of LogoContest by JamesMitchell
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by JamesMitchell: http://wiki.apache.org/shale/LogoContest The comment on the change is: Images have moved -- To upload and display your images, you must login (create a new account if you don't already have one), then choose attachments from the More actions select list, upload your files (give them a unique name) and then edit this page and follow the example below. - === The deadline for submissions is August 31, 2006. === + === The deadline for submissions was August 31, 2006. === The winner will need to sign an ASF [http://www.apache.org/licenses/index.html#clas Contributor License Agreeement] and provide the source code for the images (most likely the original layered !PhotoShop/GIMP/Illustrator files from which the submitted image was created.) Thank you and good luck! - - (For example) - || Joey Jones || [EMAIL PROTECTED] || attachment:shale-logo-example-jmitchell.jpg || attachment:shale-logo-powered-example-jmitchell.jpg || - || Dennis Byrne || [EMAIL PROTECTED] || attachment:shale_dennisbyrne.jpg || TODO || - || Jacob Hookom || [EMAIL PROTECTED] || attachment:shale01_lg_jhook.gif || attachment:shale01_sm_jhook.gif || - || Jacob Hookom || [EMAIL PROTECTED] || attachment:shale03_lg_jhook.gif || attachment:shale03_sm_jhook.gif || - || Jacob Hookom || [EMAIL PROTECTED] || attachment:shale04_lg_jhook.gif || attachment:shale04_sm_jhook.gif || - || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_pyramid.gif || attachment:shale_pyramid_pow.gif|| - || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_nature.gif || attachment:shale_nature_pow.gif|| - || Stephan Opitz || [EMAIL PROTECTED] || attachment:shale_nature_2.gif || attachment:shale_nature_pow_2.gif|| - || Ransford Segu-Baffoe || [EMAIL PROTECTED] || attachment:shalepaksegu.gif || - || ugodiggi || [EMAIL PROTECTED] || attachment:Shale_large_udg.png || attachment:Shale_power_udg.png || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:a-peak_master.jpg || attachment:a-peak_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:blocks_master.jpg || attachment:blocks_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:blue_peaks_master.jpg || attachment:blue_peaks_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:coca_cola_shale_master.jpg || attachment:coca_cola_shale_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:copper_shale_master.jpg || attachment:copper_shale_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:orange_panels_master.jpg || attachment:orange_panels_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:orange_sphere_master.jpg || attachment:orange_sphere_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:copper_shale_master.jpg || attachment:copper_shale_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:orange_wave_master.jpg || attachment:orange_wave_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:pepsi_style_master.jpg || attachment:pepsi_style_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:rainbow_master.jpg || attachment:rainbow_power.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:swiss_master.jpg || attachment:swiss_power.jpg || - || Agharta || [EMAIL PROTECTED] || attachment:shaleAgharta1.png || attachment:shaleAgharta2.png || - || Allistair Crossley || [EMAIL PROTECTED] || attachment:ACShale.gif || attachment:ACPBShale.gif || - || Arun Sreedharan || [EMAIL PROTECTED] || attachment:aksSHALE_mst.gif || attachment:aksSHALE_pb.gif || - || Andrei Dragomir || [EMAIL PROTECTED] || attachment:apacheshale_ro_buc.jpg || attachment:poweredbyapacheshale_ro_buc.jpg || - || Mihai Copae || [EMAIL PROTECTED] || attachment:mihai_copae_logo.jpg || attachment:mihai_copae_powered.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:6balls.jpg || attachment:powered6balls.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:bic.jpg || attachment:poweredbic.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:rocky.jpg || attachment:poweredrocky.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:star.jpg || attachment:poweredstar.jpg || - || Michael Ameduri || [EMAIL PROTECTED] || attachment:wolf.jpg || attachment:poweredwolf.jpg || - || Rajen Pulai || [EMAIL PROTECTED] || attachment:ApacheShaleLogo_Rpulai.jpg || attachment:Pwredby_ApacheShaleLogo_Rpulai.jpg || - || Connor Garvey || [EMAIL PROTECTED] || attachment:shale_engraved.png || attachment:shale_engraved_powered.png || - || Connor Garvey || [EMAIL PROTECTED] || attachment:Shale-3D.png || attachment:Powered-by-Shale-3D.png || - || Gulam Patel (Mikael)
[Shale Wiki] Update of UserDoc by WendySmoak
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/shale/UserDoc -- * ShaleAndFacelets * ClayAndTomahawk * ExceptionHandling + * ShaleAndTiles
[Shale Wiki] Update of LogoContest by JamesMitchell
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by JamesMitchell:
http://wiki.apache.org/shale/LogoContest
The comment on the change is:
Send these to the list, not posted on the wiki -- thanks
--
Images have been moved to http://shale.apache.org/logo-contest.html
-
- Shale logo contest vote:
-
- 1st choice: # {55 #}
- 2nd choice: # {25 #}
- 3rd choice: # {73 #}
- 4th choice: # {50 #}
- 5th choice: # {57 #}
-
[Shale Wiki] Update of ClayAndTiles by WendySmoak
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by WendySmoak:
http://wiki.apache.org/shale/ClayAndTiles
The comment on the change is:
Preserving Gary's post on Clay and Tiles
New page:
Shale Clay and Tiles are similar in that they provide a layer of metadata that
is used to compose a page. They are different in the problem space that they
are uses in and the granularity of reuse.
Clay is designed around providing information to create a JSF page where Tiles
provides information about creating JSP pages.
Tiles allows you to create an abstraction of a JSP page. The entry point of the
page is an abstracted metadata definition defined in an XML configuration file.
The tiles definition is a collection of symbols that are used by a generic
layout to pull in various JSP fragments.
Clay also allows you to create an abstract page entry point similar to Tiles.
The entry point is a resource identifier that is not a physical file under the
context root. We call these full XML views.
The two look very similar if you would compare the definitions.
Tiles:
{{{
definition name=â.mainLayoutâ path=â/mainLayout.jspâ
put name=âheaderâ value=â/header.jspâ/
put name=âbodyâ value=â/body.jspâ/
/definition
definition name=â.indexâ extends=.mainLayout
put name=âbodyâ value=â/pages/index.jspâ/
/definition
}}}
Clay:
{{{
component jsfid=basePage extends=clay
attributes
set name=clayJsfid value=/pages/layout_nsjsp.html /
/attributes
symbols
set name=@title value=commonTitle /
set name=@bodycontent value=space /
/symbols
/component
component jsfid=/index.cxv extends=basePage
symbols
set name=@bodycontent value=/pages/index_nsjsp.html/
/symbols
/component
}}}
Clay's focus is meta-data at a component level. At the top level, the component
is a page. You could also argue that Tiles could be used the same way. The
reuse granularity that I've stated is different between Tiles and Clay (JSP
versus JSF) might be more conceptual than what is possible in terms of
meta-data.
However, the limitations and strengths are defined by how JSF uses JSP. Lets
talk about Clay first. When you use Clay full xml views, the page is completely
defined by the JSF component tree. The Clay component is specifically build for
creating a subtree that adds to the the JSF component tree. All markup that is
not a JSF component is added to the tree as an outputText component.
When you use JSP with JSF in version 1.1, the JSP, non JSF/JSP tags and JSF
components all write markup to the same writer. The JSF/JSP tags don't actually
render markup. They build the component tree and tell the component to render
itself as the tree is build.
Clay builds the entire component tree first and then invokes rendering. All of
the page content is represented by a JSF component. Rendering is in two steps.
Build the tree and render the markup.
This is one of the challenges of trying to combine Clay full views that include
JSP fragments. Clay wants to build the full tree first and then invoke
rendering but the fragment would want to invoke rendering while the component
tree was being built.
Another challenge is how the JSF/JSP tags keep track of the last JSF/JSP tag.
If we wanted to mix view technologies for creating a page, there would have to
be a standard for how the JSP/JSF tags work. Right now this is implementation
specific. Myfaces handles it different than the 1.1 RI.
Now, JSF 1.2 has changed how the JSF/JSP works together. JSF 1.2 has two steps
to rendering, like Clay. The entire component tree is created first and then
rendering invoked. The content of the non JSF/JSP tags and markup in the JSP
page is robbed from the writer and made into a JSF outputText component.
If we can figure out a common exchange between non-JSP/JSF page composition
(Clay) and JSP/JSF page composition, we would be closer to accomplishing the
niche that Tiles provides.
I have an example in the sandbox of using clay full xml views
(http://svn.apache.org/viewvc/shale/sandbox/shale-clay-mailreader/)
=== References ===
* [http://mail-archives.apache.org/mod_mbox/shale-user/200609.mbox/[EMAIL
PROTECTED] 20060915 [EMAIL PROTECTED] post]
[Shale Wiki] Update of UserDoc by RyanWynn
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by RyanWynn: http://wiki.apache.org/shale/UserDoc -- * ClayAndTiles * ExceptionHandling * ShaleAndTiles + * ReusableClayJars
[Shale Wiki] Update of ReleaseProcess by WendySmoak
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/shale/ReleaseProcess The comment on the change is: From SHALE-319, distribution management repository has changed. -- + === Build and Deploy the release === + + Maven artifacts are staged under http://people.apache.org/builds/shale/m2-snapshot-repository. + + Each build should be staged separately, so once the build is complete, move the 'm2-snapshot-repository' underneath the (for example) builds/shale/shale-1.0.4 directory. + === Archive the SNAPSHOT version in JIRA === 1.) Create a new JIRA version for the release (ex. 1.0.3)
[Shale Wiki] Update of UserDoc by SimonKitching
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by SimonKitching: http://wiki.apache.org/shale/UserDoc The comment on the change is: Add link to (new) ViewController page -- * [:ShaleRemoting:Remoting] * [:ShaleAndSpring:Spring Integration] * [:ShaleValidation:Validation] + * [:ShaleViewController:ViewController] * ShaleAndFacelets * ClayAndTomahawk * ClayAndTiles
[Shale Wiki] Update of ShaleViewController by SimonKitching
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by SimonKitching: http://wiki.apache.org/shale/ShaleViewController The comment on the change is: Add details about ViewController not in main docs New page: == Overview == The Shale `ViewController` functionality allows a managed bean to get callbacks on a per-view (ie per-page) basis, in contrast to the normal callbacks invoked per-component. == Configuration == The jsf configuration files included in the shale-core jarfiles automatically registers the necessary shale objects with the JSF implementation, so no changes need to be made to web.xml; just placing the shale jarfile in the webapp's WEB-INF/lib directory is sufficient. The `ViewViewHandler` class implements the JSF standard `ViewHandler` class. It is installed as a wrapper around the `ViewHandler` implementation provided by the underlying JSF implementation. It is this class that invokes the setPostBack method on the `ViewController`. In order to tell shale's view controller framework which bean to call for each page, it is necessary to define a `ViewControllerMapper` strategy which creates a managed bean name from the value returned by `UIViewRoot.getViewId()`, ie from the portion of the page url between the webapp name and the query params. An instance of `DefaultViewControllerMapper` is used by default; see the documentation for that class for details of the mapping. The managed bean with that name is expected to implement the `ViewController` interface (but see comments on Tiger below). It is possible to override the default `ViewControllerMapper` simply by defining an application-scoped managed bean with name org$apache$shale$view$VIEW_MAPPER that implements the `ViewControllerMapper` interface. == Subviews == In the Shale 1.0.3 release (latest at the current date) there is no support for callbacks for subviews. This means that even if a page is composed of multiple other pages (via jsp:include or other mechanism), all page-related callbacks must go through a single managed bean which introduces undesirable coupling. The trunk code as at 2006-11-07 contains some code that appears to support a separate ViewController managed bean for each f:subview in the page by overriding the renderer for subviews to invoke preprocess on processDecodes and prerender on encodeBegin. == Tiger == If the Shale Tiger libraries are present, then a few more features are available. Tiger is specifically for java 1.5 and allows the use of annotations on ordinary managed beans to mark the view-controller callback methods rather than requiring the managed bean to implement the `ViewController` interface. == Implementation Classes == * `org.apache.shale.view.faces.ViewController` defines the callbacks available; the managed bean needs to implement this interface in order to get callbacks. Alternately, concrete subclass `AbstractViewController` can be subclassed. * `org.apache.shale.view.faces.LifecycleListener` invokes the init and destroy callbacks. * `ViewViewHandler` wraps the standard `ViewHandler` and whenever a view is created (eg restore or forward) it determines which managed bean corresponds to this view and caches this in the current request. * `ViewPhaseListener` invokes the preprocess/prerender methods on the `ViewController` managed bean located earlier by the `ViewViewHandler`.
[Shale Wiki] Update of ShaleViewController by CraigMcClanahan
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/ShaleViewController The comment on the change is: Add some notes about what is changing in 1.0.4 -- == Configuration == - The jsf configuration files included in the shale-core jarfiles automatically registers the necessary shale objects with + The jsf configuration files included in the shale-core jarfile automatically registers the necessary shale objects with - the JSF implementation, so no changes need to be made to web.xml; just placing the shale jarfile in the webapp's WEB-INF/lib + the JSF implementation, so no changes need to be made to web.xml; just placing the shale-core jarfile in the webapp's WEB-INF/lib - directory is sufficient. + directory is sufficient. (NOTE -- as of version 1.0.4, this logic will be factored out into the new shale-view jarfile, and this refactoring exists in current nightly buids.) The `ViewViewHandler` class implements the JSF standard `ViewHandler` class. It is installed as a wrapper around the `ViewHandler` implementation provided by the underlying JSF implementation. It is this class that invokes the setPostBack method on the @@ -30, +30 @@ which introduces undesirable coupling. The trunk code as at 2006-11-07 contains some code that appears to support a separate ViewController managed bean for each f:subview - in the page by overriding the renderer for subviews to invoke preprocess on processDecodes and prerender on encodeBegin. + in the page by overriding the renderer for subviews to invoke preprocess on processDecodes and prerender on encodeBegin. (NOTE - as of version 1.0.4, subview lifecycle events will be fully supported, and this support exists in current nightly builds.) == Tiger ==
[Shale Wiki] Update of ShaleCore by Adrian Mitev
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by Adrian Mitev:
http://wiki.apache.org/shale/ShaleCore
--
* [http://shale.apache.org/shale-core/apidocs/index.html API Docs]
- === Token ===
-
- {{{
- h:form
- s:token id=token/
- h:message for=token/
- ...
- /h:form
- }}}
-
== Tutorials and Guides ==
-
+ * [http://wiki.apache.org/shale/Token Token] (Explains how to use the token
component)
* ViewController (Several minor questions, e.g. When to use `init()`,
`preprocess()` and `prerender()`)
* ViewControllerMapper (Explains the default view controller mapper and how
to use a custom one)
[Shale Wiki] Update of ShaleCore by Adrian Mitev
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Adrian Mitev: http://wiki.apache.org/shale/ShaleCore -- * [http://shale.apache.org/shale-core/apidocs/index.html API Docs] == Tutorials and Guides == - * [http://wiki.apache.org/shale/Token Token] (Explains how to use the token component) + * [:Token:Token] (Explains how to use the token component) * ViewController (Several minor questions, e.g. When to use `init()`, `preprocess()` and `prerender()`) * ViewControllerMapper (Explains the default view controller mapper and how to use a custom one)
[Shale Wiki] Update of UserDoc by shiraz
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by shiraz: http://wiki.apache.org/shale/UserDoc -- + === Shale Installation Instructions === + + * Step by Step Installation instructions (would someone please have these at http://shale.apache.org/ or here) + === Shale Framework Components === * [:ShaleCore:Core Library]
[Shale Wiki] Update of FrontPage by gonzalad
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by gonzalad: http://wiki.apache.org/shale/FrontPage The comment on the change is: Added chapter Shale And Other JSF libraries -- * DialogManagerFeature + === Shale And Other JSF libraries === + + * ShaleAndADF +
[Shale Wiki] Update of ShaleAndClayTutorial by MatthiasWessendorf
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by MatthiasWessendorf: http://wiki.apache.org/shale/ShaleAndClayTutorial New page: Describe ShaleAndClayTutorial here.
[Shale Wiki] Update of 维基沙盘演练 b y CraigMcClanahan
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by CraigMcClanahan:
http://wiki.apache.org/shale/%e7%bb%b4%e5%9f%ba%e6%b2%99%e7%9b%98%e6%bc%94%e7%bb%83
--
+ deleted
- ## Please edit system and help pages ONLY in the moinmaster wiki! For more
- ## information, please see MoinMaster:MoinPagesEditorGroup.
- ##master-page:WikiSandBox
- ##master-date:2004-10-06 09:33:07
- #format wiki
- #language zh
- == 请注æ ==
-
- å¨ä¸é¢çå个ç横åé¢æ¨å¯ä»¥éæç¼è¾ç»ä¹ ...
ä½è¯·'''ä¸è¦'''ä»
ä»
为äºè¯ä¸ä¸ï¼å°±å¨æ²¡ææä»·å¼å
容çæ
åµä¸å建æ°çç½é¡µï¼
-
- '''æå·§:'''
Shift-ç¹å»[帮å©-ç¼è¾]å¨å¦å¤ä¸ä¸ªçªå£ä¸é
读帮å©ç½é¡µã
-
-
- hello
- == æç ==
-
-
- ''æä½'' '''ç²ä½''' {{{æåæºåä½}}}
-
- `ç¨åå¼å·æ¬èµ·çæåæºåä½` (å¯è½éè¦è®¾ç½®)
-
- ~+ 大ä¸ç¹ +~ ~- å°ä¸äº -~
-
- {{{
- é¢å
æ好ç
- }}}
-
- {{{#!python
- def syntax(highlight):
- print on
- return None
- }}}
-
- == é¾æ¥ ==
-
- HelpOnEditing MoinMoin:InterWiki
-
- [帮å©-ç¼è¾]
-
- http://purl.net/wiki/moin/ [http://www.python.org/ Python]
-
- [EMAIL PROTECTED]
-
-
- === å¾çé¾æ¥ ===
- [http://c2.com/cgi/wiki http://c2.com/sig/wiki.gif]
-
- == å表 ==
-
- === åç¹ ===
- * ä¸
-1. åµå¥å¹¶ç¼å·
-1. ç¼å·çå表æ»æ¯éæ°ç¼å·ç
- * äº
- * ä¸
-é£ä¹ãé£ä¹
- 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨
大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨
大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨
大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨ 大åå¼ç¨
大åå¼ç¨
-æ´å¤ç¼©è¿
-
- === è¯æ±è¡¨===
- æ¯è¯:: å®ä¹
-
- === å¾ç» ===
- drawing:mytest
-
- = æ é¢ 1 =
- == æ é¢ 2 ==
- === æ é¢ 3 ===
- æ é¢ 4
- = æ é¢ 5=
-
- å
容
-
- = IRCæ¥å¿æµè¯ =
-
- {{{#!irc
- (23:18) jroes ah
- (23:19) jroes hm, i like the way {{{ works, but i was hoping the lines
would wrap
- (23:21) -!- gpciceri [EMAIL PROTECTED] has quit [Read error: 110 (Connection
timed out)]
- (23:36) ThomasWal you could also write a parser or processor
- (23:38) jroes i could?
- (23:38) jroes would that require modification on the moin end though?
- (23:38) jroes i cant change the wiki myself :x
- (23:39) ThomasWal parsers and processors are plugable
- (23:39) ThomasWal so you dont need to change the core code
- (23:40) ThomasWal you need to copy it to the wiki data directory though
- (23:40) jroes well, what i meant to say was that i dont have access to
the box running the wiki
- (23:40) ThomasWal then this is no option awdsd asdasd sa asdasd sad
asdadasds adasd asd asd asd asd asd a dadad ad adad ad asd asd adad asdasd asd
adad as d
- (23:40) jroes yeah :/
- }}}
-
- æ¤é¡µçè±æçæ¬ï¼WikiSandBox
-
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- - Describe ShaleAndClayTutorial here. + * Getting started with Shale and Clay
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- - * Getting started with Shale and Clay + = Getting started with Shale and Clay = + == Preface == + + This tutorial is based on Maven and Eclipse. The guidelines also apply to any other scenario, but you must find the appropriate way of doing it within your IDE. The attached zip file contains a complete Maven/Eclipse project which you may use as basis for this. + + The easiest way to get started with Shale and Clay is by starting with the Maven2 clay-starter archetype. + + Since the archetype currently has not made its way into the distribution, you will need to get the archetype from the Shale Subversion repository located at: + + https://svn.apache.org/repos/asf/shale/sandbox/maven/archetypes/shale-clay-starter-archetype + + After you have downloaded the sources, you need to run the following Maven2 command in the shale-starter-archetype directory: + + mvn clean install. + + This will build the archetype and install into your local repository so that it is available to you. + + Create a directory where you want the project, ex. C:\My projects\ShaleClay. Open a shell (CMD) and type in (on one line): + + mvn archetype:create -DarchetypeGroupId=org.apache.shale.clay -DarchetypeArtifactId=clay-starter-archetype -DarchetypeVersion=1.0-SNAPSHOT -DgroupId=com.acme.test -DpackageName=com.acme.test -DartifactId=shaleclay + + What happens here is that Maven will create a project based on Shale and Clay. The parameters are: + + * archetypeGroupId â The archetype groupIdbr/ + * archetypeArtifactId â The archetype artifactId br/ + * archetypeVersion â The archetype version numberbr/ + * groupId â The groupId of you projectbr/ + * packageName â The default package name of your project â included source is placed herebr/ + * artifactId - The groupId of you project br/ + + After you have done his, a project will have been created for you in a directory with the same name as you gave for the artifactId. Move to this directory. + + To make Eclipse understand that this is an Eclipse project you need to run the following Maven2 command. + + mvn eclipse:eclipse âDwtpversion=1.5 + + After running this command a couple of files and a directory will be created, that is need for Eclipse. Your layout should look something like this: + + attachement:shaleclaydir.gif +
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- After running this command a couple of files and a directory will be created, that is need for Eclipse. Your layout should look something like this: - attachement:shaleclaydir.gif + attachement:shaleclaydir.jpg
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- attachement:shaleclaydir.jpg + Start Eclipse and open a workspace that points to C:\My projects\ShaleClay (or wherever you chose as a workspace for this project) + + For Eclipse you now need to import the newly created project into the workspace: + + Choose âFile-Importâ. In the next dialog select General-Exisiting projects into workspace + + attachement:shaleclaydir2.jpg + http://wiki.apache.org/shale/ShaleAndClayTutorial/shaleclaydir2.jpg + + You should the get the following: + + http://wiki.apache.org/shale/ShaleAndClayTutorial/shaleclaydir.jpg + + In the field Select root directory enter the name of you workspace or use the âBrowse..â button to navigate to it. Eclipse should now list all available projects. Select the ShaleClay project and hit the âFinishâ button. + + You may see a red cross on your projectname if you have not defined the maven classpath variable âM2_REPOâ. You ca add it under Window-preferences and then Java-Build Path-Classpath Variables + + attachement:shaleclay4.jpg + + Press the New... button. In the next dialog type inn M2_REPO in the name field and in the âPath:â field you enter the path to your local Maven2 repository. Press Ok and Ok again in the next dialog. + + attachement:shaleclay5.jpg + + Eclipse will then inform you that it has to rebuild the workspace. Press the Yes button. + + If you still have a re cross after it has recompiled, check the default Java version in Eclipse. If you have Java5 as standard the cause is the compiler-level is mismatched with what Maven set when it generated the project. Go to the problems view, right click on the message and choose âQuick Fixâ + + attachement:shaleclay6.jpg + + Select Change Java compiler level to 1.4 and press âOkâ. + + Your project should now compile ok. Now comes the time to look at the project it self and how it is organized. If you expand your project it should look something like this: + + attachement:shaleclay7.jpg + + In the Java sourcefolder (src/main/java) under the packagename you provided you should find two classes: + Person og TestVC. + + In the resources folder (src/main/resources) you will find three property files. This is actually one property file with two language provisions of it. These can be identified by their nameextention. + + In the web sources folder (src/main/webapp) you will find several folders: + + The folder âimagesâ contains the images and backgrouns that are used for the site. + + The folder âpagesâ contains standard definitions (defaultxxx.html) of the various parts tghat make up the site, along with som specific definitions (pageXbody.html) + + The folder âtemplatesâ contains the template that we are using to build our site â we will return to this shortly + + The folder âthemeâ contains the cascading stylesheet we use to format our site. + + In the folder âWEB-INFâ we find all the important configurationfiles. + + attachement:shaleclay8.jpg + + Lets take a closer look at these, starting with web.xml where we find these important declarations: + +!-- Override the default suffix for extension-mapped -- +context-param + param-namejavax.faces.DEFAULT_SUFFIX/param-name + param-value.jsf/param-value +/context-param + +!-- Select JSF State Saving Mode -- +context-param + param-namejavax.faces.STATE_SAVING_METHOD/param-name + param-valueclient/param-value +/context-param + +!-- Clay Common Configuration Resources -- +context-param + param-name + org.apache.shale.clay.COMMON_CONFIG_FILES + /param-name + param-value/WEB-INF/clay-config.xml/param-value +/context-param + +!-- Clay Configuration Full XML view Resources -- +context-param + param-name + org.apache.shale.clay.FULLXML_CONFIG_FILES + /param-name + param-value/WEB-INF/clay-views-config.xml/param-value +/context-param + +!-- Clay XML View Suffix -- +context-param + param-name + org.apache.shale.clay.XML_TEMPLATE_SUFFIX + /param-name + param-value.jsf/param-value +/context-param + + These declarations (context-param) are used by Clay and the JavaServer Faces (JSF) implementation at startup. + + * javax.faces.DEFAULT_SUFFIX â Tells which page suffixes should be handled by JSF + * javax.faces.STATE_SAVING_METHOD â How should session state be persisted (Client-side or Server-side) + * org.apache.shale.clay.COMMON_CONFIG_FILES â What are the name(s )of the Clay configuration file(s), providing absolute path within the web-context + *
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- After running this command a couple of files and a directory will be created, that is need for Eclipse. Your layout should look something like this: + ##URL: attachement:shaleclaydir.jpg Start Eclipse and open a workspace that points to C:\My projects\ShaleClay (or wherever you chose as a workspace for this project)
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- What happens here is that Maven will create a project based on Shale and Clay. The parameters are: - * archetypeGroupId â The archetype groupIdbr/ + * archetypeGroupId â The archetype groupId[[BR]] - * archetypeArtifactId â The archetype artifactId br/ + * archetypeArtifactId â The archetype artifactId[[BR]] - * archetypeVersion â The archetype version numberbr/ + * archetypeVersion â The archetype version number[[BR]] - * groupId â The groupId of you projectbr/ + * groupId â The groupId of you project[[BR]] - * packageName â The default package name of your project â included source is placed herebr/ + * packageName â The default package name of your project â included source is placed here[[BR]] - * artifactId - The groupId of you project br/ + * artifactId - The groupId of you project[[BR]] After you have done his, a project will have been created for you in a directory with the same name as you gave for the artifactId. Move to this directory. @@ -39, +39 @@ After running this command a couple of files and a directory will be created, that is need for Eclipse. Your layout should look something like this: - ##URL: attachement:shaleclaydir.jpg Start Eclipse and open a workspace that points to C:\My projects\ShaleClay (or wherever you chose as a workspace for this project) @@ -49, +48 @@ Choose âFile-Importâ. In the next dialog select General-Exisiting projects into workspace attachement:shaleclaydir2.jpg - http://wiki.apache.org/shale/ShaleAndClayTutorial/shaleclaydir2.jpg You should the get the following: - http://wiki.apache.org/shale/ShaleAndClayTutorial/shaleclaydir.jpg + attachement:shaleclaydir3.jpg In the field Select root directory enter the name of you workspace or use the âBrowse..â button to navigate to it. Eclipse should now list all available projects. Select the ShaleClay project and hit the âFinishâ button. @@ -98, +96 @@ Lets take a closer look at these, starting with web.xml where we find these important declarations: -!-- Override the default suffix for extension-mapped -- +!-- Override the default suffix for extension-mapped --[[BR]] -context-param +context-param[[BR]] - param-namejavax.faces.DEFAULT_SUFFIX/param-name + param-namejavax.faces.DEFAULT_SUFFIX/param-name[[BR]] - param-value.jsf/param-value + param-value.jsf/param-value[[BR]] -/context-param +/context-param[[BR]] -!-- Select JSF State Saving Mode -- +!-- Select JSF State Saving Mode --[[BR]] -context-param +context-param[[BR]] - param-namejavax.faces.STATE_SAVING_METHOD/param-name + param-namejavax.faces.STATE_SAVING_METHOD/param-name[[BR]] - param-valueclient/param-value + param-valueclient/param-value[[BR]] -/context-param +/context-param[[BR]] -!-- Clay Common Configuration Resources -- +!-- Clay Common Configuration Resources --[[BR]] -context-param +context-param[[BR]] - param-name + param-name[[BR]] - org.apache.shale.clay.COMMON_CONFIG_FILES + org.apache.shale.clay.COMMON_CONFIG_FILES[[BR]] - /param-name + /param-name[[BR]] - param-value/WEB-INF/clay-config.xml/param-value + param-value/WEB-INF/clay-config.xml/param-value[[BR]] -/context-param +/context-param[[BR]] -!-- Clay Configuration Full XML view Resources -- +!-- Clay Configuration Full XML view Resources --[[BR]] -context-param +context-param[[BR]] - param-name + param-name[[BR]] - org.apache.shale.clay.FULLXML_CONFIG_FILES + org.apache.shale.clay.FULLXML_CONFIG_FILES[[BR]] - /param-name + /param-name[[BR]] - param-value/WEB-INF/clay-views-config.xml/param-value + param-value/WEB-INF/clay-views-config.xml/param-value[[BR]] -/context-param +/context-param[[BR]] -!-- Clay XML View Suffix -- +!-- Clay XML View Suffix --[[BR]] -context-param +context-param[[BR]] - param-name + param-name[[BR]] - org.apache.shale.clay.XML_TEMPLATE_SUFFIX + org.apache.shale.clay.XML_TEMPLATE_SUFFIX[[BR]] - /param-name + /param-name[[BR]] - param-value.jsf/param-value + param-value.jsf/param-value[[BR]] -/context-param +/context-param[[BR]] These declarations (context-param) are used by Clay and the JavaServer Faces (JSF) implementation at startup. @@ -144, +142 @@ The are the Filter defintions. A filter is a Javaclass that will be called by the webcontainer on every request that comes into it (Actually only requests that
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- These declarations (context-param) are used by Clay and the JavaServer Faces (JSF) implementation at startup. - * javax.faces.DEFAULT_SUFFIX â Tells which page suffixes should be handled by JSF + * javax.faces.DEFAULT_SUFFIX â Tells which page suffixes should be handled by JSF[[BR]] - * javax.faces.STATE_SAVING_METHOD â How should session state be persisted (Client-side or Server-side) + * javax.faces.STATE_SAVING_METHOD â How should session state be persisted (Client-side or Server-side)[[BR]] - * org.apache.shale.clay.COMMON_CONFIG_FILES â What are the name(s )of the Clay configuration file(s), providing absolute path within the web-context + * org.apache.shale.clay.COMMON_CONFIG_FILES â What are the name(s )of the Clay configuration file(s), providing absolute path within the web-context[[BR]] - * org.apache.shale.clay.FULLXML_CONFIG_FILES â What are the name(s) of the Clay configuration file(s) that tells Clay about our page definitions. + * org.apache.shale.clay.FULLXML_CONFIG_FILES â What are the name(s) of the Clay configuration file(s) that tells Clay about our page definitions.[[BR]] - * org.apache.shale.clay.XML_TEMPLATE_SUFFIX â Which page suffixes should be handled by Clay. + * org.apache.shale.clay.XML_TEMPLATE_SUFFIX â Which page suffixes should be handled by Clay.[[BR]] The are the Filter defintions. A filter is a Javaclass that will be called by the webcontainer on every request that comes into it (Actually only requests that match a certain predefined pattern â See filter-mapping below) @@ -183, +183 @@ The next file we look at is the faces-config.xml file. This file governs the setup of JSF. It is normally divided into three sections - * General information - application + * General information - application [[BR]] - * Navigation rules - navigation-rule + * Navigation rules - navigation-rule[[BR]] - * Managed beans - managed-bean + * Managed beans - managed-bean[[BR]] First in out file we define which languages this application supports; Norwegian(no) and English(en), and that the default is English. @@ -201, +201 @@ If we take a closer look at it we see that it is devided into sections. These sections are the parts of the page that naturally lend tem selves to a functionalitygroup and as such are candidates for reuse. This is known as templating. The page is formatted as a âliquid designâ layout. If you want to read up on this, a good place to start is [http://www.mardiros.net/liquid-css-layouts.html/ Carmen Mardios] + The section that the page is divided into are: + +* Pagetitle[[BR]] +* Leftmenu[[BR]] +* Content[[BR]] +* Footer[[BR]] + + body[[BR]] + div id=headspan jsfid=clay clayjsfid=@headerContent[[BR]] + allowbody=falseHeader Content/span/div[[BR]] + div id='logo'nbsp;/div[[BR]] + div id=leftnbsp;/div[[BR]] + div id=menuspan jsfid=clay clayjsfid=@leftContent[[BR]] + allowbody=falseLeft Content/span/div[[BR]] + div id=pad1nbsp;/div[[BR]] + div id='content'span jsfid=clay clayjsfid=@bodyContent[[BR]] + allowbody=falseBody Content/span/div[[BR]] + div id=pad1nbsp;/div[[BR]] + div id=footerspan jsfid=clay clayjsfid=@footerContent[[BR]] + allowbody=falseFooter Content/span/div[[BR]] + /body[[BR]] + + These sections are identifiable with the help of the attribute âclayjsfidâ on the SPAN tags. Here we see that we have: @headerContent, @leftContent. @bodyContent and @footerContent. These are what we refer to as symbols in Clay. This means that Clay processes the page looking for symbols and replaces them with their counterpart efinition in the configuration file(s). Lets look at how this template is defined as a Clay component in the clay-config.xml file: + + component jsfid=baseLayout extends=clay id=base[[BR]] + attributes[[BR]] + set name=clayJsfid value=/templates/standard.html /[[BR]] + /attributes[[BR]] + symbols[[BR]] + set name=title value=Hello World /[[BR]] + set name=leftContent value=/pages/defaultLeftNav.html /[[BR]] + set name=headerContent value=/pages/defaultHeader.html /[[BR]] + set name=bodyContent value=/pages/defaultBody.html /[[BR]] + set name=footerContent value=/pages/defaultFooter.html /[[BR]] + /symbols[[BR]] + /component[[BR]] +
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by Hermod Opstvedt:
http://wiki.apache.org/shale/ShaleAndClayTutorial
--
/symbols[[BR]]
/component[[BR]]
+ As we can see we have a section named âsymbolsâ, Here we instruct Clay
what to substitute the symbols with. In this case we have made some defaults to
substitute in and the will be used unless we override them when defining a
specific page. Now that we have a template to work with the work of creating
specific pages start. Since we for now only want to replace the content part
(defined by the symbol bodyContent) and the page title, we only need to create
those parts. We now need to let Clay know about these. To tell Clay how to
build our specifi pages we do that in the clay-views.xml file. If we open this
file, we will find several page definitions:
+
+ component jsfid=/page1.jsf extends=baseLayout[[BR]]
+ symbols[[BR]]
+ set name=title value=Page 1 /[[BR]]
+ set name=bodyContent value=/pages/page1Body.html
/[[BR]]
+ /symbols[[BR]]
+ /component
+ component jsfid=/page2.jsf extends=baseLayout[[BR]]
+ symbols[[BR]]
+ set name=title value=Page 2 /[[BR]]
+ set name=bodyContent value=/pages/page2Body.html
/[[BR]]
+ /symbols[[BR]]
+ /component
+ component jsfid=/page3.jsf extends=baseLayout[[BR]]
+ symbols[[BR]]
+ set name=title value=Page 3 /[[BR]]
+ set name=bodyContent value=/pages/page3Body.html
/[[BR]]
+ /symbols[[BR]]
+ /component[[BR]]
+
+ Here we define 3 components that inherit from our basecomponent
âbaseLayoutâ. As we mentioned we override the definitions of the title and
bodyContent. We have now created 3 components based on a common template, but
where the title and content vary. If we now look at for instance page1Body.html:
+
+ h3[[BR]]
+ span jsfid=outputText value=#{messages['content.title.page1']}
allowBody=falseClay template application - Page 1/span[[BR]]
+ /h3[[BR]]
+ p[[BR]]
+ span jsfid=outputText value=#{messages['content.message.page1']}
allowBody=falseThis is Page 1 content/span[[BR]]
+ /p[[BR]]
+
+ then we see that we refer to the jsfid âoutputTextâ. This is one of the
standard predefined Clay components that we can utilize. Itâs purpose is to
output text. Further we refer to â#{messages['content.message.page1']}. This
is a reference to a âmanaged-beanâ named messages. This is a bean that
Shale will instantiate for us, If you open the faces-config.xml file you will
find this at the bottom:
+
+ !-- Make resources available to the pages by defining it here (in a
page use messages['propertyname'] as value --[[BR]]
+ managed-bean[[BR]]
+ managed-bean-namemessages/managed-bean-name[[BR]]
+ managed-bean-class[[BR]]
+ org.apache.shale.util.LoadBundle[[BR]]
+ /managed-bean-class[[BR]]
+ managed-bean-scopeapplication/managed-bean-scope[[BR]]
+ managed-property[[BR]]
+ property-namebasename/property-name[[BR]]
+ value[[BR]]
+ ResourceBundle[[BR]]
+ /value[[BR]]
+ /managed-property[[BR]]
+ /managed-bean[[BR]]
+
+ Here we define the messages bean. In the this case it is a special purpose
Shale bean. It purpose it to make available to us a resourcebundle that we have
created. The name of that is ResourceBundle.properties. You will find it the
folder src/main/resources. This bean is available application wide (given by
the scope section). It supports internationalization (I18N), so we can have
several versions of the file where the are unique by their extension (_en, _no
etc.).
+
+ Another attribute to note is âallowBodyâ. This attribute tells Clay
whether or not to include any content within this tags body or not. Another way
to achieve the same is through the Clay meta information !-- ### clay:remove
### -- !-- ### /clay:remove ### --. One of the nice things about this that
we can have mock content on a page so that during design time w eget the full
picture, and then have it removed during runtime so that it does not interfere
with the actual content (Open the page in a browser to see this effect).
+
+ If we more on and look at the second page (/page2.jsf) and its content
(pageBody2.html) we see that we have used more of Clays functionalities.
+
+ h3[[BR]]
+ span jsfid=outputText value=#{messages['content.title.page2']}
allowBody=falseClay template application - Page 2/span[[BR]]
+ /h3[[BR]]
+ p[[BR]]
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- == Preface == + + /!\ '''Edit conflict - other version:''' This tutorial is based on Maven and Eclipse. The guidelines also apply to any other scenario, but you must find the appropriate way of doing it within your IDE. [attachment:ShaleClay.zip/ This] attached zip file contains a complete Maven/Eclipse project which you may use as basis for this. + + /!\ '''Edit conflict - your version:''' + This tutorial is based on Maven and Eclipse. The guidelines also apply to any other scenario, but you must find the appropriate way of doing it within your IDE. [attachment:ShaleClay.zip/ This] attached zip file contains a complete Maven/Eclipse project which you may use as basis for this. + + /!\ '''End of edit conflict''' The easiest way to get started with Shale and Clay is by starting with the Maven2 clay-starter archetype.
[Shale Wiki] Update of FrontPage by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/FrontPage -- * [:UserDoc:User Documentation] + === Tutotials === + + * [:ShaleClayTutorial:Shale and Clay starter] + === Project Maintenance === * MavenBuild
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- == Preface == - /!\ '''Edit conflict - other version:''' This tutorial is based on Maven and Eclipse. The guidelines also apply to any other scenario, but you must find the appropriate way of doing it within your IDE. [attachment:ShaleClay.zip/ This] attached zip file contains a complete Maven/Eclipse project which you may use as basis for this. - - /!\ '''Edit conflict - your version:''' - This tutorial is based on Maven and Eclipse. The guidelines also apply to any other scenario, but you must find the appropriate way of doing it within your IDE. [attachment:ShaleClay.zip/ This] attached zip file contains a complete Maven/Eclipse project which you may use as basis for this. - - /!\ '''End of edit conflict''' The easiest way to get started with Shale and Clay is by starting with the Maven2 clay-starter archetype.
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- == Preface == - This tutorial is based on Maven and Eclipse. The guidelines also apply to any other scenario, but you must find the appropriate way of doing it within your IDE. [attachment:ShaleClay.zip/ This] attached zip file contains a complete Maven/Eclipse project which you may use as basis for this. + This tutorial is based on Maven and Eclipse. The guidelines also apply to any other scenario, but you must find the appropriate way of doing it within your IDE. The attachment:ShaleClay.zip file contains a complete Maven/Eclipse project which you may use as basis for this. The easiest way to get started with Shale and Clay is by starting with the Maven2 clay-starter archetype.
[Shale Wiki] Update of FrontPage by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/FrontPage -- * [:UserDoc:User Documentation] - === Tutotials === + === Tutorials === * [:ShaleAndClayTutorial:Shale and Clay starter] + * [:ReusableClayJars:Creating reusable Clay components and distribute them as jar files] === Project Maintenance ===
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by Hermod Opstvedt:
http://wiki.apache.org/shale/ShaleAndClayTutorial
--
/managed-bean-class[[BR]]
managed-bean-scoperequest/managed-bean-scope[[BR]]
/managed-bean[[BR]]
+ managed-bean id=page2[[BR]]
+ managed-bean-namepage2/managed-bean-name[[BR]]
+ managed-bean-class[[BR]]
+ com.acme.test.TestVC[[BR]]
+ /managed-bean-class[[BR]]
+ managed-bean-scoperequest/managed-bean-scope[[BR]]
+ managed-property[[BR]]
+ property-nameperson/property-name[[BR]]
+ property-class[[BR]]
+ com.acme.test.Person[[BR]]
+ /property-class[[BR]]
+ value#{person}/value[[BR]]
+ /managed-property[[BR]]
+ /managed-bean[[BR]]
+
- What we do here is to define what is known as a backing bean or managed bean.
This is a that Shale will make available to us. Shale uses an implicit mapping
strategy to decide which beans it should instantiate for a given view. Since
our page is called page1, it will then look for a managed bean with the same
name and instantiate it. If you have a path to your page that spans several
folders as in /foo/bar/pages/page1 then you need to define it as
foo$bar$pages$page1 for Shale to find it and associate it with the page.
+ What we do here is to define what is known as a backing beans or managed
beans. These are beans that Shale will make available to us. Shale uses an
implicit mapping strategy to decide which beans it should instantiate for a
given view. If our page is called page1, it will then look for a managed bean
with the same name and instantiate it. If you have a path to your page that
spans several folders as in /foo/bar/pages/page1 then you need to define it as
foo$bar$pages$page1 for Shale to find it and associate it with the page.
- Clay will when it sees the symbol managed-bean-name, replace it with the
implicitly mapped bean that Shale is providing. In our case page1
+ Clay will when it sees the symbol managed-bean-name, replace it with the
implicitly mapped bean that Shale is providing. In our case page1.
- Lets take a closer look at this bean (com.acme.test.TestVC). The first thing
we notice is that it inherits from fra
[http://shale.apache.org/shale-view/index.html/ AbstractViewController]. This
class gives us some hooks (callbacks) into some Shale added lifecycle methods
so that we can perform certain tasks that are relevant to that particular
lifecycle. The next thing to notice is that is refers to a class Person. If you
look in the faces-config.xml file again you will find the following declaration:
+ Lets take a closer look at the bean (com.acme.test.TestVC) that we are using
for our backing bean. The first thing we notice is that it inherits from fra
[http://shale.apache.org/shale-view/index.html/ AbstractViewController]. This
class gives us some hooks (callbacks) into some Shale added lifecycle methods
so that we can perform certain tasks that are relevant to that particular
lifecycle. The next thing to notice is that is refers to a class Person. If you
look in the faces-config.xml file again you will find the following declaration:
managed-bean id=person[[BR]]
managed-bean-nameperson/managed-bean-name[[BR]]
@@ -359, +374 @@
managed-bean-scopesession/managed-bean-scope[[BR]]
/managed-bean[[BR]]
+ If you look at the above definition you will see that Person has been
declared as a managed bean. Because Person is defined as a managed bean, Shale
will inject it into our page2 definition because we instructed it to through
the use of the managed-property section. Since Person has a scope of session it
will be persisted between request so that any value that we set on one request
will be available on the next. Finally we see that we define a method sayHello
on the TestVC bean, and that we refer to that method in the page2Body.html in
the âactionâ attribute (: [EMAIL PROTECTED]).
+
+ One of the thing that separate JavaServer Faces from an ordinary
webapplication is that most interaction with the server is through http POST.
This means that all fields and actions must be surrounded with a form tag.
+
+ Another important thing to notice is that if declare your backing beans to
extend AbstractViewController you have to declare them with request scope for
the lifecycle methods to be called. If you declare it with scope session they
will not be called!
+
+ When we do a post against the server JSF/Shale will populate all fields in
the managed bean that we have associated with fields on the page (There is
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by Hermod Opstvedt:
http://wiki.apache.org/shale/ShaleAndClayTutorial
--
Another important thing to notice is that if declare your backing beans to
extend AbstractViewController you have to declare them with request scope for
the lifecycle methods to be called. If you declare it with scope session they
will not be called!
- When we do a post against the server JSF/Shale will populate all fields in
the managed bean that we have associated with fields on the page (There is a
lot of other things going on too but that is beyond the scope of this
tutorial). That means that when the method sayHello is invoked a bean Person
will have been instantiated and filled with the values coming from our page. In
the method sayHello we do not actually do anything other that return a string.
+ When we do a post against the server JSF/Shale will populate all fields in
the managed bean that we have associated with fields on the page (There is a
lot of other things going on too but that is beyond the scope of this
tutorial). That means that when the method sayHello is invoked a bean Person
will have been instantiated and filled with the values coming from our page. In
the method sayHello we do not actually do anything other that return a string.
This string is used by JSF to figure out which view it should render. This is
also defined in the faces-config.xml file under the navigation rules section.
+
+ navigation-rule[[BR]]
+ !-- These pages should be accessable form everywhere --[[BR]]
+ from-view-id*/from-view-id[[BR]]
+ navigation-case[[BR]]
+ from-outcomehome/from-outcome[[BR]]
+ to-view-id/page1.jsf/to-view-id[[BR]]
+ /navigation-case[[BR]]
+ navigation-case[[BR]]
+ from-outcomepage2/from-outcome[[BR]]
+ to-view-id/page2.jsf/to-view-id[[BR]]
+ /navigation-case[[BR]]
+ navigation-case[[BR]]
+ from-outcomepage3/from-outcome[[BR]]
+ to-view-id/page3.jsf/to-view-id[[BR]]
+ /navigation-case[[BR]]
+ /navigation-rule[[BR]]
+
+ In TestVC.sayHello we returned the string page3, and in the navigation rules
we see that this will send us to /page3.jsf. You can define many navigation
rules, and also note that a navigation rule always must have a from view. If
you use the asterix (*) then that will mean that unless otherwise specified the
outcomes become global rules.
+
+ As a result of our action page3 will be rendered. If we look at the
bodyCOntent definition for page3 in the clay-views-config.xml file we will se
that it refers to page3Body.html.
+
+ h3[[BR]]
+ span jsfid=outputText value=#{messages['content.title.page3']}
allowBody=falseClay template application - Page 3/span[[BR]]
+ /h3[[BR]]
+ p[[BR]]
+ span jsfid=outputText value=#{messages['content.message.page3']}
allowBody=falseThis is Page 3 content/span[[BR]]
+ /p[[BR]]
+ p[[BR]]
+ span jsfid=outputText value=#{messages['hello']}
allowBody=falseHello/span span jsfid=outputText value=#{person.name}
allowBody=falseWorld/span[[BR]]
+ /p[[BR]]
+
+ Here again we refer to the person bean, butt his time we are displaying a
value from it (#{person.name}. As we mentioned this bean has bean declared
with session scope, so that the name we entered on page2 is now available on
page3 for as long as our session exists. We can also refer to any other managed
bean, and properties in these.
+
+ We have now been through a simple Shale/Clay application. It is recommended
that you play around with it to see the effects of your changes. When you are
ready to move on a natural step is to follow the [:CreatingClayComponents/
Create Clay components tutorial] to learn haw to create reusable Clay
components for your pages.
+
+ Hermod Opstvedt
+ February 2007
+
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by Hermod Opstvedt:
http://wiki.apache.org/shale/ShaleAndClayTutorial
--
span jsfid=outputText value=#{messages['hello']}
allowBody=falseHello/span span jsfid=outputText value=#{person.name}
allowBody=falseWorld/span[[BR]]
/p[[BR]]
- Here again we refer to the person bean, butt his time we are displaying a
value from it (#{person.name}. As we mentioned this bean has bean declared
with session scope, so that the name we entered on page2 is now available on
page3 for as long as our session exists. We can also refer to any other managed
bean, and properties in these.
+ Here again we refer to the person bean, but this time we are displaying a
value from it (#{person.name}. As we mentioned this bean has bean declared
with session scope, so that the name we entered on page2 is now available on
page3 for as long as our session exists. We can also refer to any other managed
bean, and properties in these.
- We have now been through a simple Shale/Clay application. It is recommended
that you play around with it to see the effects of your changes. When you are
ready to move on a natural step is to follow the [:CreatingClayComponents/
Create Clay components tutorial] to learn haw to create reusable Clay
components for your pages.
+ We have now been through a simple Shale/Clay application. It is recommended
that you play around with it to see the effects of your changes. When you are
ready to move on a natural step is to follow the [:CreatingClayComponents/
Create Clay components tutorial] to learn how to create reusable Clay
components for your pages.
Hermod Opstvedt
February 2007
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Shale Wiki for change
notification.
The following page has been changed by Hermod Opstvedt:
http://wiki.apache.org/shale/ShaleAndClayTutorial
--
Here again we refer to the person bean, but this time we are displaying a
value from it (#{person.name}. As we mentioned this bean has bean declared
with session scope, so that the name we entered on page2 is now available on
page3 for as long as our session exists. We can also refer to any other managed
bean, and properties in these.
- We have now been through a simple Shale/Clay application. It is recommended
that you play around with it to see the effects of your changes. When you are
ready to move on a natural step is to follow the [:CreatingClayComponents/
Create Clay components tutorial] to learn how to create reusable Clay
components for your pages.
+ We have now been through a simple Shale/Clay application. It is recommended
that you play around with it to see the effects of your changes. When you are
ready to move on a natural step is to follow the
[:CreatingClayComponents:Create Clay components tutorial] to learn how to
create reusable Clay components for your pages.
Hermod Opstvedt
February 2007
[Shale Wiki] Update of ShaleAndClayTutorial by Hermod Opstvedt
Dear Wiki user, You have subscribed to a wiki page or wiki category on Shale Wiki for change notification. The following page has been changed by Hermod Opstvedt: http://wiki.apache.org/shale/ShaleAndClayTutorial -- After running this command a couple of files and a directory will be created, that is need for Eclipse. Your layout should look something like this: - attachment:shaleclaydir1.jpg + attachment:ShaleClaydir1.jpg == Lets start ==
