DO NOT REPLY [Bug 35839] New: - [shale] Clay processes components inside HTML comments

2005-07-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35839

   Summary: [shale] Clay processes components inside HTML comments
   Product: Struts
   Version: Nightly Build
  Platform: Other
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P2
 Component: Shale
AssignedTo: dev@struts.apache.org
ReportedBy: [EMAIL PROTECTED]


The following snippet is treated as if the second span is not commented out.



  



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 35841] New: - [shale] Clay doesn't preserve the component hierarchy in HTML templates

2005-07-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35841

   Summary: [shale] Clay doesn't preserve the component hierarchy in
HTML templates
   Product: Struts
   Version: Nightly Build
  Platform: Other
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P2
 Component: Shale
AssignedTo: dev@struts.apache.org
ReportedBy: [EMAIL PROTECTED]


The following snippet




Some Text



is processed as follows




Some Text


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [shale][clay] Component attributes overriding. Proposals

2005-07-24 Thread Manfred Klug 

Re: [shale][clay] Component attributes overriding. Proposals

>>> [snip] 
>>> I would prefer to see the html attributes always override the xml 
>>> definitions. I say that because it favors the web designer 
>>> instead of the developer. 
>>> However, this new proposed attribute (allowOverriding="false") would give 
>>> the developer the final decision. 
>> 
>> The same as with my solution. The developer provides a value or not. 
> 
> This is a bit off tangent to this discussion but I thought it would be worth 

Maybe :(

> bringing up in the context of creating solutions that promote reuse.
> We have a half baked CMS where I work. It provides a way to apply 
> customizations/overrides to a hierarchy horizontally verses the traditional 
> vertical OO approach. This works very well for customizing sites for various 
> customers because all pages include the same component. The customizations 
> ("generalization relationships") are applied to a hierarchical structure 
> verses 
> a new hierarchy created for each new component. 
>
> This is also something we might consider for Clay. Since the jsfid's are not 
> a 
> dynamic attribute, it makes it hard to introduce customizations without 
> creating a new page that references another component. It might be 
> interesting 
> to think about applying "overrides" to an existing tree. 
>
> I see the HTML override to the XML as a similar concept.

I'm not against the setting of attributes via HTML. I only think that the
developer should always have the last word about an attribute value.

An example:

The designer should decide which colors should be used. The simple solution is
that the developer don't specify colors.

On the other hand, there may be a requirement that the colors must be specified
in a property file (for easy customization). In this case, the developer
encodes the values and the specifications from the designer are ignored.

Don't forget the following:

The html designer possibly has no knowledge about JSF or the application
requirements. He set attributes because they produce a nice look and feel.

It's the responsibility of the developer to
  - decide which components should be used
  - configure the components to resemble the design as close as possible
  - configure the components to behave correctly in the context of the
application
  - support multi language environments (which may require layout changes)
  - support dynamic customization requirements (via user profiles)
  - many many more

_
Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle 
Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Bug report for Struts [2005/07/24]

2005-07-24 Thread bugzilla 
+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| |   |   MIN=Minor   NOR=Normal  ENH=Enhancement   |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
| 5739|Opn|Enh|2002-01-08|Struts fails silently in too many places  |
| 5937|New|Enh|2002-01-21|[taglib] html:form trims all extensions   |
| 6847|Opn|Enh|2002-03-04|Multiple file upload not possible due to MultiPart|
| 7892|Opn|Enh|2002-04-09|Using Multiple Resource Bundles for an Application|
| 7902|Opn|Enh|2002-04-10|The exception handling declaration in the DTD does|
| 9088|Opn|Enh|2002-05-15|FormTag.getActionMappingURL() assumes 1 servlet ma|
| 9616|New|Enh|2002-06-05|Some more Struts docs |
| 9748|New|Enh|2002-06-10|[taglib] attribute labelKeyProperty for Options ta|
|10550|New|Enh|2002-07-08|Delegate path-management to ActionForwards|
|10552|New|Enh|2002-07-08|create helper objects in struts-config|
|10867|Opn|Enh|2002-07-16|[taglib] Add indexedProperty attribute in html tag|
|11154|Opn|Enh|2002-07-25|[taglib] html:link tag extension for multiple para|
|11733|Opn|Enh|2002-08-15|Make error keys more specific |
|12170|Opn|Enh|2002-08-29|Added functionality when extending another definit|
|12178|Opn|Nor|2002-08-29|Validator restricted to one Message Resource bundl|
|12301|Opn|Enh|2002-09-04|[taglib] nested:messages Tag does not work as expe|
|12600|New|Enh|2002-09-12|[taglib] html:form tag always prepends context pat|
|13125|Opn|Enh|2002-09-30|[taglib] Lack of character-set while using   forwardPattern should support differe|
|16708|New|Enh|2003-02-03|I18N on ActionForwards|
|16792|Ass|Enh|2003-02-05|Migrate to commons-resources for message resources|
|16814|New|Enh|2003-02-05|Add a generalized utililty class to expose informa|
|16946|Opn|Enh|2003-02-10|SwitchAction not setting context properly for tile|
|16971|New|Enh|2003-02-11|[taglib] "multiple" attribute on select tag should|
|17368|Opn|Enh|2003-02-25|[taglib]  multiple does not populate |
|17449|New|Enh|2003-02-26|[taglib] Allow relative URL in action attribute of|
|17473|New|Enh|2003-02-27|[taglib] Problem to include a jsp into an iterate |
|17530|New|Enh|2003-02-28|RequestUtils.computeURL should use the session ass|
|17559|New|Enh|2003-03-01|[tiles] key attribute for tiles (put & item)  |
|17583|Opn|Enh|2003-03-03|Handling parameters from MultipartRequestWrapper  |
|17600|New|Enh|2003-03-03|[taglib] key property for html:optionsCollection t|
|18015|Opn|Enh|2003-03-14|[taglib] New  custom tag to write form|
|18017|Opn|Enh|2003-03-14|[tiles] extends fails in JSP-based Definitions|
|18022|New|Enh|2003-03-14|HttpSessionBindingListener.valueUnbound() called o|
|18032|Opn|Enh|2003-03-16|[taglib]  tag appending session doesn't |
|18237|Opn|Enh|2003-03-21|[tiles] excessive memory usage|
|18293|New|Enh|2003-03-24|Loading language files does not use Resource Bundl|
|18788|New|Enh|2003-04-07|Multiple input hook for multipage forms in process|
|18981|New|Enh|2003-04-13|[upload] File upload maximum size validator   |
|19346|New|Enh|2003-04-26|Errors and Messages should be easier to manage|
|19539|New|Enh|2003-05-02|Add checks for List and Map-backed properties in D|
|19631|New|Enh|2003-05-04|Enhancements to RequestUtils tests|
|19812|New|Enh|2003-05-10|[taglib] BaseFieldTag don't use ConvertUtils as St|
|19903|New|Enh|2003-05-13|Field considered valid if no ActionError created  |
|19925|New|Enh|2003-05-14|Server side solution for DispatchAction and : Make value optional when id|
|21282|Ass|Enh|2003-07-02|[validator] numeric validations should use locales|
|21508|New|Enh|2003-07-11|[tiles]  element too restrictive|
|21512|New|Enh|2003-07-11|exception tag's path attribute accepts only web re|
|21514|New|Enh|2003-07-11|[taglib] html:form focus function could be more po|
|21517|New|Enh|2003-07-11|[tiles] definition's put tag works in non-standard|
|21575|New|Enh|2003-07-14|RequestProcessor : Populating non-String Bean fiel|
|21624|Opn|Enh|2003-07-15|Extend TokenProcessor to handle a list of tra

Re: [shale][clay] Component attributes overriding. Proposals

2005-07-24 Thread gvanmatre 

> 
> Re: [shale][clay] Component attributes overriding. Proposals 
> 
> >>> [snip] 
> >>> I would prefer to see the html attributes always override the xml 
> >>> definitions. I say that because it favors the web designer 
> >>> instead of the developer. 
> >>> However, this new proposed attribute (allowOverriding="false") would give 
> >>> the developer the final decision. 
> >> 
> >> The same as with my solution. The developer provides a value or not. 
> > 
> > This is a bit off tangent to this discussion but I thought it would be 
> > worth 
> 
> Maybe :( 
> 
> > bringing up in the context of creating solutions that promote reuse. 
> > We have a half baked CMS where I work. It provides a way to apply 
> > customizations/overrides to a hierarchy horizontally verses the traditional 
> > vertical OO approach. This works very well for customizing sites for 
> > various 
> > customers because all pages include the same component. The customizations 
> > ("generalization relationships") are applied to a hierarchical structure 
> verses 
> > a new hierarchy created for each new component. 
> > 
> > This is also something we might consider for Clay. Since the jsfid's are 
> > not a 
> > dynamic attribute, it makes it hard to introduce customizations without 
> > creating a new page that references another component. It might be 
> > interesting 
> > to think about applying "overrides" to an existing tree. 
> > 
> > I see the HTML override to the XML as a similar concept. 
> 
> I'm not against the setting of attributes via HTML. I only think that the 
> developer should always have the last word about an attribute value. 
> 
> An example: 
> 
> The designer should decide which colors should be used. The simple solution 
> is 
> that the developer don't specify colors. 
> 
> On the other hand, there may be a requirement that the colors must be 
> specified 
> in a property file (for easy customization). In this case, the developer 
> encodes the values and the specifications from the designer are ignored. 
> 
> Don't forget the following: 
> 
> The html designer possibly has no knowledge about JSF or the application 
> requirements. He set attributes because they produce a nice look and feel. 
> 
> It's the responsibility of the developer to 
> - decide which components should be used 
> - configure the components to resemble the design as close as possible 
> - configure the components to behave correctly in the context of the 
> application 
> - support multi language environments (which may require layout changes) 
> - support dynamic customization requirements (via user profiles) 
> - many many more 
> 

Manfred,  I agree with what you have stated here.  We should add this content 
to the Shale Clay overrview (http://struts.apache.org/shale/features.html#clay) 
soon. 

Gary 
  

> _ 
> Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle 
> Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179 
> 
> 
> 
> 
> - 
> To unsubscribe, e-mail: [EMAIL PROTECTED] 
> For additional commands, e-mail: [EMAIL PROTECTED] 
>

DO NOT REPLY [Bug 35841] - [shale] Clay doesn't preserve the component hierarchy in HTML templates

2005-07-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35841





--- Additional Comments From [EMAIL PROTECTED]  2005-07-25 03:36 ---
Created an attachment (id=15760)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=15760&action=view)
patch

Changed the code to match the java doc comments?  

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r224685 - in /struts/shale/trunk: build.properties.sample default.properties

2005-07-24 Thread wsmoak 
Author: wsmoak
Date: Sun Jul 24 20:11:26 2005
New Revision: 224685

URL: http://svn.apache.org/viewcvs?rev=224685&view=rev
Log:
Moving items that a developer is expected to edit into build.properties.sample

Modified:
struts/shale/trunk/build.properties.sample
struts/shale/trunk/default.properties

Modified: struts/shale/trunk/build.properties.sample
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/build.properties.sample?rev=224685&r1=224684&r2=224685&view=diff
==
--- struts/shale/trunk/build.properties.sample (original)
+++ struts/shale/trunk/build.properties.sample Sun Jul 24 20:11:26 2005
@@ -25,6 +25,27 @@
 # $Id:  $
 #
 
+# Fully qualified pathname of the directory containing this file, and the
+# corresponding overall "build.xml" file.  THIS VALUE MUST BE SET CORRECTLY
+# FOR THE BUILD TO FUNCTION!
+root.dir=${user.home}/Apache/struts/current/shale
+
+# Fully qualified pathname of the directory into which you have unpacked
+# a binary distribution of the JavaServer Faces Reference Implementation
+jsfri.dir=/usr/local/jsf-1_1_01
+
+# Fully qualified pathname of the directory containing the "dist" output
+# of a build of the standalone version of Tiles (currently in the Struts
+# Sandbox).
+tiles.dir=${root.dir}/../sandbox/tiles/core-library/dist
+
+# FindBugs Output File
+findbugs.outputFile=${root.dir}/find-bugs.html
+
+# Name of the library repository directory into which we will download
+# our dependencies
+lib.dir=${root.dir}/lib
+
 # The absolute or relative pathname of the directory containing the
 # Jakarta Commons BeanUtils library
 beanutils.home = /usr/local/commons-beanutils-1.7

Modified: struts/shale/trunk/default.properties
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/default.properties?rev=224685&r1=224684&r2=224685&view=diff
==
--- struts/shale/trunk/default.properties (original)
+++ struts/shale/trunk/default.properties Sun Jul 24 20:11:26 2005
@@ -17,17 +17,8 @@
 #
 
 
-#  Required Customzations 
-
-
-# Fully qualified pathname of the directory containing this file, and the
-# corresponding overall "build.xml" file.  THIS VALUE MUST BE SET CORRECTLY
-# FOR THE BUILD TO FUNCTION!
-root.dir=${user.home}/Apache/struts/current/shale
+#  Optional Customizations ---
 
-# Fully qualified pathname of the directory into which you have unpacked
-# a binary distribution of the JavaServer Faces Reference Implementation
-jsfri.dir=/usr/local/jsf-1_1_01
 
 # Version Identifier to append to artifact filenames, and embed in
 # JavaDoc comments
@@ -36,21 +27,10 @@
 # Location in which state saving should take place (client or server)
 state.saving=client
 
-
-# Fully qualified pathname of the directory containing the "dist" output
-# of a build of the standalone version of Tiles (currently in the Struts
-# Sandbox).
-tiles.dir=${root.dir}/../sandbox/tiles/core-library/dist
-
 # Uncomment the following to compile and execute with MyFaces
 # rather than the JSF Reference Implementation
 #use.myfaces=true
 
-
-
-#  Optional Customizations ---
-
-
 # Name of the Maven repository from which we will download dependencies
 # that are freely available
 maven.repo=http://www.ibiblio.org/maven
@@ -67,13 +47,6 @@
 
 # State for the "optimize" attribute of the "javac" task
 compile.optimize=true
-
-# FindBugs Output File
-findbugs.outputFile=${root.dir}/find-bugs.html
-
-# Name of the library repository directory into which we will download
-# our dependencies
-lib.dir=${root.dir}/lib
 
 # State for the "halt on error" attribute for JUnit tests
 test.haltonerror=true



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r224686 - in /struts/core/trunk/doc: roadmap.xml userGuide/preface.xml

2005-07-24 Thread wsmoak 
Author: wsmoak
Date: Sun Jul 24 20:29:55 2005
New Revision: 224686

URL: http://svn.apache.org/viewcvs?rev=224686&view=rev
Log:
- Make stronger statement about Servlet 2.3 requirement
   See: http://www.mail-archive.com/dev@struts.apache.org/msg10249.html
- Fix typos

Modified:
struts/core/trunk/doc/roadmap.xml
struts/core/trunk/doc/userGuide/preface.xml

Modified: struts/core/trunk/doc/roadmap.xml
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/doc/roadmap.xml?rev=224686&r1=224685&r2=224686&view=diff
==
--- struts/core/trunk/doc/roadmap.xml (original)
+++ struts/core/trunk/doc/roadmap.xml Sun Jul 24 20:29:55 2005
@@ -140,7 +140,7 @@
 
 
 As planned, in Struts 1.3.x we will integrate Struts Chain from 
config and add
-an "extends" attribute to all the configruation elements (a la 
Tiles). While
+an "extends" attribute to all the configuration elements (a la 
Tiles). While
 we're at it, we may also add a Ant-style properties file to make 
variable
 substitutions within the XML elements. The substitution feature is 
supported by 
 Spring and iBATIS, among others, and is a useful way to configure 
applications 
@@ -162,7 +162,7 @@
 ActionCommand - A Chain Command-like interface with one 
method:
 
 
-void Execute(ActionContext context)
+void execute(ActionContext context)
 
 
 Support for conventional Actions would stay in place, but as an 
alternative, a
@@ -479,7 +479,7 @@
 
 Craig McClanahan's http://blogs.sun.com/roller/page/craigmcc/20040927";>blog entry
 Our FAQ
-http://www.jamesholmes.com/JavaServerFaces/";>Java 
Server Faces Resources at JamesHomes.com
+http://www.jamesholmes.com/JavaServerFaces/";>Java 
Server Faces Resources at JamesHolmes.com
  
 
 

Modified: struts/core/trunk/doc/userGuide/preface.xml
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/doc/userGuide/preface.xml?rev=224686&r1=224685&r2=224686&view=diff
==
--- struts/core/trunk/doc/userGuide/preface.xml (original)
+++ struts/core/trunk/doc/userGuide/preface.xml Sun Jul 24 20:29:55 2005
@@ -534,9 +534,9 @@
   The Struts 1.0, 1.1, and 1.2 versions require only version 2.2 or 
later
   of the Servlet Specification to be implemented by your servlet container,
   so those versions of Struts do not use Filters. Beginning with the Struts
-  1.3 version, support for version 2.2 of the Servlet Specification is no
-  longer guaranteed, and it is possible that Struts itself might use 
Filters
-  in the future.
+  1.3 version, a container that supports version 2.3 or later of the 
Servlet
+  Specification is required, and it is possible that Struts itself might 
use
+  Filters in the future.
   
   
   For more about filters, see:



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r224687 - in /struts/shale/trunk/core-library: build.xml src/java/org/apache/shale/spring/webflow/ src/java/org/apache/shale/spring/webflow/WebFlowNavigationHandler.java src/java/org/apach

2005-07-24 Thread craigmcc 
Author: craigmcc
Date: Sun Jul 24 21:25:43 2005
New Revision: 224687

URL: http://svn.apache.org/viewcvs?rev=224687&view=rev
Log:
Initial compilable integration between Spring WebFlow and JSF.

NOTE:  THIS CODE ULTIMATELY BELONGS INSIDE SPRING WEBFLOW, BECAUSE IT IS NOT
DEPENDENT ON SHALE.  IT WILL BE OFFERED TO SPRING WHEN IT IS COMPLETED.

There are a bunch of FIXME issues that need to be addressed before this code
will actually function, but this gives an indication for how Spring WebFlow
(I'm testing against Spring 1.2.2 and Spring WebFlow PR4) should be able to
integrate with JavaServer Faces.

Added:
struts/shale/trunk/core-library/src/java/org/apache/shale/spring/webflow/

struts/shale/trunk/core-library/src/java/org/apache/shale/spring/webflow/WebFlowNavigationHandler.java

struts/shale/trunk/core-library/src/java/org/apache/shale/spring/webflow/WebFlowNavigationStrategy.java
Modified:
struts/shale/trunk/core-library/build.xml

Modified: struts/shale/trunk/core-library/build.xml
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/core-library/build.xml?rev=224687&r1=224686&r2=224687&view=diff
==
--- struts/shale/trunk/core-library/build.xml (original)
+++ struts/shale/trunk/core-library/build.xml Sun Jul 24 21:25:43 2005
@@ -111,6 +111,7 @@
 
 
 
+
 
 
   
@@ -131,6 +132,7 @@
 
 
 
+
   
 
 
@@ -156,6 +158,7 @@
 
 
 
+
 
 
 

Added: 
struts/shale/trunk/core-library/src/java/org/apache/shale/spring/webflow/WebFlowNavigationHandler.java
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/core-library/src/java/org/apache/shale/spring/webflow/WebFlowNavigationHandler.java?rev=224687&view=auto
==
--- 
struts/shale/trunk/core-library/src/java/org/apache/shale/spring/webflow/WebFlowNavigationHandler.java
 (added)
+++ 
struts/shale/trunk/core-library/src/java/org/apache/shale/spring/webflow/WebFlowNavigationHandler.java
 Sun Jul 24 21:25:43 2005
@@ -0,0 +1,246 @@
+/*
+ * Copyright 2004-2005 The Apache Software Foundation.
+ * 
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * 
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ * 
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.shale.spring.webflow;
+
+import javax.faces.application.NavigationHandler;
+import javax.faces.context.FacesContext;
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
+import org.springframework.web.context.WebApplicationContext;
+import org.springframework.web.jsf.FacesContextUtils;
+import org.springframework.webflow.ViewDescriptor;
+import org.springframework.webflow.execution.FlowExecutionManager;
+import 
org.springframework.webflow.execution.servlet.ServletFlowExecutionManager;
+
+
+/**
+ * An implementation of NavigationHandler that provides
+ * integration with Spring WebFlow (tested with version PR4).
+ * It delegates handling to the standard implementation when there is no
+ * current flow.
+ * 
+ * If a flow is not currently in progress:
+ * 
+ * If the specified logical outcome is not
+ * of the form webflow:xxx, delegate to the standard
+ * NavigationHandler implementation and return.
+ * If the specified logical outcome is of the
+ * form webflow:xxx, look up the corresponding
+ * Flow, and begin execution at its starting state.
+ * Record state information to indicate that this flow is
+ * in progress.
+ * 
+ * If a flow is currently in progress:
+ * 
+ * Acquire references to the current state information for the
+ * in progress flow.
+ * Continue execution of the flow until it returns a
+ * ViewDescriptor describing the next view to be
+ * rendered.
+ * Cause navigation to the requested view (FIXME - perhaps exposing
+ * any specified model state as a Map under some reasonable request
+ * attribute name.
+ * 
+ * 
+ *
+ * $Id$
+ */
+
+public class WebFlowNavigationHandler extends NavigationHandler {
+
+
+//  
Constructors
+
+
+/**
+ * Create a new [EMAIL PROTECTED] WebFlowNavigationHandler}, wrapping 
the
+ * specified standard navigation handler implementation.
+ *
+ * @param handler Standard NavigationHandler we are wrapping
+ */
+public WebFlowNavigationHandler(NavigationHandler handler) {

[Shale] Heads Up On Compiling Core Library

2005-07-24 Thread Craig McClanahan 
As I promised on the Spring developer list a while back, I'm working
on an integration between Spring WebFlow (currently at release PR4)
and JavaServer Faces.  For the moment, this code will exist in the
Shale core-library sub-module ... but the code will utlimately be
offered to the Spring project for inclusion in Spring WebFlow directly
... which is appropriate because it only depends on JSF (but that
means Shale users will get it for free too :-).

In the mean time, though, that means you need to define properties
"webflow.home" and "spring-webflow.jar" in your "build.properties"
file if you want to build the core-library sub-module.

Craig

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r224692 - in /struts/shale/trunk: build.properties.sample core-library/build.xml

2005-07-24 Thread wsmoak 
Author: wsmoak
Date: Sun Jul 24 22:09:49 2005
New Revision: 224692

URL: http://svn.apache.org/viewcvs?rev=224692&view=rev
Log:
- Updated suggested properties in sample build.properties file
- Changed core-library build to use downloaded dependencies

Modified:
struts/shale/trunk/build.properties.sample
struts/shale/trunk/core-library/build.xml

Modified: struts/shale/trunk/build.properties.sample
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/build.properties.sample?rev=224692&r1=224691&r2=224692&view=diff
==
--- struts/shale/trunk/build.properties.sample (original)
+++ struts/shale/trunk/build.properties.sample Sun Jul 24 22:09:49 2005
@@ -37,7 +37,7 @@
 # Fully qualified pathname of the directory containing the "dist" output
 # of a build of the standalone version of Tiles (currently in the Struts
 # Sandbox).
-tiles.dir=${root.dir}/../sandbox/tiles/core-library/dist
+tiles.dir=${root.dir}/../sandbox/tiles
 
 # FindBugs Output File
 findbugs.outputFile=${root.dir}/find-bugs.html
@@ -48,15 +48,15 @@
 
 # The absolute or relative pathname of the directory containing the
 # Jakarta Commons BeanUtils library
-beanutils.home = /usr/local/commons-beanutils-1.7
+beanutils.home = ${lib.dir}/commons-beanutils
 
 # The absolute or relative pathname of the directory containing the
 # Jakarta Commons Chain library
-chain.home = /usr/local/commons-chain-1.0
+chain.home = ${lib.dir}/commons-chain
 
 # The absolute or relative pathname of the directory containing the
 # Jakarta Commons Digester library
-digester.home = /usr/local/commons-digester-1.6
+digester.home = ${lib.dir}/commons-digester
 
 # The absolute or relative pathname of the JavaServer Faces 
 # implementation
@@ -69,25 +69,29 @@
 jstl.home = /Developer/Java/Tools/jakarta/jakarta-taglibs-standard-1.1.0
 
 # The absolute or relative pathname of the Commons Validator install dir
-commons-validator.home = /Developer/Java/Tools/jakarta/commons-validator-1.0.2
+validator.home = ${lib.dir}/commons-validator
 
 # (OPTIONAL) The absolute or relative pathname to the "dist" directory
 
 # The absolute or relative pathname of the directory containing the
 # Jakarta Commons Logging library
-logging.home = /usr/local/commons-logging-1.0.4
+logging.home = ${lib.dir}/commons-logging
 
 # The absolute or relative pathname of the directory containing your
 # Servlet API classes JAR file (servlet.jar)
-server.home = /usr/local/jakarta-tomcat-5.0.28
+servlet-api.home = ${lib.dir}/servlet-api
+
+# The absolute or relative pathname of the directory containing your
+# JSP API classes JAR file
+jsp-api.home = ${lib.dir}/jsp-api
 
 # The absolute or relative pathname of the Apache Struts 
 # distribution
 struts.home = /usr/local/jakarta-struts
 
 # (OPTIONAL) The absolute or relative pathname to the "dist" directory
-# of the Spring Framework distribution (version 1.1.5 or later)
-spring.home=/usr/local/spring-framework-1.1.5
+# of the Spring Framework distribution (version 1.2.2 or later)
+spring.home=${lib.dir}/springframework
 
 # (Optional) The absolute or relative pathname of the directory containing
 # the "findbugs" tool (http://findbugs.sourceforge/net/)

Modified: struts/shale/trunk/core-library/build.xml
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/core-library/build.xml?rev=224692&r1=224691&r2=224692&view=diff
==
--- struts/shale/trunk/core-library/build.xml (original)
+++ struts/shale/trunk/core-library/build.xml Sun Jul 24 22:09:49 2005
@@ -39,9 +39,11 @@
   
   
+value="${chain.home}/commons-chain.jar"/>
+  
   
 
@@ -96,7 +99,7 @@
   
 
 
-
+
 
 
 
 
 
@@ -140,7 +143,7 @@
   
 
 
-
+
 
 
 
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r224694 - /struts/shale/trunk/clay-plugin/build.xml

2005-07-24 Thread wsmoak 
Author: wsmoak
Date: Sun Jul 24 22:25:39 2005
New Revision: 224694

URL: http://svn.apache.org/viewcvs?rev=224694&view=rev
Log:
Changed clay-plugin build to use downloaded dependencies

Modified:
struts/shale/trunk/clay-plugin/build.xml

Modified: struts/shale/trunk/clay-plugin/build.xml
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/clay-plugin/build.xml?rev=224694&r1=224693&r2=224694&view=diff
==
--- struts/shale/trunk/clay-plugin/build.xml (original)
+++ struts/shale/trunk/clay-plugin/build.xml Sun Jul 24 22:25:39 2005
@@ -53,13 +53,13 @@
 
value="${jsf.home}/lib/commons-logging.jar"/>
   
   
-  
+  
   
   
-  
+  
   
   
-  
+  
   
 
   



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r224696 - in /struts/shale/trunk: test-framework/build.xml use-cases/build.xml

2005-07-24 Thread wsmoak 
Author: wsmoak
Date: Sun Jul 24 22:36:38 2005
New Revision: 224696

URL: http://svn.apache.org/viewcvs?rev=224696&view=rev
Log:
Changed test-framework and use-cases builds to use downloaded dependencies

Modified:
struts/shale/trunk/test-framework/build.xml
struts/shale/trunk/use-cases/build.xml

Modified: struts/shale/trunk/test-framework/build.xml
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/test-framework/build.xml?rev=224696&r1=224695&r2=224696&view=diff
==
--- struts/shale/trunk/test-framework/build.xml (original)
+++ struts/shale/trunk/test-framework/build.xml Sun Jul 24 22:36:38 2005
@@ -54,7 +54,7 @@
   
   
   
-  
+  
   
   
 

Modified: struts/shale/trunk/use-cases/build.xml
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/use-cases/build.xml?rev=224696&r1=224695&r2=224696&view=diff
==
--- struts/shale/trunk/use-cases/build.xml (original)
+++ struts/shale/trunk/use-cases/build.xml Sun Jul 24 22:36:38 2005
@@ -45,7 +45,7 @@
   
   
+value="${chain.home}/commons-chain.jar"/>
   
   
   
+
value="${validator.home}/commons-validator.jar"/>
 
   
   
   
   
   
-  
+  
   
   
   
   
-  
-  
-  
-  
+  
+  
+  
+  
   
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Shale] Heads Up On Compiling Core Library

2005-07-24 Thread Wendy Smoak 

From: "Craig McClanahan" <[EMAIL PROTECTED]>


In the mean time, though, that means you need to define properties
"webflow.home" and "spring-webflow.jar" in your "build.properties"
file if you want to build the core-library sub-module.


Craig, I didn't realize that was a temporary change, so I added
'spring-webflow.jar' to core-library/build.xml expecting that the .jar file
would be added to /shale/lib/springframework/.  It should be fine, as your
build.properties will take precendence.

If you're building any of the Shale modules, please run the
'download-dependencies' Ant task in the global build.xml, and then revisit
default.properties and build.properties.sample as I moved/renamed some
things.

--
Wendy Smoak



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]