Marc -
This problem is fixed[1] in the 2.1.x stream and trunk.
[1] http://issues.apache.org/jira/browse/OPENJPA-1965
Thanks,
Rick
On Thu, Mar 24, 2011 at 12:57 PM, Rick Curtis curti...@gmail.com wrote:
I have heard it said that programmatic javac compiler for debugging
means that you have
great News!
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 25.03.2011 um 15:56 schrieb Rick Curtis:
Marc -
This problem is fixed[1] in the 2.1.x stream and trunk.
[1] http://issues.apache.org/jira/browse/OPENJPA-1965
Thanks,
Rick
On Thu, Mar 24,
Hi,
this is nearly impossible because its not an Entity which makes the problem
here. Its a package. I have no idea how to unit test that. Perhaps you can try
creating
a simple package with JAXB generated classes in it and try to reproduce:
1) create a very simple XSD file
2) run the JAXB
Debugging is also not that easy within an ANT process. Perhaps someone give
me an hint how to proceed.
Invoke javac compiler programmatically. Pass opejpa.metamodel in compiler
argument.
You will require tools.jar in your classpath.
-
Pinaki
--
View this message in context:
Hi,
i am quite sure that there were a lot more jars when i had the single ALL
dependency in my ivy setup.
Dont have the time to prove right now. In fact one dont need the service file
when using the -processor flag in javac.
---
regards
Marc Logemann
http://www.logemann.org
you are late. We basically figured out all the issues. I also presented a fix
and Rick supplied a patched jar and hopefully this fix will make it into the
next 2.1 release.
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 24.03.2011 um 14:25 schrieb Pinaki Poddar:
We basically figured out all the issues.
I am sure you did. Good luck :)
you are late.
Not really. The code was written two years ago, with a programmatic javac
compiler for debugging ;)
-
Pinaki
--
View this message in context:
On Thu, Mar 24, 2011 at 10:40 AM, Marc Logemann l...@logemann.org wrote:
you are late.
Not really. The code was written two years ago, with a programmatic javac
compiler for debugging ;)
thats not what i meant. I meant in following our discussion on the list ;-)
When i am old and
Am 24.03.2011 um 17:27 schrieb Michael Dick:
On Thu, Mar 24, 2011 at 10:40 AM, Marc Logemann l...@logemann.org wrote:
you are late.
Not really. The code was written two years ago, with a programmatic javac
compiler for debugging ;)
thats not what i meant. I meant in following our
I have heard it said that programmatic javac compiler for debugging
means that you have a junit testcase which calls com.sun.tools.javac.Main.
I heard it somehow involved a chicken and some sort of voodoo dance. :)
On Thu, Mar 24, 2011 at 11:27 AM, Michael Dick michael.d.d...@gmail.comwrote:
Thats exactly what i am trying the last 10 minutes but its not that easy
because he doesnt process alphabetically or something. In fact i have more than
30 entities which are not processed. One of those is the problem of course.
the compilerarg value=-Aopenjpa.log=TRACE/ thingy doesnt reveal
one more thing.
You have something like this in the second process() method:
private boolean process(TypeElement e) {
catch (Exception e1) {
logger.error(_loc.get(mmg-process-error, e.getQualifiedName()),
e1);
return false;
} finally {
...
This is cool if
Correction:
With my program, i get a result of course because i dont leave the process on
error ;-) But this is the solution.
This is NOT the solution i meant.
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 23.03.2011 um 16:38 schrieb Marc Logemann:
Puuuh.
still a bit clueless
Me too. I just started digging into some of the annotation processor code to
see if I can learn something today So when you swallowed the exception
everything worked fine?
Thanks,
Rick
For the time being, how about the following fix in openjpa trunk:
/**
* The entry point for java compiler.
*/
@Override
public boolean process(Set? extends TypeElement annos, RoundEnvironment
roundEnv) {
if (active !roundEnv.processingOver()) {
Set?
Yes that seems reasonable. I'll get that taken care of sometime this
afternoon.
I'd like to get another JIRA opened up to investigate the JAXB
packageElements problem
Thanks,
Rick
On Wed, Mar 23, 2011 at 10:51 AM, Marc Logemann l...@logemann.org wrote:
For the time being, how about the
Hi,
hope i could help a bit in researching this. For now i will use my own variant
of AnnotationProcessor6.
BTW it was a bit of a mess to create my own version of this class because
SourceAnnotationHandler.class has a lot of package private methods which are
used by AnnotationProcessor6. So
BTW it was a bit of a mess to create my own version of this class because
SourceAnnotationHandler.class has a lot of package private methods which are
used by AnnotationProcessor6. So i also needed to clone that class too.
g. :-)
I could easily create a patch to put on top of the existing
+1 for the patch on AnnotationProcessor6 for the 2.1.x release line.
Of course this would make my life easier. I could drop my own variant.
I always like using framework classes instead of patched-own-versions.
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am
Marc -
Give this[1] patch a shot. If you can help me come up with a test Entity
model that exposes this problem I have a pretty good chance of being able to
get it into 2.1.1.
[1]
http://people.apache.org/~curtisr7/patches/annotation_processor_patch.jar
Thanks,
Rick
On Wed, Mar 23, 2011 at
20 matches
Mail list logo
