Ryan Lubke (JIRA | 3 Oct 20:04 2007
Picon

Created: (SHALE-472) Don't rely on JSF-RI specific implementation classes for implementation detection.

Don't rely on JSF-RI specific implementation classes for implementation detection.
----------------------------------------------------------------------------------

                 Key: SHALE-472
                 URL: https://issues.apache.org/struts/browse/SHALE-472
             Project: Shale
          Issue Type: Task
          Components: Core
    Affects Versions: 1.0.4
            Reporter: Ryan Lubke

Shale currently looks for com.sun.faces.config.JSFVersionTracker to determine the runtime is 1.2 RI.
However, we've recently changed the code so that this class isn't needed.  I was going to remove
it, but I remembered this dependency.

Is the RI/MyFaces determination necessary?  Couldn't the API be checked for the presence of a method added
in 1.2
to determine a 1.2 vs 1.1 runtime?

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Gregg Leichtman (JIRA | 7 Oct 13:52 2007
Picon

Commented: (SHALE-302) TilesViewHandler does not work for JSF 1.2


    [
https://issues.apache.org/struts/browse/SHALE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42350
] 

Gregg Leichtman commented on SHALE-302:
---------------------------------------

As per developer request, I have attached my modified version of Steven Oglesby JSF 1.1 TilesViewHandler.
This modifed version works with JSF 1.2 and, at a minimum, Tiles 2.0.4. This code is Sun RI specific. It will
not work with MyFaces in its current form, but it does work with the Shale 1.1.0 snapshot from 20070923,
Trinidad 1.2.1 and Tomahawk 1.1.6.

                             -=> Gregg <=-

> TilesViewHandler does not work for JSF 1.2
> ------------------------------------------
>
>                 Key: SHALE-302
>                 URL: https://issues.apache.org/struts/browse/SHALE-302
>             Project: Shale
>          Issue Type: Bug
>          Components: Tiles
>    Affects Versions: 1.0.3
>            Reporter: Steven Oglesby
>             Fix For: TBD
>
>
> The TilesViewHandler does not handle the JSF 1.2 spec. It does not fulfil the requirements of wrapping and
buffering the response. This has been introduced in the JSF 1.2 spec in order to solve the JSF / JSP content
(Continue reading)

Gregg Leichtman (JIRA | 7 Oct 13:58 2007
Picon

Updated: (SHALE-302) TilesViewHandler does not work for JSF 1.2


     [
https://issues.apache.org/struts/browse/SHALE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregg Leichtman updated SHALE-302:
----------------------------------

    Attachment: TilesViewHandler.java

See above comment from me. I have allowed inclusion of this file in ASF works, if it doesn't violate any Sun
licensing clauses. Since it is likely to be changed completely, I don't believe this will represent a problem.

                                -=> Gregg <=-

> TilesViewHandler does not work for JSF 1.2
> ------------------------------------------
>
>                 Key: SHALE-302
>                 URL: https://issues.apache.org/struts/browse/SHALE-302
>             Project: Shale
>          Issue Type: Bug
>          Components: Tiles
>    Affects Versions: 1.0.3
>            Reporter: Steven Oglesby
>             Fix For: TBD
>
>         Attachments: TilesViewHandler.java
>
>
> The TilesViewHandler does not handle the JSF 1.2 spec. It does not fulfil the requirements of wrapping and
(Continue reading)

ole ersoy (JIRA | 13 Oct 22:22 2007
Picon

Created: (SHALE-473) Spelling "handers" >> "handlers"

Spelling "handers" >> "handlers" 
---------------------------------

                 Key: SHALE-473
                 URL: https://issues.apache.org/struts/browse/SHALE-473
             Project: Shale
          Issue Type: Improvement
          Components: Website
            Reporter: ole ersoy
            Priority: Trivial

The shale home page >> Shale Features >> View Controller

There the text:
"with predefined event handers"

I think it should be:

"predefined event handlers"

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Kito D. Mann (JIRA | 17 Oct 14:32 2007
Picon

Commented: (SHALE-409) Shale 1.0.4+ incorrectly removes all entries in the request map after render response


    [
https://issues.apache.org/struts/browse/SHALE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42408
] 

Kito D. Mann commented on SHALE-409:
------------------------------------

Hmm.. I'm still seeing this issue with the latest nightly build (10/17/07) and RichFaces 3.1. Is it just me?

> Shale 1.0.4+ incorrectly removes all entries in the request map after render response
> -------------------------------------------------------------------------------------
>
>                 Key: SHALE-409
>                 URL: https://issues.apache.org/struts/browse/SHALE-409
>             Project: Shale
>          Issue Type: Bug
>          Components: View
>    Affects Versions: 1.0.1, 1.0.4, 1.0.5-SNAPSHOT, 1.1.0-SNAPSHOT
>         Environment: WinXP, AJAX4JSF-1.0.6+, Shale-1.0.4 (Application, Core, Dialog, Spring, Tiger, View)
>            Reporter: Todd Bush
>            Assignee: Gary VanMatre
>             Fix For: 1.0.5-SNAPSHOT, 1.1.0-SNAPSHOT
>
>
> I found this issue while debugging why Shale-1.0.4 caused AJAX4JSF to stop working.  Within the
ViewPhaseListener.afterRenderResponse method, all ViewControllers and AbstractRequestBeans are
removed from the request map.  Then a second loop through the request map removes all other entries in an
attempt to remove any annotated managed beans.  AJAX4JSF relies on entries in the request map while
parsing the outgoing HTML, entries which are removed by this phase listener.  Once I comment out the second
(Continue reading)

ole ersoy (JIRA | 17 Oct 17:14 2007
Picon

Created: (SHALE-474) Documentation Correction

Documentation Correction
------------------------

                 Key: SHALE-474
                 URL: https://issues.apache.org/struts/browse/SHALE-474
             Project: Shale
          Issue Type: Improvement
            Reporter: ole ersoy
            Priority: Trivial

Here:

http://shale.apache.org/shale-clay/index.html

It says:

These implicitly mappings can be overridden with a block "ignore".

I think it's supposed to be:

These implicitly defined mappings can be overridden with a block "ignore".

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Kito D. Mann (JIRA | 18 Oct 00:20 2007
Picon

Issue Comment Edited: (SHALE-409) Shale 1.0.4+ incorrectly removes all entries in the request map after render response


    [
https://issues.apache.org/struts/browse/SHALE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42408
] 

kito99 edited comment on SHALE-409 at 10/17/07 3:19 PM:
--------------------------------------------------------------

I just tried the nightly build (as of 10/17/07) with RichFaces 3.1.1 GA. I wasn't able to get things to work
until I commented out the Shale ViewHandler in the JAR file's faces-config.xml (and added it as a
configuration parameter in web.xml, as per the docs):

	<context-param>
		<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
		<param-value>
			org.apache.shale.view.faces.ViewViewHandler,com.sun.facelets.FaceletViewHandler
		</param-value>
	</context-param>

(I'm obviously using Facelets.) I also had to comment out the ShaleViewRoot component definition in the
Shale faces-config.xml. 

So my updated faces-config.xml  (in shale-view-1.1.0-SNAPSHOT.jar/META-INF) looks like this: 

<faces-config>

  <!-- Custom JSF Application Objects -->
  <application>
    <action-listener>
      org.apache.shale.view.faces.ViewActionListener
(Continue reading)

Kito D. Mann (JIRA | 18 Oct 00:20 2007
Picon

Issue Comment Edited: (SHALE-409) Shale 1.0.4+ incorrectly removes all entries in the request map after render response


    [
https://issues.apache.org/struts/browse/SHALE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42408
] 

kito99 edited comment on SHALE-409 at 10/17/07 3:20 PM:
--------------------------------------------------------------

I just tried the nightly build (as of 10/17/07) with RichFaces 3.1.1 GA. I wasn't able to get things to work
until I commented out the Shale ViewHandler in the JAR file's faces-config.xml (and added it as a
configuration parameter in web.xml, as per the RichFaces docs):

	<context-param>
		<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
		<param-value>
			org.apache.shale.view.faces.ViewViewHandler,com.sun.facelets.FaceletViewHandler
		</param-value>
	</context-param>

(I'm obviously using Facelets.) I also had to comment out the ShaleViewRoot component definition in the
Shale faces-config.xml. 

So my updated faces-config.xml  (in shale-view-1.1.0-SNAPSHOT.jar/META-INF) looks like this: 

<faces-config>

  <!-- Custom JSF Application Objects -->
  <application>
    <action-listener>
      org.apache.shale.view.faces.ViewActionListener
(Continue reading)

Chris Keefer (JIRA | 30 Oct 19:38 2007
Picon

Created: (SHALE-475) Setup managed bean in JSF 1.2

Setup managed bean in JSF 1.2
-----------------------------

                 Key: SHALE-475
                 URL: https://issues.apache.org/struts/browse/SHALE-475
             Project: Shale
          Issue Type: Bug
          Components: Test
    Affects Versions: 1.0.4
         Environment: Java 5, OS X 10.4.10, JSF 1.2
            Reporter: Chris Keefer

When trying to add a managed bean to the Mock Faces Context a Missing Resource Exception is thrown. The test
class extends AbstractJsfTestCase. The setUp method is the following:

public void setUp() throws Exception {
    super.setUp();

    // add managed bean
    _factory = application.getExpressionFactory();
    _elContext = MockFacesContext.getCurrentInstance().getELContext();
    ValueExpression expression =
        _factory.createValueExpression(_elContext, "#{leftNav}", LeftNav.class);
    MockServletContext context = (MockServletContext)session.getServletContext();
    context.setDocumentRoot(new File(DOC_ROOT));
    expression.setValue(_elContext, new LeftNav());
}

The last line throws the MissingResourceException.

(Continue reading)


Gmane