What version of DOCX4j is suitable for JDK 1.4 based java compiler. I want to convert a docx file to html file using docx4j jar
Regards
Prasad
Woah! That knowledge is lost in the mists of time!
Have a look in http://www.docx4java.org/docx4j/archive/
Try say 2.5.0? Then go earlier or later from there. Of course, the deps need to be compatible with 1.4 as well. You can use JarCheck to check those.
You'll need to download/install the JAXB reference implementation (RI), and you'll need to ensure that that also, is compatible with 1.4. Iirc, there is a question somewhere here on SO as to what is the last version of the RI compatible with 1.5; not sure whether that version also works with 1.4.
Please let us know here what you find, either in a comment or an answer of your own.
Related
We have numerous developers and we all tend to have a slightly different version of the JDK (whatever was latest when we last updated). We're all 1.8, but the x in 1.8.x.x is all over the place.
Is there a way we can define the JDK to use in our project so it is defined in files that are not part of the project and therefore not checked in? And more importantly, are not overwriting our individual choices when pulling the latest?
Just name your project/module JDK 'JDK', everyone then can point it to wherever they want.
I'm sorry in advance if this question is not well expressed, I am trying to achieve something quite new to me and I am a little lost.
I am trying to include a Canon SDK inside an Objective-C wrapper, I understand from this paragraph that I needed to download the 64bit SDK:
There are a few steps that need to be taken in order to use EOSFramework in a project. First, ensure that you have downloaded the latest Canon EDSDK 64bit. EOSFramework currently relies on ARC which is only supported in 64bit. Therefore you must use the 64bit version of EDSDK. Also ensure that you have compiled or downloaded the latest version of EOSFramework as a .framework file.
Incidentally, after following instructions, the errors that I'm getting while building the frameworks are related to 64bit. Please see picture attached:
Can someone point out a way for me to figure this out?
I'm not sure if this won't bring a problem in the long run, but I found an answer in this post: _int64 does not name a type
Following this:
It looks like you you are trying to use MSVC specific __int64 type with GCC. That does not work, use long long instead.
Can someone point out a way for me to figure this out?
You need to track down the declaration of EdsUInt64 in the SDK you have downloaded and figure out why it is not being seen by the compiler when compiling the source you've shown.
Try right-clicking on EdsUInt32 (which the compiler was happy with) and jumping to its definition. Now look around, are the 64-bit types defined in the same place? Are they inside #if constructs? If so why are the conditions not true? Etc. Do some detective work.
You can also use TextWrangler/BBEdit, or other good editor, to do quick multi-file searches over all the SDK source to find the definitions.
If you don't find the definitions then you've got the wrong version of one of the SDKs, go back to Canon and get the right one.
The solution is very unlikely to be you needing to define the type yourself. The ARC comments in particular indicate you do have Mac specific source code, Canon compile it on a Mac, so it's unlikely to be a MS or Gnu specific issue failing on a Mac etc.
Good Hunting!
HTH
I need to upgrade from NHibernate 1.2.x to the latest version. Can someone help me out by either pointing me into the right direction, explain to me what I need to do, or just shoot me for using 1.2 when it's almost 2013.
Please.
Easy Answer: Have you tried just dropping in the latest version? 3.x should be somewhat compatible with what you have.
Hard Answer: Download Fluent NHibernate and get ready for some fun learning. It all depends on why you feel the need to upgrade.
The release notes in the download list know and possible breaking changes. It may be worth looking through. Other than that, I would suggest just dropping the new files in and see what happens.
I'm migrating the data layer of our application to NH version 2.1.0 (from 2.0.1) and noticed the use of LinFu. I discovered that framework and want to use it in other pieces of the application, especially I want to use the LinFu.Reflection.dll, which requires a reference to LinFu.DynamicProxy and here comes the trouble, the 1.0 final version of LinFu that I can find on google.code is not the same version used by NHibernate itself. Do I need to rebuild NHibernate.ByteCode.LinFu.dll changing the reference to the available version? If not, what else?
I have faced the same problem a few days ago. There's a tool named ILMERGE that merges .NET DLL-files, and that way you should be able to have several versions of the same DLL in your application.
Unfortunately I haven't tested the tool yet, I didn't get around to it, but I'll test in the next week.
But Rhino Mocks for example, has a binary with all dependencies included: http://ayende.com/projects/rhino-mocks/downloads.aspx, so it seems doable.
I have code from PowerBuilder 5 that can't be built. The compiler just stops before it is done without any error codes.
I would like to upgrade the code to the recent version of PowerBuilder but there are some intermediate versions of PowerBuilder that have binary dependencies to an old Microsoft java dll that Microsoft no longer can distribute due to some court case.
So, is there a way to get my code running in a newer environment?
/johan/
Firstly, you don't need to use "intermediate versions of PowerBuilder" to migrate up to a current version, so even if this java DLL dependency sounds questionable to me (at least it doesn't ring a bell), it's irrelevant unless it affects the target version of PowerBuilder.
For migrating, you might want to check out this migration guide, as well as a list of changes to PB that may affect you.
Very unusual sounding problem. You could give a try to migrating the code to a more recent version of PowerBuilder and see if it will compile or at least fail but give you some useful error messages.
I would also recommend posting this in the PowerBuilder section of the Sybase newsgroups. They are very active and full of some brilliant PB minds with lots of experience. You can find them here: http://forums.sybase.com
From here:http://forums.sybase.com/cgi-bin/webnews.cgi?cmd=item-4558&group=sybase.public.powersite
I just learned that the combination of "severe" message, and message
that psdwc70.dll was unable to self-register is probably because
msjava.dll is not present and/or registered on your machine. The
psdwc70.dll file relies on msjava.dll in order to install properly.
/johan/
Have you tried exporting the code in PB5 and importing in new version?