logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

Re: 0.9.7 and submission problems?: msg#00001

Subject: Re: 0.9.7 and submission problems?
Par for the course, I am responding to my own post . . .

Zach Roberts wrote:

Hello All,

I am looking at upgrading from 0.9.4 to 0.9.7, specifically to take advantage of all the great file upload capabilities that have been implemented. I have two questions that have come up:

    * From the looks of CVS, there may be another release coming very
      soon.  Is there an estimated time when 0.9.8 will be coming out?
    * If 0.9.8 is far away (more than two weeks), then I think I have
      an issue with the submission handlers.  It seems that even the
      most trivial of forms will not submit successfully using a plain
      0.9.7 install.  I have been working with just the hello.xhtml
      example, and cannot get it to submit successfully.  I am on
      Tomcat 4.1.30 with jdk 1.4.2_04, and I moved the dom3 stuff to
      common/endorsed as the instructions explained.  I noticed right
      away that the example xforms did not update their xml:base
      element to point to chiba-0.9.7, and also that the xslt files
      like html4.xsl were also not pointing at chiba-0.9.7 in their
      action url parameter.  After fixing these things, I still cannot
      get a successfull submission.  Which led me to a third issue:
    * How do you enable debugging / logging for chiba without
      modifying the entire tomcat log4j setup.  I did what I
      understand to be the correct thing and modified the
      /webapps/chiba-0.9.7/WEB-INF/log4j.xml to append where I
      wanted.  This had two effects, first it set the appender for the
      entire tomcat to wherever the root appender in this log4j config
      file points, and secondly it still did not pass the debug
      parameter to the html4.xsl.  Any pointers on how to best see
      what is going on under the hood of chiba?

Debugging is standard log4j stuff, and a little more research helped clear this up. The log4j.xml that comes with chiba only has a definition for the root logger. Tomcat uses the apache commons logging facility, and therefore any log4j configuration that modifies the root logger will modify it for the entire tomcat instance. To enable logging for just chiba, I introduced a new logger using the following snippet into my log4j.xml in chiba-0.9.7/WEB-INF/log4j.xml ABOVE the root configuration section:

   <logger name="org.chiba">
       <level value="DEBUG"/>
       <appender-ref ref="SHELL"/>
   </logger>

That gave me a nice stream of nothing but chiba debugging to my SHELL log appender, which is what I was looking for. I am now hopefully able to track down my submission errors, more on that later. I realize that this is probably all trivial stuff to most java developer folks, but just in case there are some other less experienced users out there I figured it was worth a post.
Zach




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl


<Prev in Thread] Current Thread [Next in Thread>