| JRE Compliance Level and Runtime Compatibility [message #427256] |
Mon, 09 February 2009 08:41  |
 Philippe
Messages: 100
Registered: July 2009 |
Senior Member |
|
|
Hi EMF Newsgroup,
I need to evaluate the possibility to use EMF-XSD as library for
managing XML messages according to an existing XML Schema.
The bad point is that the currently targeted environment for the project
is WAS 6.0.2 running on JDK 1.4.2, thus blocking me on using EMF 2.2
runtime.
So on my local environment Eclipse 3.4 + EMF 2.4, I tried to set the
Compliance Level to 1.4 and Runtime Version to 2.2 in my genmodel,
however I get an unresolved import for
javax.xml.datatype.XMLGregorianCalendar
That is not present until JAXP 1.3, only included in JDK 1.5 as far as I
know.
Is there any way to generate JDK 1.4 compatible code from this environment ?
Otherwise, reverting to Eclipse 3.2 + EMF 2.2, that use Object where
current code use XMLGregorianCalendar would be appropriate or would it
require additional works ?
Finally, would you have killing arguments that I could use in the
discussion of possibly upgrading the targeted environment, knowing that
the core of the application will turn around sending and receiving XML
messages ?
Thanks for your precious help
Philippe
|
|
|
| Re: JRE Compliance Level and Runtime Compatibility [message #427258 is a reply to message #427256] |
Mon, 09 February 2009 10:45  |
Ed Merks
Messages: 33133
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------040403080607010102050207
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Philippe,
Comments below.
Philippe wrote:
> Hi EMF Newsgroup,
>
> I need to evaluate the possibility to use EMF-XSD as library for
> managing XML messages according to an existing XML Schema.
> The bad point is that the currently targeted environment for the
> project is WAS 6.0.2 running on JDK 1.4.2, thus blocking me on using
> EMF 2.2 runtime.
You mean locking as opposed to blocking? Using PARENT_LOADER_LAST or
some such flag, it ought to be possible to use whatever version of EMF
you want...
>
> So on my local environment Eclipse 3.4 + EMF 2.4, I tried to set the
> Compliance Level to 1.4 and Runtime Version to 2.2 in my genmodel,
> however I get an unresolved import for
> javax.xml.datatype.XMLGregorianCalendar
> That is not present until JAXP 1.3, only included in JDK 1.5 as far as
> I know.
This has been addressed in the 2.4 maintenance stream
https://bugs.eclipse.org/bugs/show_bug.cgi?id=261587
>
> Is there any way to generate JDK 1.4 compatible code from this
> environment ?
You'd need to upgrade to the latest maintenance stream will will become
the second maintenance release soon.
>
> Otherwise, reverting to Eclipse 3.2 + EMF 2.2, that use Object where
> current code use XMLGregorianCalendar would be appropriate or would it
> require additional works ?
Nope, that's pretty much it.
>
>
> Finally, would you have killing arguments that I could use in the
> discussion of possibly upgrading the targeted environment, knowing
> that the core of the application will turn around sending and
> receiving XML messages ?
Either way should work, but you have to wonder about being locked on an
end-of-life JDK level...
>
> Thanks for your precious help
> Philippe
--------------040403080607010102050207
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Philippe,<br>
<br>
Comments below.<br>
<br>
<br>
Philippe wrote:
<blockquote cite="mid:gmoq87$m2b$1@build.eclipse.org" type="cite">Hi
EMF Newsgroup,
<br>
<br>
I need to evaluate the possibility to use EMF-XSD as library for
managing XML messages according to an existing XML Schema.
<br>
The bad point is that the currently targeted environment for the
project is WAS 6.0.2 running on JDK 1.4.2, thus blocking me on using
EMF 2.2 runtime.
<br>
</blockquote>
You mean locking as opposed to blocking? Using PARENT_LOADER_LAST or
some such flag, it ought to be possible to use whatever version of EMF
you want...<br>
<blockquote cite="mid:gmoq87$m2b$1@build.eclipse.org" type="cite"><br>
So on my local environment Eclipse 3.4 + EMF 2.4, I tried to set the
Compliance Level to 1.4 and Runtime Version to 2.2 in my genmodel,
however I get an unresolved import for
javax.xml.datatype.XMLGregorianCalendar
<br>
That is not present until JAXP 1.3, only included in JDK 1.5 as far as
I know.
<br>
</blockquote>
This has been addressed in the 2.4 maintenance stream<br>
<blockquote><a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=261587">https://bugs.eclipse.org/bugs/show_bug.cgi?id=261587</a><br>
</blockquote>
<blockquote cite="mid:gmoq87$m2b$1@build.eclipse.org" type="cite"><br>
Is there any way to generate JDK 1.4 compatible code from this
environment ?
<br>
</blockquote>
You'd need to upgrade to the latest maintenance stream will will become
the second maintenance release soon.<br>
<blockquote cite="mid:gmoq87$m2b$1@build.eclipse.org" type="cite"><br>
Otherwise, reverting to Eclipse 3.2 + EMF 2.2, that use Object where
current code use XMLGregorianCalendar would be appropriate or would it
require additional works ?</blockquote>
Nope, that's pretty much it.<br>
<blockquote cite="mid:gmoq87$m2b$1@build.eclipse.org" type="cite"><br>
<br>
Finally, would you have killing arguments that I could use in the
discussion of possibly upgrading the targeted environment, knowing that
the core of the application will turn around sending and receiving XML
messages ?
<br>
</blockquote>
Either way should work, but you have to wonder about being locked on an
end-of-life JDK level...<br>
<blockquote cite="mid:gmoq87$m2b$1@build.eclipse.org" type="cite"><br>
Thanks for your precious help
<br>
Philippe
<br>
</blockquote>
</body>
</html>
--------------040403080607010102050207--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.55381 seconds
] 
Search
Help
Register
Login
Home
