Interesting, separate jars were always in the plan, so that isn't a problem. So you are saying the code can still
access the annotations at runtime?
Don
Taras Puchko wrote:
Retrotranslator replaces "extends java.lang.Annotation" with "extends
net.sf.retrotranslator.runtime.java.lang.Annotation_", "java.lang.Class.getAnnotation" with
"net.sf.retrotranslator.runtime.java.lang._Class.getAnnotation", and so on.
So application developers do not have to be aware of Retrotranslator:
http://cvs.sourceforge.net/viewcvs.py/retrotranslator/Retrotranslator/test/net/sf/retrotranslator/runtime/java/lang/_ClassTestCase.java?view=markup
The only drawback here is that translated code may be incompatible with
libraries using Java 5 API directly (mainly because annotations do not extend
java.lang.Annotation after translation). So you would have to distribute
separate jars for 1.4 and 5.0 platform.
Taras
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=27314&messageID=53964#53964
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
