Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geclipse-dev] Error due to new execution env with Java 1.6?

Hi Ariel, Thomas,

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.

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.

Cheers,
Szymon

On Wed, 5 Mar 2008, Thomas Köckerbauer wrote:

Hi

In case I'm using JDK 1.5 it accesses the javax.activation plugin in the
org.gria plugin. I've tried JDK 1.6 now too, I'm getting the same problem you
have. I've played around with the plugin dependencies a bit but haven't found
any solution yet. A question I have is, is that code that uses that
javax.activation classes used/needed at all (it accesses a hardcoded file "C:
\\test_temp\\echoTest.sh")?


Cheers,
Thomas


Am Mittwoch 05 März 2008 18:52:23 schrieb Thomas Köckerbauer:
Hi,

Today I've changed every plugin which did not have J2SE-1.5 as execution
environment to that setting. I guess it has to do with that. The funny
thing is that it does not cause any problems on my machine (I'm using
JDK1.5).


Cheers,
Thomas

Am Mittwoch 05 März 2008 18:14:18 schrieb Ariel Garcia:
Hi Thomas, Szymon,

i am getting the error
------------
Access restriction: The type DataHandler is not accessible due to
 restriction on required
library /usr/lib/jvm/java-6-sun-1.6.0.04/jre/lib/rt.jar
-----------

(same for DataSource, FileDataSource) on
  eu.geclipse.test.framework.gria.model.GriaDataLifecycle.java

This error goes away if i undo your last change regarding the execution
environment. I am running on Java 1.6.

Can we avoid using those javax.activation classes or what would be the
right solution there?

Greets, Ariel
_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev

_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev


_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev

Back to the top