>> Just a quick recall of build of rpms.
>>
>> There are built under Redhat 6.2 / Redhat 7.1 (validation)
>>
>> - using latest jikes 1.14
>> - using latest IBM SDK 1.3 (javadoc)
>> - with latest ant 1.3, xerces-j 1.4, xalan-j 2.1.0
>>
>> I encounter rare problems when building with jikes,
>> at least one with a previous release of TC 4.0....
>>
>> Also my RPM, install the current jaxp.jar and parser.jar.
>> May be fine to switch now to jaxp/crimson or xerces-j ?
>>
>> I've asked sometimes ago on how to build a crimson RPM
>> (ie where to get the latest sources) but I still wait
>> for replies.....
>>
>
>Thanks for the reponse. I just installed the RPM, and saw that it
>*didn't* seem to exhibit the same problems on my machine as it did on
>the user's that report the problem. I may revisit. It was a
>very wierd
>problem - Velocity seemed to work fine when the user was loading
>templates from files using our 'FileResourceLoader', but when the user
>switch to loading templates from a jar placed in WEB-INF/lib using the
>'ClasspathResourceLoader', which just uses getResourceAsStream() it
>stopped working. And as I said, the user installed the tgz distro of
>3.2.2, moved his webapp over (not rebuild - move), and
>restarted tomcat,
>and it worked... I don't know if it was some kind of classpath issue.
The problem could come from a RPM upgrade :! For example the RPM NEVER
replace the conf files (confdir). Also the RPM know only about webapp
in .war. When first launch webapp are expanded and you could have previous
webapp allready presents !
>I have a few comments from the RPM :
>
>- would it be possible to add the basic startup/shutdown scripts in a
>bin/ under /var/tomcat ? The reason I ask is that it might be
>convenient for people to have available the same scripts uses by other
>tomcat users, so if someone provides instructions to do something, they
>can be followed exactly to the letter, which can be important
>for new or
>unconfident users.
In the FHS you shouldn't have executable under /var/xxx. That's why I
moved the tomcat.sh in /usr/bin. And there I just couldn't put the
startup.sh/shutdown.sh (too generic). But users could still does
tomcat start, tomcat stop, tomcat run.....
>- it automatically overrides things like JAVA_HOME with a new value. I
>know that it's noted on when the rpm is installed, but its a little
>presumptive.
yes, in /etc/rc.d/init.d/tomcat script, at init time you have NO information
on JAVA_HOME since you're not really a user. These kind of informations are
usually set in (.profile, .login). But if someone could send me a JAVA
configuration detection stuff, I'll set the init JAVA_HOME at INSTALL TIME
:=)
>Thanks for the reply.
>
>geir
>
>--
>Geir Magnusson Jr. [EMAIL PROTECTED]
>System and Software Consulting
>Developing for the web? See http://jakarta.apache.org/velocity/
>You have a genius for suggesting things I've come a cropper with!
>
