I had the same Xalan problem after upgrading to JRE 5.0.  Here is my workaround:
1. Download the latest xalan.jar (http://www.apache.org/dyn/closer.cgi/xml/xalan-j  
choose a mirror and then download xalan-j-current-bin.zip)
2. Extract xalan.jar (in the bin folder)
3. Copy xalan.jar to %catalina_home%\webapps\sourcejammer\WEB-INF\lib
4. Restart Tomcat

I'm not really up on XML parsing so I'm not sure if this is the "correct" way to fix 
the issue, but it seems to have worked for me.

As for the sourcejammer.exe not running, I think if you edit the 
sourcejammer.properties file and change the JRE Version to 1.5 it should run.

Chris

"Sellers, Duane O" wrote:

> Hi,
>
> Forgive me if this is the wrong point of contact but I am trying to submit a 
> question to the Sourcejammer user list.  I have recently installed SourceJammer 
> Client and Server 2.1.0.0 on Win2000 with:
>
>         TomCat 5.0.28
>         JDK5.0 and JRE5.0
>
> Java_Home points to the JDK5.0 installation.
> The JDK bin directory is in the path.
> Browsing: http://myserver/sourcejammer/ provides the expected web interface however 
> of course at this point there are not archives to browse.
>
> Likewise browsing: http://myserver/sourcejammer/soap/admin provides the expected 
> little XML-Soap Admin utility.
>
> I observe two unfortunate behaviors however:
>
>         1, When I run the SJ_GUI.bat file the client
>            executes without error.  However when I
>            attempt to create the first archive I
>            receive the error:
>
>            SourceJammer is having trouble communicating with the
>            server.  A fault was generated:
>                 Fault Code = SOAP-ENV:Server
>                 Fault String = Exception from service object: Provider
>                 org.apache.xalan.processor.TransformerFactoryImpl not found
>
>         2, When I run the Sourcejammer.exe client utility
>            it reports that the JRE is not installed however
>            the JRE is in fact installed.
>            If I use the SJ_GUI.bat file it appears to function
>            properly.
>
> I think the second behavior is unrelated to the first but is more likely the result 
> of something wrong in my classpath settings ... Although running sourcejammer.exe 
> worked fine when using J2SDK1.4.2.
>
> Any help on these issues would be appreciated.
>
> Thanks,
>         Duane
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> SourceJammer-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/sourcejammer-users



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
SourceJammer-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sourcejammer-users

Reply via email to