If you're using Glassfish, you're using the JSF 1.2 RI. I recall that there were issues that were fixed in Tomahawk 1.1.5 in order to make it compatible with JSF 1.1 RI javascript. That would explain differences between 1.1.3 and 1.1.5 behavior.
Working with the examples is probably the best thing to verify behavior. Have you compared that behavior to the online examples at http://www.irian.at/home.jsf? You'll need to select Products -> Myfaces and try the two tomahawk example sets (one is the latest build -- not sure what the version number for the other one is). On 1/24/07, Dennis Gesker <[EMAIL PROTECTED]> wrote:
I moved the elements of my web.xml configuration around but no luck. Just for the heck of it I replaced tomahawk-1.1.3 with tomahawk-1.1.5-SNAPSHOT from today. t:dataTable/t:column in my application now works. t:collapsiblePanel still does not work. To try and rule out that something is strange in my web.xml I deployed the myfaces-example-simple-1.1.5-SNAPSHOT.war to glassfish. (I did not examine the web.xml in the example.war but figured it would be good.) The first t:collapsiblePanel on the collapsiblePanel page of the example war did not work and there were no errors in the logs. The others on the page did work. Is there something else I should be looking at? Dennis Mike Kienenberger wrote: > What is happening is that all of your filters are being ignored. Your > primary problem is that your web.xml elements are in the wrong order. > They must be llisted in this order. > > <context-param> > <filter> > <filter-mapping> > <listener> > <servlet> > <servlet-mapping> > > Your container should be generating warnings about this when your > application starts up. > > You can see the full details by clicking on the link for the dtd at > the top of your web.xml file: > > http://java.sun.com/dtd/web-app_2_3.dtd > > This is the specific definition of the top-level elements: > > <!ELEMENT web-app (icon?, display-name?, description?, distributable?, > context-param*, filter*, filter-mapping*, listener*, servlet*, > servlet-mapping*, session-config?, mime-mapping*, welcome-file-list?, > error-page*, taglib*, resource-env-ref*, resource-ref*, > security-constraint*, > login-config?, security-role*, env-entry*, ejb-ref*, ejb-local-ref*)> > > > On 1/24/07, Dennis Gesker <[EMAIL PROTECTED]> wrote: >> I suspect that it is a configuration issue. (tomahawk-1.1.3) I've >> started the server using 'asadmin start-domain --verbose' so I can watch >> the log output. My application deploys with no error messages. My page >> seems to render correctly i.e. the drop downs pull data from the >> database correctly and the proper information appears in my report. >> >> This page/report uses: >> >> t:collapsiblePanel to hide show report options >> t:dataTable / t:column so I can sort columns >> t:buffer for some excel exporting capabilites >> >> When I click on my t:collapsiblePanel I get no log errors the whole page >> looks as if its trying to reload (and appears to complete) but no >> content of the t:collapsiblePanel is displayed. No errors are displayed >> in the logs. >> >> When I click on my t:dataTable / t:column controls no sorting occurs and >> the browser (firefox) indicates "done." Again, no errors are displayed >> in the logs. >> >> >> >> My logging in glassfish for all items is set to INFO. >> >> The context param /servlet and filter config from my web.xml are as >> follows: >> >> <!-- Context Paramaters --> >> <context-param> >> <param-name>com.sun.faces.verifyObjects</param-name> >> <param-value>false</param-value> >> </context-param> >> <context-param> >> <param-name>com.sun.faces.validateXml</param-name> >> <param-value>true</param-value> >> </context-param> >> <context-param> >> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> >> <param-value>client</param-value> >> </context-param> >> >> <!-- Context Paramaters org.apache.myfaces --> >> <context-param> >> <param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name> >> <param-value>true</param-value> >> </context-param> >> <context-param> >> <param-name>org.apache.myfaces.DETECT_JAVASCRIPT</param-name> >> <param-value>false</param-value> >> </context-param> >> <context-param> >> <param-name>org.apache.myfaces.PRETTY_HTML</param-name> >> <param-value>true</param-value> >> </context-param> >> <context-param> >> <param-name>org.apache.myfaces.AUTO_SCROLL</param-name> >> <param-value>true</param-value> >> </context-param> >> <context-param> >> >> <param-name>org.apache.myfaces.CHECK_EXTENSIONS_FILTER</param-name> >> <param-value>true</param-value> >> </context-param> >> <context-param> >> <param-name>org.apache.myfaces.ADD_RESOURCE_CLASS</param-name> >> >> <param-value>org.apache.myfaces.renderkit.html.util.DefaultAddResource</param-value> >> >> </context-param> >> <context-param> >> >> <param-name>org.apache.myfaces.redirectTracker.POLICY</param-name> >> >> <param-value>org.apache.myfaces.redirectTracker.NoopRedirectTrackPolicy</param-value> >> >> </context-param> >> <context-param> >> >> <param-name>org.apache.myfaces.redirectTracker.MAX_REDIRECTS</param-name> >> >> <param-value>20</param-value> >> </context-param> >> <context-param> >> >> <param-name>org.apache.myfaces.COMPRESS_STATE_IN_SESSION</param-name> >> <param-value>false</param-value> >> </context-param> >> <context-param> >> >> <param-name>org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</param-name> >> <param-value>false</param-value> >> </context-param> >> >> >> <!-- Servlet --> >> <servlet> >> <servlet-name>Faces Servlet</servlet-name> >> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> >> <load-on-startup>1</load-on-startup> >> </servlet> >> >> <!-- Servlet Mapping --> >> <servlet-mapping> >> <servlet-name>Faces Servlet</servlet-name> >> <url-pattern>/faces/*</url-pattern> >> </servlet-mapping> >> <servlet-mapping> >> <servlet-name>Faces Servlet</servlet-name> >> <url-pattern>*.jsf</url-pattern> >> </servlet-mapping> >> >> >> <!-- Session Configuration --> >> <session-config> >> <session-timeout>120</session-timeout> >> </session-config> >> >> >> <!-- Welcome File List --> >> <welcome-file-list> >> <welcome-file>index.jsp</welcome-file> >> </welcome-file-list> >> >> >> <!-- Extensions Filter --> >> >> <filter> >> <filter-name>extensionsFilter</filter-name> >> <!-- >> <filter-class>org.apache.myfaces.component.html.util.ExtensionsFilter</filter-class> >> >> --> >> >> <filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class> >> >> <init-param> >> <param-name>uploadMaxFileSize</param-name> >> <param-value>10m</param-value> >> </init-param> >> <init-param> >> <param-name>uploadThresholdSize</param-name> >> <param-value>100k</param-value> >> </init-param> >> <init-param> >> <param-name>uploadRepositoryPath</param-name> >> <param-value>/tmp</param-value> >> </init-param> >> </filter> >> >> <!-- Extensions Filter Mapping--> >> <filter-mapping> >> <filter-name>extensionsFilter</filter-name> >> <url-pattern>/faces/*</url-pattern> >> </filter-mapping> >> <filter-mapping> >> <filter-name>extensionsFilter</filter-name> >> <url-pattern>*.jsf</url-pattern> >> </filter-mapping> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Romanowski, Tim wrote: >> > I'm using Tomahawk components on Glassfish V2, along with Facelets, >> Ajax4JSF >> > and the SUN RI (is MyFaces core even an option on Glassfish?). Any >> problems >> > I've had have not been due to the app server. There were no tricks >> to get >> > it to work. >> > >> > What Tomahawk components are causing problems? What other >> libraries are you >> > using? If you were implying that all your components are failing, >> perhaps >> > there were some special configuration options you needed to set for >> JBoss >> > that must now be disabled? >> > >> > Tim >> > >> > -----Original Message----- >> > From: Dennis Gesker [mailto:[EMAIL PROTECTED] >> > Sent: Tuesday, January 23, 2007 7:55 PM >> > To: MyFaces Discussion >> > Subject: Tomahawk on Glassfish-v2 >> > >> > Can Tomahawk be used on Glassfish-v2? If it can are there any >> tricks to >> > get it working? >> > >> > I'm trying to port a small application that works fine under JBoss >> > 4.0.4 but seem to be having some difficulty getting the tomahawk parts >> > of the same application working under Glassfish-v2. >> > >> > Dennis >> > >>
