[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

comments on proposed java policy



Hi,

I'm just subscribed to this list, but just caught the announcement and went through it.
Some comments and questions:

1. why is there a difference between java1 and java2? Isn't java1 virtually obsolete? (I work on a java project where the life-cycle is short and customers upgrade rather quick, so it's easy to upgrade jvm).

2. why must java-compiler depend on java-runtime???? I propose to make this a suggestion. For example, gcj isn't a java class. Perhaps a note to enlighten naive readers like me?

3. I don't understand why 'auxliary classes' (section 2.3) must follow the naming for libraries. I can image that the name often is determined upstream.

4. what about JNI? As you note in the heading of chapter 2, java bytecode is portable. But packages may contain JNI.

5. what about j2ee? I propose to further make difference between java1, j2se, j2ee and j2me? I think we must be prepared for at least the ee version to be packaged.

6. How to handle apis? things like jaxp, jndi ext. These may be available as separate libraries or included in a runtime (see Suns JDK 1.4). Do we (and where) determine virtual packages for those?

I guess that's enought for now...

Good luck,
Jan Evert





Reply to: