Craig McClanahan (JIRA | 1 Sep 08:19 2006
Picon

Commented: (SHALE-263) Explore use of Commons SCXML for dialogs

    [ http://issues.apache.org/struts/browse/SHALE-263?page=comments#action_38109 ] 

Craig McClanahan commented on SHALE-263:
----------------------------------------

I've committed the basic implementation classes in SHALE-263-01.diff.

> Explore use of Commons SCXML for dialogs
> ----------------------------------------
>
>                 Key: SHALE-263
>                 URL: http://issues.apache.org/struts/browse/SHALE-263
>             Project: Shale
>          Issue Type: New Feature
>          Components: Dialog
>    Affects Versions: 1.0.4-SNAPSHOT
>            Reporter: Rahul Akolkar
>         Attachments: dialogconfig2scxml.xml, SHALE-263-01.diff
>
>
> Based on dev list discussions, it will be worthwhile to explore the possibility of using Commons SCXML for
the internals of Shale dialogs. Additionally, supporting the use of SCXML documents to describe Shale
dialogs also has numerous advantages. A starting point for this work is available here:
>  http://jakarta.apache.org/commons/scxml/usecases/scxml-in-shale-dialogs.html
> Now that we've had a Commons SCXML release and discussions about Shale dialogs have begun afresh, its a
good time to add this request as a JIRA ticket.

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

alberto (JIRA | 1 Sep 18:39 2006
Picon

Created: (SHALE-270) Illegal date format

Illegal date format 
--------------------

                 Key: SHALE-270
                 URL: http://issues.apache.org/struts/browse/SHALE-270
             Project: Shale
          Issue Type: Bug
          Components: Remoting
    Affects Versions: 1.0.4-SNAPSHOT
         Environment: JSF 1.2, Glassfish.
            Reporter: alberto

I am serving my javascript resource with shale-remoting.
When the resorce enters in client cache, and the browser try to validate a cache entry I get this exception:

phase(RESTORE_VIEW 1,com.sun.faces.context.FacesContextImpl <at> 1a6af53) threw exception:
java.lang.IllegalArgumentException: ven, 01 set 2006 16:00:23 GMT ven, 01 set 2006 16:00:23 GMT
org.apache.coyote.tomcat5.CoyoteRequest.getDateHeader(CoyoteRequest.java:2104)
org.apache.coyote.tomcat5.CoyoteRequestFacade.getDateHeader(CoyoteRequestFacade.java:652)
javax.servlet.http.HttpServletRequestWrapper.getDateHeader(HttpServletRequestWrapper.java:83)
org.apache.shale.remoting.impl.AbstractResourceProcessor.ifModifiedSince(AbstractResourceProcessor.java:349)
org.apache.shale.remoting.impl.AbstractResourceProcessor.process(AbstractResourceProcessor.java:101)
org.apache.shale.remoting.faces.RemotingPhaseListener.afterPhase(RemotingPhaseListener.java:102)
...

You can see that "ven, 01 set 2006 16:00:23 GMT ven, 01 set 2006 16:00:23 GMT" is an italian date format.
I use FireFox, but I think FF is not the problem.
What I believe is that Shale is sending the "Last-Modified" date in an italian format (I am italian).

--

-- 
(Continue reading)

sean schofield (JIRA | 3 Sep 20:07 2006
Picon

Created: (SHALE-271) Dialog2 can't find my dialog definitions

Dialog2 can't find my dialog definitions
----------------------------------------

                 Key: SHALE-271
                 URL: http://issues.apache.org/struts/browse/SHALE-271
             Project: Shale
          Issue Type: Bug
          Components: Sandbox
            Reporter: sean schofield
         Assigned To: sean schofield
             Fix For: 1.0.4-SNAPSHOT

Apparently the dialog stuff is unable to find my dialog definition.  I have it in
WEB-INF/dialog-config.xml so I will investigate and see what the issue is.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Craig McClanahan (JIRA | 4 Sep 01:36 2006
Picon

Resolved: (SHALE-271) Dialog2 can't find my dialog definitions

     [ http://issues.apache.org/struts/browse/SHALE-271?page=all ]

Craig McClanahan resolved SHALE-271.
------------------------------------

    Resolution: Fixed

This should be fixed now in the latest trunk code (we're not publishing nightly builds of the sandbox
stuff).  The "shale-test-dialog2-legacy" webapp in the sandbox illustrates that this works, because it
now comments out the name of the default resource that is loaded automatically.

> Dialog2 can't find my dialog definitions
> ----------------------------------------
>
>                 Key: SHALE-271
>                 URL: http://issues.apache.org/struts/browse/SHALE-271
>             Project: Shale
>          Issue Type: Bug
>          Components: Sandbox
>            Reporter: sean schofield
>         Assigned To: sean schofield
>             Fix For: 1.0.4-SNAPSHOT
>
>
> Apparently the dialog stuff is unable to find my dialog definition.  I have it in
WEB-INF/dialog-config.xml so I will investigate and see what the issue is.

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

sean schofield (JIRA | 4 Sep 03:06 2006
Picon

Created: (SHALE-272) LegacyDialogManager should issue warning when no dialog config information is found

LegacyDialogManager should issue warning when no dialog config information is found
-----------------------------------------------------------------------------------

                 Key: SHALE-272
                 URL: http://issues.apache.org/struts/browse/SHALE-272
             Project: Shale
          Issue Type: Improvement
    Affects Versions: 1.0.4-SNAPSHOT
            Reporter: sean schofield
         Assigned To: sean schofield
            Priority: Minor
             Fix For: 1.0.4-SNAPSHOT

Currently, if the dialog-config.xml file is missing, there is just an empty HashMap with no dialogs.  It
would be good to issue a warning if this happens so that the user has some insight into why there dialogs are
not working properly.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

sean schofield (JIRA | 4 Sep 03:25 2006
Picon

Resolved: (SHALE-272) LegacyDialogManager should issue warning when no dialog config information is found

     [ http://issues.apache.org/struts/browse/SHALE-272?page=all ]

sean schofield resolved SHALE-272.
----------------------------------

    Resolution: Fixed

> LegacyDialogManager should issue warning when no dialog config information is found
> -----------------------------------------------------------------------------------
>
>                 Key: SHALE-272
>                 URL: http://issues.apache.org/struts/browse/SHALE-272
>             Project: Shale
>          Issue Type: Improvement
>    Affects Versions: 1.0.4-SNAPSHOT
>            Reporter: sean schofield
>         Assigned To: sean schofield
>            Priority: Minor
>             Fix For: 1.0.4-SNAPSHOT
>
>
> Currently, if the dialog-config.xml file is missing, there is just an empty HashMap with no dialogs.  It
would be good to issue a warning if this happens so that the user has some insight into why there dialogs are
not working properly.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
(Continue reading)

Wendy Smoak (JIRA | 4 Sep 21:26 2006
Picon

Created: (SHALE-273) Document the Sandbox policy on access for existing Apache committers

Document the Sandbox policy on access for existing Apache committers
--------------------------------------------------------------------

                 Key: SHALE-273
                 URL: http://issues.apache.org/struts/browse/SHALE-273
             Project: Shale
          Issue Type: Task
          Components: Documentation
            Reporter: Wendy Smoak
             Fix For: 1.0.4-SNAPSHOT

Proposal thread: http://www.nabble.com/-PROPOSAL--Open-the-Shale-Sandbox-to-any-interested-Apache-committer-t2200372.html

The Shale Sandbox is now open to any existing Apache committer.

Add an index page for the sandbox, and add a link to the Sandbox from the shale.apache.org website.

Though it doesn't affect the framework, I'm marking this as fix-for 1.0.4 so it will show up in the release notes.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Craig McClanahan (JIRA | 4 Sep 22:22 2006
Picon

Created: (SHALE-274) [dialog2] Clean up static resources at application shutdown

[dialog2] Clean up static resources at application shutdown
-----------------------------------------------------------

                 Key: SHALE-274
                 URL: http://issues.apache.org/struts/browse/SHALE-274
             Project: Shale
          Issue Type: Bug
          Components: Sandbox
            Reporter: Craig McClanahan
             Fix For: 1.0.4-SNAPSHOT

The legacy dialog2 implementation relies on both Commons Logging and Commons Digester (which implies a
transitive dependence on Commons BeanUtils).  Therefore, we need to clean up at application shutdown by
executing the following in a contextDestroyed() lifecycle listener (or equivalent):

    PropertyUtils.clearDescriptors();
    LogFactory.release(Thread.currentThread().getContextClassLoader());

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

sean schofield (JIRA | 4 Sep 23:25 2006
Picon

Commented: (SHALE-113) [shale] Create "Dialog Aware" button panel component

    [ http://issues.apache.org/struts/browse/SHALE-113?page=comments#action_38128 ] 

sean schofield commented on SHALE-113:
--------------------------------------

My proposal would be to supply the mechanism for applications to provide their own dialog aware buttons.  In
other words, provide a hook for EL expressions so you can have something like:

<h:commandButton action"next" value="Next" rendered="#{someBean.isNextAvailable}"/>

This way we don't have to be involved with the look and feel of buttons, etc.  We just provide an easy way for
developers to design their own.  If the ability to determine whether the buttons should be rendered became
available, it would be easy to provide your own reusable button panel and layout using Tiles, Facelets,
Clay or whatever.

> [shale] Create "Dialog Aware" button panel component
> ----------------------------------------------------
>
>                 Key: SHALE-113
>                 URL: http://issues.apache.org/struts/browse/SHALE-113
>             Project: Shale
>          Issue Type: Improvement
>          Components: Dialog
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Ed Burns
>            Priority: Minor
>
> There really should be a dialog aware button panel component that automatically
> generates next and previous buttons, greying things out as appropriate.
(Continue reading)

Wendy Smoak (JIRA | 5 Sep 00:47 2006
Picon

Resolved: (SHALE-273) Document the Sandbox policy on access for existing Apache committers

     [ http://issues.apache.org/struts/browse/SHALE-273?page=all ]

Wendy Smoak resolved SHALE-273.
-------------------------------

    Resolution: Fixed
      Assignee: Wendy Smoak

Done  http://shale.apache.org/sandbox/

> Document the Sandbox policy on access for existing Apache committers
> --------------------------------------------------------------------
>
>                 Key: SHALE-273
>                 URL: http://issues.apache.org/struts/browse/SHALE-273
>             Project: Shale
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Wendy Smoak
>         Assigned To: Wendy Smoak
>             Fix For: 1.0.4-SNAPSHOT
>
>
> Proposal thread: http://www.nabble.com/-PROPOSAL--Open-the-Shale-Sandbox-to-any-interested-Apache-committer-t2200372.html
> The Shale Sandbox is now open to any existing Apache committer.
> Add an index page for the sandbox, and add a link to the Sandbox from the shale.apache.org website.
> Though it doesn't affect the framework, I'm marking this as fix-for 1.0.4 so it will show up in the release notes.

--

-- 
This message is automatically generated by JIRA.
(Continue reading)


Gmane