[
https://jira.jboss.org/jira/browse/JBWEB-108?page=com.atlassian.jira.plug...
]
Remy Maucherat resolved JBWEB-108.
----------------------------------
Fix Version/s: JBossWeb-2.1.1.GA
Resolution: Done
I have added an optional JCI (1.0) compiler (use with compiler init-param with
jci:compilername).
It is not functional for Jasper, though, because:
- JCI has (many) undocumented dependencies, and more importantly the dependencies are out
of date and not backwards compatible
- error reporting is bad (returns null with no logging if a compiler cannot be created for
some reason ...)
- settings API is not done at all
- could not get it to work with javac, although paths and source file appear correct
- could not get it to create a JDT compiler (it could need an older version)
I will keep the class as experimental (and accept patches for it), since if JCI 1.1 is
usable support for it would be nice to have.
Please update JDT Compiler or provide a JCI compiler
----------------------------------------------------
Key: JBWEB-108
URL:
https://jira.jboss.org/jira/browse/JBWEB-108
Project: JBoss Web
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Mark Proctor
Assignee: Remy Maucherat
Fix For: JBossWeb-2.1.1.GA
Tomcat uses a very old version of the JDT Compiler, not supported by the commons JCI
compiler adapter. This means that Drools has to use the Janino compiler, which is not
JDK1.5 compliant. If you where to use JCI itself you would benefit from a pluggable
compiler interface. I'd also recommend not polluting the user classpath space with
tomcat dependencies.
--
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