[jira] [Commented] (MYFACES-4131) begin and end do not look to be implemented / working

2017-08-03 Thread Dora Rajappan (JIRA)

[ 
https://issues.apache.org/jira/browse/MYFACES-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112730#comment-16112730
 ] 

Dora Rajappan commented on MYFACES-4131:


This feature is not implemented in myfaces. Im working out a patch.

>  begin and end do not look to be implemented / working
> --
>
> Key: MYFACES-4131
> URL: https://issues.apache.org/jira/browse/MYFACES-4131
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-372
>Affects Versions: 2.3.0-beta
>Reporter: Paul Nicolucci
>
> I started to test the  constraint feature of JSF 2.3 and it does 
> not look to function on MyFaces. 
> The changes required are for the following JSF 2.3 spec issue : 
> https://github.com/javaee/javaserverfaces-spec/issues/1102
> According to the spec the  tag will now have begin and end 
> attributes. For instance:
> 
> #{x}
> 
> In the above example if testList had 10 items in it each entry containing a 
> number 0-9 then we would expect the following output:
> 0123456789
> If we changed it to:
> 
> #{x}
> 
> We would expect the following output:
> 56789



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (TOBAGO-1752) DeltaSpike WindowId doesn't work correctly with Tobago

2017-08-03 Thread Henning Noeth (JIRA)

[ 
https://issues.apache.org/jira/browse/TOBAGO-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112650#comment-16112650
 ] 

Henning Noeth commented on TOBAGO-1752:
---

Automatic tests updated.

> DeltaSpike WindowId doesn't work correctly with Tobago
> --
>
> Key: TOBAGO-1752
> URL: https://issues.apache.org/jira/browse/TOBAGO-1752
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Core, Themes
>Affects Versions: 3.0.4
>Reporter: Udo Schnurpfeil
>Assignee: Henning Noeth
> Fix For: 3.0.5, 4.0.0
>
>
> Problem is, that CSP conflicts with code rendered by 
> {code:java}
> 
> {code}
> Solution: Tobago renders all the stuff, there is *no need* to use this tag.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (TOBAGO-1774) No Margin-bottom for TabGroup

2017-08-03 Thread Henning Noeth (JIRA)
Henning Noeth created TOBAGO-1774:
-

 Summary: No Margin-bottom for TabGroup
 Key: TOBAGO-1774
 URL: https://issues.apache.org/jira/browse/TOBAGO-1774
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Themes
Reporter: Henning Noeth
Assignee: Henning Noeth
Priority: Minor


 doesn't render a margin to the bottom.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (TOMAHAWK-1684) Getting a blank page after migrating from JSF 1.0 to JSF 1.2 with myfaces+tomahawk+tiles

2017-08-03 Thread Vemuri A Ramakrishna (JIRA)

[ 
https://issues.apache.org/jira/browse/TOMAHAWK-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112396#comment-16112396
 ] 

Vemuri A Ramakrishna commented on TOMAHAWK-1684:


I am gettng this when i include the source of myfaces and tomahawk and debug 
the issue

javax.faces.FacesException: weblogic.servlet.jsp.CompilationException: Failed 
to compile JSP /start.jsp
start.jsp:3:5: No tag library could be found with this URI. Possible causes 
could be that the URI is incorrect, or that there were errors during parsing of 
the .tld file.
<%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t"%>
^^
start.jsp:3:5: No tag library could be found with this URI. Possible causes 
could be that the URI is incorrect, or that there were errors during parsing of 
the .tld file.
<%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t"%>
^^
start.jsp:4:5: No tag library could be found with this URI. Possible causes 
could be that the URI is incorrect, or that there were errors during parsing of 
the .tld file.
<%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h"  %>
^^
start.jsp:4:5: No tag library could be found with this URI. Possible causes 
could be that the URI is incorrect, or that there were errors during parsing of 
the .tld file.
<%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h"  %>
^^
start.jsp:5:5: No tag library could be found with this URI. Possible causes 
could be that the URI is incorrect, or that there were errors during parsing of 
the .tld file.
<%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f" %>
^^
start.jsp:5:5: No tag library could be found with this URI. Possible causes 
could be that the URI is incorrect, or that there were errors during parsing of 
the .tld file.
<%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f" %>
^^
start.jsp:13:46: The deferred EL expression is not allowed since 
deferredSyntaxAllowedAsLiteral is false.

  ^^
start.jsp:13:46: The deferred EL expression is not allowed since 
deferredSyntaxAllowedAsLiteral is false.

  ^^

> Getting a blank page after migrating from JSF 1.0 to JSF 1.2 with 
> myfaces+tomahawk+tiles
> 
>
> Key: TOMAHAWK-1684
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1684
> Project: MyFaces Tomahawk
>  Issue Type: Bug
>  Components: Column
>Affects Versions: 1.1.14
> Environment: RHEL 7.3
>Reporter: Vemuri A Ramakrishna
>Priority: Blocker
>
> Upgraded the JSF 1.0 version to JSF 1.2. Using myfaces 1.2.9 (api+impl) , 
> tomahawk12(1.1.9) and richfaces(3.3.3) , jstl 1.2, jsf 1.2 tag lib for the 
> upgrade.
> Application gets deployed but tags are rendering blank,
> 2017-07-26 14:10:03,906 [ACTIVE] ExecuteThread: '5' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.ajax4jsf.cache.LRUMapCacheFactory - Creating LRUMap cache instance of 
> default capacity
> 2017-07-26 14:15:12,262 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' WARN  org.ajax4jsf.webapp.BaseFilter 
> - MyFaces Extensions Filter should be configured to execute *AFTER* RichFaces 
> filter. Refer to SRV.6.2.4 section of Servlets specification on how to 
> achieve that.
> 2017-07-26 14:15:12,368 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.RENDER_CLEAR_JAVASCRIPT_FOR_BUTTON' found, 
> using default value false
> 2017-07-26 14:15:12,368 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.SAVE_FORM_SUBMIT_LINK_IE' found, using default 
> value false
> 2017-07-26 14:15:12,368 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using 
> default value true
> 2017-07-26 14:15:12,369 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.RENDER_VIEWSTATE_ID' found, using default value 
> true
> 2017-07-26 14:15:12,369 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No

[jira] [Commented] (TOMAHAWK-1684) Getting a blank page after migrating from JSF 1.0 to JSF 1.2 with myfaces+tomahawk+tiles

2017-08-03 Thread Vemuri A Ramakrishna (JIRA)

[ 
https://issues.apache.org/jira/browse/TOMAHAWK-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112395#comment-16112395
 ] 

Vemuri A Ramakrishna commented on TOMAHAWK-1684:


Not sure why Tomahawk implementation is trying compile JSPs which were working 
in JSF 1.0

> Getting a blank page after migrating from JSF 1.0 to JSF 1.2 with 
> myfaces+tomahawk+tiles
> 
>
> Key: TOMAHAWK-1684
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1684
> Project: MyFaces Tomahawk
>  Issue Type: Bug
>  Components: Column
>Affects Versions: 1.1.14
> Environment: RHEL 7.3
>Reporter: Vemuri A Ramakrishna
>Priority: Blocker
>
> Upgraded the JSF 1.0 version to JSF 1.2. Using myfaces 1.2.9 (api+impl) , 
> tomahawk12(1.1.9) and richfaces(3.3.3) , jstl 1.2, jsf 1.2 tag lib for the 
> upgrade.
> Application gets deployed but tags are rendering blank,
> 2017-07-26 14:10:03,906 [ACTIVE] ExecuteThread: '5' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.ajax4jsf.cache.LRUMapCacheFactory - Creating LRUMap cache instance of 
> default capacity
> 2017-07-26 14:15:12,262 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' WARN  org.ajax4jsf.webapp.BaseFilter 
> - MyFaces Extensions Filter should be configured to execute *AFTER* RichFaces 
> filter. Refer to SRV.6.2.4 section of Servlets specification on how to 
> achieve that.
> 2017-07-26 14:15:12,368 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.RENDER_CLEAR_JAVASCRIPT_FOR_BUTTON' found, 
> using default value false
> 2017-07-26 14:15:12,368 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.SAVE_FORM_SUBMIT_LINK_IE' found, using default 
> value false
> 2017-07-26 14:15:12,368 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using 
> default value true
> 2017-07-26 14:15:12,369 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.RENDER_VIEWSTATE_ID' found, using default value 
> true
> 2017-07-26 14:15:12,369 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.STRICT_XHTML_LINKS' found, using default value 
> true
> 2017-07-26 14:15:12,369 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.CONFIG_REFRESH_PERIOD' found, using default 
> value 2
> 2017-07-26 14:15:12,369 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.VIEWSTATE_JAVASCRIPT' found, using default 
> value false
> 2017-07-26 14:15:12,369 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default 
> value /faces/myFacesExtensionResource
> 2017-07-26 14:15:12,369 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init 
> parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default 
> value true
> 2017-07-26 14:15:12,369 [ACTIVE] ExecuteThread: '6' for queue: 
> 'weblogic.kernel.Default (self-tuning)' INFO  
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - Starting up 
> Tomahawk on the MyFaces-JSF-Implementation
> Nothing happens after the last statement and the jsp page is blank



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)