RE: RE: [geclipse-dev] Error due to new execution env with Java 1.6?

[Szymon Mueller <mael@xxxxxxxxxxxxxxxxxx>]

Hi all,

Problem lies when the only installed JRE (in Eclipse) is 1.6. In that 
case, when searching for javax.activation.DataHandler (.DataSource, 
.FileDataSource) classes, it first queries java 1.6 env. Due to 
restrictions of the gEclipse plugins (Java 1.5) they can't be accessed and 
build error is thrown. When you had both Java 1.5 and Java 1.6 or only 
Java 1.5 it compiles OK.

There is fix in cvs (see my post from thursday), which changes order in 
which dependencies are resolved - plugin dependencies are before "JRE 
System Library [J2SE-1.5]", so javax.activation classes are found from 
dependant Activation.jar in eu.geclipse.test.framework.gria plugin.

As for not using javax.activation classes: as Mark said there is another 
method copyFromURL( String url ), but only http and ftp urls are usable. 
So for any other data transfer uploading files to gria data stager (local 
-> gria, gsiftp -> gria, ... ) we will need to use 
DataConversation.save(DataHandler handler) method.

Cheers,
Szymon

On Wed, 12 Mar 2008, Mark McArdle wrote:

> Hi Ariel,
>
> I did send this to the mailing list, and I am registered. I received the
> emails from it :)
> I'm not sure why that reply didn't get through.
>
> I have created a bugzilla account also.
>
> Mark
>
> -----Original Message-----
> From: Ariel Garcia [mailto:garcia@xxxxxxxxxx]
> Sent: 12 March 2008 08:32
> To: Developer mailing list
> Cc: Mark McArdle
> Subject: Fwd: RE: [geclipse-dev] Error due to new execution env with
> Java 1.6?
>
> Hi guys,
>
> re-sending this email from Mark to the list, i don't see it in my
> folders.
>
> What happened with this, Szymon, Thomas, could you please follow it?
>
> @ Mark: are you registered to this mailing list? you cannot post
> otherwise
>    You should also register in bugzilla
> (https://bugs.eclipse.org/bugs),
> we cannot involve you in bugs otherwise ;-)
>
> Cheers, Ariel
>
>
> ----------  Forwarded Message  ----------
>
> Subject: RE: [geclipse-dev] Error due to new execution env with Java
> 1.6?
> Date: Friday 07 March 2008
> From: "Mark McArdle" <mm@xxxxxxxxxxxxxxxxxxxxxxxxx>
> To: "Ariel Garcia" <garcia@xxxxxxxxxx>, geclipse-dev@xxxxxxxxxxx
>
>
> Hi All,
>
> There is another method DataConversation.copyFromURL(URL url) which will
> pull data into the DataStager from a publically available address.
> But there is no reason I can see that DataConversation.save(DataHandler)
> shouldn't work.
>
> Just to see if I have the facts clear:
>
> Java 1.5 OK
> Java 1.6 OK
> Java 1.6 Compatibility Mode Fails
>
> Do we need to compatiblity mode for a reason?
>
> I will check if we have tested with it.
>
> Mark McArdle
> IT Innovation Centre
> 2 Venture Road
> Chilworth Science Park
> Southampton, SO16 7NP, UK
>
> tel: +44 23 8076 0834
> fax: +44 23 8076 0833
>
> mailto:mm@xxxxxxxxxxxxxxxxxxxxxxxxx
> http://www.it-innovation.soton.ac.uk
>
> > -----Original Message-----
> > From: Ariel Garcia [mailto:garcia@xxxxxxxxxx]
> > Sent: 06 March 2008 16:02
> > To: geclipse-dev@xxxxxxxxxxx
> > Cc: Mark McArdle
> > Subject: Re: [geclipse-dev] Error due to new execution env
> > with Java 1.6?
> >
> > Hi Szymon, all,
> >
> > > The only way (correct me if I'm wrong) to upload data to GRIA Data
> > > Stager is by using  DataConversion.save( DataHandler
> > handler ) method,
> > > so indeed those javax.activation classes are needed to
> > fully use data
> > > transfer with GRIA.
> >
> > i guess the expert here is Mark (in CC, Mark, you are in this
> > mailing list,
> > right?)
> > Are you aware of this thread/discussion, how do you suggest
> > to deal with
> > it?
> >
> > > However we found a solution to compile errors - you need to
> > change build
> > > class path order and move "Plug-in Dependencies" above "JRE System
> > > Library [J2SE-1.5]" for eu.geclipse.test.framework.gria. Is this
> > > solution plausible? If there won't be any objections I will commit
> > > proper change to CVS.
> >
> > looks more like a short-term workaround, does anybody
> > precisely understand
> > why is this access restriction happening with  J1.6 when set in 1.5
> > compatibility mode, but not in 1.5 or 1.6 native environments?
> >
> > Cheers, Ariel
>
>
> -------------------------------------------------------
> _______________________________________________
> geclipse-dev mailing list
> geclipse-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/geclipse-dev