Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Won't Fix
    • Affects Version/s: 4.2.0.GA_CP09, 4.3.0.GA_CP08
    • Fix Version/s: 4.3.0.GA_CP09, 4.2.0.GA_CP10
    • Component/s: Seam
    • Labels:
    • Environment:
    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Use different cache (OSCache) by setting the following environment variable:
      org.ajax4jsf.cache.CacheFactory=org.ajax4jsf.cache.OSCacheCacheFactory

      Show
      Use different cache (OSCache) by setting the following environment variable: org.ajax4jsf.cache.CacheFactory=org.ajax4jsf.cache.OSCacheCacheFactory
    • Release Notes Text:
      Hide
      Java Server Faces applications that use ajax4jsf do not work with IBM JDK 1.6. The workaround for this issue is to use a different cache, such as OSCache, by setting the following environment variable:
      org.ajax4jsf.cache.CacheFactory=org.ajax4jsf.cache.OSCacheCacheFactory
      Alternatively, customers can turn off the cache by setting the following parameter in components.xml:
      enable-cache=false
      components.xml can be found in the following locations:
          * The WEB-INF directory of a WAR.
          * The META-INF directory of a JAR.
          * Any JAR directory containing classes with a @Name annotation.
      Show
      Java Server Faces applications that use ajax4jsf do not work with IBM JDK 1.6. The workaround for this issue is to use a different cache, such as OSCache, by setting the following environment variable: org.ajax4jsf.cache.CacheFactory=org.ajax4jsf.cache.OSCacheCacheFactory Alternatively, customers can turn off the cache by setting the following parameter in components.xml: enable-cache=false components.xml can be found in the following locations:     * The WEB-INF directory of a WAR.     * The META-INF directory of a JAR.     * Any JAR directory containing classes with a @Name annotation.
    • Release Notes Docs Status:
      Documented as Known Issue

      Description

      It is not possible to deploy booking example. Stacktrace from JBossAS console can be seen in the attached file.

      Several last lines of the output is here:
      2010-04-22 17:04:13,053 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] ConfigureListener.contextInitialized(/seam-booking)
      2010-04-22 17:04:13,054 DEBUG [org.jboss.web.tomcat.filters.ReplyHeaderFilter] Adding header name: X-Powered-By='Servlet 2.4; JBoss-4.2.0.GA_CP09 (build: SVNTag=JBPAPP_4_2_0_GA_CP09 date=201004202158)/JBossWeb-2.0'
      2010-04-22 17:04:13,057 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@24c824c8, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@40fd40fd

      { url=null ,addedOrder=0}

      2010-04-22 17:04:13,079 DEBUG [org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter] Init ajax4jsf filter with nane: ajax4jsf
      2010-04-22 17:04:13,079 DEBUG [org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter] Init parameters :

      2010-04-22 17:04:13,079 DEBUG [org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter] init XML filter service with class org.ajax4jsf.framework.ajax.xmlfilter.tidy.TidyXMLFilter
      2010-04-22 17:04:13,089 INFO [org.ajax4jsf.cache.CacheManager] Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  manaRH Marek Novotny
                  Reporter:
                  mgencur Martin Gencur
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: