Skip to main content

[JAI] Do you still require Java 1.3 compatibility?

23 replies [Last post]
Anonymous

Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools requires
1.4 or newer, of course).

Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
software that you produce which depends on JAI?

Thanks,

Brian

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Guillaume Helle

Not a problem. We require Java 1.4 and Java 1.5.

Guillaume Helle

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Robert Engels

Don't you have the same problems in moving to a new JAI version?

-----Original Message-----
From: aleoo@solarapex.com [mailto:aleoo@solarapex.com]
Sent: Wednesday, October 19, 2005 6:24 PM
To: interest@jai.dev.java.net
Subject: Re: [JAI] Do you still require Java 1.3 compatibility?

Brian,

> Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools
> requires 1.4 or newer, of course).
>
> Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
> software that you produce which depends on JAI?

It may. We have a Java application that uses JAI running under J2SE 1.3.
This is a mission critical application. Now dropping support for 1.3 adds
some risk for us. If the application gets any issues that are related to
JAI and are fixed in latter versions of JAI, it may force us to move to
J2SE 1.4. Due to some regulations these kind of changes are not easy for
pharmaceutical companies since these changes should go through certain
formal and sometimes lengthy and costly process especially if an
application runs on a large number of desktops.

Regards,
Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

aleoo@solarapex.com

>>> Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools
>>> requires 1.4 or newer, of course).
>>>
>>> Would requiring J2SE 1.4 for JAI pose a problem for you or customers
>>> of
>>> software that you produce which depends on JAI?
>>
>> It may. We have a Java application that uses JAI running under J2SE
>> 1.3. This is a mission critical application. Now dropping support for
>> 1.3 adds some risk for us. If the application gets any issues that are
>> related to JAI and are fixed in latter versions of JAI, it may force
>> us to move to J2SE 1.4. Due to some regulations these kind of changes
>> are not easy for pharmaceutical companies since these changes should
>> go through certain formal and sometimes lengthy and costly process
>> especially if an application runs on a large number of desktops.
>
> This is useful information. At some point I imagine we will move to
> requiring J2SE 1.4 but when is as yet indeterminate. It may be that we
> would keep a parallel version of JAI around that requires 1.3 only.
> The issue in that case is which if any bug fixes were back propagated.
> Such backward propagation is of course possible via direct use of the
> source code.

This would help. I am glad you asked this question.

> Don't you have the same problems in moving to a new JAI version?

No. That's different. Here is why. In order to cut down costs for desktop
support in many large organizations often applications are distributed and
installed via the network using different kind of software like Novell
Application Launcher. If you have Java desktop applications and a Java plug-
in distributed via the network, you need to be careful and need to
validate/test that updating the Java plug-in does not break any Java
applications instead of validating/testing only one Java application that
uses JAI. We have had some issues with Oracle applications. Using install
on demand is not an option since most of users do not have administrative
privileges for security reasons.

As a matter of fact, we found that after Oracle 9i Client is installed, JAI
initialization fails with security exceptions. Luckily we discovered that
before it hit production.

Regards,
Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Robert Engels

I still using the automated update/install features using JNLP is the way to
go. You can multiple versions of the JRE installed, and multiple versions of
extensions (like JAI).

Let the great Java deployment system handle the work.

-----Original Message-----
From: aleoo@solarapex.com [mailto:aleoo@solarapex.com]
Sent: Wednesday, October 19, 2005 8:07 PM
To: interest@jai.dev.java.net
Subject: RE: [JAI] Do you still require Java 1.3 compatibility?

>>> Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools
>>> requires 1.4 or newer, of course).
>>>
>>> Would requiring J2SE 1.4 for JAI pose a problem for you or customers
>>> of
>>> software that you produce which depends on JAI?
>>
>> It may. We have a Java application that uses JAI running under J2SE
>> 1.3. This is a mission critical application. Now dropping support for
>> 1.3 adds some risk for us. If the application gets any issues that are
>> related to JAI and are fixed in latter versions of JAI, it may force
>> us to move to J2SE 1.4. Due to some regulations these kind of changes
>> are not easy for pharmaceutical companies since these changes should
>> go through certain formal and sometimes lengthy and costly process
>> especially if an application runs on a large number of desktops.
>
> This is useful information. At some point I imagine we will move to
> requiring J2SE 1.4 but when is as yet indeterminate. It may be that we
> would keep a parallel version of JAI around that requires 1.3 only.
> The issue in that case is which if any bug fixes were back propagated.
> Such backward propagation is of course possible via direct use of the
> source code.

This would help. I am glad you asked this question.

> Don't you have the same problems in moving to a new JAI version?

No. That's different. Here is why. In order to cut down costs for desktop
support in many large organizations often applications are distributed and
installed via the network using different kind of software like Novell
Application Launcher. If you have Java desktop applications and a Java plug-
in distributed via the network, you need to be careful and need to
validate/test that updating the Java plug-in does not break any Java
applications instead of validating/testing only one Java application that
uses JAI. We have had some issues with Oracle applications. Using install
on demand is not an option since most of users do not have administrative
privileges for security reasons.

As a matter of fact, we found that after Oracle 9i Client is installed, JAI
initialization fails with security exceptions. Luckily we discovered that
before it hit production.

Regards,
Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Aaron Bruegl

Not a problem. We require Java 1.4 and Java 1.5.

-Aaron Bruegl

-----Original Message-----
From: Brian.Burkhalter@Sun.COM [mailto:Brian.Burkhalter@Sun.COM]
Sent: Wednesday, October 19, 2005 12:54 PM
To: Java Advanced Imaging discussion list
Subject: [JAI] Do you still require Java 1.3 compatibility?

Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools requires
1.4 or newer, of course).

Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
software that you produce which depends on JAI?

Thanks,

Brian

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

David Clunie

We are now 1.4.2 or later, since we use JIIO and NIO.

David

Aaron Bruegl wrote:
> Not a problem. We require Java 1.4 and Java 1.5.
>
> -Aaron Bruegl
>
> -----Original Message-----
> From: Brian.Burkhalter@Sun.COM [mailto:Brian.Burkhalter@Sun.COM]
> Sent: Wednesday, October 19, 2005 12:54 PM
> To: Java Advanced Imaging discussion list
> Subject: [JAI] Do you still require Java 1.3 compatibility?
>
> Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools requires
> 1.4 or newer, of course).
>
> Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
> software that you produce which depends on JAI?
>
> Thanks,
>
> Brian
>
> ----------------
> Brian Burkhalter
> Java Multimedia, Imaging, and Graphics
> Sun Microsystems, Inc.

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Fabrizio Giudici

On Oct 20, 2005, at 21:45 , David Clunie wrote:

> We are now 1.4.2 or later, since we use JIIO and NIO.
>

I'm on 1.4 and 1.5, but now that Java 5 is well supported also under
Mac OS X I'll drop 1.4.

--
Fabrizio Giudici, Ph.D. - Java Architect, Tidalwave s.a.s.
email: Fabrizio.Giudici@tidalwave.it
mobile: +39 348.150.6941 - fax: +39 027.005.105.36

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Stéphane WASSERHARDT

No problem here !

-----Message d'origine-----
De : Brian.Burkhalter@Sun.COM [mailto:Brian.Burkhalter@Sun.COM]
Envoyé : mercredi 19 octobre 2005 19:54
À : Java Advanced Imaging discussion list
Objet : [JAI] Do you still require Java 1.3 compatibility?

Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools requires
1.4 or newer, of course).

Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
software that you produce which depends on JAI?

Thanks,

Brian

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

aleoo@solarapex.com

Brian,

> Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools
> requires 1.4 or newer, of course).
>
> Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
> software that you produce which depends on JAI?

It may. We have a Java application that uses JAI running under J2SE 1.3.
This is a mission critical application. Now dropping support for 1.3 adds
some risk for us. If the application gets any issues that are related to
JAI and are fixed in latter versions of JAI, it may force us to move to
J2SE 1.4. Due to some regulations these kind of changes are not easy for
pharmaceutical companies since these changes should go through certain
formal and sometimes lengthy and costly process especially if an
application runs on a large number of desktops.

Regards,
Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Brian Burkhalter

Alex,

>> Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools
>> requires 1.4 or newer, of course).
>>
>> Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
>> software that you produce which depends on JAI?
>
> It may. We have a Java application that uses JAI running under J2SE 1.3.
> This is a mission critical application. Now dropping support for 1.3 adds
> some risk for us. If the application gets any issues that are related to
> JAI and are fixed in latter versions of JAI, it may force us to move to
> J2SE 1.4. Due to some regulations these kind of changes are not easy for
> pharmaceutical companies since these changes should go through certain
> formal and sometimes lengthy and costly process especially if an
> application runs on a large number of desktops.

This is useful information. At some point I imagine we will move to requiring
J2SE 1.4 but when is as yet indeterminate. It may be that we would keep a
parallel version of JAI around that requires 1.3 only. The issue in that case
is which if any bug fixes were back propagated. Such backward propagation is
of course possible via direct use of the source code.

Brian

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Jeff Moroski

We already require Java 1.4 or better.

-----Original Message-----
From: Brian.Burkhalter@Sun.COM [mailto:Brian.Burkhalter@Sun.COM]
Sent: Wednesday, October 19, 2005 1:54 PM
To: Java Advanced Imaging discussion list
Subject: [JAI] Do you still require Java 1.3 compatibility?

Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools
requires
1.4 or newer, of course).

Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
software that you produce which depends on JAI?

Thanks,

Brian

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Martin Desruisseaux

We already use J2SE 1.4 too. Actually, upgrating JAI to J2SE 1.4 may
simplify usage of DataBufferFloat and DataBufferDouble, which would be
quite appreciated.

Martin.

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Brian Burkhalter

Yes, and we could deprecate ComponentSampleModelJAI and FloatDoubleColorModel
and better yet move the ImageRead and ImageWrite operations from JAI-Image I/O
to JAI.

Brian

On Thu, 20 Oct 2005, Martin Desruisseaux wrote:

> Actually, upgrating JAI to J2SE 1.4 may simplify
> usage of DataBufferFloat and DataBufferDouble, which would be quite
> appreciated.

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Martin Desruisseaux

Brian Burkhalter a écrit :
> Yes, and we could deprecate ComponentSampleModelJAI and
> FloatDoubleColorModel and better yet move the ImageRead and ImageWrite
> operations from JAI-Image I/O to JAI.

Moving ImageRead and ImageWrite in JAI would be very appreciated as
well. It would allow us to require a single extension installation from
our users instead of two as today. Actually, having JAI-Image I/O and
JAI bundled in a single download and installation program would be quite
convenient. If JAI upgrate to 1.4, would it be doable to merge JAI-Image
I/O with JAI?

Martin.

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Brian Burkhalter

On Fri, 21 Oct 2005, Martin Desruisseaux wrote:

> Brian Burkhalter a écrit :
>> Yes, and we could deprecate ComponentSampleModelJAI and
>> FloatDoubleColorModel and better yet move the ImageRead and ImageWrite
>> operations from JAI-Image I/O to JAI.
>
> Moving ImageRead and ImageWrite in JAI would be very appreciated as well. It
> would allow us to require a single extension installation from our users
> instead of two as today.

Note that putting ImageRead and ImageWrite in JAI would not mean that all the
various plug-ins (TIFF, etc.) would be also be moved to JAI.

> Actually, having JAI-Image I/O and JAI bundled in a
> single download and installation program would be quite convenient. If JAI
> upgrate to 1.4, would it be doable to merge JAI-Image I/O with JAI?

I suspect that this would not be desirable for a number of users, for example
those that use JAI-Image I/O but not JAI itself. There is I suppose however
the possiblity of considering some sort of additional combined installer.

For any ideas such as this, or for any problems or ideas, the best thing to do
is to file an issue in the appropriate Issue Tracker (jai-core or
jai-imageio-core) so it is not forgotten and so that project members may vote
on it.

Brian

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Robert Engels

Please do not combine ImageIO and JAI. We use ImageIO (and the tools)
extensively without JAI.

-----Original Message-----
From: Brian.Burkhalter@Sun.COM [mailto:Brian.Burkhalter@Sun.COM]
Sent: Thursday, October 20, 2005 6:28 PM
To: interest@jai.dev.java.net
Subject: Re: [JAI] Do you still require Java 1.3 compatibility?

On Fri, 21 Oct 2005, Martin Desruisseaux wrote:

> Brian Burkhalter a écrit :
>> Yes, and we could deprecate ComponentSampleModelJAI and
>> FloatDoubleColorModel and better yet move the ImageRead and ImageWrite
>> operations from JAI-Image I/O to JAI.
>
> Moving ImageRead and ImageWrite in JAI would be very appreciated as well.
It
> would allow us to require a single extension installation from our users
> instead of two as today.

Note that putting ImageRead and ImageWrite in JAI would not mean that all
the
various plug-ins (TIFF, etc.) would be also be moved to JAI.

> Actually, having JAI-Image I/O and JAI bundled in a
> single download and installation program would be quite convenient. If JAI
> upgrate to 1.4, would it be doable to merge JAI-Image I/O with JAI?

I suspect that this would not be desirable for a number of users, for
example
those that use JAI-Image I/O but not JAI itself. There is I suppose however
the possiblity of considering some sort of additional combined installer.

For any ideas such as this, or for any problems or ideas, the best thing to
do
is to file an issue in the appropriate Issue Tracker (jai-core or
jai-imageio-core) so it is not forgotten and so that project members may
vote
on it.

Brian

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

David Clunie

I agree - do not make JIIO codecs depend on JAI.

David

Robert Engels wrote:
> Please do not combine ImageIO and JAI. We use ImageIO (and the tools)
> extensively without JAI.
>
> -----Original Message-----
> From: Brian.Burkhalter@Sun.COM [mailto:Brian.Burkhalter@Sun.COM]
> Sent: Thursday, October 20, 2005 6:28 PM
> To: interest@jai.dev.java.net
> Subject: Re: [JAI] Do you still require Java 1.3 compatibility?
>
>
> On Fri, 21 Oct 2005, Martin Desruisseaux wrote:
>
>
>>Brian Burkhalter a écrit :
>>
>>>Yes, and we could deprecate ComponentSampleModelJAI and
>>>FloatDoubleColorModel and better yet move the ImageRead and ImageWrite
>>>operations from JAI-Image I/O to JAI.
>>
>>Moving ImageRead and ImageWrite in JAI would be very appreciated as well.
>
> It
>
>>would allow us to require a single extension installation from our users
>>instead of two as today.
>
>
> Note that putting ImageRead and ImageWrite in JAI would not mean that all
> the
> various plug-ins (TIFF, etc.) would be also be moved to JAI.
>
>
>>Actually, having JAI-Image I/O and JAI bundled in a
>>single download and installation program would be quite convenient. If JAI
>>upgrate to 1.4, would it be doable to merge JAI-Image I/O with JAI?
>
>
> I suspect that this would not be desirable for a number of users, for
> example
> those that use JAI-Image I/O but not JAI itself. There is I suppose however
> the possiblity of considering some sort of additional combined installer.
>
> For any ideas such as this, or for any problems or ideas, the best thing to
> do
> is to file an issue in the appropriate Issue Tracker (jai-core or
> jai-imageio-core) so it is not forgotten and so that project members may
> vote
> on it.
>
> Brian
>
> ----------------
> Brian Burkhalter
> Java Multimedia, Imaging, and Graphics
> Sun Microsystems, Inc.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> This email message is for the sole use of the intended recipient(s)
> and may contain confidential and privileged information. Any
> unauthorized review, use, disclosure or distribution is prohibited.
> If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
> For additional commands, e-mail: interest-help@jai.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Brian Burkhalter

We have no intention of doing so. We might investigate providing an additional
installer that includes both but given the quantity of other work to do I
don't know that that either is very likely to happen.

Brian

On Fri, 21 Oct 2005, David Clunie wrote:

