[xmlc] Re: can not generate any html page after deployed at tomcat 5

At 04:28 PM 6/26/2007, you wrote:
>Hi Jacob:
>
>Thanks for your advise. I have done what your
>suggestion: put following jar at WEB-INF/lib
>
>gnu-regexp.jar *
>nekohtml.jar *
>resolver.jar *
>xmlc-all-runtime.jar
>
>xercesImpl.jar
>xml-apis.jar
>
>removed the previous xercesImpl.jar at tomcat 5 and
>restart the server.

By "removed", do you mean "replaced"?  If not, you should be 
replacing the existing xercesImpl.jar and xml-apis.jar in 
CATALINA_HOME/common/endorsed with the ones that ship with 
XMLC.  These 2 jars should not go in WEB-INF/lib.

> I still get blank page and no html
>page is generated from xmlc, even though I can see
>static html page if I put one there.
>

Seems like you'd at least have some console output.  Is there a stack 
trace?  I'd be surprised if there wasn't.  Try putting Log4j.jar and 
common-logging.jar in CATALINA_HOME/common/lib and create a 
log4j.properties in CATALINA_HOME/common/classes that has a basic 
console appender.  Add the appender to the ROOT logger.  Try a level 
of WARN first.  If you don't see anything move back to INFO and DEBUG 
until you see the errors.  That would be very helpful.

>I converted all html pages into java class during
>compile time, packaged all java class and others into
>a war file and deployed the war file at tomcat/webapps
>

Standard procedure.

>You mentioned that "If you were using static parsing
>(the default) with XMLC 2.2.xx, then you have a few
>changes to make to your deployment step.)". would you
>please advise what changes I should make?
>

So, are you saying that you weren't using the "-for-deferred-parsing" 
flag when you were using XMLC-2.2.xx?  Please look at the Tomcat 
example app that is part of the XMLC source for a build example.  It 
does one thing that you probably won't do, and that is configure 
reparseResourceDirs.  You can probably ignore that.  It's more for 
speedy development, but could be confusing.  It allows you to store 
your markup and options.xmlc file in some directory on the file 
system.  When it changes, XMLC will automatically reload the 
change.  Nice feature, but don't worry about it until you've got it 
working with the markup and metadata files in the classpath alongside 
the compiled generated classes.

Basically, whatever package your compiled classes are in, copy the 
markup files to that package.  Also, either copy the options.xmlc 
file into the common base package of your compiled XMLC classes or 
use the -keep flag to keep the source and copy any generated *.xmlc 
files (next to the generated *HTML.java XMLC source files) into the 
corresponding package of your compiled generated classes and 
corresponding markup.   For instance, your package might look like this...

MyPage.html
MyPageHTML.class
MyPageHTML.xmlc
MyPageHTMLImpl.class

Now you can deploy and it should work.

Jake

>Thanks.
>
>-Steve
>
>
>
>______________________________________________________________________
>______________Ready for the edge of your seat?
>Check out tonight's top picks on Yahoo! TV.
>http://tv.yahoo.com/



--
You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx mailing list.
To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws