Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipselink-dev] RE: Fix for 307897 (JRockit+ASM issue) requires servlet jar (CQ 2505)

So the additional dependencies are:
 
1. servlet.jar to compile against
 
2. Must have JDK with compiler and not just  a JRE to run Java code
 
Not sure if the second dependency changes anything from an IPLog perspective.
 
Doug
-----Original Message-----
From: Michael Norman
Sent: May 7, 2010 3:43 PM
To: Dev mailing list for Eclipse Persistence Services
Cc: Douglas Clarke
Subject: Fix for 307897 (JRockit+ASM issue) requires servlet jar (CQ 2505)

https://bugs.eclipse.org/bugs/show_bug.cgi?id=307897

I have the fix for the JRockit+ASM issue (don't use ASM) where the source to _dbws.DBWSProvider is generated (as before)
then passed to the Java compiler using the javax.tools.JavaCompiler class. This fixes the problem for all combinations of JDK platforms.

There is one additional dependency which is that servlet.jar must be on the classpath when the DBWSBuilder is invoked.
We already have an approved CQ 2505 and we stated waay back in 1.1 that DBWS requires this (when DBWSBuilder was
an Ant task). Later DBWSBuilder was converted to a Java-main program and the provider class was generated using ASM
so we stopped shipping the jar.

I have spoken with Peter and he thinks we are in the clear to included it in 2.0.3 and 2.1 - any objections?

--
Mike Norman | Principal Software Designer | 613.288.4638
Oracle Server Technologies | EclipseLink Product
45 O'Connor Street, Suite 400 | Ottawa, ON K1P 1A4 | (fax) 613.238.2818

Back to the top