> I agree - do not make JIIO codecs depend on JAI.
>
> David
>
> Robert Engels wrote:
>> Please do not combine ImageIO and JAI. We use ImageIO (and the tools)
>> extensively without JAI.
>>
>> -----Original Message-----
>> From: Brian.Burkhalter@Sun.COM [mailto:Brian.Burkhalter@Sun.COM]
>> Sent: Thursday, October 20, 2005 6:28 PM
>> To: interest@jai.dev.java.net
>> Subject: Re: [JAI] Do you still require Java 1.3 compatibility?
>>
>>
>> On Fri, 21 Oct 2005, Martin Desruisseaux wrote:
>>
>>
>>> Brian Burkhalter a écrit :
>>>
>>>> Yes, and we could deprecate ComponentSampleModelJAI and
>>>> FloatDoubleColorModel and better yet move the ImageRead and ImageWrite
>>>> operations from JAI-Image I/O to JAI.
>>>
>>> Moving ImageRead and ImageWrite in JAI would be very appreciated as well.
>>
>> It
>>
>>> would allow us to require a single extension installation from our users
>>> instead of two as today.
>>
>>
>> Note that putting ImageRead and ImageWrite in JAI would not mean that all
>> the
>> various plug-ins (TIFF, etc.) would be also be moved to JAI.
>>
>>
>>> Actually, having JAI-Image I/O and JAI bundled in a
>>> single download and installation program would be quite convenient. If JAI
>>> upgrate to 1.4, would it be doable to merge JAI-Image I/O with JAI?
>>
>>
>> I suspect that this would not be desirable for a number of users, for
>> example
>> those that use JAI-Image I/O but not JAI itself. There is I suppose however
>> the possiblity of considering some sort of additional combined installer.
>>
>> For any ideas such as this, or for any problems or ideas, the best thing to
>> do
>> is to file an issue in the appropriate Issue Tracker (jai-core or
>> jai-imageio-core) so it is not forgotten and so that project members may
>> vote
>> on it.
>>
>> Brian
>>
>> ----------------
>> Brian Burkhalter
>> Java Multimedia, Imaging, and Graphics
>> Sun Microsystems, Inc.
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> This email message is for the sole use of the intended recipient(s)
>> and may contain confidential and privileged information. Any
>> unauthorized review, use, disclosure or distribution is prohibited.
>> If you are not the intended recipient, please contact the sender by
>> reply email and destroy all copies of the original message.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
>> For additional commands, e-mail: interest-help@jai.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
> For additional commands, e-mail: interest-help@jai.dev.java.net
>
>

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Paul Kling

I am currently not a huge user of JAI yet, but I do support some other new
Java code that has to run on older Mac's. Currently our limitation is Java
1.3.1 due to Mac OS 10.2. I believe there is no upgrade path to Java 1.4 for
the older Mac OS's.

Thanks
Paul

-----Original Message-----
From: Brian.Burkhalter@Sun.COM [mailto:Brian.Burkhalter@Sun.COM]
Sent: Wednesday, October 19, 2005 12:54 PM
To: Java Advanced Imaging discussion list
Subject: [JAI] Do you still require Java 1.3 compatibility?

Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools requires
1.4 or newer, of course).

Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
software that you produce which depends on JAI?

Thanks,

Brian

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

Russell East

[att1.html]

Fritz Cathey

none

At 10:54 AM 10/19/2005 -0700, you wrote:

>Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools
>requires 1.4 or newer, of course).
>
>Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
>software that you produce which depends on JAI?
>
>Thanks,
>
>Brian
>
>----------------
>Brian Burkhalter
>Java Multimedia, Imaging, and Graphics
>Sun Microsystems, Inc.
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>This email message is for the sole use of the intended recipient(s)
>and may contain confidential and privileged information. Any
>unauthorized review, use, disclosure or distribution is prohibited.
>If you are not the intended recipient, please contact the sender by
>reply email and destroy all copies of the original message.
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
>For additional commands, e-mail: interest-help@jai.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net

gwampole
Offline
Joined: 2005-02-15
Points: 0

Echoing Mr. Thompson's sentiments; 1.4 is already a requrement of our systems for reasons apart from JAI.

Thompson, Joe

Our group here in Gaithersburg would have no problem with a 1.4
requirement. We already require it for other reasons.

Joe Thompson
Lockheed Martin IS&S
Gaithersburg, MD
See our Geospatial Intelligence Solutions Web Site at
www.lockheedmartin.com/GEOINT

-----Original Message-----
From: Brian.Burkhalter@Sun.COM [mailto:Brian.Burkhalter@Sun.COM]
Sent: Wednesday, October 19, 2005 1:54 PM
To: Java Advanced Imaging discussion list
Subject: [JAI] Do you still require Java 1.3 compatibility?

Currently JAI requires only J2SE 1.3 or newer (JAI-Image I/O Tools
requires
1.4 or newer, of course).

Would requiring J2SE 1.4 for JAI pose a problem for you or customers of
software that you produce which depends on JAI?

Thanks,

Brian

----------------
Brian Burkhalter
Java Multimedia, Imaging, and Graphics
Sun Microsystems, Inc.

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@jai.dev.java.net
For additional commands, e-mail: interest-help@jai.dev.java.net