Best way to build

Hello everyone,

I build my WM5/WEME 6.1 application using jdk 1.4 and it works very well. I 
had an issue the other day though where I wrote some code only to find out 
at runtime that I had utilized an unsupported class (can't remember what it 
was). Not the end of the world, I went back and made a substitution and the 
world was right again.

My question is: is there a way to detect unsupported classes/methods before 
runtime, ie at compile time?

Back in the WEME 5.7 days, there was a j9c that was very helpful but it 
looks like using the standard jdk is the way to go these days.

Thanks for any help,
Phil 

On 01/03/2008 08:59:32 AM "Phil"wrote:

>I build my WM5/WEME 6.1 application using jdk 1.4 and it works very well. 
I
>had an issue the other day though where I wrote some code only to find 
out
>at runtime that I had utilized an unsupported class (can't remember what 
it
>was). Not the end of the world, I went back and made a substitution and 
the
>world was right again.
>
>My question is: is there a way to detect unsupported classes/methods 
before
>runtime, ie at compile time?

I do two things: 

1) I develop on Windows XP and test on the same version (2.3) of J9, as 
I'm using on WM5.

2) I refer to the following:

http://java.sun.com/products/cdc/reference/cdc_packages.pdf

So it looks like there is no way to flag those errors at compile time? 
Shame.

But yes, I have that chart handy all the time. I can't remember what class 
it was but the class in question was missing some methods. So that chart 
didn't help too much. Like I said, it's not the end of the world because the 
issues do get caught at runtime but it would be nicer to get them at compile 
time. Ah well.

Thanks for the help!

Phil

<JRancier@penntraffic.com> wrote in message 
news:fllne3$1i43u$1@news.boulder.ibm.com...
> On 01/03/2008 08:59:32 AM "Phil"wrote:
>
>>I build my WM5/WEME 6.1 application using jdk 1.4 and it works very
well.
> I
>>had an issue the other day though where I wrote some code only to find
> out
>>at runtime that I had utilized an unsupported class (can't remember
what
> it
>>was). Not the end of the world, I went back and made a substitution and
> the
>>world was right again.
>>
>>My question is: is there a way to detect unsupported classes/methods
> before
>>runtime, ie at compile time?
>
> I do two things:
>
> 1) I develop on Windows XP and test on the same version (2.3) of J9, as
> I'm using on WM5.
>
> 2) I refer to the following:
>
> http://java.sun.com/products/cdc/reference/cdc_packages.pdf
> 

Why don't you use the bootclasspath option of JDK javac?

If you are compiling for WEME CDC/FP 1.0, type like this:

> javac -source 1.3 -target 1.3
  -bootclasspath /path-to-weme/lib/jclFoundation10/classes.zip [your .java
files]

This should detect J2SE-only features used in your code.

If you are building for CDC/FP 1.1, use "-source 1.4 -target 1.4"
instead,
and point to the jclFoundation11/classes.zip.
If you are building for PPro, add the WEME PPro class library to the
bootclasspath option.

Hope this helps.

Hi Konno,

Thank you for the information, it sounds very promising! I will give it a 
try when I have some time.

Phil

"KONNO Kazuhiro" <no_spam@127.0.0.1> wrote in message 
news:fluo6e$1n82g$1@news.boulder.ibm.com...
> Why don't you use the bootclasspath option of JDK javac?
>
> If you are compiling for WEME CDC/FP 1.0, type like this:
>
>> javac -source 1.3 -target 1.3
>  -bootclasspath /path-to-weme/lib/jclFoundation10/classes.zip [your .java 
> files]
>
> This should detect J2SE-only features used in your code.
>
> If you are building for CDC/FP 1.1, use "-source 1.4 -target 1.4"
instead,
> and point to the jclFoundation11/classes.zip.
> If you are building for PPro, add the WEME PPro class library to the
> bootclasspath option.
>
> Hope this helps.
>
> KONNO Kazuhiro