[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean

2017-07-28 Thread Dora Rajappan (JIRA) 

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

Dora Rajappan commented on MYFACES-4127:


If the  
FacesContext.getCurrentInstance().getApplication().getFlowHandler().getCurrentFlowScope()
 returns null for various reasons (includes invalid declarations such as 
postconstruct method in which case session will be null, or when its not inside 
a flow window will be null ); cdi throws the said exception. How to notify CDI 
whats the reason for the nulls will solve the problem. Need to throw 
appropriate exceptions from getCurrentFlowScope method so cdi can capture it 
show meaningful exception to the user.

> Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
> 
>
> Key: MYFACES-4127
> URL: https://issues.apache.org/jira/browse/MYFACES-4127
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
>Priority: Minor
> Attachments: ConfigItems.java
>
>
> When @FlowMap is injected on a RequestScoped bean, and you try to use that 
> object (which should be null since we are not inside of a flow), an 
> unexpected exception is thrown. This was noted after JIRA issue: 
> https://issues.apache.org/jira/browse/MYFACES-4126
> Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: 
> Cannot return null from a non-dependent producer method: Producer for 
> Producer Method [Map] with qualifiers [@FlowMap @Any] 
> declared as [[UnbackedAnnotatedMethod] @Produces @FlowMap @ApplicationScoped 
> public 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap()] 
> declared on Managed Bean [class 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer] with qualifiers 
> [@Any @Default]
>   at 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap(ApplicationScopeObjectProducer.java:73)
>   StackTrace:
>   at 
> org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:136)
>   at [internal classes]
>   at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
>   at 
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
>   at [internal classes]
>   at java.lang.String.valueOf(String.java:2994)
>   at java.lang.StringBuilder.append(StringBuilder.java:131)
>   at 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)
> On Mojarra 2.3, we get a different exception which looks more appropriate.
> org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active 
> contexts for scope type javax.faces.flow.FlowScoped
>   
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:623)
>   
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
>   
> org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
>   
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
>   
> org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
>   
> org.jboss.weld.util.Map$1302817811$Proxy$_$$_WeldClientProxy.toString(Unknown 
> Source)
>   java.lang.String.valueOf(String.java:2994)
>   java.lang.StringBuilder.append(StringBuilder.java:131)
>   
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)



--
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-07-28 Thread Mike Kienenberger (JIRA) 

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

Mike Kienenberger commented on TOMAHAWK-1684:
-

I think I had a legacy JSF 1.2 app running on Weblogic (probably 12c).

weblogic-application.xml is the only special configuration I see.

 
http://xmlns.oracle.com/weblogic/weblogic-application";>

   org.apache.*
javax.faces.*
javax.el.*
   com.sun.*
   com.bea.faces.*


   
   org.apache.*
   javax.faces.*
   javax.el.*
   com.sun.*
   com.bea.faces.*
 
META-INF/services/javax.servlet.ServletContainerInitializer
   


And it had a commit comment of "Ignore jsf libraries and el libraries and 
anything else we can think of which would be presupplied by weblogic 12c"

These were the jars at the time.

commons-el-1.0.jar
el-api.jar
el-ri.jar
jsf-facelets.jar
myfaces-api-1.1.10.jar
myfaces-impl-1.1.10.jar
tomahawk-1.1.6-SNAPSHOT.jar
tomahawk-sandbox-1.1.6-SNAPSHOT.jar

So I guess it was still JSF 1.1.   I know we went through the 1.0 to 1.2 to 2.1 
to 2.2 migration for another project, but I don't remember if we were on 
weblogic for the 1.0 to 1.2 migration, nor what version of weblogic it might 
have been.   

> 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 q

[jira] [Commented] (TOBAGO-1767) tc:date: days in the past should have an specific CSS class

2017-07-28 Thread Hudson (JIRA) 

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

Hudson commented on TOBAGO-1767:


SUCCESS: Integrated in Jenkins build Tobago Trunk #966 (See 
[https://builds.apache.org/job/Tobago%20Trunk/966/])
TOBAGO-1767 tc:date: days in the past should have an specific CSS class
* use '' (Year) instead of '' (Week year) (hnoeth: 
[http://svn.apache.org/viewvc/?view=rev&rev=1803267])
* (edit) 
tobago-trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/DateRenderer.java
TOBAGO-1767 tc:date: days in the past should have an specific CSS class
* get current date from server (hnoeth: 
[http://svn.apache.org/viewvc/?view=rev&rev=1803265])
* (edit) 
tobago-trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/DateRenderer.java
* (edit) 
tobago-trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/renderkit/html/DataAttributes.java
* (edit) 
tobago-trunk/tobago-example/tobago-example-demo/src/main/webapp/content/20-component/010-input/40-date/date.test.js
* (edit) 
tobago-trunk/tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/js/tobago-calendar.js


> tc:date: days in the past should have an specific CSS class
> ---
>
> Key: TOBAGO-1767
> URL: https://issues.apache.org/jira/browse/TOBAGO-1767
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Themes
>Affects Versions: 3.0.4
>Reporter: Henning Noeth
>Assignee: Henning Noeth
>Priority: Minor
>
> Add the css class 'past' to all days which are in the past.
> This provides an easy way to greyout the numbers of the past days with CSS.



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

Re: Migrate all MyFaces projects to Git

2017-07-28 Thread Dora Rajappan 
mojarra download url of github.com is also mirror and it actually goes to 
java.net 
domain.https://maven.java.net/content/repositories/releases/org/glassfish/javax.faces/2.3.2/


On Friday, July 28, 2017, 2:22:03 PM GMT+5:30, Dora Rajappan 
 wrote:

Hi ,
 Thanks for the information on Git hub for apache. I found mojarra latest 
downloads in github.com and understand the domain is a trusted site from this 
discussion. https://github.com/javaserverfaces/mojarra/releases/tag/2.3.2.    
Nice to know myfaces projects are going to apache git. I can find the myfaces 
mirrors already in github.com!
Thanks & Regards,Dora Rajappan,9986201824.


On Thursday, July 27, 2017, 9:03:55 PM GMT+5:30, Bernd Bohmann 
 wrote:

Hello Dora
this is not possible for apache projects
see: https://git-wip-us.apache.org

and
https://www.apache.org/dev/writable-git

but there are readonly mirrors at https://github.com/apache
Regards
Bernd
On Thu, Jul 27, 2017 at 4:10 PM, Dora Rajappan  wrote:

Is it github.com where you are going to migrate myfaces to?

On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann 
 wrote:

for Trinidad as well
On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil  wrote:

Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io  -
>     fresh Web Components info
>     +1 203-998-0403 
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg      > wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann           > :
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>          - fresh Web Components info
>         > +1 203-998-0403 
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>                  > wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         mailto:lu4...@gmail.com>> wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/ myfaces
>         
>         >
>         > It says:
>         >
>         > mirrored from git://git.apache.org/myfaces. git
>         
>         >
>         > But I have never checked where that file is or how to change it.
>         >
>         > Looking in deltaspike, the svn repo only has the site (for the
>     

Re: Migrate all MyFaces projects to Git

2017-07-28 Thread Dora Rajappan 
Hi ,
 Thanks for the information on Git hub for apache. I found mojarra latest 
downloads in github.com and understand the domain is a trusted site from this 
discussion. https://github.com/javaserverfaces/mojarra/releases/tag/2.3.2.    
Nice to know myfaces projects are going to apache git. I can find the myfaces 
mirrors already in github.com!
Thanks & Regards,Dora Rajappan,9986201824.


On Thursday, July 27, 2017, 9:03:55 PM GMT+5:30, Bernd Bohmann 
 wrote:

Hello Dora
this is not possible for apache projects
see: https://git-wip-us.apache.org

and
https://www.apache.org/dev/writable-git

but there are readonly mirrors at https://github.com/apache
Regards
Bernd
On Thu, Jul 27, 2017 at 4:10 PM, Dora Rajappan  wrote:

Is it github.com where you are going to migrate myfaces to?

On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann 
 wrote:

for Trinidad as well
On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil  wrote:

Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io  -
>     fresh Web Components info
>     +1 203-998-0403 
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg      > wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann           > :
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>          - fresh Web Components info
>         > +1 203-998-0403 
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>                  > wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         mailto:lu4...@gmail.com>> wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/ myfaces
>         
>         >
>         > It says:
>         >
>         > mirrored from git://git.apache.org/myfaces. git
>         
>         >
>         > But I have never checked where that file is or how to change it.
>         >
>         > Looking in deltaspike, the svn repo only has the site (for the
>         CMS) and the source code lives on git. If that so, we still need
>         the svn, so I agree it is a good idea to move only some
>         subprojects to git.
>         >
>         > regards,
>         >
>         > Leonardo Uribe
>         >
> 

[jira] [Resolved] (TOBAGO-1768) Append datepickermenu to tobago-page-menuStore

2017-07-28 Thread Henning Noeth (JIRA) 

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

Henning Noeth resolved TOBAGO-1768.
---
   Resolution: Fixed
Fix Version/s: 4.0.0

> Append datepickermenu to tobago-page-menuStore
> --
>
> Key: TOBAGO-1768
> URL: https://issues.apache.org/jira/browse/TOBAGO-1768
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Themes
>Affects Versions: 3.0.4
>Reporter: Henning Noeth
>Assignee: Henning Noeth
> Fix For: 4.0.0
>
>
> The datepicker menu is add to the body of a html document. It should be added 
> to the tobago-page-menuStore.



--
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-07-28 Thread Vemuri A Ramakrishna (JIRA) 

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

Vemuri A Ramakrishna commented on TOMAHAWK-1684:


Weblogic 12c supports JSF 1.2 and we can override weblogic to use JSF 1.2 
implementation in the weblogic.xml while deploying.

Also i find that we are including standard-faces-config.xml which is having 
errors and also web-facesconfig_1_2.xsd which is having errors in the 
myfaces-impl source code. I think this issue with xml not following the right 
xsd and structure has to be resolved.


> 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)