
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Windows XP, 2GB RAM.
|
|
| Build: |
7,941
|
| Severity: |
Extreme
|
Blu-ray Disc Java development requires a development environment based upon the following APIs:
- Source code for the Personal Basis Profile 1.0 and JSSE for CDC 1.0.
Sun is preparing a download of these components (which will also
include Java TV), but this probably won't be ready before October 2008.
In the meantime, you can get a copy of "fake" stubs that contain the
correct API signatures, but that have had the API element descriptions
replaced with a disclaimer. This can be downloaded from
http://hdcookbook.com/bdj_platform/fake_stubs_pbp_jsse.zip .
Development in BD-J is similar to development in J2ME, however it has a different subset of APIs. Ideally, a custom JDK configuration could be created to allow the user to specify a JDK built upon this API, using the compiler from any 1.3+ JDK.
The problem with the current approach (attaching JDK 1.3 and the above libraries) is that the user sees two versions of every Personal Basis Profile class (one from PBP and one from JDK). Also, the JavaDocs come from the JDK. Thus, it is hard to tell if the incorrect APIs are being coded against until the project is compiled with Ant.
I have attempted to create a hybrid JDK 1.3 install with the rt.jar replaced with the BD-J stubs, however this results in IDEA reporting a corrupt JDK. Also, the project will not compile. The better approach would probably involve using a J2ME wireless SDK as the basis, but I don't have a lot of hope that this would work.
This sort of approach (using custom API, compiling with JDK) works easily in Eclipse. It should be simple in IDEA.
Thanks for helping a long-time, faithful customer.
|
|
Description
|
Blu-ray Disc Java development requires a development environment based upon the following APIs:
- Source code for the Personal Basis Profile 1.0 and JSSE for CDC 1.0.
Sun is preparing a download of these components (which will also
include Java TV), but this probably won't be ready before October 2008.
In the meantime, you can get a copy of "fake" stubs that contain the
correct API signatures, but that have had the API element descriptions
replaced with a disclaimer. This can be downloaded from
http://hdcookbook.com/bdj_platform/fake_stubs_pbp_jsse.zip
.
Development in BD-J is similar to development in J2ME, however it has a different subset of APIs. Ideally, a custom JDK configuration could be created to allow the user to specify a JDK built upon this API, using the compiler from any 1.3+ JDK.
The problem with the current approach (attaching JDK 1.3 and the above libraries) is that the user sees two versions of every Personal Basis Profile class (one from PBP and one from JDK). Also, the JavaDocs come from the JDK. Thus, it is hard to tell if the incorrect APIs are being coded against until the project is compiled with Ant.
I have attempted to create a hybrid JDK 1.3 install with the rt.jar replaced with the BD-J stubs, however this results in IDEA reporting a corrupt JDK. Also, the project will not compile. The better approach would probably involve using a J2ME wireless SDK as the basis, but I don't have a lot of hope that this would work.
This sort of approach (using custom API, compiling with JDK) works easily in Eclipse. It should be simple in IDEA.
Thanks for helping a long-time, faithful customer. |
Show » |
| There are no comments yet on this issue.
|
|