«

Would it be fair to say that it is javac?

Wisgary wrote:
> Would it be fair to say that it is javac?

Absolutely.

jikes is a niche.

The IBM, BEA and Oracle ones are mostly used for big
production boxes not so much for development.

Arne

For IBM's JDK, the compiler also called javac, just another
implementation. But if you are dealing with some IBM's products such
as Websphere or something, you must have the IBM's JDK(in some cases,
there is a special edition for Websphere) as your development base, as
there're some differences between IBM's and Sun's


On Mar 13, 8:46 am, Arne Vajhøj <a...@vajhoej.dk> wrote:
> Wisgary wrote:
> > Would it be fair to say that it is javac?
>
> Absolutely.
>
> jikes is a niche.
>
> The IBM, BEA and Oracle ones are mostly used for big
> production boxes not so much for development.
>
> Arne

Alan Cui wrote:
> For IBM's JDK, the compiler also called javac, just another
> implementation. But if you are dealing with some IBM's products such
> as Websphere or something, you must have the IBM's JDK(in some cases,
> there is a special edition for Websphere) as your development base, as
> there're some differences between IBM's and Sun's

WAS requires IBM JDK to run.

But the code you write should hopefully compile
fine with a SUN javac.

Arne

"Arne Vajhøj" <> wrote:
>
> WAS requires IBM JDK to run.
>
> But the code you write should hopefully compile
> fine with a SUN javac.
>

That's kind of creepy: WAS is only source-compatible, not
bytecode-compatible?

-- Adam Maass

Adam Maass wrote:
> "Arne Vajhøj" <> wrote:
>> WAS requires IBM JDK to run.
>>
>> But the code you write should hopefully compile
>> fine with a SUN javac.
>
> That's kind of creepy: WAS is only source-compatible, not
> bytecode-compatible?

The IBM JVM is fully byte compatible.

It is a either a library issue or a support issue.

Arne

Not exactly, it depends on which version of Sun JVM you used to
compile. IBM's WAS JDK only compatible with Sun JDK 1.4x. But in this
version also some constant are not exactly same with sun's. I can't
remember which constants, something relative to jar package schema.


On Mar 13, 6:15 pm, Arne Vajhøj <a...@vajhoej.dk> wrote:
> Adam Maass wrote:



> > "Arne Vajhøj" <a...@vajhoej.dk> wrote:
> >> WAS requires IBM JDK to run.
>
> >> But the code you write should hopefully compile
> >> fine with a SUN javac.
>
> > That's kind of creepy: WAS is only source-compatible, not
> > bytecode-compatible?
>
> The IBM JVM is fully byte compatible.
>
> It is a either a library issue or a support issue.
>
> Arne

Alan Cui wrote:
> Not exactly, it depends on which version of Sun JVM you used to
> compile. IBM's WAS JDK only compatible with Sun JDK 1.4x. But in this
> version also some constant are not exactly same with sun's. I can't
> remember which constants, something relative to jar package schema.

I find it very questionable whether any IBM Java is only compatible
with SUN Java 1.4.x.

IBM Java is certified as being J2SE compliant, so if a *documented*
features does not work, then you should ask IBM to fix it.

If it is *undocumented*, then ...

Arne

On Mar 13, 1:01 pm, Arne Vajhøj <a...@vajhoej.dk> wrote:
> Alan Cui wrote:
> > For IBM's JDK, the compiler also called javac, just another
> > implementation. But if you are dealing with some IBM's products such
> > as Websphere or something, you must have the IBM's JDK(in some cases,
> > there is a special edition for Websphere) as your development base, as
> > there're some differences between IBM's and Sun's
>
> WAS requires IBM JDK to run.
>
> But the code you write should hopefully compile
> fine with a SUN javac.
>
> Arne


I was under the impression that WAS uses the IBM JDK on some platforms
and not on others. I think on Solaris WAS uses the SUN JDK.


http://frustrationsofaprogrammer.blogspot.com/

wrote:
> On Mar 13, 1:01 pm, Arne Vajhøj <a...@vajhoej.dk> wrote:
>> Alan Cui wrote:
>>> For IBM's JDK, the compiler also called javac, just another
>>> implementation. But if you are dealing with some IBM's products such
>>> as Websphere or something, you must have the IBM's JDK(in some cases,
>>> there is a special edition for Websphere) as your development base, as
>>> there're some differences between IBM's and Sun's
>> WAS requires IBM JDK to run.
>>
>> But the code you write should hopefully compile
>> fine with a SUN javac.
>
> I was under the impression that WAS uses the IBM JDK on some platforms
> and not on others. I think on Solaris WAS uses the SUN JDK.

Sounds likely since I don't think that IBM JDK exist for Solaris.

Arne