We ran into an issue when we changed the default dita.temp.dir property
(in conductor.xml) from the default "${basedir}${file.separator}temp" to
a directory on a mapped drive, and deleted the temp directory from the
DITA-OT1.1.2.1 directory tree.
FYI - the mapped drive is different for each user.
Everything was fine except that the "property.temp" file was still being
written to the 'default' DITA-OT/temp directory (and the temp directory
was being created), rather than to the directory on the mapped drive.
This created a problem from a permissions point of view in that a user
who couldn't write to the 'default' DITA-OT/temp directory couldn't run
any transforms - even though he had permission to the new temp directory
on the mapped drive, he had no write permissions to the 'default'
directory where DITA-OT was installed. He now has to have permission to
write here.
As a temporary fix, I make sure to delete the 'default' DITA-OT/temp
directory after every transform - but this still presents a problem
because different users could potentially overwrite (or delete) each
other's property.temp file because that file always get written to the
same place.
------------------------------------------
Jerry Kimmel - jkimmel at vasont dot com
Jerry,
If possible, can you have a try on the latest release of DITA-OT. I
tested on release 1.2 and believe that this bug is fixed on release
1.2 . Thanks.
Best Regards,
Stephen Zhang
--- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@...> wrote:
>
> We ran into an issue when we changed the default dita.temp.dir property
> (in conductor.xml) from the default "${basedir}${file.separator}temp" to
> a directory on a mapped drive, and deleted the temp directory from the
> DITA-OT1.1.2.1 directory tree.
>
> FYI - the mapped drive is different for each user.
>
> Everything was fine except that the "property.temp" file was still being
> written to the 'default' DITA-OT/temp directory (and the temp directory
> was being created), rather than to the directory on the mapped drive.
>
> This created a problem from a permissions point of view in that a user
> who couldn't write to the 'default' DITA-OT/temp directory couldn't run
> any transforms - even though he had permission to the new temp directory
> on the mapped drive, he had no write permissions to the 'default'
> directory where DITA-OT was installed. He now has to have permission to
> write here.
>
> As a temporary fix, I make sure to delete the 'default' DITA-OT/temp
> directory after every transform - but this still presents a problem
> because different users could potentially overwrite (or delete) each
> other's property.temp file because that file always get written to the
> same place.
>
> ------------------------------------------
> Jerry Kimmel - jkimmel at vasont dot com
>
Change the dita.temp.dir property in conductor_template.xml from the
default "${basedir}${file.separator}temp" to C:${file.separator}temp.
Delete the DITA-OT1.2\temp directory
Run an xhtml transform from the commandline.
As the transform is running, watch the DITA-OT1.2 directory – you
will see a temp directory be created.
Watch the c:\temp directory - you will see all of the other temp
files populate this temp directory.
After the transform is finished, open the DITA-OT1.2\temp directory –
the property.temp file will have been created here, rather than in the c:\temp
directory.
There is one difference between DITA-OT1.1.2.1 and DITA-OT1.2. For DITA-OT1.2
I must edit the conductor_template.xml, whereas in DITA-OT1.1.2.1 I edit conductor.xml.
The conductor.xml is rewritten each time a transform is run in DITA-OT1.2.
FYI – I was unable to actually complete a transform in DITA-OT1.2.
I added the DITA-OT1.2 dost.jar to my CLASSPATH, but did not install Sun JDK
1.5. (I get the “Unable to instantiate specified logger class
org.dita.dost.log.DITAOTBuildlogger” error.)
Will DITA-OT1.2 *only* run
in Sun JDK 1.5.x? If so, this needs to be spelled out more clearly in the
release notes.
Even though my transform failed, the DITA-OT1.2\temp directory is
created and populated with the new property.temp file in DITA-OT1.2.
------------------------------------------ Jerry Kimmel - jkimmel at vasont
dot com
-----Original Message----- From: dita-users@yahoogroups.com
[mailto:dita-users@yahoogroups.com] On Behalf
Of imagiczhang Sent:Thursday, March
16, 20068:40 PM To: dita-users@yahoogroups.com Subject: [dita-users] Re:
DITA-OT1.1.2.1 Temp directory problem
Jerry, If possible, can you have a try on the latest
release of DITA-OT. I tested on release 1.2 and believe that this bug is
fixed on release 1.2 . Thanks.
Best Regards, Stephen Zhang
--- In dita-users@yahoogroups.com, "Jerry
Kimmel" <jkimmel@...> wrote: > > We ran into an issue when we changed the
default dita.temp.dir property > (in conductor.xml) from the default
"${basedir}${file.separator}temp" to > a directory on a mapped drive, and deleted
the temp directory from the > DITA-OT1.1.2.1 directory tree. > > FYI - the mapped drive is different for each
user. > > Everything was fine except that the
"property.temp" file was still being > written to the 'default' DITA-OT/temp
directory (and the temp directory > was being created), rather than to the
directory on the mapped drive. > > This created a problem from a permissions
point of view in that a user > who couldn't write to the 'default'
DITA-OT/temp directory couldn't run > any transforms - even though he had
permission to the new temp directory > on the mapped drive, he had no write
permissions to the 'default' > directory where DITA-OT was installed. He now
has to have permission to > write here. > > As a temporary fix, I make sure to delete the
'default' DITA-OT/temp > directory after every transform - but this
still presents a problem > because different users could potentially
overwrite (or delete) each > other's property.temp file because that file
always get written to the > same place. > > ------------------------------------------ > Jerry Kimmel - jkimmel at vasont dot
com >
If I add the dita.temp.dir property to the ant script and
process a transform through ant, my temp files end up in c:\temp where I expect
them.
If I change the conductor_template.xml dita.temp.dir property to C:${file.separator}temp
and run a transform through ant, my temp files end up in the c:\temp directory where
I expect them.
I am still not able to run a transform through the java
command line with dita-ot1.2. I can’t get past the “Unable to instantiate
specified logger class org.dita.dost.log.DITAOTBuildlogger” even though all
of my install directories and environment variables match the 1.2 install docs.
------------------------------------------ Jerry Kimmel – jkimmel at vasont dot com
-----Original Message----- From: dita-users@yahoogroups.com
[mailto:dita-users@yahoogroups.com] On Behalf
Of Jerry Kimmel Sent:Friday, March
17, 20069:42 AM To: dita-users@yahoogroups.com Subject: RE: [dita-users] Re:
DITA-OT1.1.2.1 Temp directory problem
Stephen,
No, the same issue also exists in release 1.2.
Here is my test for DITA-OT1.2:
Change the dita.temp.dir property in
conductor_template.xml from the default
"${basedir}${file.separator}temp" to C:${file.separator}temp.
Delete the DITA-OT1.2\temp directory
Run an xhtml transform from the commandline.
As the transform is running, watch the DITA-OT1.2
directory – you will see a temp directory be created.
Watch the c:\temp directory - you will see all
of the other temp files populate this temp directory.
After the transform is finished, open the
DITA-OT1.2\temp directory – the property.temp file will have been created
here, rather than in the c:\temp directory.
There is one difference between DITA-OT1.1.2.1 and
DITA-OT1.2. For DITA-OT1.2 I must edit the conductor_template.xml, whereas in
DITA-OT1.1.2.1 I edit conductor.xml. The conductor.xml is rewritten each time a
transform is run in DITA-OT1.2.
FYI – I was unable to actually complete a
transform in DITA-OT1.2. I added the DITA-OT1.2 dost.jar to my CLASSPATH, but
did not install Sun JDK 1.5. (I get the “Unable to instantiate specified
logger class org.dita.dost.log.DITAOTBuildlogger” error.)
Will DITA-OT1.2 *only*
run in Sun JDK 1.5.x? If so, this needs to be spelled out more clearly in the
release notes.
Even though my transform failed, the DITA-OT1.2\temp
directory is created and populated with the new property.temp file in
DITA-OT1.2.
------------------------------------------ Jerry Kimmel - jkimmel at vasont dot com
-----Original Message----- From: dita-users@yahoogroups.com
[mailto:dita-users@yahoogroups.com] On Behalf
Of imagiczhang Sent: Thursday, March 16, 2006
8:40 PM To: dita-users@yahoogroups.com Subject: [dita-users] Re: DITA-OT1.1.2.1
Temp directory problem
Jerry, If possible, can you have a try on the latest
release of DITA-OT. I tested on release 1.2 and believe that this bug is
fixed on release 1.2 . Thanks.
Best Regards, Stephen Zhang
--- In dita-users@yahoogroups.com, "Jerry
Kimmel" <jkimmel@...> wrote: > > We ran into an issue when we changed the
default dita.temp.dir property > (in conductor.xml) from the default
"${basedir}${file.separator}temp" to > a directory on a mapped drive, and deleted
the temp directory from the > DITA-OT1.1.2.1 directory tree. > > FYI - the mapped drive is different for each
user. > > Everything was fine except that the
"property.temp" file was still being > written to the 'default' DITA-OT/temp
directory (and the temp directory > was being created), rather than to the
directory on the mapped drive. > > This created a problem from a permissions
point of view in that a user > who couldn't write to the 'default'
DITA-OT/temp directory couldn't run > any transforms - even though he had permission
to the new temp directory > on the mapped drive, he had no write
permissions to the 'default' > directory where DITA-OT was installed. He now
has to have permission to > write here. > > As a temporary fix, I make sure to delete the
'default' DITA-OT/temp > directory after every transform - but this
still presents a problem > because different users could potentially
overwrite (or delete) each > other's property.temp file because that file
always get written to the > same place. > > ------------------------------------------ > Jerry Kimmel - jkimmel at vasont dot
com >
To change the temp directory through Java command, you need to set the
"/tempdir" parameter in the Java command.
About the logger problem, it seems that the Logger class can't be
found, please ensure that you have put the "dost.jar" into the CLASSPATH.
Regards,
Charlie
--- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@...> wrote:
>
> Stephen,
>
>
>
> If I add the dita.temp.dir property to the ant script and process a
> transform through ant, my temp files end up in c:\temp where I expect
> them.
>
>
>
> If I change the conductor_template.xml dita.temp.dir property to
> C:${file.separator}temp and run a transform through ant, my temp files
> end up in the c:\temp directory where I expect them.
>
>
>
> I am still not able to run a transform through the java command line
> with dita-ot1.2. I can't get past the "Unable to instantiate specified
> logger class org.dita.dost.log.DITAOTBuildlogger" even though all of my
> install directories and environment variables match the 1.2 install
> docs.
>
> ------------------------------------------
> Jerry Kimmel - jkimmel at vasont dot com
>
>
>
> -----Original Message-----
> From: dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com] On
> Behalf Of Jerry Kimmel
> Sent: Friday, March 17, 2006 9:42 AM
> To: dita-users@yahoogroups.com
> Subject: RE: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
>
>
>
> Stephen,
>
>
>
> No, the same issue also exists in release 1.2.
>
>
>
> Here is my test for DITA-OT1.2:
>
> Change the dita.temp.dir property in conductor_template.xml from the
> default "${basedir}${file.separator}temp" to C:${file.separator}temp.
>
>
>
> Delete the DITA-OT1.2\temp directory
>
>
>
> Run an xhtml transform from the commandline.
>
>
>
> As the transform is running, watch the DITA-OT1.2 directory - you will
> see a temp directory be created.
>
> Watch the c:\temp directory - you will see all of the other temp files
> populate this temp directory.
>
> After the transform is finished, open the DITA-OT1.2\temp directory -
> the property.temp file will have been created here, rather than in the
> c:\temp directory.
>
>
>
> There is one difference between DITA-OT1.1.2.1 and DITA-OT1.2. For
> DITA-OT1.2 I must edit the conductor_template.xml, whereas in
> DITA-OT1.1.2.1 I edit conductor.xml. The conductor.xml is rewritten each
> time a transform is run in DITA-OT1.2.
>
>
>
> FYI - I was unable to actually complete a transform in DITA-OT1.2. I
> added the DITA-OT1.2 dost.jar to my CLASSPATH, but did not install Sun
> JDK 1.5. (I get the "Unable to instantiate specified logger class
> org.dita.dost.log.DITAOTBuildlogger" error.)
>
>
>
> Will DITA-OT1.2 *only* run in Sun JDK 1.5.x? If so, this needs to be
> spelled out more clearly in the release notes.
>
>
>
> Even though my transform failed, the DITA-OT1.2\temp directory is
> created and populated with the new property.temp file in DITA-OT1.2.
>
>
>
> ------------------------------------------
> Jerry Kimmel - jkimmel at vasont dot com
>
>
>
> -----Original Message-----
> From: dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com] On
> Behalf Of imagiczhang
> Sent: Thursday, March 16, 2006 8:40 PM
> To: dita-users@yahoogroups.com
> Subject: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
>
>
>
> Jerry,
> If possible, can you have a try on the latest release of DITA-OT. I
> tested on release 1.2 and believe that this bug is fixed on release
> 1.2 . Thanks.
>
> Best Regards,
> Stephen Zhang
>
> --- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@> wrote:
> >
> > We ran into an issue when we changed the default dita.temp.dir
> property
> > (in conductor.xml) from the default "${basedir}${file.separator}temp"
> to
> > a directory on a mapped drive, and deleted the temp directory from the
> > DITA-OT1.1.2.1 directory tree.
> >
> > FYI - the mapped drive is different for each user.
> >
> > Everything was fine except that the "property.temp" file was still
> being
> > written to the 'default' DITA-OT/temp directory (and the temp
> directory
> > was being created), rather than to the directory on the mapped drive.
> >
> > This created a problem from a permissions point of view in that a user
> > who couldn't write to the 'default' DITA-OT/temp directory couldn't
> run
> > any transforms - even though he had permission to the new temp
> directory
> > on the mapped drive, he had no write permissions to the 'default'
> > directory where DITA-OT was installed. He now has to have permission
> to
> > write here.
> >
> > As a temporary fix, I make sure to delete the 'default' DITA-OT/temp
> > directory after every transform - but this still presents a problem
> > because different users could potentially overwrite (or delete) each
> > other's property.temp file because that file always get written to the
> > same place.
> >
> > ------------------------------------------
> > Jerry Kimmel - jkimmel at vasont dot com
> >
>
>
>
>
>
>
>
>
> SPONSORED LINKS
>
>
> Xml
> <http://groups.yahoo.com/gads?t=ms&k=Xml&w1=Xml&w2=How+to+format+a+compu
> ter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=rKxkBU5
> ScMPkEPHYrV6GFw>
>
> How
> <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer+hard+drive
> &w1=Xml&w2=How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+
> a+computer&c=4&s=90&.sig=ouvDNimQP6RB9NVToWPLCg> to format a computer
> hard drive
>
> Dita
> <http://groups.yahoo.com/gads?t=ms&k=Dita&w1=Xml&w2=How+to+format+a+comp
> uter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=92Qlvf
> tI8r8oge18N2nzVQ>
>
>
> How
> <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer&w1=Xml&w2=
> How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+a+computer&
> c=4&s=90&.sig=isWfK4ikU4LVc8_98iRRWA> to format a computer
>
>
>
>
>
>
>
> _____
>
> YAHOO! GROUPS LINKS
>
>
>
> * Visit your group "dita-users
> <http://groups.yahoo.com/group/dita-users> " on the web.
>
>
> * To unsubscribe from this group, send an email to:
> dita-users-unsubscribe@yahoogroups.com
> <mailto:dita-users-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>
> * Your use of Yahoo! Groups is subject to the Yahoo!
> <http://docs.yahoo.com/info/terms/> Terms of Service.
>
>
>
> _____
>
Jerry,
I'm new to this group, having attended the User Group conference in
Raleigh this May 2006. I've downloaded the toolkit (1.2) and installed
the tools. I too am stuck at the "Unable to instantiate specified
logger class org.dita.dost.log.DITAOTBuildlogger". I've run it from
the command prompt with the following. "java -jar lib/dost.jar
/i:samples/sequence.ditamap /outdir:out /transtype:xhtml".
I haven't changed any of the provided XML files and am just working on
trying to understand the calls. Your message thread below implies that
I should be using the Java SDK 1.5. I've installed and am using
version j2sdk1.4.2_08 (installed at the C: root). So.....
1. What do you (or anyone in the DITA group)suggest for
troubleshooting this step?
2. Does anyone have any (good) experience using the SDK1.5 version?
3. I know I'm missing something but I don't know where to look next.
Thanks in advance for any and all help.
David Oliver
--- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@...> wrote:
>
> Stephen,
>
> If I add the dita.temp.dir property to the ant script and process a
> transform through ant, my temp files end up in c:\temp where I expect
> them.
> If I change the conductor_template.xml dita.temp.dir property to
> C:${file.separator}temp and run a transform through ant, my temp files
> end up in the c:\temp directory where I expect them.
> I am still not able to run a transform through the java command line
> with dita-ot1.2. I can't get past the "Unable to instantiate specified
> logger class org.dita.dost.log.DITAOTBuildlogger" even though all of my
> install directories and environment variables match the 1.2 install
> docs.
> ------------------------------------------
> Jerry Kimmel - jkimmel at vasont dot com
> -----Original Message-----
> From: dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com]
On Behalf Of Jerry Kimmel
> Sent: Friday, March 17, 2006 9:42 AM
> To: dita-users@yahoogroups.com
> Subject: RE: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
> Stephen,
> No, the same issue also exists in release 1.2.
> Here is my test for DITA-OT1.2:
>
> Change the dita.temp.dir property in conductor_template.xml from the
> default "${basedir}${file.separator}temp" to C:${file.separator}temp.
>
> Delete the DITA-OT1.2\temp directory
>
> Run an xhtml transform from the commandline.
>
> As the transform is running, watch the DITA-OT1.2 directory - you will
> see a temp directory be created.
>
> Watch the c:\temp directory - you will see all of the other temp files
> populate this temp directory.
>
> After the transform is finished, open the DITA-OT1.2\temp directory -
> the property.temp file will have been created here, rather than in the
> c:\temp directory.
>
> There is one difference between DITA-OT1.1.2.1 and DITA-OT1.2. For
> DITA-OT1.2 I must edit the conductor_template.xml, whereas in
> DITA-OT1.1.2.1 I edit conductor.xml. The conductor.xml is rewritten each
> time a transform is run in DITA-OT1.2.
>
> FYI - I was unable to actually complete a transform in DITA-OT1.2. I
> added the DITA-OT1.2 dost.jar to my CLASSPATH, but did not install Sun
> JDK 1.5. (I get the "Unable to instantiate specified logger class
> org.dita.dost.log.DITAOTBuildlogger" error.)
>
> Will DITA-OT1.2 *only* run in Sun JDK 1.5.x? If so, this needs to be
> spelled out more clearly in the release notes.
>
>
>
> Even though my transform failed, the DITA-OT1.2\temp directory is
> created and populated with the new property.temp file in DITA-OT1.2.
>
>
>
> ------------------------------------------
> Jerry Kimmel - jkimmel at vasont dot com
>
>
>
> -----Original Message-----
> From: dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com] On
> Behalf Of imagiczhang
> Sent: Thursday, March 16, 2006 8:40 PM
> To: dita-users@yahoogroups.com
> Subject: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
>
>
>
> Jerry,
> If possible, can you have a try on the latest release of DITA-OT. I
> tested on release 1.2 and believe that this bug is fixed on release
> 1.2 . Thanks.
>
> Best Regards,
> Stephen Zhang
>
> --- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@> wrote:
> >
> > We ran into an issue when we changed the default dita.temp.dir
> property
> > (in conductor.xml) from the default "${basedir}${file.separator}temp"
> to
> > a directory on a mapped drive, and deleted the temp directory from the
> > DITA-OT1.1.2.1 directory tree.
> >
> > FYI - the mapped drive is different for each user.
> >
> > Everything was fine except that the "property.temp" file was still
> being
> > written to the 'default' DITA-OT/temp directory (and the temp
> directory
> > was being created), rather than to the directory on the mapped drive.
> >
> > This created a problem from a permissions point of view in that a user
> > who couldn't write to the 'default' DITA-OT/temp directory couldn't
> run
> > any transforms - even though he had permission to the new temp
> directory
> > on the mapped drive, he had no write permissions to the 'default'
> > directory where DITA-OT was installed. He now has to have permission
> to
> > write here.
> >
> > As a temporary fix, I make sure to delete the 'default' DITA-OT/temp
> > directory after every transform - but this still presents a problem
> > because different users could potentially overwrite (or delete) each
> > other's property.temp file because that file always get written to the
> > same place.
> >
> > ------------------------------------------
> > Jerry Kimmel - jkimmel at vasont dot com
> >
>
>
>
>
>
>
>
>
> SPONSORED LINKS
>
>
> Xml
> <http://groups.yahoo.com/gads?t=ms&k=Xml&w1=Xml&w2=How+to+format+a+compu
> ter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=rKxkBU5
> ScMPkEPHYrV6GFw>
>
> How
> <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer+hard+drive
> &w1=Xml&w2=How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+
> a+computer&c=4&s=90&.sig=ouvDNimQP6RB9NVToWPLCg> to format a computer
> hard drive
>
> Dita
> <http://groups.yahoo.com/gads?t=ms&k=Dita&w1=Xml&w2=How+to+format+a+comp
> uter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=92Qlvf
> tI8r8oge18N2nzVQ>
>
>
> How
> <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer&w1=Xml&w2=
> How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+a+computer&
> c=4&s=90&.sig=isWfK4ikU4LVc8_98iRRWA> to format a computer
>
>
>
>
>
>
>
> _____
>
> YAHOO! GROUPS LINKS
>
>
>
> * Visit your group "dita-users
> <http://groups.yahoo.com/group/dita-users> " on the web.
>
>
> * To unsubscribe from this group, send an email to:
> dita-users-unsubscribe@yahoogroups.com
> <mailto:dita-users-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>
> * Your use of Yahoo! Groups is subject to the Yahoo!
> <http://docs.yahoo.com/info/terms/> Terms of Service.
>
>
>
> _____
>
David,
In order to fix the problem you have, you need to set that jar file
lib\dost.jar in DITA-OT directory into your CLASSPATH.
In windows, please use set CLASSPATH=<DIT-OT DIR>\lib\dost.jar
In linux, please use export CLASSPATH=<DIT-OT DIR>/lib/dost.jar
Best Regards,
Stephen
--- In dita-users@yahoogroups.com, "David" <davidlasvegasati@...> wrote:
>
> Jerry,
> I'm new to this group, having attended the User Group conference in
> Raleigh this May 2006. I've downloaded the toolkit (1.2) and installed
> the tools. I too am stuck at the "Unable to instantiate specified
> logger class org.dita.dost.log.DITAOTBuildlogger". I've run it from
> the command prompt with the following. "java -jar lib/dost.jar
> /i:samples/sequence.ditamap /outdir:out /transtype:xhtml".
> I haven't changed any of the provided XML files and am just working on
> trying to understand the calls. Your message thread below implies that
> I should be using the Java SDK 1.5. I've installed and am using
> version j2sdk1.4.2_08 (installed at the C: root). So.....
> 1. What do you (or anyone in the DITA group)suggest for
> troubleshooting this step?
> 2. Does anyone have any (good) experience using the SDK1.5 version?
> 3. I know I'm missing something but I don't know where to look next.
> Thanks in advance for any and all help.
> David Oliver
>
> --- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@> wrote:
> >
> > Stephen,
> >
> > If I add the dita.temp.dir property to the ant script and process a
> > transform through ant, my temp files end up in c:\temp where I expect
> > them.
> > If I change the conductor_template.xml dita.temp.dir property to
> > C:${file.separator}temp and run a transform through ant, my temp files
> > end up in the c:\temp directory where I expect them.
> > I am still not able to run a transform through the java command line
> > with dita-ot1.2. I can't get past the "Unable to instantiate specified
> > logger class org.dita.dost.log.DITAOTBuildlogger" even though all
of my
> > install directories and environment variables match the 1.2 install
> > docs.
> > ------------------------------------------
> > Jerry Kimmel - jkimmel at vasont dot com
> > -----Original Message-----
> > From: dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com]
> On Behalf Of Jerry Kimmel
> > Sent: Friday, March 17, 2006 9:42 AM
> > To: dita-users@yahoogroups.com
> > Subject: RE: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
> > Stephen,
> > No, the same issue also exists in release 1.2.
> > Here is my test for DITA-OT1.2:
> >
> > Change the dita.temp.dir property in conductor_template.xml from the
> > default "${basedir}${file.separator}temp" to C:${file.separator}temp.
> >
> > Delete the DITA-OT1.2\temp directory
> >
> > Run an xhtml transform from the commandline.
> >
> > As the transform is running, watch the DITA-OT1.2 directory - you will
> > see a temp directory be created.
> >
> > Watch the c:\temp directory - you will see all of the other temp
files
> > populate this temp directory.
> >
> > After the transform is finished, open the DITA-OT1.2\temp directory -
> > the property.temp file will have been created here, rather than in the
> > c:\temp directory.
> >
> > There is one difference between DITA-OT1.1.2.1 and DITA-OT1.2. For
> > DITA-OT1.2 I must edit the conductor_template.xml, whereas in
> > DITA-OT1.1.2.1 I edit conductor.xml. The conductor.xml is
rewritten each
> > time a transform is run in DITA-OT1.2.
> >
> > FYI - I was unable to actually complete a transform in DITA-OT1.2. I
> > added the DITA-OT1.2 dost.jar to my CLASSPATH, but did not install Sun
> > JDK 1.5. (I get the "Unable to instantiate specified logger class
> > org.dita.dost.log.DITAOTBuildlogger" error.)
> >
> > Will DITA-OT1.2 *only* run in Sun JDK 1.5.x? If so, this needs to be
> > spelled out more clearly in the release notes.
> >
> >
> >
> > Even though my transform failed, the DITA-OT1.2\temp directory is
> > created and populated with the new property.temp file in DITA-OT1.2.
> >
> >
> >
> > ------------------------------------------
> > Jerry Kimmel - jkimmel at vasont dot com
> >
> >
> >
> > -----Original Message-----
> > From: dita-users@yahoogroups.com
[mailto:dita-users@yahoogroups.com] On
> > Behalf Of imagiczhang
> > Sent: Thursday, March 16, 2006 8:40 PM
> > To: dita-users@yahoogroups.com
> > Subject: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
> >
> >
> >
> > Jerry,
> > If possible, can you have a try on the latest release of DITA-OT. I
> > tested on release 1.2 and believe that this bug is fixed on release
> > 1.2 . Thanks.
> >
> > Best Regards,
> > Stephen Zhang
> >
> > --- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@> wrote:
> > >
> > > We ran into an issue when we changed the default dita.temp.dir
> > property
> > > (in conductor.xml) from the default
"${basedir}${file.separator}temp"
> > to
> > > a directory on a mapped drive, and deleted the temp directory
from the
> > > DITA-OT1.1.2.1 directory tree.
> > >
> > > FYI - the mapped drive is different for each user.
> > >
> > > Everything was fine except that the "property.temp" file was still
> > being
> > > written to the 'default' DITA-OT/temp directory (and the temp
> > directory
> > > was being created), rather than to the directory on the mapped
drive.
> > >
> > > This created a problem from a permissions point of view in that
a user
> > > who couldn't write to the 'default' DITA-OT/temp directory couldn't
> > run
> > > any transforms - even though he had permission to the new temp
> > directory
> > > on the mapped drive, he had no write permissions to the 'default'
> > > directory where DITA-OT was installed. He now has to have permission
> > to
> > > write here.
> > >
> > > As a temporary fix, I make sure to delete the 'default' DITA-OT/temp
> > > directory after every transform - but this still presents a problem
> > > because different users could potentially overwrite (or delete) each
> > > other's property.temp file because that file always get written
to the
> > > same place.
> > >
> > > ------------------------------------------
> > > Jerry Kimmel - jkimmel at vasont dot com
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> > SPONSORED LINKS
> >
> >
> > Xml
> >
<http://groups.yahoo.com/gads?t=ms&k=Xml&w1=Xml&w2=How+to+format+a+compu
> >
ter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=rKxkBU5
> > ScMPkEPHYrV6GFw>
> >
> > How
> >
<http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer+hard+drive
> >
&w1=Xml&w2=How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+
> > a+computer&c=4&s=90&.sig=ouvDNimQP6RB9NVToWPLCg> to format a computer
> > hard drive
> >
> > Dita
> >
<http://groups.yahoo.com/gads?t=ms&k=Dita&w1=Xml&w2=How+to+format+a+comp
> >
uter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=92Qlvf
> > tI8r8oge18N2nzVQ>
> >
> >
> > How
> >
<http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer&w1=Xml&w2=
> >
How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+a+computer&
> > c=4&s=90&.sig=isWfK4ikU4LVc8_98iRRWA> to format a computer
> >
> >
> >
> >
> >
> >
> >
> > _____
> >
> > YAHOO! GROUPS LINKS
> >
> >
> >
> > * Visit your group "dita-users
> > <http://groups.yahoo.com/group/dita-users> " on the web.
> >
> >
> > * To unsubscribe from this group, send an email to:
> > dita-users-unsubscribe@yahoogroups.com
> > <mailto:dita-users-unsubscribe@yahoogroups.com?subject=Unsubscribe>
> >
> >
> > * Your use of Yahoo! Groups is subject to the Yahoo!
> > <http://docs.yahoo.com/info/terms/> Terms of Service.
> >
> >
> >
> > _____
> >
>
--- In dita-users@yahoogroups.com, "imagiczhang" <zhangyp@...> wrote:
>
> David,
> In order to fix the problem you have, you need to set that jar file
> lib\dost.jar in DITA-OT directory into your CLASSPATH.
> In windows, please use set CLASSPATH=<DIT-OT DIR>\lib\dost.jar
> In linux, please use export CLASSPATH=<DIT-OT DIR>/lib/dost.jar
>
> Best Regards,
> Stephen
>
> --- In dita-users@yahoogroups.com, "David" <davidlasvegasati@> wrote:
> >
> > Jerry,
> > I'm new to this group, having attended the User Group conference in
> > Raleigh this May 2006. I've downloaded the toolkit (1.2) and installed
> > the tools. I too am stuck at the "Unable to instantiate specified
> > logger class org.dita.dost.log.DITAOTBuildlogger". I've run it from
> > the command prompt with the following. "java -jar lib/dost.jar
> > /i:samples/sequence.ditamap /outdir:out /transtype:xhtml".
> > I haven't changed any of the provided XML files and am just working on
> > trying to understand the calls. Your message thread below implies that
> > I should be using the Java SDK 1.5. I've installed and am using
> > version j2sdk1.4.2_08 (installed at the C: root). So.....
> > 1. What do you (or anyone in the DITA group)suggest for
> > troubleshooting this step?
> > 2. Does anyone have any (good) experience using the SDK1.5 version?
> > 3. I know I'm missing something but I don't know where to look next.
> > Thanks in advance for any and all help.
> > David Oliver
> >
> > --- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@> wrote:
> > >
> > > Stephen,
> > >
> > > If I add the dita.temp.dir property to the ant script and process a
> > > transform through ant, my temp files end up in c:\temp where I
expect
> > > them.
> > > If I change the conductor_template.xml dita.temp.dir property to
> > > C:${file.separator}temp and run a transform through ant, my temp
files
> > > end up in the c:\temp directory where I expect them.
> > > I am still not able to run a transform through the java command line
> > > with dita-ot1.2. I can't get past the "Unable to instantiate
specified
> > > logger class org.dita.dost.log.DITAOTBuildlogger" even though all
> of my
> > > install directories and environment variables match the 1.2 install
> > > docs.
> > > ------------------------------------------
> > > Jerry Kimmel - jkimmel at vasont dot com
> > > -----Original Message-----
> > > From: dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com]
> > On Behalf Of Jerry Kimmel
> > > Sent: Friday, March 17, 2006 9:42 AM
> > > To: dita-users@yahoogroups.com
> > > Subject: RE: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
> > > Stephen,
> > > No, the same issue also exists in release 1.2.
> > > Here is my test for DITA-OT1.2:
> > >
> > > Change the dita.temp.dir property in conductor_template.xml from the
> > > default "${basedir}${file.separator}temp" to
C:${file.separator}temp.
> > >
> > > Delete the DITA-OT1.2\temp directory
> > >
> > > Run an xhtml transform from the commandline.
> > >
> > > As the transform is running, watch the DITA-OT1.2 directory -
you will
> > > see a temp directory be created.
> > >
> > > Watch the c:\temp directory - you will see all of the other temp
> files
> > > populate this temp directory.
> > >
> > > After the transform is finished, open the DITA-OT1.2\temp
directory -
> > > the property.temp file will have been created here, rather than
in the
> > > c:\temp directory.
> > >
> > > There is one difference between DITA-OT1.1.2.1 and DITA-OT1.2. For
> > > DITA-OT1.2 I must edit the conductor_template.xml, whereas in
> > > DITA-OT1.1.2.1 I edit conductor.xml. The conductor.xml is
> rewritten each
> > > time a transform is run in DITA-OT1.2.
> > >
> > > FYI - I was unable to actually complete a transform in DITA-OT1.2. I
> > > added the DITA-OT1.2 dost.jar to my CLASSPATH, but did not
install Sun
> > > JDK 1.5. (I get the "Unable to instantiate specified logger class
> > > org.dita.dost.log.DITAOTBuildlogger" error.)
> > >
> > > Will DITA-OT1.2 *only* run in Sun JDK 1.5.x? If so, this needs to be
> > > spelled out more clearly in the release notes.
> > >
> > >
> > >
> > > Even though my transform failed, the DITA-OT1.2\temp directory is
> > > created and populated with the new property.temp file in DITA-OT1.2.
> > >
> > >
> > >
> > > ------------------------------------------
> > > Jerry Kimmel - jkimmel at vasont dot com
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: dita-users@yahoogroups.com
> [mailto:dita-users@yahoogroups.com] On
> > > Behalf Of imagiczhang
> > > Sent: Thursday, March 16, 2006 8:40 PM
> > > To: dita-users@yahoogroups.com
> > > Subject: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
> > >
> > >
> > >
> > > Jerry,
> > > If possible, can you have a try on the latest release of DITA-OT. I
> > > tested on release 1.2 and believe that this bug is fixed on release
> > > 1.2 . Thanks.
> > >
> > > Best Regards,
> > > Stephen Zhang
> > >
> > > --- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@> wrote:
> > > >
> > > > We ran into an issue when we changed the default dita.temp.dir
> > > property
> > > > (in conductor.xml) from the default
> "${basedir}${file.separator}temp"
> > > to
> > > > a directory on a mapped drive, and deleted the temp directory
> from the
> > > > DITA-OT1.1.2.1 directory tree.
> > > >
> > > > FYI - the mapped drive is different for each user.
> > > >
> > > > Everything was fine except that the "property.temp" file was still
> > > being
> > > > written to the 'default' DITA-OT/temp directory (and the temp
> > > directory
> > > > was being created), rather than to the directory on the mapped
> drive.
> > > >
> > > > This created a problem from a permissions point of view in that
> a user
> > > > who couldn't write to the 'default' DITA-OT/temp directory
couldn't
> > > run
> > > > any transforms - even though he had permission to the new temp
> > > directory
> > > > on the mapped drive, he had no write permissions to the 'default'
> > > > directory where DITA-OT was installed. He now has to have
permission
> > > to
> > > > write here.
> > > >
> > > > As a temporary fix, I make sure to delete the 'default'
DITA-OT/temp
> > > > directory after every transform - but this still presents a
problem
> > > > because different users could potentially overwrite (or
delete) each
> > > > other's property.temp file because that file always get written
> to the
> > > > same place.
> > > >
> > > > ------------------------------------------
> > > > Jerry Kimmel - jkimmel at vasont dot com
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > SPONSORED LINKS
> > >
> > >
> > > Xml
> > >
> <http://groups.yahoo.com/gads?t=ms&k=Xml&w1=Xml&w2=How+to+format+a+compu
> > >
> ter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=rKxkBU5
> > > ScMPkEPHYrV6GFw>
> > >
> > > How
> > >
> <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer+hard+drive
> > >
> &w1=Xml&w2=How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+
> > > a+computer&c=4&s=90&.sig=ouvDNimQP6RB9NVToWPLCg> to format a
computer
> > > hard drive
> > >
> > > Dita
> > >
> <http://groups.yahoo.com/gads?t=ms&k=Dita&w1=Xml&w2=How+to+format+a+comp
> > >
> uter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=92Qlvf
> > > tI8r8oge18N2nzVQ>
> > >
> > >
> > > How
> > >
> <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer&w1=Xml&w2=
> > >
> How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+a+computer&
> > > c=4&s=90&.sig=isWfK4ikU4LVc8_98iRRWA> to format a computer
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > _____
> > >
> > > YAHOO! GROUPS LINKS
> > >
> > >
> > >
> > > * Visit your group "dita-users
> > > <http://groups.yahoo.com/group/dita-users> " on the web.
> > >
> > >
> > > * To unsubscribe from this group, send an email to:
> > > dita-users-unsubscribe@yahoogroups.com
> > > <mailto:dita-users-unsubscribe@yahoogroups.com?subject=Unsubscribe>
> > >
> > >
> > > * Your use of Yahoo! Groups is subject to the Yahoo!
> > > <http://docs.yahoo.com/info/terms/> Terms of Service.
> > >
> > >
> > >
> > > _____
> > >
> >
>
No, I have not had any luck running any
version of the DITA-OT with Java 1.5.
The Java 1.5 comment is in response to the
release notes (relnotes.txt) for DITA-OT1.2 where the following is found:
3. SF RFE 1331727 Toolkit need to run on
JDK 1.5.x(only support to run under Sun JDK 1.5 with saxon in normal case)
To me, this seems to say that this version
of the toolkit (DITA-OT1.2) will only run in Java 1.5, and not in 1.4.2_x.
In my experience, this is not the case. My
problem is that I cannot run any toolkit transformations from the Java
commandline for DITA-OT1.2
An Ant script transform runs just fine
under Java 1.4.2_xx with DITA-OT1.2
Have you had any luck?
Stephen,
I am still unable to run a transform from
the Java command line in DITA-OT1.2
My classpath currently reads: CLASSPATH=C:\DITA-OT1.2\lib\dost.jar
which seems to match your instruction just
fine: CLASSPATH=<DIT-OT
DIR>\lib\dost.jar
Even though I seem to have my environment set up correctly, and transforms run
correctly in Ant, I still get the:
"Unable to
instantiate specified logger class org.dita.dost.log.DITAOTBuildlogger" when
running from the Java commandline.
-------------------------------------------
Jerry Kimmel – jkimmel at
vasont dot com
From:
dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com] On Behalf Of imagiczhang Sent: Thursday, April 13, 2006
10:08 PM To: dita-users@yahoogroups.com Subject: [dita-users] Re: Unable
to instantiate specified logger class org.dita.dost.log.DITAOTBuildl
--- In dita-users@yahoogroups.com,
"imagiczhang" <zhangyp@...> wrote: > > David, > In order to fix the problem you have, you
need to set that jar file > lib\dost.jar in DITA-OT directory into your
CLASSPATH. > In windows, please use set
CLASSPATH=<DIT-OT DIR>\lib\dost.jar > In linux, please use export
CLASSPATH=<DIT-OT DIR>/lib/dost.jar > > Best Regards, > Stephen > > --- In dita-users@yahoogroups.com, "David"
<davidlasvegasati@> wrote: > > > > Jerry, > > I'm new to this group, having attended
the User Group conference in > > Raleigh
this May 2006. I've downloaded the toolkit (1.2) and installed > > the tools. I too am stuck at the
"Unable to instantiate specified > > logger class
org.dita.dost.log.DITAOTBuildlogger". I've run it from > > the command prompt with the following.
"java -jar lib/dost.jar > > /i:samples/sequence.ditamap /outdir:out
/transtype:xhtml". > > I haven't changed any of the provided XML
files and am just working on > > trying to understand the calls. Your
message thread below implies that > > I should be using the Java SDK 1.5. I've
installed and am using > > version j2sdk1.4.2_08 (installed at the
C: root). So..... > > 1. What do you (or anyone in the DITA
group)suggest for > > troubleshooting this step? > > 2. Does anyone have any (good)
experience using the SDK1.5 version? > > 3. I know I'm missing something but I
don't know where to look next. > > Thanks in advance for any and all help. > > David Oliver > > > > --- In dita-users@yahoogroups.com,
"Jerry Kimmel" <jkimmel@> wrote: > > > > > > Stephen, > > > > > > If I add the dita.temp.dir property
to the ant script and process a > > > transform through ant, my temp
files end up in c:\temp where I expect > > > them. > > > If I change the
conductor_template.xml dita.temp.dir property to > > > C:${file.separator}temp and run a
transform through ant, my temp files > > > end up in the c:\temp directory
where I expect them. > > > I am still not able to run a
transform through the java command line > > > with dita-ot1.2. I can't get past
the "Unable to instantiate specified > > > logger class
org.dita.dost.log.DITAOTBuildlogger" even though all > of my > > > install directories and environment
variables match the 1.2 install > > > docs. > > >
------------------------------------------ > > > Jerry Kimmel - jkimmel at
vasont dot com > > > -----Original Message----- > > > From: dita-users@yahoogroups.com
[mailto:dita-users@yahoogroups.com] > > On Behalf Of Jerry Kimmel > > > Sent: Friday, March 17, 2006 9:42
AM > > > To: dita-users@yahoogroups.com > > > Subject: RE: [dita-users] Re:
DITA-OT1.1.2.1 Temp directory problem > > > Stephen, > > > No, the same issue also exists in
release 1.2. > > > Here is my test for DITA-OT1.2: > > > > > > Change the dita.temp.dir property
in conductor_template.xml from the > > > default
"${basedir}${file.separator}temp" to C:${file.separator}temp. > > > > > > Delete the DITA-OT1.2\temp
directory > > > > > > Run an xhtml transform from the
commandline. > > > > > > As the transform is running, watch
the DITA-OT1.2 directory - you will > > > see a temp directory be created. > > > > > > Watch the c:\temp directory -
you will see all of the other temp > files > > > populate this temp directory. > > > > > > After the transform is finished,
open the DITA-OT1.2\temp directory - > > > the property.temp file will have
been created here, rather than in the > > > c:\temp directory. > > > > > > There is one difference between
DITA-OT1.1.2.1 and DITA-OT1.2. For > > > DITA-OT1.2 I must edit the
conductor_template.xml, whereas in > > > DITA-OT1.1.2.1 I edit
conductor.xml. The conductor.xml is > rewritten each > > > time a transform is run in DITA-OT1.2. > > > > > > FYI - I was unable to actually
complete a transform in DITA-OT1.2. I > > > added the DITA-OT1.2 dost.jar to my
CLASSPATH, but did not install Sun > > > JDK 1.5. (I get the "Unable to
instantiate specified logger class > > > org.dita.dost.log.DITAOTBuildlogger"
error.) > > > > > > Will DITA-OT1.2 *only* run in Sun
JDK 1.5.x? If so, this needs to be > > > spelled out more clearly in the
release notes. > > > > > > > > > > > > Even though my transform failed,
the DITA-OT1.2\temp directory is > > > created and populated with the new
property.temp file in DITA-OT1.2. > > > > > > > > > > > >
------------------------------------------ > > > Jerry Kimmel - jkimmel at
vasont dot com > > > > > > > > > > > > -----Original Message----- > > > From: dita-users@yahoogroups.com > [mailto:dita-users@yahoogroups.com] On > > > Behalf Of imagiczhang > > > Sent: Thursday, March 16, 2006 8:40
PM > > > To: dita-users@yahoogroups.com > > > Subject: [dita-users] Re:
DITA-OT1.1.2.1 Temp directory problem > > > > > > > > > > > > Jerry, > > > If possible, can you have a try on
the latest release of DITA-OT. I > > > tested on release 1.2 and believe
that this bug is fixed on release > > > 1.2 . Thanks. > > > > > > Best Regards, > > > Stephen Zhang > > > > > > --- In dita-users@yahoogroups.com,
"Jerry Kimmel" <jkimmel@> wrote: > > > > > > > > We ran into an issue when we
changed the default dita.temp.dir > > > property > > > > (in conductor.xml) from the
default > "${basedir}${file.separator}temp" > > > to > > > > a directory on a mapped drive,
and deleted the temp directory > from the > > > > DITA-OT1.1.2.1 directory tree. > > > > > > > > FYI - the mapped drive is
different for each user. > > > > > > > > Everything was fine except
that the "property.temp" file was still > > > being > > > > written to the 'default'
DITA-OT/temp directory (and the temp > > > directory > > > > was being created), rather
than to the directory on the mapped > drive. > > > > > > > > This created a problem from a
permissions point of view in that > a user > > > > who couldn't write to the
'default' DITA-OT/temp directory couldn't > > > run > > > > any transforms - even though
he had permission to the new temp > > > directory > > > > on the mapped drive, he had no
write permissions to the 'default' > > > > directory where DITA-OT was
installed. He now has to have permission > > > to > > > > write here. > > > > > > > > As a temporary fix, I make
sure to delete the 'default' DITA-OT/temp > > > > directory after every
transform - but this still presents a problem > > > > because different users could
potentially overwrite (or delete) each > > > > other's property.temp file
because that file always get written > to the > > > > same place. > > > > > > > >
------------------------------------------ > > > > Jerry Kimmel - jkimmel
at vasont dot com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > SPONSORED LINKS > > > > > > > > > Xml > > > > <http://groups.yahoo.com/gads?t=ms&k=Xml&w1=Xml&w2=How+to+format+a+compu > > > >
ter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=rKxkBU5 > > > ScMPkEPHYrV6GFw> > > > > > > How > > > > <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer+hard+drive > > > >
&w1=Xml&w2=How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+ > > >
a+computer&c=4&s=90&.sig=ouvDNimQP6RB9NVToWPLCg> to format
a computer > > > hard drive > > > > > > Dita > > > > <http://groups.yahoo.com/gads?t=ms&k=Dita&w1=Xml&w2=How+to+format+a+comp > > > >
uter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=92Qlvf > > > tI8r8oge18N2nzVQ> > > > > > > > > > How > > > > <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer&w1=Xml&w2= > > > >
How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+a+computer& > > >
c=4&s=90&.sig=isWfK4ikU4LVc8_98iRRWA> to format a computer > > > > > > > > > > > > > > > > > > > > > > > > _____ > > > > > > YAHOO! GROUPS LINKS > > > > > > > > > > > >
* Visit your group
"dita-users > > > <http://groups.yahoo.com/group/dita-users>
" on the web. > > > > > > > > >
* To unsubscribe from
this group, send an email to: > > >
dita-users-unsubscribe@yahoogroups.com > > >
<mailto:dita-users-unsubscribe@yahoogroups.com?subject=Unsubscribe> > > > > > > > > >
* Your use of Yahoo! Groups
is subject to the Yahoo! > > > <http://docs.yahoo.com/info/terms/>
Terms of Service. > > > > > > > > > > > > _____ > > > > > >
The toolkit continues to run fine on the long-tested Java 1.4.2 base. In
the full discussion for this bug (see the link), I see that the developers
discovered that Sun JDK 1.5 will not work with the default Xalan processor,
but will work with saxon 6.5.4 using either IBM SDK or Sun JDK 1.5. I'll
ask the tools team to update the Tested Platforms and Tools document
(http://dita-ot.sourceforge.net/doc/DITA-tested.html) with this latest
information.
Regards,
--
Don Day
Chair, OASIS DITA Technical Committee
IBM Lead DITA Architect
Email: dond@...
11501 Burnet Rd. MS9033E015, Austin TX 78758
Phone: +1 512-838-8550
T/L: 678-8550
"Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?"
--T.S. Eliot
"Jerry Kimmel"
<jkimmel@...
om> To
Sent by: <dita-users@yahoogroups.com>
dita-users@yahoog cc
roups.com
Subject
RE: [dita-users] Re: Unable to
04/21/2006 03:54 instantiate specified logger class
PM org.dita.dost.log.DITAOTBuildl
Please respond to
dita-users@yahoog
roups.com
David,
No, I have not had any luck running any version of the DITA-OT with Java
1.5.
The Java 1.5 comment is in response to the release notes (relnotes.txt) for
DITA-OT1.2 where the following is found:
3. SF RFE 1331727 Toolkit need to run on JDK 1.5.x(only support to run
under Sun JDK 1.5 with saxon in normal case)
To me, this seems to say that this version of the toolkit (DITA-OT1.2) will
only run in Java 1.5, and not in 1.4.2_x.
In my experience, this is not the case. My problem is that I cannot run any
toolkit transformations from the Java commandline for DITA-OT1.2
An Ant script transform runs just fine under Java 1.4.2_xx with DITA-OT1.2
Have you had any luck?
Stephen,
I am still unable to run a transform from the Java command line in
DITA-OT1.2
My classpath currently reads: CLASSPATH=C:\DITA-OT1.2\lib\dost.jar
which seems to match your instruction just fine: CLASSPATH=<DIT-OT
DIR>\lib\dost.jar
Even though I seem to have my environment set up correctly, and transforms
run correctly in Ant, I still get the:
"Unable to instantiate specified logger class
org.dita.dost.log.DITAOTBuildlogger" when running from the Java
commandline.
-------------------------------------------
Jerry Kimmel – jkimmel at vasont dot com
--- In dita-users@yahoogroups.com, "imagiczhang" <zhangyp@...> wrote:
>
> David,
> In order to fix the problem you have, you need to set that jar file
> lib\dost.jar in DITA-OT directory into your CLASSPATH.
> In windows, please use set CLASSPATH=<DIT-OT DIR>\lib\dost.jar
> In linux, please use export CLASSPATH=<DIT-OT DIR>/lib/dost.jar
>
> Best Regards,
> Stephen
>
> --- In dita-users@yahoogroups.com, "David" <davidlasvegasati@> wrote:
> >
> > Jerry,
> > I'm new to this group, having attended the User Group conference in
> > Raleigh this May 2006. I've downloaded the toolkit (1.2) and installed
> > the tools. I too am stuck at the "Unable to instantiate specified
> > logger class org.dita.dost.log.DITAOTBuildlogger". I've run it from
> > the command prompt with the following. "java -jar lib/dost.jar
> > /i:samples/sequence.ditamap /outdir:out /transtype:xhtml".
> > I haven't changed any of the provided XML files and am just working on
> > trying to understand the calls. Your message thread below implies that
> > I should be using the Java SDK 1.5. I've installed and am using
> > version j2sdk1.4.2_08 (installed at the C: root). So.....
> > 1. What do you (or anyone in the DITA group)suggest for
> > troubleshooting this step?
> > 2. Does anyone have any (good) experience using the SDK1.5 version?
> > 3. I know I'm missing something but I don't know where to look next.
> > Thanks in advance for any and all help.
> > David Oliver
> >
> > --- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@> wrote:
> > >
> > > Stephen,
> > >
> > > If I add the dita.temp.dir property to the ant script and process a
> > > transform through ant, my temp files end up in c:\temp where I
expect
> > > them.
> > > If I change the conductor_template.xml dita.temp.dir property to
> > > C:${file.separator}temp and run a transform through ant, my temp
files
> > > end up in the c:\temp directory where I expect them.
> > > I am still not able to run a transform through the java command line
> > > with dita-ot1.2. I can't get past the "Unable to instantiate
specified
> > > logger class org.dita.dost.log.DITAOTBuildlogger" even though all
> of my
> > > install directories and environment variables match the 1.2 install
> > > docs.
> > > ------------------------------------------
> > > Jerry Kimmel - jkimmel at vasont dot com
> > > -----Original Message-----
> > > From: dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com]
> > On Behalf Of Jerry Kimmel
> > > Sent: Friday, March 17, 2006 9:42 AM
> > > To: dita-users@yahoogroups.com
> > > Subject: RE: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
> > > Stephen,
> > > No, the same issue also exists in release 1.2.
> > > Here is my test for DITA-OT1.2:
> > >
> > > Change the dita.temp.dir property in conductor_template.xml from the
> > > default "${basedir}${file.separator}temp" to
C:${file.separator}temp.
> > >
> > > Delete the DITA-OT1.2\temp directory
> > >
> > > Run an xhtml transform from the commandline.
> > >
> > > As the transform is running, watch the DITA-OT1.2 directory -
you will
> > > see a temp directory be created.
> > >
> > > Watch the c:\temp directory - you will see all of the other temp
> files
> > > populate this temp directory.
> > >
> > > After the transform is finished, open the DITA-OT1.2\temp
directory -
> > > the property.temp file will have been created here, rather than
in the
> > > c:\temp directory.
> > >
> > > There is one difference between DITA-OT1.1.2.1 and DITA-OT1.2. For
> > > DITA-OT1.2 I must edit the conductor_template.xml, whereas in
> > > DITA-OT1.1.2.1 I edit conductor.xml. The conductor.xml is
> rewritten each
> > > time a transform is run in DITA-OT1.2.
> > >
> > > FYI - I was unable to actually complete a transform in DITA-OT1.2. I
> > > added the DITA-OT1.2 dost.jar to my CLASSPATH, but did not
install Sun
> > > JDK 1.5. (I get the "Unable to instantiate specified logger class
> > > org.dita.dost.log.DITAOTBuildlogger" error.)
> > >
> > > Will DITA-OT1.2 *only* run in Sun JDK 1.5.x? If so, this needs to be
> > > spelled out more clearly in the release notes.
> > >
> > >
> > >
> > > Even though my transform failed, the DITA-OT1.2\temp directory is
> > > created and populated with the new property.temp file in DITA-OT1.2.
> > >
> > >
> > >
> > > ------------------------------------------
> > > Jerry Kimmel - jkimmel at vasont dot com
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: dita-users@yahoogroups.com
> [mailto:dita-users@yahoogroups.com] On
> > > Behalf Of imagiczhang
> > > Sent: Thursday, March 16, 2006 8:40 PM
> > > To: dita-users@yahoogroups.com
> > > Subject: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
> > >
> > >
> > >
> > > Jerry,
> > > If possible, can you have a try on the latest release of DITA-OT. I
> > > tested on release 1.2 and believe that this bug is fixed on release
> > > 1.2 . Thanks.
> > >
> > > Best Regards,
> > > Stephen Zhang
> > >
> > > --- In dita-users@yahoogroups.com, "Jerry Kimmel" <jkimmel@> wrote:
> > > >
> > > > We ran into an issue when we changed the default dita.temp.dir
> > > property
> > > > (in conductor.xml) from the default
> "${basedir}${file.separator}temp"
> > > to
> > > > a directory on a mapped drive, and deleted the temp directory
> from the
> > > > DITA-OT1.1.2.1 directory tree.
> > > >
> > > > FYI - the mapped drive is different for each user.
> > > >
> > > > Everything was fine except that the "property.temp" file was still
> > > being
> > > > written to the 'default' DITA-OT/temp directory (and the temp
> > > directory
> > > > was being created), rather than to the directory on the mapped
> drive.
> > > >
> > > > This created a problem from a permissions point of view in that
> a user
> > > > who couldn't write to the 'default' DITA-OT/temp directory
couldn't
> > > run
> > > > any transforms - even though he had permission to the new temp
> > > directory
> > > > on the mapped drive, he had no write permissions to the 'default'
> > > > directory where DITA-OT was installed. He now has to have
permission
> > > to
> > > > write here.
> > > >
> > > > As a temporary fix, I make sure to delete the 'default'
DITA-OT/temp
> > > > directory after every transform - but this still presents a
problem
> > > > because different users could potentially overwrite (or
delete) each
> > > > other's property.temp file because that file always get written
> to the
> > > > same place.
> > > >
> > > > ------------------------------------------
> > > > Jerry Kimmel - jkimmel at vasont dot com
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > SPONSORED LINKS
> > >
> > >
> > > Xml
> > >
> <http://groups.yahoo.com/gads?t=ms&k=Xml&w1=Xml&w2=How+to+format+a+compu
> > >
> ter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=rKxkBU5
> > > ScMPkEPHYrV6GFw>
> > >
> > > How
> > >
> <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer+hard+drive
> > >
> &w1=Xml&w2=How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+
> > > a+computer&c=4&s=90&.sig=ouvDNimQP6RB9NVToWPLCg> to format a
computer
> > > hard drive
> > >
> > > Dita
> > >
> <http://groups.yahoo.com/gads?t=ms&k=Dita&w1=Xml&w2=How+to+format+a+comp
> > >
> uter+hard+drive&w3=Dita&w4=How+to+format+a+computer&c=4&s=90&.sig=92Qlvf
> > > tI8r8oge18N2nzVQ>
> > >
> > >
> > > How
> > >
> <http://groups.yahoo.com/gads?t=ms&k=How+to+format+a+computer&w1=Xml&w2=
> > >
> How+to+format+a+computer+hard+drive&w3=Dita&w4=How+to+format+a+computer&
> > > c=4&s=90&.sig=isWfK4ikU4LVc8_98iRRWA> to format a computer
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > _____
> > >
> > > YAHOO! GROUPS LINKS
> > >
> > >
> > >
> > > * Visit your group "dita-users
> > > <http://groups.yahoo.com/group/dita-users> " on the web.
> > >
> > >
> > > * To unsubscribe from this group, send an email to:
> > > dita-users-unsubscribe@yahoogroups.com
> > > <mailto:dita-users-unsubscribe@yahoogroups.com?subject=Unsubscribe>
> > >
> > >
> > > * Your use of Yahoo! Groups is subject to the Yahoo!
> > > <http://docs.yahoo.com/info/terms/> Terms of Service.
> > >
> > >
> > >
> > > _____
> > >
> >
>
Cool. That’s what I thought. It’s
the 3rd party tools that don’t play nice with Java 1.5 –
and I should have spelled that out more clearly in my last post.
I’ve all but given up on using Java 1.5
(despite Unicode support for surrogate code points) for the time being until the
entire suite of tools work correctly with Java 1.5.
Glad to see this disclaimer since I was still
up in the air on the issue.
-------------------------------------------
Jerry Kimmel – jkimmel at vasont dot com
From:
dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com] On Behalf Of Don Day Sent: Friday, April 21, 2006 5:52
PM To: dita-users@yahoogroups.com Subject: [dita] RE: [dita-users]
Re: Unable to instantiate specified logger class org.dita.dost.log.DITAOTBuildl
The toolkit continues to run fine on the long-tested Java 1.4.2 base. In
the full discussion for this bug (see the link), I see that the developers
discovered that Sun JDK 1.5 will not work with the default Xalan processor,
but will work with saxon 6.5.4 using either IBM SDK or Sun JDK 1.5. I'll
ask the tools team to update the Tested Platforms and Tools document
(http://dita-ot.sourceforge.net/doc/DITA-tested.html)
with this latest
information.
Regards,
--
Don Day
Chair, OASIS DITA Technical Committee
IBM Lead DITA Architect
Email: dond@... 11501 Burnet Rd.
MS9033E015, Austin TX 78758
Phone: +1 512-838-8550
T/L: 678-8550
"Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?"
--T.S. Eliot
"Jerry
Kimmel"
<jkimmel@...
om>
To
Sent
by:
<dita-users@yahoogroups.com>
dita-users@yahoog
cc
roups.com
Subject
RE: [dita-users] Re: Unable to
04/21/2006 03:54
instantiate specified logger class
PM
org.dita.dost.log.DITAOTBuildl
Please
respond
to
dita-users@yahoog
roups.com
David,
No, I have not had any luck running any version of the DITA-OT with Java
1.5.
The Java 1.5 comment is in response to the release notes (relnotes.txt) for
DITA-OT1.2 where the following is found:
3. SF RFE 1331727 Toolkit need to run on JDK 1.5.x(only support to run
under Sun JDK 1.5 with saxon in normal case)
To me, this seems to say that this version of the toolkit (DITA-OT1.2) will
only run in Java 1.5, and not in 1.4.2_x.
In my experience, this is not the case. My problem is that I cannot run any
toolkit transformations from the Java commandline for DITA-OT1.2
An Ant script transform runs just fine under Java 1.4.2_xx with DITA-OT1.2
Have you had any luck?
Stephen,
I am still unable to run a transform from the Java command line in
DITA-OT1.2
My classpath currently reads: CLASSPATH=C:\DITA-OT1.2\lib\dost.jar
which seems to match your instruction just fine: CLASSPATH=<DIT-OT
DIR>\lib\dost.jar
Even though I seem to have my environment set up correctly, and transforms
run correctly in Ant, I still get the:
"Unable to instantiate specified logger class
org.dita.dost.log.DITAOTBuildlogger" when running from the Java
commandline.
-------------------------------------------
Jerry Kimmel – jkimmel at vasont dot com
From: dita-users@yahoogroups.com [mailto:dita-users@yahoogroups.com] On
Behalf Of imagiczhang
Sent: Thursday, April 13, 2006 10:08 PM
To: dita-users@yahoogroups.com
Subject: [dita-users] Re: Unable to instantiate specified logger class
org.dita.dost.log.DITAOTBuildl
--- In dita-users@yahoogroups.com, "imagiczhang" <zhangyp@...>
wrote:
>
> David,
> In order to fix the problem you have, you need to set that jar file
> lib\dost.jar in DITA-OT directory into your CLASSPATH.
> In windows, please use set CLASSPATH=<DIT-OT DIR>\lib\dost.jar
> In linux, please use export CLASSPATH=<DIT-OT DIR>/lib/dost.jar
>
> Best Regards,
> Stephen
>
> --- In dita-users@yahoogroups.com, "David"
<davidlasvegasati@> wrote:
> >
> > Jerry,
> > I'm new to this group, having attended the User Group conference in
> > Raleigh
this May 2006. I've downloaded the toolkit (1.2) and installed
> > the tools. I too am stuck at the "Unable to instantiate
specified
> > logger class org.dita.dost.log.DITAOTBuildlogger". I've run it
from
> > the command prompt with the following. "java -jar lib/dost.jar
> > /i:samples/sequence.ditamap /outdir:out /transtype:xhtml".
> > I haven't changed any of the provided XML files and am just working
on
> > trying to understand the calls. Your message thread below implies
that
> > I should be using the Java SDK 1.5. I've installed and am using
> > version j2sdk1.4.2_08 (installed at the C: root). So.....
> > 1. What do you (or anyone in the DITA group)suggest for
> > troubleshooting this step?
> > 2. Does anyone have any (good) experience using the SDK1.5 version?
> > 3. I know I'm missing something but I don't know where to look next.
> > Thanks in advance for any and all help.
> > David Oliver
> >
> > --- In dita-users@yahoogroups.com, "Jerry Kimmel"
<jkimmel@> wrote:
> > >
> > > Stephen,
> > >
> > > If I add the dita.temp.dir property to the ant script and
process a
> > > transform through ant, my temp files end up in c:\temp where I
expect
> > > them.
> > > If I change the conductor_template.xml dita.temp.dir property to
> > > C:${file.separator}temp and run a transform through ant, my temp
files
> > > end up in the c:\temp directory where I expect them.
> > > I am still not able to run a transform through the java command
line
> > > with dita-ot1.2. I can't get past the "Unable to
instantiate
specified
> > > logger class org.dita.dost.log.DITAOTBuildlogger" even though
all
> of my
> > > install directories and environment variables match the 1.2
install
> > > docs.
> > > ------------------------------------------
> > > Jerry Kimmel - jkimmel at vasont dot com
> > > -----Original Message-----
> > > From: dita-users@yahoogroups.com
[mailto:dita-users@yahoogroups.com]
> > On Behalf Of Jerry Kimmel
> > > Sent: Friday, March 17, 2006 9:42 AM
> > > To: dita-users@yahoogroups.com
> > > Subject: RE: [dita-users] Re: DITA-OT1.1.2.1 Temp directory
problem
> > > Stephen,
> > > No, the same issue also exists in release 1.2.
> > > Here is my test for DITA-OT1.2:
> > >
> > > Change the dita.temp.dir property in conductor_template.xml from
the
> > > default "${basedir}${file.separator}temp" to
C:${file.separator}temp.
> > >
> > > Delete the DITA-OT1.2\temp directory
> > >
> > > Run an xhtml transform from the commandline.
> > >
> > > As the transform is running, watch the DITA-OT1.2 directory -
you will
> > > see a temp directory be created.
> > >
> > > Watch the c:\temp directory - you will see all of the
other temp
> files
> > > populate this temp directory.
> > >
> > > After the transform is finished, open the DITA-OT1.2\temp
directory -
> > > the property.temp file will have been created here, rather than
in the
> > > c:\temp directory.
> > >
> > > There is one difference between DITA-OT1.1.2.1 and DITA-OT1.2.
For
> > > DITA-OT1.2 I must edit the conductor_template.xml, whereas in
> > > DITA-OT1.1.2.1 I edit conductor.xml. The conductor.xml is
> rewritten each
> > > time a transform is run in DITA-OT1.2.
> > >
> > > FYI - I was unable to actually complete a transform in
DITA-OT1.2. I
> > > added the DITA-OT1.2 dost.jar to my CLASSPATH, but did not
install Sun
> > > JDK 1.5. (I get the "Unable to instantiate specified logger
class
> > > org.dita.dost.log.DITAOTBuildlogger" error.)
> > >
> > > Will DITA-OT1.2 *only* run in Sun JDK 1.5.x? If so, this needs
to be
> > > spelled out more clearly in the release notes.
> > >
> > >
> > >
> > > Even though my transform failed, the DITA-OT1.2\temp directory
is
> > > created and populated with the new property.temp file in
DITA-OT1.2.
> > >
> > >
> > >
> > > ------------------------------------------
> > > Jerry Kimmel - jkimmel at vasont dot com
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: dita-users@yahoogroups.com
> [mailto:dita-users@yahoogroups.com] On
> > > Behalf Of imagiczhang
> > > Sent: Thursday, March 16, 2006 8:40 PM
> > > To: dita-users@yahoogroups.com
> > > Subject: [dita-users] Re: DITA-OT1.1.2.1 Temp directory problem
> > >
> > >
> > >
> > > Jerry,
> > > If possible, can you have a try on the latest release of
DITA-OT. I
> > > tested on release 1.2 and believe that this bug is fixed on
release
> > > 1.2 . Thanks.
> > >
> > > Best Regards,
> > > Stephen Zhang
> > >
> > > --- In dita-users@yahoogroups.com, "Jerry Kimmel"
<jkimmel@> wrote:
> > > >
> > > > We ran into an issue when we changed the default
dita.temp.dir
> > > property
> > > > (in conductor.xml) from the default
> "${basedir}${file.separator}temp"
> > > to
> > > > a directory on a mapped drive, and deleted the temp
directory
> from the
> > > > DITA-OT1.1.2.1 directory tree.
> > > >
> > > > FYI - the mapped drive is different for each user.
> > > >
> > > > Everything was fine except that the "property.temp"
file was still
> > > being
> > > > written to the 'default' DITA-OT/temp directory (and the
temp
> > > directory
> > > > was being created), rather than to the directory on the
mapped
> drive.
> > > >
> > > > This created a problem from a permissions point of view in
that
> a user
> > > > who couldn't write to the 'default' DITA-OT/temp directory
couldn't
> > > run
> > > > any transforms - even though he had permission to the new
temp
> > > directory
> > > > on the mapped drive, he had no write permissions to the
'default'
> > > > directory where DITA-OT was installed. He now has to have
permission
> > > to
> > > > write here.
> > > >
> > > > As a temporary fix, I make sure to delete the 'default'
DITA-OT/temp
> > > > directory after every transform - but this still presents a
problem
> > > > because different users could potentially overwrite (or
delete) each
> > > > other's property.temp file because that file always get
written
> to the
> > > > same place.
> > > >
> > > > ------------------------------------------
> > > > Jerry Kimmel - jkimmel at vasont dot com