Re: [sca-j] NEW ISSUE: JCI90003 -- Java SE 5 requirement should be on the runtime not on the class

Hi Anish,

I'm not sure the intent of this is to disallow classes that use a feature in Java 6 or greater, but the issue reads that way. For example, a component implementation class could make use of a JDK 6 API. I think it should be valid for a runtime to support use of those APIs.

Jim



On May 9, 2011, at 8:22 AM, Anish Karmarkar wrote:

> Title: JCI90003 -- Java SE 5 requirement should be on the runtime not on the class
> 
> Specification: Java POJO CI
> 
> Description:
> 
> JCI90003 say --
> The Java class referenced by the @class attribute of <implementation.java/> MUST conform to Java SE version 5.0. [JCI90003]
> 
> This seems unnecessary. We should allow classes compiled using earlier version of Java SE to be used with SCA. We should also allow classes complied with Java SE version > 5.0 as long as the classes don't use any features that are not present in 5.0.
> 
> If we need a requirement for Java SE version, that requirement should be on the Runtime not the class.
> 
> Proposal:
> 
> Change the target of the requirement to be the Runtime not the class.
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php