[gatein-issues] [JBoss JIRA] Commented: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://jira.jboss.org/jira/browse/GTNPORTAL-66?page=com.atlassian.jira.p...
]
Luca Stancapiano commented on GTNPORTAL-66:
-------------------------------------------
- Is there a workaround for the JDK6 bug ? Did you get Sun interest to fix it ?
I signalized the problem in the bugs resolution application of the sun and actually there
is no response actually. Some day ago I've seen some interest to this in the sun
forums (http://forums.sun.com/thread.jspa?threadID=5416155&tstart=0). I think in
theese days I will know something more. Actually to resolve this problem you should delete
the 'default' operator by the enums. An example of 'default' operator is
inside the org.exoplatform.webui.event.Event.Phase class
- Can this be used to precompile the groovy templates and reduce the first time access
when unzipping and running GateIn ?
It compiles the groovy scripts through the exo groovy compiler, so I suppose it builds
new class files. I have verify if the achievement is the same as for the runtime compiling
(verify where the class files are created )
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-66
Project: GateIn Portal
Issue Type: Task
Components: Common integration
Affects Versions: 3.0.0-Beta01, 3.0.0-Beta02
Environment: jdk 1.6.0_17, jboss 5.1, mvn 2.2.1
Reporter: Luca Stancapiano
Priority: Minor
Fix For: 3.0.0-Beta04
Attachments: GroovyAnnotationProcessor.java, patch_28_nov_2009.zip,
patch_28_nov_2009.zip, patch_6_dec_2009.zip, patch_7_dec_2009.zip, prova.zip
maybe useful a mechanism that validates the groovy templates passed in the
org.exoplatform.webui.config.annotation.ComponentConfig annotation declared in the
exo.portal.webui.core project.
This annotation is actually used in the exo.portal.component.dashboard project.
Using the Pluggable Annotation Processing API for java 6 (here some detail of the
technology:
http://www.javabeat.net/articles/14-java-60-features-part-2-pluggable-ann...)
we can validate the groovy templates so we are not forced to load them at runtime and we
avoid a boring testing navigations.
The idea is introduce the Pluggable Annotation Processing in the pom.xml so we validate
the templates through the 'mvn install' command
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira